Manufacturing

Continuous lines, patterns that do not drift.

Rotating patterns expressed once rather than retyped each cycle, operators matched to the equipment they are signed off on, and overtime seen while it is still a decision.

The daily reality

The problems you know too well

  • A pattern that drifted from the one agreed
  • An operator on a machine they are not signed off for
  • Overtime discovered on the payroll run
With Formclock

How Formclock handles it

  • Positions seeded for manufacturing: Line Operator, Shift Lead, Maintenance, Quality
  • Coverage the agent fills and explains
  • Compliance enforced before every publish
  • Fair rotation everyone can see
Coverage

Gaps show up before the shift does.

Coverage requirements per day and position mean a hole in Friday shows up on Monday, and the agent can offer it to the right people before it becomes an emergency.

How gaps get filled
1 gap · Fri 4–10pFill gap

On a continuous line the handover is the expensive minute

A line that runs three shifts hands over twice a day, and each handover is the moment where a tolerance drifting, a machine sounding wrong, or a batch part-finished either transfers or does not. Nothing about it is visible in the output until later.

A written note attached to the shift survives the crew leaving and reaches whoever comes on rather than whoever was standing there. On a line, the cost of a lost handover is measured in a batch, which makes it the cheapest documentation any plant does. Three honest sentences written at the changeover are worth more than a shift report nobody reads, because the cost of the thing they prevent is measured in a batch rather than in minutes.

Scheduling the overlap is the part most rotas skip. If two shifts are planned to change at six with no overlap, the handover happens in the gap between one person leaving and another arriving, which is to say it does not really happen. A short scheduled overlap is a cost you can see and control, and the alternative is a cost you cannot.

Sign-off belongs to the machine, not to the shift

An operator qualified on one line is not automatically qualified on another, and the difference is a safety matter rather than a preference. Rotas that schedule people to shifts rather than to equipment lose that distinction the moment somebody covers a gap.

Attaching the requirement to the position means a substitution is checked as carefully as the original plan. That is the case that actually goes wrong: the planned rota is usually correct, and the Tuesday-afternoon swap is where an unsigned-off operator ends up on a machine. Sign-off travels with the machine rather than the person's job title, so the check has to happen where the assignment is made instead of at induction.

The practical consequence is that a swap needs the same check as an assignment. Two operators trading a shift is usually harmless and occasionally removes the only person on that shift signed off on a particular machine. Both look identical as a request, and only checking the sign-off at the point of approval tells them apart.

A pattern copied by hand drifts, and nobody notices for weeks

Continental, four-on-four-off and other rotating patterns look simple and decay identically. Somebody copies last cycle forward, a shift moves for a bank holiday, and two months later the pattern no longer matches the one the workforce agreed to.

Expressing the rotation once as a recurrence removes the copying step and with it the drift. The pattern then stays the pattern, which matters more than it sounds: a drifted rota is usually discovered as a grievance rather than as an error. A pattern generated from its own rule keeps its shape for as long as the rule holds, and when the rule changes it changes everywhere at once.

Drift is expensive because it is invisible while it accumulates. Nobody sees the week the pattern slipped; they see the quarter in which one crew has worked more nights than another, by which time the conversation is about fairness rather than about a copying error. Generating from the rule means the error either does not happen or happens once, visibly.

Planned overtime and the overtime that finds you

These cost identical money and are entirely different management problems. Planned overtime is a throughput decision made against a target. Discovered overtime is a decision somebody else made by covering a gap, learned about once it is unchangeable.

Checking the threshold while the week is still being built moves the discovery to the point where a shift can be moved or split. It does not make the hours cheaper. It makes them a choice, and it stops the same few people quietly absorbing every gap. Overtime that is planned is a cost with a decision behind it, and overtime that accumulates is the same cost with nobody's name on it.

There is a distributional half to this as well. Unplanned overtime lands on whoever is easiest to ask, which over a quarter is a small number of the same people. Watching who is absorbing it is worth as much as watching the total, because the total is a cost and the distribution is a retention problem that arrives later and costs more.

The shift pattern outlives the person who designed it

Patterns get built by somebody who understood the constraints at the time, and then run for years after that person moves on. What is lost is not the pattern but the reasoning, so nobody knows which parts are load-bearing and which were preference.

A rota that records what each shift requires, and refuses to publish one that breaks a rest rule, keeps the constraints visible even when the reasoning is gone. The next planner inherits a system rather than a tradition. Writing down why a pattern is shaped the way it is takes an afternoon, and reconstructing it from a rota nobody can explain takes considerably longer.

Patterns also need to change occasionally, and that is where an undocumented one becomes genuinely expensive. Changing a rule you can read is an afternoon's work. Changing a pattern nobody can explain means reverse-engineering it from a year of rotas first, and doing it with the knowledge that some of what you find was a mistake somebody made and everybody has since worked around.

The pattern is the pattern now, not whatever last month's copy became.
Production manager, two-line plant

Illustrative scenario, not a customer quote.

Questions

Manufacturing scheduling, answered.

Can it handle four-on-four-off and continental patterns?+
Yes. A rotating pattern is expressed once as a recurrence rather than retyped each cycle, which is what stops it drifting. Nights crossing midnight are stored in UTC against the site timezone so the hours land on the day they belong to. Yes, generated from a recurrence rule rather than copied forward by hand. That is what stops the pattern drifting, and it means an exception stays visible as an exception rather than becoming a new fact in a grid nobody can explain.
Can we stop an operator running equipment they are not signed off on?+
Yes. Sign-off is a requirement on the position, and somebody without a current one is not offered that work, including when the coverage agent fills a gap unattended. Yes, and the check applies to swaps as well as to assignments. Two operators trading a shift is usually harmless and occasionally removes the only person on that shift signed off on a particular machine, and both look identical as a request.
How do we see overtime before payroll does?+
The threshold your organisation sets is checked while the week is being built, so hours crossing it surface at the point a shift can still be moved. Planned overtime is a throughput decision. Overtime found at payroll is the same money and a worse conversation. The threshold lives in your organisation settings, so the warning appears while the week is still being built and four hours can be moved for nothing. Payroll is where it appears if you do not, and by then it costs what it costs.
Does it help with the handover between shifts?+
Handover notes attach to the shift rather than a group chat, so the incoming crew reads what happened on the line rather than hearing a version of it. On a continuous line that minute is the most expensive one of the day. Yes, and the part worth getting right is scheduling the overlap. Two shifts planned to change at six with no overlap hand over in the gap between one person leaving and another arriving, which is to say they do not really hand over at all.
Can shift leads see only their own line?+
A lead can be restricted to the locations they run, and the restriction holds on the server rather than merely hiding menus. Roles rank from employee up to admin and the server enforces the boundary rather than the interface merely hiding it. A shift lead works within their scope, and anything they change is recorded against them in the audit log.

See it with your own schedule

Set up a workspace, add your team, and build a week. It takes about ten minutes and costs nothing.

Start free