How to Screen a Temporary Field Change in 8 Steps

Temporary field changes create risk when a team treats them as small because they are short-lived. A changed barricade, a new access route, a swapped isolation point, a bypass that was meant to last one hour, or a nearby crew that starts work late in the shift can all shift the control picture before anyone notices.

A temporary field change is any short-term change in the worksite that alters who is exposed, which barrier is active, or what the next crew can safely assume when work resumes.

Across 25+ years in executive EHS and more than 250 cultural transformation projects, Andreza Araujo has seen the same pattern repeat. The paper stays tidy while the field changes under it. In Safety Culture: From Theory to Practice, she argues that repeated decisions under pressure are the real culture signal, and a temporary change is one of the cleanest places to see that signal in action.

This guide is for supervisors, EHS managers, and risk owners who need a clear way to decide whether a temporary change can stay in place, whether it needs another control, or whether the job should stop until the field is reset. It also fits a site that wants the same discipline in every shift, because a short change is still a change in control.

What you need before starting

Before you screen the change, collect the current work plan, the last field walk, the active permit or control sheet, and the name of the person who can approve a hold. If the change touches isolation, access, lifting, hot work, or contractor overlap, bring the supervisor who owns the job and the person who will inherit it next.

The point is not to build a thick folder. The point is to make sure the screening conversation starts with the real field, not with memory. If you want the next step to work, the starting point must already include the place, the people, the barrier that changed, and the reset condition that ends the change.

Step 1: Define the change in one sentence

Write the change in plain language before you discuss controls. Say what moved, who moved it, and what part of the work it affects. A sentence such as "the access route moved to the east side for two hours" is useful because it points to the control that needs a fresh look.

When the change cannot be named clearly, the team usually does not understand it yet. That is not a paperwork problem. It is a control problem, because a vague change cannot be screened with discipline. James Reason's latent-condition view helps here, since the visible event is often only the last sign that the system has already drifted.

Step 2: Decide whether the change is truly temporary

Some changes are temporary in name only. If the change will survive into the next shift, the next crew, or the next permit cycle, it needs a stronger decision than a casual yes. Temporary is not a label. It is a time limit with a reset condition.

If the worksite cannot say when the change ends, treat it as a structural change until proved otherwise. A short detour, a portable barrier, or a temporary bypass can stay in place long enough to become normal. That is where the trap lives, because the team starts to trust the exception more than the original control.

Andreza Araujo's book The Illusion of Compliance is useful here because it warns against confusing a neat document with a controlled job. A tidy label does not tell you whether the field is still safe.

Step 3: Walk the field with the person who owns the job

Do not screen a field change from a desk only. Walk the area with the supervisor or owner who can act on the result, and compare the permit or plan with the place itself. The route, the barrier, the line of fire, the access path, and the neighboring activity should all be visible to both people at the same time.

This is where many teams discover that the control they thought was active is already missing or already moved. If the field walk and the paper disagree, the field wins. That rule may sound obvious, but it is the rule that keeps the next person from inheriting a false sense of safety.

If the change touches energy isolation, use LOTO verification: how to prove zero energy shutdown as the next check. If the change affects the permit itself, compare it with Permit to Work vs JSA vs Control Verification so the team does not confuse a task analysis with a live control check.

Step 4: Identify who is exposed now, not who was exposed before

A temporary change often shifts exposure to a new group. The original crew may understand the change, but contractors, nearby operators, or the next shift may not. Screen the change by naming everyone who can now touch it, cross it, or be surprised by it.

Then ask a second question. Which person now has the highest chance of being caught by the change if the job restarts in a hurry? That person usually reveals the real control gap. When the answer is not obvious, the team has not yet mapped the exposure correctly.

That is also why simultaneous work matters. A temporary change beside another active task is not temporary in practice because the interface becomes the hazard. If the same zone is being shared, the screening has to cover both jobs, not only the one that created the change.

Step 5: Test the barrier that changed

The screening fails when the team says the barrier is still in place but never proves it. If the change affects access, test the access. If it affects isolation, test the isolation. If it affects supervision, test whether the supervisor can still see and manage the work from the new position.

Use one question for each barrier. What would happen if the temporary fix slipped back into the old state? What would be the first visible sign that the change is no longer holding? Those questions keep the team focused on the barrier itself, not on the story around it.

A useful way to think about this is the logic in Safety Culture: From Theory to Practice. A barrier is only real when people keep testing it under the pressure of real work. A temporary field change deserves that same discipline.

Step 6: Write one decision, one owner, one expiry

After the field walk, do not leave the conclusion as a discussion summary. Write one decision in simple language, assign one owner, and state one expiry or reset condition. If the team cannot do those three things, it has not yet made a decision.

A useful format is this: hold the change, approve the change with controls, or stop the job until the field is reset. That language is clear because it tells the next person what to do without needing to reinterpret the conversation. It also creates decision memory, which is the part that usually disappears first when the shift changes.

The logic is close to what supervisors need in the first hour of a problem. The closer the decision sits to the field, the less room there is for drift. That is why the note should include what will trigger a reset, not just what the team prefers today.

Step 7: Brief the next shift and any adjacent crew

Do not let the change travel by rumor. The next shift, the contractor lead, and any adjacent crew that shares the space need the same short explanation of what changed, what remains active, and what must not restart until the reset condition is met. A brief that lands only in one group is not enough.

Ask the receiver to repeat the decision back in their own words. If they cannot repeat it cleanly, the screen has not yet transferred control. That is not a communication nicety. It is a test of whether the site actually understands the field change.

If the shift boundary is part of the problem, pair this step with Shift Start Safety Walk, Weekly Risk Review. The walk shows whether the control still exists, and the brief shows whether the next person knows what to do with it.

Step 8: Verify the change after restart

The screen is not finished when the briefing ends. It is finished when the work restarts and the field still matches the decision. Check early, not late. Look for the first sign that the temporary arrangement is slipping, because small drift at the start usually becomes hidden drift by the end of the shift.

Use a short verification window and ask three questions. Is the barrier still where it should be, is the exposure still limited to the intended people, and did the next crew see the same condition that was screened? If any answer is unclear, reopen the decision before the work keeps moving.

Andreza Araujo's experience in more than 250 cultural transformation projects points to the same practical lesson. Control improves when leaders verify the field after the decision, not only before it. That is also the difference between a controlled exception and a temporary change that quietly becomes the new normal.

FAQ

What counts as a temporary field change?

It is any short-term change that alters who is exposed, which barrier is active, or what the next crew can safely assume. That can include a moved barrier, a temporary bypass, a changed route, a new exclusion area, or a nearby task that changes the interface.

Who should screen the change?

The screen should be done by the person who owns the job, with the supervisor or risk owner who can approve a hold or a reset. If the change affects more than one work group, the adjacent group should also hear the decision before work resumes.

What if the change seems too small to matter?

Small changes matter when they change exposure, access, or the next person's assumption. Many incidents grow from changes that looked temporary and harmless until the work accelerated and the field no longer matched the plan.

Which Andreza Araujo book fits this topic best?

Safety Culture: From Theory to Practice fits best because it explains why repeated decisions under pressure define the real culture. The Illusion of Compliance is the next best fit because it shows why a tidy form does not prove control.

What should happen if the screen finds a gap?

The job should hold until the gap has a named owner, a reset condition, and a field check that proves the new control works. If the team cannot name those three things, the safest answer is to stop and reset the worksite before moving on.

Conclusion

A temporary field change is safe only when the team can define it, test it, brief it, and verify it after restart. If the paper says one thing and the field says another, the screen is not done yet.