The editorial decision

List the statements in an article that a reader might rely on when making a decision. Separate facts, company claims, assumptions, opinions and future plans. For each factual claim, record the supporting material and the date it was checked. For an assumption, explain where it came from and why it is being used. A ledger helps the editor see the difference between a compelling sentence and a sentence the publication can actually substantiate.

A working method

Give each claim an owner and a review trigger. Product availability may need review after a release; a projection may need review when its inputs change. If evidence is incomplete, narrow the wording or mark the uncertainty instead of filling the gap with confidence. Keep private supporting documents in an appropriate restricted location, while providing readers with public evidence where available. Use the ledger during revisions so a design or copy change does not accidentally remove an important qualification.

Imagine this

Hypothetical example

A growth article contains a retail-sales target, a current product feature and a planned service. The editor records the calculation, product confirmation and roadmap source separately. The published wording makes their different statuses clear, preventing a future plan from appearing as a live capability.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Further reading: Google people-first content guidance ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.