An evidence register connects each material statement on a product page to the person and record that support it. Start with the exact wording a visitor sees, then capture the product version, audience, conditions, and review date. An editor can use that record to check a draft, answer a sales question, and find claims that need attention after a product change.
Give each claim a separate record
Copy the published sentence into the register and add the page URL and section name. If the sentence contains two promises, give each one its own claim ID. A sentence about availability and processing speed, for example, needs evidence for both the plans that include the feature and the conditions behind the speed statement. Linking both to a single general product brief can hide an unanswered question.
Use a practical set of fields for each record:
- Claim ID and wording. Keep the precise sentence or fragment and a stable identifier that remains recognizable when the page moves.
- Page and placement. Record the URL, section, and any other page that reuses the wording.
- Evidence reference. Name the document, product specification, measurement, or decision record and the relevant passage. Store sensitive material in its approved location.
- Scope and conditions. Note the product edition, plan, geography, integration, role, and version whenever those details affect the statement.
- Owner and dates. Identify who can confirm the claim, when it was last checked, and when the editor should ask again.
- Status and next action. Mark the item as confirmed, awaiting clarification, or due for review. Add an owner for any open question.
Choose labels that fit the team’s workflow and define them in the register. A confirmed item should point to an actual source and the scope the owner checked. If the answer is unknown, keep the question visible and avoid turning it into a published promise.
Work through a mixed feature claim
Imagine a fictional SaaS company called Fieldnote. Its draft says, “Every customer can export reports instantly across all projects.” The product editor assigns the sentence ID C-014, then asks the product owner to check availability, coverage, and timing separately.
The owner supplies a current internal feature specification. In this example, exports are available on the Team plan, include projects selected by an administrator, and run as background jobs. The team has no measurement that supports the word “instantly.” The original sentence therefore contains three separate points requiring different treatment.
The editor creates C-014A for plan availability, C-014B for project selection, and C-014C for processing speed. The first two records point to the relevant sections of the specification and name the product owner. The third stays open with a request for a measured definition and the conditions under which it would apply. The editor also records the draft’s URL and planned publication date so the reviewer can find the affected passage.
The revised page says, “Administrators on the Team plan can export reports for selected projects. Exports run in the background.” The editor removes the unsupported timing claim and asks the owner to confirm the replacement sentence. After approval, the register records the exact wording, document version, confirmation date, and location of the page. The case is illustrative and its plan and feature details are invented.
Review the wording alongside its evidence
Before publication, a reviewer should open the source and the page together. Check that the subject, scope, and degree of certainty still match. A source that says a feature is available to administrators does not by itself establish access for every user. A result measured on a test dataset needs its dataset and conditions if it is reused as a performance claim.
Ask the reviewer to trace sample records. If a source conflicts with the draft, return the item to its owner and record the decision.
A register can also reveal reuse. When a plan condition changes, search for the claim ID and review the linked product page, sales sheet, and help article. Assign a person to each affected location and record when the update is complete. A source reference is useful only while the referenced version can still be found.
Keep the register useful after launch
Schedule a review based on what the team knows about each claim. A feature tied to an active rollout may need an early check. A stable description can have a later review date, provided an owner will flag material changes in between. Add change triggers such as a plan revision, integration replacement, release, or new measurement.
At each review, record the source examined and the outcome. “Checked, wording still supported” is a useful result when it includes a date and an owner. If the owner cannot confirm the claim, mark the record for clarification and decide whether the page needs narrower wording while the question is resolved.
Frequently asked questions
Does every sentence need its own row? Focus on statements a reader might rely on when evaluating or using the product. Split a sentence when its parts have different evidence, conditions, or owners. Navigation labels and ordinary transitions can be handled through the team’s normal editorial review.
What if the only source is a product owner’s message? Record the exact message, its date, the owner, and the scope confirmed. Ask for a durable specification when one exists. If the message leaves a condition unclear, keep that question open before publishing a broader claim.
How should we handle an old source? Ask the owner whether it still describes the current product and save the confirmation or a newer source. Record the date of the check. If the owner cannot confirm it, update the page to the narrower supported wording or hold the claim for review.
Should the register contain confidential documents? Store a reference and access location when the underlying evidence is confidential. Give reviewers the access they need through the team’s established process, and keep the public page free of private source material.