The owner decision log: the simplest project control there is
Short answer
An owner decision log is a running record of choices requiring owner direction, including the deadline, responsible party, final decision, and project consequences. Used alongside disciplined meeting minutes, it helps prevent unresolved or conflicting direction from disrupting design, pricing, procurement, permitting, or construction.
Projects rarely fail from one bad decision. They erode through dozens of small ones nobody wrote down.
What a decision log contains
One row per decision: the date, the question, who decided, what was decided, and the cost or schedule impact if known. Nothing else. It fits on one page and takes ten minutes a week.
Why it works
- It converts hallway conversations into a record
- It exposes decisions waiting on you before they become delay claims
- It makes change order entitlement arguments short
- It gives new team members the project's history in one read
Meeting discipline
- A published agenda before every progress meeting
- Minutes issued within 48 hours, with an objection window
- Action items with owners and dates, carried forward until closed
- Silence treated as acceptance only if the contract says so — and it should say so
The owner's half of the bargain
Contractors are entitled to timely decisions. If you hold selections, approvals, or answers, you are creating delay and, under most contracts, paying for it. The decision log makes your own responsiveness visible, which is uncomfortable and useful.
Start it today
Even mid-project, a log begun now is better than none. The first entries will be the ones you argue about later.
When a decision should be escalated
Escalate an item when delay could affect a permit submission, inspection, material release, trade sequencing, financing condition, resident communication, or planned occupancy. Also elevate decisions that exceed delegated authority, alter the approved scope, draw from contingency, create a recurring operating cost, or shift risk between project parties.
For each escalated item, ask: What is the last responsible decision date? What work depends on it? Is the cost confirmed, estimated, or unknown? Does the decision require board, lender, insurer, architect, or contract approval? Is there a reversible interim step? These questions help the owner act with enough information while avoiding an unnecessary stop in the work.
Use the log before, during, and after each meeting
Before the meeting, circulate the open decisions in priority order, with near-term schedule items first. Each item should include the information the decision-maker needs: available options, recommendation, budget effect, schedule effect, and decision deadline. If that information is incomplete, assign responsibility for completing it rather than using meeting time to rediscover the gap.
During the meeting, state the decision and confirm who accepted it. Afterward, update the log promptly, distribute it with the meeting record, and carry unresolved items forward with revised actions and dates. Close an item only when the direction is documented and the required follow-up—such as pricing, a drawing revision, procurement, or contract authorization—has been assigned.
Separate owner choices from contract decisions
Not every open question belongs with the owner. The architect may control design interpretations, the contractor may control means and methods, and the owner may retain decisions about scope, budget, finishes, operations, or risk. Set these boundaries early and identify who can approve on behalf of an ownership group or association.
Also distinguish the decision log from formal notices, change orders, architect’s supplemental instructions, submittal approvals, and requests for information. The log can point to those records, but it should not replace procedures required by the contracts. A direction discussed in a meeting may still need written authorization in the form the agreement requires.
What every owner decision log should capture
Each entry should state the decision required, who has authority to make it, the date it is needed, and what happens if that date passes. Include the related drawing, specification, contract item, allowance, or meeting topic so the team can trace the decision back to its source. Record the final direction in plain language rather than relying on a chain of emails.
Add the cost and schedule effect when known, but do not hold the entry open while waiting for perfect information. Note whether pricing is preliminary or confirmed, identify any assumptions, and assign the next action to one person. A useful log shows both the decision and what must happen because of it.
Why owner decisions become project risks
Projects often slow down because a choice is discussed repeatedly without a clear decision, deadline, or responsible party. The uncertainty then reaches drawings, pricing, procurement, or field work.
A decision log makes that risk visible. It gives the owner a short list of choices requiring direction and gives the project team a record of what was authorized.
Build a log people will maintain
A spreadsheet or table is usually enough. Use one row per decision and include a unique number, date raised, description, decision owner, required date, status, final direction, and links to supporting material.
Assign one person to maintain the log and issue it consistently. Team members may contribute information, but a single custodian reduces duplicate entries and conflicting versions.
Set deadlines from project consequences
A decision date should reflect when the team needs direction, not when the topic first appears. Work backward from permit submissions, pricing milestones, material releases, and field activities. The log should show the consequence of missing the date so the owner can set priorities.
Not every issue needs immediate action. Separate decisions that control active work from choices that can wait without affecting cost or schedule. This keeps the owner focused on matters with a real project consequence.
Close decisions without losing the record
Once the owner gives direction, record the decision in plain language and mark the item closed. Do not delete it. A closed record helps explain why drawings changed, why an allowance was accepted, or why one option was rejected.
If later information requires reconsideration, open a new entry and reference the earlier decision. This preserves the sequence of events instead of rewriting the history to fit the latest direction.
What belongs in an owner decision log
A useful decision log records the issue, the options considered, the owner’s decision, the person responsible for the next step, and the date the decision is needed. It should also note any known effect on scope, cost, schedule, permitting, or operations.
Keep the log separate from general meeting notes. Minutes document the discussion; the decision log identifies what must be decided and preserves the final direction. Link supporting drawings, estimates, or correspondence rather than copying them into the log.
How to use the log in project meetings
Review open decisions before routine status updates. Start with items that could delay design, pricing, permitting, procurement, or field work, then confirm who will prepare the information the owner needs.
At the end of each meeting, read back new decisions and unresolved items. Issue the updated log with the meeting record so the owner, design team, and contractor are working from the same direction.
Common questions
- Who should maintain the owner decision log?
- Assign one person to maintain and distribute the official version. That may be the owner’s representative, project manager, or another designated team member, but the responsibility should be explicit.
- Should email approvals be added to the log?
- Yes. Record the decision in the log and link or reference the email that documents the approval. The log becomes the index, while the original correspondence preserves the supporting record.
- What happens when the owner changes a prior decision?
- Keep the original entry closed and create a new entry that references it. Record the revised direction and identify any resulting review of scope, cost, schedule, or completed work.