How should a comparison page handle unknown product features?
Keep an unknown product feature unresolved until a suitable source establishes its scope. Procore's page comparison read on 8 October 2026 recorded 20 criteria stated, 44 not stated and 28 unknown, out of 92. Neither the unstated nor the unknown label gives you permission to publish that the product lacks the feature.
What we measured
Measured. The Study 7 method first extracted criteria stated before the first vendor name, then compared them with dated vendor pages. For construction answers captured on 22 September 2026, its Procore page read on 8 October produced three source states across 92 criteria: 20 stated, 44 not stated and 28 unknown. That is a page-comparison classification, not a feature test. The extracted criteria are not independently verified requirements, and team review remains in progress. No one cause can be assigned to all 28 unknowns from these totals.
What this means for you
Reasoned. Give the comparison three distinct source states. Stated means the dated page supports the scoped claim. Not stated means the reviewed page does not say it. Unknown means the available evidence cannot resolve the comparison as defined. These labels describe what you can support from the source, not an exhaustive test of the software.
Before filling a comparison cell, check product, module, plan, region and date. A capability described for a connected tool does not automatically belong to the native product. A broad suite description may not settle the narrower use case a buyer asked about. If those boundaries do not match, retain the uncertainty and link the source that shows why.
Use precise wording on the public page. Write that the reviewed source did not state the feature, rather than marking a universal No. If you later receive a suitable primary source, update the claim and its review date together. Keep the previous evidence in your records so that the correction has a traceable basis.
For the 92-criterion example, 20 plus 44 plus 28 reconciles the full page-comparison set. It does not imply that 72 features are missing or that 28 cases have one shared explanation. A comparison becomes more useful when its unanswered questions remain visible.
- For a publisher: link the supporting passage and keep page silence distinct from product absence.
- For a vendor: provide a source with the matching module, plan and use case when requesting a correction.
- For a buyer: treat an unknown cell as a question to resolve before selection.
Also asked as
How should a comparison page handle unknown product features?
Related
Next step
Use the Free 10-question check (one engine). No email is needed; runs are limited per network and per day, and by the site's daily allowance. Use a specific disputed comparison cell as the starting point.
To correct one comparison cell with scoped evidence, Fix one answer, $490.
Our answer-study method, v1.1.
Claiming or correcting a vendor record is free and never depends on a purchase.
Prepared by the Broadcastwell team.
Page owner: Rohan Iyer, AI Engineer. Corrections: hello@broadcastwell.com