How to Prepare a Safety Decision Memo for a Capital Project in 8 Review Moves

F2 how-to guide for project sponsors, engineering leaders, and EHS decision owners

A capital project can receive technical approval while its most serious safety assumptions remain invisible to the people funding the work. The problem is rarely a missing spreadsheet. It is that hazard scenarios, design choices, temporary exposures, and control ownership sit in different documents, so the final decision appears cleaner than the work will be.

A safety decision memo closes that gap. It gives the sponsor a short record of what can go wrong, which controls are being purchased or accepted, who owns each control, what evidence supports the recommendation, and which conditions require a stop or redesign. OSHA's safety and health program guidance explains why management leadership and worker participation must connect with hazard identification and prevention rather than remain separate program statements.

The method below is designed for a project gate, not for a ceremonial report. It also complements the control ownership decision rights already used by safety leaders who need critical risk to remain visible after approval.

What you need before starting

Collect the project scope, process description, layout or design package, change register, risk assessments, procurement assumptions, commissioning plan, contractor interface plan, and the names of the people who can approve, reject, or modify the work. Include the latest worker or operator input when the project changes access, workload, sequence, alarm response, maintenance, or emergency action.

The memo should be short enough for an executive meeting and detailed enough for a technical challenge. Set a decision boundary before writing. For example, the question may be whether to release design funds, approve equipment purchase, authorize construction, begin commissioning, or accept a temporary control while a permanent solution is delivered.

Step 1: State the decision in one sentence

Write the decision as an action with a clear boundary. “Approve the new solvent transfer skid for construction, subject to the listed conditions” is more useful than “Review project safety.” A sponsor should know exactly what becomes possible after the decision and what remains outside its scope.

Include the decision date, project phase, affected area, and decision owner. If the memo covers several approvals, split them into separate decisions because one broad signature can hide a disagreement about design, schedule, or residual risk.

Verify the sentence with the project manager and the person accountable for the hazard controls. If either person describes a different decision, the memo is not ready.

Step 2: Describe the exposure before the control

Describe the credible exposure in operational terms. Name the energy, material, movement, pressure, temperature, access condition, human interaction, or failure sequence that could harm someone. Avoid beginning with a control such as “install a guard,” because that makes the proposed solution look like the hazard itself.

Use a specific work situation, such as maintenance during a changeover or contractor access during commissioning, rather than a broad phrase such as “process safety risk.” The decision latency tests for safety-critical work are useful here because they force the team to show when a concern becomes an owned decision instead of remaining an observation.

Verify the exposure description with an operator, maintainer, or field supervisor who understands the future task. A design review that no field user can recognize has not tested the work.

Step 3: Separate assumptions from evidence

Make a two-column record of what the project assumes and what supports each assumption. An assumption might be that an isolation point will remain accessible, that a detection system will be tested before occupancy, or that a contractor will follow the same emergency route as the operating team. Evidence might be a drawing, test specification, task simulation, manufacturer document, or verified field inspection.

Mark unknowns instead of filling them with confidence. ISO 45001 specifies the management-system requirements that organizations use to identify hazards, assess risks, and improve occupational health and safety performance. The memo translates that discipline into a project choice, while keeping the evidence visible enough for a later reviewer to challenge.

Verify the list by asking what would change the recommendation. If a missing fact cannot change the decision, it may be background information. If it could change the decision, give it an owner and a due date.

Step 4: Show the control choice and its limit

Describe the selected control, the failure path it interrupts, and the conditions under which it stops being reliable. A fixed separation may depend on layout discipline. An interlock may depend on proof testing. A procedure may depend on access, time, competence, and supervision. Naming the limit prevents the memo from presenting a control as permanent protection when it only works under ideal conditions.

Use the hierarchy of controls to challenge a solution that relies mainly on warning, training, or personal protection. NIOSH describes the hierarchy of controls as a way to choose measures that remove or reduce exposure before relying on administrative action or personal protective equipment.

Verify the control with the person who will maintain it after handover. A control that has no maintenance, test, inspection, or response owner is an intention, not a dependable barrier.

Step 5: Assign decision rights and control ownership

List who recommends the decision, who can approve it, who can reject it, who owns the control during construction, and who owns it after startup. These roles may belong to different people, but the boundaries must be explicit. A project sponsor can approve funding without owning the daily performance of a detector, guard, permit, or emergency arrangement.

Include the escalation route when evidence changes. The person who discovers a failed assumption should know whether to return to engineering, stop commissioning, notify the sponsor, or revise the risk assessment. This is where leadership becomes operational because authority is attached to a condition rather than to hierarchy alone.

Verify the assignment by asking each named owner what they are expected to decide next. If the answer is “someone from the project team,” the role is still vague.

Step 6: Put cost and schedule beside the safety choice

Show the cost, schedule effect, and operational consequence of the recommended control, along with the consequence of deferring it. This is not a request to reduce safety to a financial score. It is a way to stop the project from comparing the price of a control with no visible alternative.

When a permanent control is unavailable before startup, state the temporary arrangement, its expiry date, its owner, its verification method, and the trigger that requires work to stop. A temporary measure without an end condition tends to become the design by habit.

Verify the comparison with finance, engineering, operations, and EHS together. A memo that only shows the preferred option cannot reveal whether the decision is actually informed.

Step 7: Define the evidence required at the next gate

Turn every condition into an observable deliverable. Examples include a completed proof test, a signed isolation review, a simulated rescue route, a contractor competency check, a verified line-of-fire separation, or a worker review of the operating sequence. Avoid conditions such as “improve communication,” which cannot be checked consistently.

Set the evidence owner, due date, acceptance criterion, and reviewer. The safety-walk decision method provides a useful companion when the next gate depends on field evidence rather than document completion.

Verify the gate by testing whether another reviewer could decide pass, hold, or return without asking the original author to interpret the condition.

Step 8: Record the challenge and final decision

Capture the material questions raised during review, the evidence used to answer them, the unresolved points, and the final decision with its conditions. A clean approval that hides disagreement is weaker than a conditional approval that records what still requires attention.

Ask the sponsor to state what would cause the decision to be reopened. That trigger may be a design change, failed test, new interface, changed work sequence, incident, or evidence that the control does not perform under real conditions. The trigger turns the memo into a living governance record rather than a one-time approval artifact.

Verify the final version against the project change register and handover plan. If the approved memo no longer matches the design being built, the project has crossed its decision boundary without review.

Final checklist for the project gate

• The decision, phase, scope, and owner are explicit.
• The exposure is described before the proposed control.
• Assumptions are separated from evidence, with unknowns assigned.
• Each control has a stated limit, owner, test, and maintenance expectation.
• Approval, rejection, escalation, and post-handover ownership are distinct.
• Cost, schedule, temporary controls, and expiry conditions are visible.
• The next gate has observable evidence and a named reviewer.
• The final decision records challenges and reopening triggers.

Conclusion: make approval a safety control

A safety decision memo is useful when it changes the quality of the decision, not when it adds another approval document. The strongest memo makes the exposure concrete, tests the evidence, states what the control cannot do, assigns authority, and defines what must be proven before the project moves forward.

That approach reflects the Headline Podcast's central question about leadership and safety. Leaders do not make risk visible by asking for more reassurance. They make it visible by giving people a clear route to challenge assumptions and by refusing to approve conditions that no one can verify.