Practical guide: Summarise
From source to a checked result: Summarise. A useful result starts with a clearly defined task. This worked example separates the source material, the proposed output and the checks needed before publication.
A useful result starts with a clearly defined task. This worked example separates the source material, the proposed output and the checks needed before publication.
Source material
Our bakery in Kraków has been baking sourdough bread since 1998. Every morning from 6 am we sell bread, rolls and cakes. On Sundays we are closed. Birthday cakes need two days’ notice.Example result
Summary: A Kraków bakery that has made sourdough bread since 1998 sells bread, rolls and cakes every morning except Sunday.
Key points:
• Open from 6 am, closed on Sundays
• Birthday cakes: order two days aheadWhat matters in this example
A summary succeeds when the essential promise and the details needed to act remain visible. In the bakery example, opening time, location and the type of bread matter more than a long company introduction. The check compares each retained fact with the original; shortening must not turn a limited offer into a general promise.
A repeatable workflow
- 1Define the purpose and collect the relevant source material.
- 2Compare the result with the source; check names, numbers, dates and meaning.
- 3Resolve uncertain details, then copy or export the approved version.
Before publication
A fluent result is not evidence of accuracy. Missing facts should remain open rather than being filled with assumptions. A final review in the actual page or document checks context and presentation.