What is a Decision Log?
A decision log is a running record of important decisions made during a project or initiative. It includes details like what was decided, why it was decided, who was involved, and when the decision was made.
In higher education, where projects often span multiple months and involve many collaborators across a range of units, a decision log helps maintain clarity over time, especially when leadership or team members change midstream.
Unlike a change log, which focuses on updates to plans or deliverables, a decision log captures key moments of choice and strategy that shape the direction of a project.
What are the benefits of using a Decision Log?
Documenting decisions may feel like a formality, but it has a big impact on how smoothly a project runs. Some key benefits of keeping a decision log include:
- Clear Institutional Memory: Decision logs help you avoid “why did we do that again?” moments by recording the rationale behind project choices.
- Improved Communication: When decisions are shared clearly, everyone can stay aligned and informed, even if they were not in the room when the decision was made.
- Fewer Redundant Conversations: You can avoid rehashing settled issues if there’s a reliable place to point back to.
- Transparency and Trust: A decision log shows the thinking behind choices and the stakeholders involved, which is critical in cross-functional or high-visibility projects.
- Accountability: Knowing that decisions will be recorded encourages thoughtful, inclusive deliberation.
Where might you see a Decision Log in higher education?
A decision log is helpful for any initiative where multiple choices shape the project’s direction. For example:
- Academic policy updates, where you might be tracking key decisions made by governance committees, deans, or working groups.
- Software implementation, where you are documenting why certain vendors, platforms, or features were selected (or not).
- Strategic initiatives, including logging decisions related to budget priorities, program expansion, or community partnerships.
- Event planning, such as capturing agreements about formats, locations, speaker selection, and contingency plans.
When questions resurface later, the log becomes a reliable source of truth.
A step-by-step guide to creating and using a Decision Log
- Start with a simple table or spreadsheet that’s easy to update and share. Include fields such as date, decision summary, rationale, stakeholders involved, and related documentation.
- Identify what to track. You don’t need to log every small choice, but rather focus on decisions that significantly shape project direction, resourcing, or timing.
- Designate someone (e.g., project lead or notetaker) to update the log consistently.
- Save the log in a shared space (e.g., Teams, Google Drive, project management tool) where all stakeholders can access it.
- Use the decision log during project check-ins and after-action reviews to ensure continued alignment and institutional learning.
- At project close, archive the decision log with other final documentation, so that future teams can benefit.
Reflective questions
- What kinds of decisions in your projects often get lost or forgotten over time?
- How might a decision log support clearer communication in your current or upcoming initiatives?
- What format would be easiest for your team to maintain a decision log consistently?
- How can you use decision logs to build greater transparency across departments or roles?
- What’s one decision from a current project you could log today?