Standard operating procedures are written during the day. They are reviewed by engineers who work regular hours. They are approved by managers who leave at five. And they are tested, when they are tested at all, under conditions that roughly approximate the best-case scenario: full crew, experienced operators on hand, supervisors reachable by phone.
The night shift operates in a different environment. Fewer experienced people on the floor. Different ambient temperatures in facilities without climate control. Lighting conditions that change how you read gauges and indicator lights. Fatigue that narrows attention after twelve hours. And, critically, no supervisor on call in many operations - just a phone number that rings to voicemail after midnight.
The deviation grows after dark
Every plant has informal protocols that exist alongside the official SOP. The experienced operator on day shift knows when to deviate from the written procedure and why. She knows that pump number four runs hot in summer and cold in winter, and that the SOP's temperature threshold does not account for seasonal variation. She knows that the vibration reading on conveyor B is always slightly elevated on Mondays because of the weekend cooldown cycle, and that this is not a fault condition despite what the manual says.
On the night shift, that operator is not there. The person standing in front of the same equipment has the same SOP binder, the same digital procedure on their tablet, and none of the contextual judgment that makes the SOP useful rather than misleading. The deviation between what the procedure says and what the situation actually requires is widest precisely when the people who understand that deviation are not available.
What happens in practice
A night-shift operator encounters an alarm condition not covered by the SOP. The documented procedure says to contact the supervisor. The supervisor is not answering. The operator has three choices: shut down the line (expensive, and potentially unnecessary), reset the alarm and hope (risky, and the incident report will not be kind), or call the retired expert who used to run this equipment and ask what he would do.
That third option happens more often than operations leaders realize. Retired technicians fielding phone calls from former colleagues at two in the morning is not a knowledge-transfer strategy. It is a symptom of a gap that the SOP was never designed to fill.
The SOP is necessary but not sufficient
This is not an argument against standard operating procedures. SOPs serve a function: compliance, training baseline, regulatory documentation. The argument is that SOPs, by design, capture the standard case. They do not capture the judgment that experienced operators apply when conditions deviate from standard. And conditions deviate from standard most often on the night shift, when the people who carry that judgment are asleep at home.
The gap is structural. You cannot close it with better SOPs, because the knowledge that fills it is not procedural. It is situational, conditional, and often contradicts the written procedure in ways that are correct and necessary. What you need is a way to capture that judgment in structured form - attributed to the named expert who holds it, validated by them, and available to the person on the floor at three in the morning without a phone call.
Structured expert judgment does not replace the SOP. It fills the space between what the SOP says and what the floor actually needs. That space is largest on the night shift. And it is growing wider every time an experienced operator retires without their judgment being captured.