Work as Imagined vs Work as Done
A procedure can look complete on paper and still fail the moment it meets heat, noise, time pressure, missing tools, changing weather, equipment wear, and competing production demands.
That gap is the space between work-as-imagined and work-as-done. It is one of the most useful ideas in modern health, safety, and environment practice because it shifts attention from blame to learning. It asks a better question: What does the system ask people to do, and what does the real job actually require?
Procedures matter. Permits, method statements, safe work instructions, risk assessments, and job safety analyses all help set expectations. But written controls are often created away from the workface. They may describe how a task should happen under stable conditions, with the right equipment, the right staffing, and enough time. Real operations are rarely that tidy.
For HSE professionals, closing this gap is not about catching people out. It is about understanding normal work well enough to make procedures, controls, and decisions fit reality.
What Work-as-Imagined and Work-as-Done Mean
Work-as-imagined is the version of the job described in procedures, plans, risk assessments, training materials, and management expectations. It is the work as people believe it will happen when they are not standing in the operating environment.
Work-as-done is the work that actually happens in the field. It includes the adjustments, trade-offs, workarounds, pauses, checks, conversations, and judgments people use to get the task finished safely.
The two are linked, but they are not the same.
A lifting plan may assume clear access, good visibility, stable ground, and no last-minute interface with other crews. On the day, the team may find a parked vehicle in the exclusion zone, a radio with poor reception, a load that behaves differently than expected, and another work group nearby trying to finish a related job. The lift team must adapt.
That adaptation is not automatically unsafe. Often, it is what keeps work safe.
People in real operations constantly manage variation. They notice when equipment sounds different. They slow down when a valve is stiff. They wait when another crew is too close. They ask an experienced colleague to verify a step. These actions may not appear in the procedure, but they can be critical to safe performance.
The risk appears when the system does not know these adaptations are happening. If leaders believe the written method matches the field method, they may miss weak controls, poor design, unclear instructions, and pressure points that increase risk.
Work As Imagined: The task as described in documents, systems, and planning discussions.
Work As Done
The task as carried out in real conditions, including adjustments workers make.
The difference between expected work and actual work.
Better learning, stronger controls, and procedures that people can use.
Why The Gap Develops
The gap between procedures and reality usually doesn't appear because someone was careless. It grows through normal business activity, gradual change, and incomplete feedback.
Procedures are often written for ideal conditions
Many procedures describe a clean sequence of steps. They assume the task starts on time, the area is prepared, the equipment is available, and the hazards are known.
Fieldwork often involves changing conditions:
Weather affects access, visibility, and footing.
Equipment ages and behaves differently over time.
Work groups overlap in tight spaces.
Tools are shared, missing, modified, or delayed.
Operators face alarms, production targets, and handover gaps.
Contractors may bring different methods and experience levels.
A document cannot predict every combination of these conditions. If it tries, it may become so long that people stop using it. Good procedures need enough detail to guide work, but enough flexibility to support judgment.
Work changes faster than documents
Operations change through small decisions. A temporary hose becomes a long-term fixture. A crew changes its access route because a gate is often locked. A tool is replaced with another model. A task that used to take place during shutdown now happens during live operations with extra controls.
Each change may seem minor. Over time, the procedure falls behind.
This slow drift is common. It does not always show up in audits because audits often compare paperwork against paperwork. A stronger review compares paperwork against the way work is actually performed.
People create workarounds to get the job done
A workaround is not always a sign of poor discipline. It can be a sign that the system is difficult to use.
For example, a form may require workers to record a control that no longer exists. A procedure may tell workers to use an access point that is blocked during normal operation. A permit process may require approval from a person who is rarely available during night shift. Workers then find a way to proceed.
Some workarounds create risk. Others reduce risk. The point is to learn why they exist.
If HSE professionals treat every workaround as non-compliance, people will hide them. If they treat workarounds as system signals, they can find weak spots before an incident exposes them.
Non-Compliance Is Too Simple An Explanation
When actual work does not match the procedure, the quick explanation is often “workers did not follow the rules.” Sometimes that is true. People can take shortcuts, ignore controls, or make poor decisions. HSE systems still need clear expectations and accountability.
But stopping at non-compliance can hide deeper causes.
A worker may skip a step because the step is impossible in the current layout. A crew may sign a document they do not fully use because the document is too generic. A supervisor may accept a deviation because stopping the job has become culturally difficult. A technician may rely on memory because the procedure is locked in a system they cannot access at the worksite.
These are not excuses. They are facts that matter.
A mature HSE approach asks several questions before reaching for blame:
Was the procedure available at the point of work?
Did it reflect current plant, equipment, and staffing?
Was the language clear to the people using it?
Did the task require trade-offs that the procedure did not address?
Were time pressure, access limits, or production demands shaping decisions?
Did supervisors and managers know how the task was really being done?
Were previous concerns raised and left unresolved?
This helps separate reckless behavior from normal adaptation. That distinction matters. Treating every gap as a discipline issue can damage trust and reduce reporting. Treating every gap as harmless can normalize risk. The aim is to understand the difference.
When real work departs from written work, the most useful first response is curiosity, not accusation.
The phrase Work as Imagined vs Work as Done Closing the Gap Between Procedures and Reality describes a practical challenge for HSE teams: systems improve when the organization learns how work succeeds most of the time, not only how it fails during events.
How field engagement improves understanding
Field engagement is more than a site walk. It is a structured way to learn from people who perform, plan, supervise, and support the work.
The quality of engagement matters. If workers expect a compliance inspection, they will show the version of work they think leaders want to see. If they expect a genuine conversation, they are more likely to explain what helps, what gets in the way, and where the procedure does not match the job.
Good field engagement includes three habits.
Ask about normal work before asking about failure
Incident investigations often focus on what went wrong. Field engagement should also ask what usually goes right.
Useful questions include:
What part of this task is harder than it looks?
Which step in the procedure is least useful?
What conditions would make you stop?
What do experienced workers know that new workers may miss?
What tools or information do you need before starting?
Where do people usually adapt the method?
These questions reveal hidden controls. They also show where the system depends too much on individual skill.
Watch the task without interrupting the flow
Operational observations should not become a performance test. The goal is to see the job as it is normally done.
That means observing setup, access, communication, tool use, waiting time, handoffs, and closeout. Many important decisions happen before the first formal step in a procedure. Others happen after the task appears complete, such as reinstatement, housekeeping, or shift handover.
A short observation during the “main activity” may miss the real risk.
Reflect findings back to the workforce
Field engagement loses value when information flows up but never comes back down. Workers should see what changed because of their input.
That could be a revised procedure, a removed duplicate form, a better isolation point label, a new tool, a clearer hold point, or a decision to stop doing a task in a certain condition.
Feedback builds trust. It also proves that speaking up is worth the effort.
How Learning Teams Turn Gaps Into Improvements
Learning teams offer a practical method for exploring work-as-done. They bring together people who understand different parts of the task, including operators, maintainers, supervisors, planners, engineers, contractors, and HSE professionals.
The goal is not to find fault. The goal is to understand how the system shapes the work.
A learning team can focus on a task, a recurring issue, a near miss, a successful recovery, or a procedure that people struggle to follow. It works best when the group discusses real examples, not abstract opinions.
A simple learning team process can look like this:
Choose a task with meaningful risk or repeated variation
Pick work where the written method and actual method may differ.
Map the task as imagined
Review the procedure, permits, forms, tools, roles, and controls.
Map the task as done
Ask workers to describe the job from preparation to closeout. Include interruptions, waiting, checks, and informal decisions.
Identify gaps and pressures
Look for unclear steps, missing resources, conflicting goals, access problems, and points where people must improvise.
Agree on system improvements
Focus on changes to design, planning, tools, training, supervision, and procedures.
Test the change in the field
Confirm that the new control works where the job happens.
Learning teams are especially useful because they make trade-offs visible. A procedure may say “verify zero energy,” but the team may reveal that the test point is hard to access, the label is faded, and the correct meter is stored far from the job. The solution may involve better labeling, equipment redesign, tool availability, and a clearer verification step.
That is far stronger than reminding people to “follow the procedure.”
How Operational Observations Strengthen Procedures
Operational observations help HSE teams move from assumption to evidence. They show how work changes across shifts, crews, contractors, locations, and conditions.
A good observation is focused. Instead of trying to inspect everything, choose a task or control and study how it functions.
For example, when observing confined space entry, do not only check whether the permit is complete. Watch how the team controls access, communicates, tests the atmosphere, manages equipment at the entry point, and responds to interruptions. The paper permit matters, but the real control is the way people use it.
When reviewing observations, look for patterns:
Steps that workers regularly skip or repeat
Controls that exist on paper but not in practice
Tasks that rely heavily on one experienced person
Words in the procedure that workers interpret differently
Conditions that trigger informal stop-work decisions
Mismatches between training and actual equipment
Approval steps that delay work without reducing risk
These patterns point to system fixes. They may lead to shorter procedures, clearer diagrams, better pre-job briefings, improved tool control, stronger supervision, or redesigned equipment.
The best procedures become field tools, not archive documents. They help people make safe decisions under real conditions. They also tell workers when to stop and seek help.
Closing The Gap Without Adding Unnecessary Complexity
One common reaction to a procedure gap is to add more detail. Sometimes that helps. Often, it makes the document harder to use.
Better improvement starts with understanding the purpose of the procedure. Does it guide a high-risk, rarely performed task? Does it support a routine job with known variation? Does it define critical steps that must never be missed? Does it help new workers learn the task?
The answer should shape the document.
A useful procedure often has these features:
Clear scope and limits
Simple language
Steps in the order work is performed
Critical controls that stand outrocedure's purpose
Stop-work points
Photos or diagrams where they help
Space for local conditions or task-specific controls
Alignment with permits, training, and tools
A review cycle linked to field feedback
HSE professionals can also improve the system around the procedure. A good document will still fail if planning is weak, spares are missing, staffing is thin, or supervisors reward speed over safe execution.
Closing the gap takes shared ownership. Operations, maintenance, engineering, planning, procurement, supervision, and HSE all influence how work happens. The written procedure is only one part of that system.
The most useful mindset is simple: if people regularly adapt the work, learn why. If the adaptation makes the job safer, capture it. If it adds risk, change the conditions that make it necessary.
The Takeaway for HSE Professionals
The gap between work-as-imagined and work-as-done is not a defect to hide. It is a source of learning.
Procedures written away from the workface can miss the details that shape real decisions. Workers often bridge those gaps through skill, experience, and practical judgment. Some adaptations protect the operation. Others signal rising risk. HSE professionals add value when they can tell the difference.
Field engagement shows what normal work requires. Learning teams explain why gaps exist. Operational observations test whether controls work under real conditions. Together, these practices turn procedures into living tools that reflect the job, support the workforce, and reduce risk where it matters most: at the point of work.
