Execution / Monitoring · Log + form
Decision Log & Change Request Form
The anti-scope-creep pair, with a built-in escalation path.
The problem it solves
Scope grows quietly, and six weeks later nobody remembers who agreed to what, or why.
How to run it
- 1Log every decision the day it happens: date, decision, owner, rationale, rejected options.
- 2Route anything that changes scope, date or cost through the change request form.
- 3Require an impact statement — no impact, no approval.
- 4Review open requests at a fixed weekly slot.
- 5Link approved changes back to the baseline and tell the team.
What's inside
- Decision log with rationale and rejected-options columns
- Change request form with impact assessment
- Approval thresholds and escalation path
Related downloads
Get this template
Sent as an editable document. No account, no drip sequence.
Want this facilitated with your team rather than filled in alone? I run these as a 90-minute session — free, no obligation.
Related templates
Work with me
Sometimes the fix needs a person, not a template.
I am Tigran Zakarian, a senior project manager with 13 years of end-to-end delivery for clients such as H&M Group, TV4, SEB and Clear Channel. I work on exactly the situations described across this site: rescuing drifting deliveries, setting up governance that people actually use, and facilitating the workshops that unblock decisions.
Projects & programmes
- Interim / rescue project management
- Programme & multi-team delivery ownership
- PMO, governance and steering setup
- Product ownership & backlog clarity
Workshops
- Risk analysis workshops
- Planning and prioritisation sessions
- Decision and stakeholder alignment
- Retrospectives that change something
Talks & training
- Educational talks and keynotes
- Hybrid PMBOK + Agile training
- Kanban / flow ways of working
- Team coaching for new PMs