The status should identify the relevant field or test. A screenshot can document what appeared at a moment, but it does not independently prove every claim made about that page.
A status should describe completed work
Useful evidence labels distinguish source located, source inspected, observation recorded and claim checked. They can also identify a conflict or an outdated record. A source link does not imply that a screenshot exists, and a screenshot does not imply that a transaction was completed. The status should name the particular evidence requirement.
For example, a promotion can have an official terms URL and a completed wording check while its screenshot archive remains empty. Screenshot pending should then refer to that missing capture, not imply that no source was found. Separately, a payout-time claim may still lack an observed transaction even when advertised terms are available.
Avoid one badge for several claims
Offer amount, licensing and withdrawal performance can have different evidence. A general checked badge should not silently cover fields that were never examined. Link the status to a claim, source, date and method so readers can distinguish a published assertion from a measured result.
Changes and correction history
A source can change after inspection. Record what was observed and when, then recheck claims affected by new information. If evidence conflicts, preserve both records rather than hiding one to create artificial certainty. A concise public status can link to fuller detail without cluttering every paragraph. Its purpose is to communicate the scope of support accurately, not to replace the explanation.
In practice
An offer may have an official source URL while a separate withdrawal test has no transaction evidence. Those fields can legitimately have different evidence statuses.
What to check
Read the status alongside its source, scope and date. Do not treat a page-level badge as proof that every number has the same support.