A report is useful only when its question, source records, definitions, access boundary, and limitations are clear. Start with the decision a person needs to make.
Scope note: This is a vendor-neutral reporting checklist. It does not claim that any product offers report builders, templates, queries, dashboards, charts, exports, scheduling, permissions, AI suggestions, or calculated measures.
Frame one decision
Write a single decision question. For example: “What information must be verified before we change this operating process?” Avoid questions that implicitly assume causation, performance, profit, conversion, or return on investment.
Record the decision owner, relevant period, source records, and the condition that would make the result too uncertain to use.
Define every field and state
For each field, document its source, meaning, owner, update process, and known limitations. Keep distinct:
- a request;
- a scheduled item;
- performed work;
- an issued record;
- a payment indication;
- collected cash;
- an adjustment or correction.
Do not combine them to produce a conclusion the records do not support.
Set the access and sharing boundary
Use only data that is necessary for the question. Confirm who may view, edit, export, or share it. Remove or avoid names, contact details, addresses, locations, payment information, account IDs, internal links, screenshots, logs, credentials, and unverified business figures from public examples.
An external report needs a defined recipient, authorized purpose, retention expectation, and removal of fields that are not necessary.
Check the result against source evidence
A chart, query, template, calculation, or AI-generated narrative is not proof by itself. Test for:
| Check | Expected control |
|---|---|
| Complete record | Defined observation and source |
| Missing or late record | Limitation is visible |
| Duplicate or conflict | Reconciliation before conclusion |
| Sensitive data request | Authorization checked |
| Automated summary | Verified against underlying records |
Preserve a correction path
Keep an owner, review date, and method to correct a definition or source record. If the input is incomplete, stale, or unclear, label the output unresolved rather than presenting it as a fact.
Discussion
What question would your team answer more safely if the source, definition, and limitation were visible beside it?