Product pages do not always give every field the same level of support. A simple three-state note—confirmed, unclear or not stated—keeps visible wording separate from ambiguity and absence. It also stops a missing detail from becoming a guessed product fact.

1. Define the three states before comparing

Use confirmed only when the named field is visible on the checked product page and the model identity is consistent. Use unclear when fields conflict, the wording is ambiguous or the context needed to interpret it is missing. Use not stated when the checked page does not provide the field at the time of review. “Not stated” describes the page record; it does not prove the opposite about the product.

2. Verify one field at a time

Open a direct listing such as the T528 product page or T529 product page. Write the field name first—title, description, option label or image caption—then record only what that field supports. A value seen in one field should not silently validate a different field.

3. Check model identity before assigning “confirmed”

Compare the visible model marker across the title, page URL and description before saving a confirmed note. If those markers disagree, label the field unclear and preserve the conflict. The T527 listing can be recorded separately from the T528 and T529 pages even when the navigation or page layout looks similar.

4. Keep completeness separate from accuracy

The UK Government’s Data Quality Framework distinguishes completeness from accuracy: having every field populated does not make every value accurate. Apply the same discipline to listing notes. A filled field still needs a clear source and matching identity; a blank field stays not stated rather than being completed from memory.

5. Make uncertainty visible

For an unclear field, record the competing wording or the missing context and add the access date. Do not choose the version that seems more likely. For a not-stated field, record the page and field checked. These labels make later rechecks useful because a reviewer can see whether the source changed or the earlier note was simply incomplete.

6. Keep each model’s evidence record separate

Maintain separate rows for the T61 listing and T69 listing. Repeated wording, similar visuals or adjacent links do not transfer a fact from one model to another. Each row should retain its own URL, model marker, field name, evidence state and access time.

This method classifies what a checked page supports. It does not verify manufacturing details, predict future page content or turn an absent statement into a product claim.