Work as Done Explained: 4 Comparison Points That Reveal Risk-Control Gaps

A procedure can be complete, approved, and still fail to describe the work that actually exposes people to risk. The useful comparison is not between a perfect plan and an imperfect worker. It is between the conditions the control assumes and the conditions the task creates.

Work as done is the task as it is performed under real conditions, including changes, interruptions, trade-offs, and recovery actions. Comparing it with work as planned reveals where a control depends on assumptions that no longer hold, which makes the comparison a risk-management activity rather than a blame exercise.

Key Takeaways

• Work as planned describes intended sequence and controls, while work as done shows how exposure is actually managed.
• The most useful comparison examines conditions, sequence, information, and recovery rather than searching for individual fault.
• A gap matters when it changes the barrier, the decision authority, or the time available to respond.
• Supervisors can learn from normal variation without treating every adaptation as non-compliance.
• Andreza Araujo's safety-culture work supports a practical test, because visible compliance is not proof that the operating control is sound.

What work as done means in risk management

Work as done is not an excuse for ignoring a procedure. It is the evidence needed to test whether the procedure fits the operating environment. A crew may follow the written sequence while also using a temporary access route, waiting for another team, compensating for a missing tool, or changing the order after a condition shifts.

James Reason's analysis of latent conditions is useful here because the final deviation may be shaped by earlier design, planning, maintenance, staffing, or supervision decisions. The question is not only why a person adapted. It is also which condition made that adaptation necessary and whether the system recognized it.

In The Illusion of Compliance, Andreza Araujo examines the difference between visible process completion and reliable control. A signed plan is evidence that a plan exists, not evidence that the plan still matches the work.

Comparison 1: Conditions

Work as planned starts with assumed conditions. The drawing is current, the equipment is available, the isolation is complete, the area is accessible, and the people assigned to the job have the required competence. Work as done shows which of those conditions were present when exposure began.

Review the difference with observable evidence. Check the actual equipment state, access, energy sources, weather, staffing, materials, and simultaneous activities. A condition gap deserves escalation when it changes the control boundary or removes a safeguard that the plan treated as available.

Comparison 2: Sequence

Plans often describe a clean sequence, although real work can include pauses, handovers, rework, and temporary repositioning. Sequence changes become important when they place people in an exposure before the control that was meant to precede it is established.

Ask which step moved, disappeared, or became conditional. If the change improved access without altering exposure, it may be benign. If it moved verification after the task began, the sequence has changed the barrier and requires a decision, not a retrospective signature.

Comparison 3: Information

Work as planned assumes that the crew receives the right information at the right time. Work as done reveals what the team actually knew, what was unclear, and which questions had no fast route to an answer.

Information gaps often hide inside familiar language. “The area was checked” says little unless the review identifies what was checked, by whom, and against which current source. A useful debrief names the missing fact that would have changed the work, then assigns an owner who can improve the information before the next exposure.

Comparison 4: Recovery

Plans usually emphasize prevention, while work as done also includes recovery when prevention is incomplete. People notice a tool failure, a blocked route, a communication breakdown, or an unexpected energy state and decide whether to pause, escalate, or continue.

Recovery is a control signal. If the only available response is personal improvisation, the system has placed too much responsibility at the point of exposure. Across more than 25 years of EHS leadership, Andreza Araujo has kept the focus on whether organizations convert operational learning into stronger decisions rather than merely recording that an adaptation occurred.

How to differentiate a useful gap from a paperwork violation

Treating every variation as misconduct drives the real work underground. Treating every variation as harmless allows a changed barrier to pass as normal. The comparison should identify the condition that made adaptation necessary and the control decision that must change.

When to use the comparison

Use the review after a serious near miss, before a non-routine task, following a significant change, or when repeated observations show that crews routinely compensate for the same design weakness. It is especially valuable when the paperwork looks stable but frontline decisions keep changing.

The review should end with one operational decision. Change the plan, change the control, change the resource, clarify the authority, or stop the work until the gap is resolved. That is how a descriptive comparison becomes risk management.

Why the comparison strengthens safety culture

Andreza Araujo's Safety Culture: From Theory to Practice treats culture as something visible in decisions, not just in stated values. Comparing planned and performed work makes those decisions visible without pretending that a completed form proves reliability.

The strongest organizations do not ask only whether employees followed instructions. They ask whether the instructions matched the conditions, whether leaders supplied usable controls, and whether people had a credible route to pause and escalate.

What leaders should decide after the review

A review has little value when it produces a narrative but no owner. The responsible leader should name the gap, state the exposure it created, assign the person with authority to change the condition, and set a date for checking whether the revised control works in practice.

Across more than 250 cultural-transformation projects, Andreza Araujo's editorial position has been consistent: safety improves when leadership decisions reach the work, not when organizations add another layer of formal reassurance. If the planned control and the performed task differ, first determine whether the plan, resource, sequence, information, or decision right made the adaptation necessary.