TAP TAP GO
Preserve the distinction
Store the source document separately from the presentation built around it. Label extracts with the document name, relevant section and date. If a table has been simplified, say what was omitted and why. Avoid copying a screenshot into a deck in a way that removes the surrounding assumptions. A clean visual should not make an uncertain or conditional statement look final.
Provide an inspection route
Decide who can see the original and how to request access. For public content, a useful summary may be enough; for a formal review, the underlying record may be necessary. Keep a translation or interpretation labelled as such. When a source changes, update the summary and note the revision. Readers should not have to resolve a disagreement between two apparently authoritative versions themselves. Ask an independent colleague to compare the important numbers before distribution.
Put the guide to work
Where a summary combines several sources, identify which source supports each part. A single citation at the end can conceal differences in scope or date. Ask whether a reader could retrace the summary without needing the author to explain which document they had in mind.
Hypothetical example
A project brochure summarises a technical assessment in one sentence. During preparation, the team notices that the conclusion depends on an inspection date. It adds that date to the summary and offers the complete assessment through the approved review process.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
