Shop floor control: what the supervisor decides between the plan and the product

The dispatch decision when two jobs are both ready

Supervisors need a rule they can apply in seconds and defend afterwards. Usually it combines the published sequence with two overrides: keep the pacing resource fed, and do not break a setup family without a reason worth the changeover. Whatever the rule, it should be written and known, because in its absence the priority becomes whoever asked most recently or most loudly, which produces a plant that responds to volume of complaint rather than to customer risk. Record deviations from the published sequence with a one-line reason; the accumulated reasons show whether the schedule is unrealistic or whether the floor is simply choosing convenience.

An escalation ladder people actually use

Define what triggers a call for help, whom to call, and how long to wait before going up a level. Common triggers are a stoppage lasting beyond a set point, a quality event affecting product already made, a safety concern, and a shortage that will stop the line within the shift. The ladder fails in two directions: supervisors who escalate nothing because previous calls produced criticism, and supervisors who escalate everything because no threshold was set. Managers should measure the response time on their side of the ladder, since a support function that answers slowly teaches the floor to stop calling.

Keeping the span of control small enough to control

A supervisor responsible for too many people, machines or square metres cannot do the observation that control requires, and defaults to firefighting whatever is loudest. When considering the span, count not just headcount but the number of distinct processes, the frequency of changeovers, the proportion of new or agency staff, and how much of the shift is spent on administration. If the answer is that nobody could realistically watch this area, the fix is structural — a team leader layer, a smaller area, or removing administrative work — rather than exhorting the individual to be more organised.

Short interval control instead of end-of-shift surprise

Checking progress at intervals well inside the shift converts a bad day into a series of small recoverable gaps. The routine is simple: at each interval the team compares what was produced with what was expected, writes the reason for any gap, and the supervisor acts on it or escalates. What makes it work is that the reaction to reported loss is help rather than blame, and that someone visibly uses the recorded reasons afterwards. Where neither is true, the board gets filled in retrospectively at the end of the shift and becomes a compliance exercise with no operational value.

Making decisions survive the change of shift

Half of shop floor control is ensuring the next team inherits the reasoning, not just the state. A job left part-run with an unrecorded adjustment, a machine running with a temporary fix nobody documented, a deviation agreed verbally with quality — each becomes an incident on the following shift. The discipline is to record the decision alongside the condition, in a place the incoming supervisor reads before starting. Plants with continuous operation should treat this record as part of the control system rather than as a courtesy between colleagues.

Frequently asked questions

How much authority should a shift supervisor have to spend money?

Enough to keep the plant running until the next management presence, with a limit written down and a requirement to record what was spent and why. Typical delegated decisions include calling in a contractor for a breakdown, authorising overtime for the shift, and expediting a component. Setting the limit too low guarantees that expensive hours are lost waiting for approval overnight or at weekends, which usually costs far more than the decisions being controlled.

Should supervisors be doing production work themselves?

Sparingly and by exception. A supervisor who fills a gap on the line stops observing, stops responding to escalation and stops making the decisions only they can make, so the area drifts while they are occupied. Persistent hands-on working is a symptom of understaffing or missing flexibility rather than of dedication, and it should be recorded as such so the resourcing problem becomes visible instead of being absorbed by the individual.

What is the difference between shop floor control and production control?

Shop floor control is the execution layer inside the area: sequencing at the machine, allocating people, responding to stoppages within the shift. Production control is the plant-level loop that releases work, monitors commitments across areas and closes orders. They share data and they overlap at the dispatch list, but the decision rights differ, and confusing them tends to leave either the supervisor without authority or the plant without an overall view.