Give each unresolved claim its own record
Create a separate record for each proposition that could change a decision. Use a stable identifier and write a sentence specific enough to challenge. For example, a claim about an intermittent page failure is narrower than saying the website is broken. Record which URL, period and audience the claim concerns and who is responsible for reviewing it.
Keep the proposition separate from the action someone wants to take. A request to replace a template is not evidence that the template caused an incident. This register supports the investigation behind a report; it is not a collection of polished conclusions or a substitute for recording the underlying observations.
Name the kind of uncertainty
Distinguish unavailable evidence, incompatible observations and an unresolved explanation. Unavailable means a required measurement was not collected. Incompatible means the records appear to disagree and need their scopes checked. An unresolved explanation means the observations may be sound while several causes remain plausible. These distinctions suggest different next checks.
Do not assign a confidence percentage without a defensible method. Instead, write the exact limitation beside the claim: only one device was tested, the historical response was not retained, or the reports cover different periods. Google’s diagnostic guidance describes multiple possible causes of traffic changes; a familiar explanation is not automatically the right one.
Preserve disagreement without choosing a convenient winner
For every item, record the method, timestamp, scope and what it can establish. When two items differ, check whether they describe the same page version, time and conditions before calling either wrong. URL Inspection distinguishes stored information from live testing, illustrating why evidence from different moments should not be collapsed into one timeless verdict.
Add a proposed check that could change the conclusion, plus the result expected under each plausible explanation. Prefer a check that separates alternatives over another screenshot of the same ambiguous chart. If historical evidence cannot be recovered, say so. Repeated current tests cannot reconstruct every past state.
Use an illustrative conflict record
Imagine a fictional service page for which a visitor reports an error at 09:10, while an analyst records a successful response at 09:40. Claim U07 says the page may have failed intermittently. The success does not disprove the earlier report, and the report alone does not establish a sitewide outage. The two records cover different moments.
The next check is the relevant availability evidence around 09:10, with the affected route and time zone confirmed. If that evidence is unavailable, U07 remains unresolved with that limitation recorded. If a matching failure is found, update the supported scope of the finding. Do not silently expand one route’s failure into a claim about all visitors or all search traffic.
Version the conclusion when evidence changes
Retain the original claim and append a dated revision rather than overwriting the history. Mark it supported within a stated scope, contradicted by specified evidence, or still unresolved. Link the new finding and explain which part of the interpretation changed. A reviewer should be able to reconstruct why yesterday’s uncertainty differs from today’s conclusion.
Assign an owner and a practical next review trigger. Resolve verified factual defects even when the wider causal explanation remains uncertain, but keep those two decisions separate. Close an investigation only with an explicit disposition for its open claims. An unresolved claim can be archived as unresolved; it must not become a confirmed fact merely because the team stopped checking.