Decision Log Template
A log for recording decisions and their reasons over time.
Download this template
Choose the file you need, then download it. No sign-up, no payment.
Choose a design
The same document in 9 designs, same content and editable fields, different styling. Pick the design you like and download that version. Click any design to preview it larger before downloading. The Sample card shows a completed example, filled in with sample details.
Classic Navy
Executive Charcoal
Modern Minimal
Compact
Burgundy
Forest
Teal Professional
Warm Copper
Mono
Sample
What’s Included in This Resource
Every resource on The Office File provides a complete toolkit rather than an empty, unhelpful document shell:
- Editable Microsoft Word (.docx) template (41 KB)
- Printable PDF version (94 KB)
Sample included: Example: Decision Log Template in use. Stopping decisions from being re-argued: what was decided, why, by whom, and when it takes effect, in one running log.
How to Use This Template
Follow these practical steps to customize and roll out this procedure with your team:
1. Set the purpose first
Write one sentence stating what decision or outcome the meeting must produce.
2. Assign an owner per item
Every agenda item and action needs one named owner, not a team.
3. Record decisions, not just discussion
Write down what was decided, by whom, and by when it must happen.
4. Circulate within one working day
Send the completed record to all attendees while the discussion is still fresh.
About This Template
Memory fades; written logs do not. This template gives you a structured format for recording events as they happen, with timestamps, descriptions, and responsible persons. Make logging a habit and you will wonder how you ever operated without it.
Stopping decisions from being re-argued: what was decided, why, by whom, and when it takes effect, in one running log.
When to Use This Template
- Maintaining legally defensible records for compliance purposes
- Handing over shift or project history without relying on memory
- Identifying recurring problems by reviewing logged patterns over time
- Supporting investigations with contemporaneous, factual notes
- Tracking maintenance, inspections, or checks with dated entries
Key Sections Explained
Understanding what goes in each part of the document helps you fill it in correctly the first time:
People involved
Who was present, who acted, and who was notified, names and roles, not just 'someone'.
Date and time
When each entry occurred, contemporaneous timestamps are what give a log its credibility.
Follow-up actions
What needs to happen next, who owns it, and by when, so the log drives action, not just archives history.
Event description
What happened, stated factually. Keep opinion out; record what was observed.
Log title and purpose
What events this log captures and why the record matters.
Frequently Asked Questions
What should never go in a log?
Opinions, speculation, and blame. Record what was observed factually, logs get read in disputes, and editorialising undermines their credibility.
What if we missed logging something?
Add it as soon as possible, clearly marked as a late entry with the actual date of the event and the date of recording. A marked late entry beats a gap or a backdated fiction.
Who can access the log?
Define this upfront, especially for sensitive logs like incidents or complaints. Controlled access protects both the subjects and the integrity of the record.
How detailed should entries be?
Enough that someone reading in six months understands what happened without needing to ask you. Names, times, and specific observations beat vague summaries.