A project decision log records what was decided, who approved it, and what information the team used. It is particularly useful when a small choice affects several drawings, suppliers, or budget lines.

Capture decisions at the right scale

Each entry should describe one actionable question. Include a reference number, responsible decision-maker, needed-by date, options considered, final direction, and links to supporting documents. Record the effect on cost or schedule when known, and identify when that effect still needs assessment.

For example, “select exterior doors” may be too broad. A useful entry could ask whether the loading entrance needs the revised opening arrangement, identify the drawing affected, and record the person authorized to approve the change.

Separate discussion from approval

Meeting notes often contain preferences, suggestions, and instructions together. The decision log should make the distinction visible. A supplier's recommendation is not an owner approval, and an owner preference may still require technical review before it can become an instruction.

Avoid relying on a chat message without context. Link the final decision to the relevant issue and confirm how it will be incorporated into the project's formal documents.

Review open items before they block work

At regular meetings, focus on overdue decisions and those needed before upcoming orders or installations. If the team cannot decide, record what evidence is missing and who will obtain it.

Keep closed entries available. Months later, they can explain why a material or layout differs from an early concept. The purpose is not to create a bureaucratic archive; it is to prevent the team from repeatedly reopening settled questions or executing different interpretations of the same conversation.