Keep examples and measured results clearly separate

Readers should be able to tell whether a number is a fixture, an estimate or an observed result. Label evidence consistently before turning task output into public content.

Work through these checks

1. Origin

record where each number came from. Record the evidence or the unresolved question before moving on.

2. Status

label illustrative and estimated values. Record the evidence or the unresolved question before moving on.

3. Method

describe actual transformations. Record the evidence or the unresolved question before moving on.

4. Date

state the source period or snapshot. Record the evidence or the unresolved question before moving on.

5. Claim

ensure the conclusion matches the evidence. Record the evidence or the unresolved question before moving on.

Put the checklist to work

A five-row sample used to test a sales report must be described as a fixture, never as a customer’s actual revenue.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

A chart can make invented data look authoritative. Visual polish does not change its evidential status.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.