Skip to content
← Back to glossary

Intrashift Scheduling

Intrashift scheduling, also written intra-shift scheduling, is the planning of what happens inside a shift: which position each person occupies, how long they hold it, when they move, and who relieves them. Shift scheduling decides that somebody works from 8am to 4pm. Intrashift scheduling decides what those eight hours are actually made of.

The unit of planning is a position-interval, not a shift. One person on an eight-hour shift rotating every 45 minutes is not one planning object, it is roughly ten of them, each with its own location, skill requirement, and handover. Forty people on the floor produce several hundred position-intervals a day, which is the point where a whiteboard stops being a plan and becomes a record of good intentions.

How it differs from the neighboring disciplines

  • Shift scheduling: fills coverage at the day level by putting named people on shifts. It is silent about where anyone stands once they have clocked in.
  • Intraday management: the contact center discipline of tracking actual volume against forecast through the day and adjusting breaks, channels, and activities. Interval-based and demand-driven, but not position-based.
  • Task management: a list of things to finish before going off shift. Sequence and timing stay open, so it answers what rather than where and when.

The separation matters because operators looking for the third thing keep landing on the other two. Intrashift scheduling is the layer between a published roster and the moment a supervisor has to say who is standing where at 14:15.

What a rotation plan has to satisfy

Rotation intervals commonly sit between 45 and 60 minutes, and tighten to 15 or 30 when people work in outdoor heat or cold, or in heavy costume. Positions carry skills and certifications, some with expiry dates that force refresher training, some safety-critical: a console that legally requires a certified operator cannot be handed to the nearest available body. Other positions are merely preferred, and can be downgraded on a thin day.

Travel is a scheduled quantity too. Crossing a large site can take 10 to 15 minutes, and that walk is time during which nobody is covering anything, so a rotation that ignores it overstates its own coverage. Variety belongs in the same list of constraints: nobody wants eight straight hours on one register, and the plan is where that preference gets honored consistently rather than left to whoever is leading that day.

Bumps and staggered relief

In attractions and hospitality the mechanic has a name: the bump. A relief worker walks to a position, says they are taking it and where the current occupant goes next, and that person moves on and displaces somebody else in turn. Relief travels down a chain in staggered steps instead of everybody swapping at once, which keeps every position occupied while the rotation runs. In union contexts bumping usually means seniority displacement during layoffs. The sense used here is narrower and purely operational: a handover at a post, not a claim on a job.

Why this matters for planners and team leads

A published roster tells a planner what the day costs. It says nothing about whether those hours land in the right places, and that gap is where the avoidable damage accumulates. Somebody left on one counter all day becomes a resignation two months later. A safety-critical post filled by an uncertified person becomes a shutdown. A rotation drawn without walk time loses ten minutes of real coverage every time it fires, which nobody notices because the plan says otherwise.

The second reason to care is that the plan does not hold still. A late return from break, an unplanned absence, a weather closure that strands an entire area's labor: each one invalidates the remainder of the day's rotation, and a large site can end up re-solving hundreds of times before close. Planners who treat the rotation as a printed artifact spend their afternoon patching it over the radio.

Soon's intraday management view holds positions, coverage, and the rotations still to come in one place, so an 11:00 change shows what it does to 15:00 before anyone commits to it.

Example in practice

A large attraction opens with sixty frontline staff across ride operations, food kiosks, and retail. Each ride team works a four position cycle of greeter, grouper, loader, and dispatch. Dispatch needs a current certification, the other three do not. The plan rotates every 50 minutes and books 10 minutes of walk time for anyone moving between areas.

At 12:40 an outdoor ride goes down with a mechanical fault and eight people have nothing to cover. At 12:55 a kiosk supervisor reports someone home sick. The area lead sends two of the eight to the kiosk, and puts three more on the busiest queue line so that team can drop to 25 minute rotations while the afternoon heat peaks. The remaining three go to retail, a different cost center from the one they are homed to.

None of them are carrying a phone. The revised chain reaches them the way it always does: a printed slip pinned up in the break room, a radio call to each area lead, and the bump itself, where whoever arrives tells the person leaving which position they are going to next.

Put this into practice

See how Soon handles intrashift scheduling in your shift scheduling workflow.

See the product