
A project can have excellent meeting notes and still lose track of its decisions. Three weeks later, someone asks why the team chose a particular deadline, and everyone remembers a different reason. A decision log gives that answer a stable home. It works for a shared project, a freelance assignment, or your own recurring work.
Start with one document or spreadsheet beside the project’s other working files. The goal is to preserve the reasoning behind meaningful choices, without transcribing every conversation. Use the six steps below to make the log small enough to maintain and specific enough to settle questions later.
1. Decide which choices deserve an entry
Record a decision when reversing it would affect another person’s work, a delivery date, the budget, or an agreed requirement. Choosing a launch date qualifies. Moving your private draft from one folder to another probably does not. This boundary keeps small administrative choices from burying the decisions people need.
Give each entry a short, searchable title: “Use the existing checkout for the pilot” is more useful than “Website discussion.” Add the date and project name. If several projects share one file, a project column lets people filter the entries without building separate systems.
2. Separate the choice from its reason
Use a compact set of fields: decision, reason, alternatives considered, owner, next action, and review trigger. The decision should be a complete statement of what will happen. The reason should explain the constraint or evidence that made this option preferable at the time.
Keep assumptions visible. “The supplier has confirmed delivery by Friday” and “We expect delivery by Friday” are different foundations for a plan. Link to the relevant message or document when the evidence is already written down; do not copy a long conversation into the log.
3. Write one entry while the context is fresh
Here is a fictional example: Decision: use the current checkout for the November pilot. Reason: the new checkout is not ready for accessibility review. Alternative: delay the pilot. Owner: project lead. Next action: confirm the existing payment flow before invitations go out. Review trigger: the new version passes the agreed checks.
Notice that the entry explains both the choice and its limits. It does not imply that the current checkout is the permanent answer. Write the first draft immediately after agreement, then let the responsible person correct anything that misrepresents the decision.
4. Connect the log to the work
Put the link where people already look: the project overview, the task description, or your meeting notes. A perfectly organized file hidden in someone’s private folder will not answer a colleague’s question. Check that the intended readers have access before relying on it.
Keep tasks in the task system. The log can name the next action and link to it, but copying every subtask creates a second place to maintain. In a project update, mention only decisions that changed the plan or need someone’s attention.
5. Revisit decisions when a condition changes
A review trigger can be a date, a test result, or a changed requirement. Pick one that would genuinely justify another look. “Review next month” is less helpful than “Review when the pilot’s support requests have been categorized.” Avoid reopening settled choices simply because the log exists.
When a decision changes, mark the old entry as superseded and link to the replacement. Preserve the earlier reasoning rather than silently editing it to match today’s view. That history is particularly useful when preparing a project handoff.
6. Test whether someone else can use it
Ask a colleague to find one recent decision and explain the next action from the entry alone. If they need your verbal explanation, add the missing context. If they have to read several paragraphs to find the choice, shorten the entry and move supporting detail to a linked document.
Begin with the next meaningful decision, not a reconstruction of the entire project. At your next routine project review, check for missing owners, broken links, and decisions whose review condition has arrived. A useful log stays close to the work that created it.
Cover: AI-generated editorial illustration.
Join the conversation
Share a useful tip or ask a question. Comments are reviewed before publication. Your email address will not be displayed.



Leave a Reply