Three weeks after a project meeting, the team cannot agree why a delivery option was rejected. The minutes record a discussion but no clear choice. A project decision log keeps the decision, authority, reasoning and consequences in one place so the team can act consistently afterwards.
Photo by Iuliia Pilipeichenko on Unsplash.
Use it for decisions that affect scope, commitments, approach or important dependencies. Routine task choices rarely need the same treatment.
Make the decision understandable on its own
A useful entry contains:
Decision needed and the date it was made.
Person or group with authority to decide.
Options considered and the chosen option.
Main reason, evidence and relevant constraints.
Conditions or assumptions attached to the choice.
Actions, owners and affected records.
Trigger for revisiting the decision, if applicable.
Link to meeting notes and supporting evidence where they live. Avoid copying the full conversation into the decision field. Someone joining later should be able to understand what they must follow without reconstructing the meeting.
Distinguish a proposal from a decision
“Everyone seemed happy” is not a reliable approval record. Mark unresolved recommendations as pending and identify the approver. If the decision exceeds the team's authority, escalate it rather than treating silence as acceptance.
Distribute the confirmed outcome to the people whose work changes. Recording a choice without updating the plan can leave the team following yesterday's instructions.
An illustrative entry
A hypothetical project chooses a phased release rather than one launch. The sponsor approves the option because operational support is available for a limited first group. The entry records the first group's boundaries, the review evidence needed before expansion and the owner of the revised communications.
Later, somebody proposes adding another group immediately. The team can check the original condition and seek a fresh decision instead of arguing from memory.
Keep a visible history
When a choice changes, add a superseding entry and explain the new evidence. Do not silently overwrite the earlier reasoning. This is especially useful when an assumption proves false or an authorised change alters the original constraints.
Related guidance: small-team project planning guide.
If decisions keep being reopened because their basis disappears between meetings, Hili Consulting can help establish a decision record that supports delivery without creating another administrative burden.
