Collection
Documents and team updates
Have work notes, meeting notes or a long document? Choose the matching guide below. A weekly report checks progress; meeting notes separate decisions from proposals; a document brief keeps its sources. Once the facts are checked, use the audience update to explain them to a different team. You do not need to do all four.
4 guides · 4 written
Draft a weekly report without overstating progress
Ready to useTurn one reporting period of work notes into four clear sections while pending approvals, blockers, conflicting updates and unknown details stay visible. Draft it yourself or use an assistant you are allowed to use, then verify every claim.
Turn meeting notes into decisions and owned actions
Ready to useTurn one meeting’s notes into decisions, actions and open questions. Replace names with roles where possible. Keep proposals separate from decisions and leave missing owners unassigned. The result is a draft for review, not approved minutes.
Build a document brief with traceable evidence and limits
Ready to useTurn a numbered excerpt into a short brief. Keep the supporting passages, limits and unanswered questions beside the main points.
Rewrite one update for business, engineering and management
Ready to useStart with checked facts and name your reader. Remove internal identifiers and confidential data. Adjust the emphasis without changing status, scope or promises, and keep risks visible to every audience.
