Who is this for, and what should they understand or decide?
Document review checklist
Check reader, facts, structure and next step before anything is sent.
Work through it in order.
Is the purpose stated early enough to be found?
Is every fact complete and approved by its owner?
Can the reader reach the important part without effort?
Is the required action explicit, with an owner and a deadline?
Did the edit turn a tentative statement into a confirmed one?
What it looks like in use.
Filled example: Reader — client's project manager. Purpose — approve scope change. Facts — two dates unconfirmed, marked for the owner. Structure — decision request moved to the top. Next step — approval needed by Thursday, 4 PM. Certainty — Friday delivery kept as tentative.
Illustrative example with fictional names and dates — not client material.
Keep going.
Action-focused email template
Organise context, request and deadline so the reader knows what to do.
OpenMeeting decision & action log
Record decisions, owners, due dates and unresolved issues after every meeting.
OpenWeekly project update template
Communicate progress, risk and required decisions without mixing them together.
OpenClient handover checklist
Clarify deliverables, access, ownership and pending work at handover.
Open