Decision support
A decision log that explains why the owner chose an option
Months after a project decision, the owner remembers the selected option but not the assumptions or concerns that shaped it.
A decision log preserves the reasoning available at the time, including what was uncertain.
The record does not need to reproduce every conversation. Focus on the question being decided, the options considered and the reasons that mattered. Include important constraints such as access, timing, scope or information that was unavailable. This helps a future reviewer understand the decision without assuming the owner had facts that emerged later.
Be precise about authority. A staff recommendation, provider proposal and owner approval are separate events. Record them in their proper roles. If a professional adviser supplied a conclusion, attribute it and keep its scope and limitations. Do not turn a summary into a broader assurance than the underlying advice supports.
Revisit the decision when its assumptions change or a review date arrives. The original choice may remain appropriate, or new evidence may justify a different course. Keeping the reasoning makes that discussion more productive. The purpose is accountable continuity, not defending every earlier decision regardless of what the building’s current evidence shows. A brief record created promptly is often easier to understand than a detailed reconstruction prepared months afterward.
Put it into practice
- Record the decision, date and authorized decision-maker.
- Link the options, supporting records and unresolved questions.
- Name the event or date that should trigger a review.
What to verify
Keep the approved decision separate from earlier proposals. Preserve original supporting documents and note later information as an update rather than rewriting history.
Write a short decision record for your next meaningful commitment.