Walk Time: The Hidden Variable in Rotation Schedules

Walk time is the travel time between one assignment and the next inside a shift. It is paid, it is staffed, and on a large site it is not small: getting from a base to the next position can take ten to fifteen minutes.

Almost no rotation plan accounts for it. Plans are written as interval arithmetic: rotate every 45 minutes, four positions, four people. That arithmetic assumes everyone arrives the instant somebody else leaves. The gap between plan and floor opens on the first handoff and widens all shift.

This guide does the subtraction most rotation plans skip, then works through proximity aware assignment, route sequencing for mobile teams, and the trade-off nobody names: the schedule with the least walking in it is also the most boring schedule you can hand someone.

The subtraction nobody does

Take a 45 minute rotation interval and an average move of 12 minutes. The person leaves position 3, walks, arrives at position 7, has the handoff, and starts work. Position 7 is staffed by that person for 33 minutes, not 45.

That is 27 percent of the interval. Nobody was idle, because walking to a position is part of the job. What was lost is coverage, which is a different problem and a worse one, because the plan on the wall claims the position is staffed for the full 45.

The arithmetic hides a second cost: the handoff itself. In a bump, the relief walks up, says who they are relieving and where that person goes next, and the two swap. Short, but not free, and a plan that budgets 12 minutes of walking and zero seconds of handoff is already behind.

One note on vocabulary, because the word collides. In union contexts, bumping usually means seniority displacement during a layoff. The operational sense used here is the relief handoff at a position. Same word, unrelated mechanics, and worth saying out loud in any document a union representative will read.

What twelve minutes costs across a shift and a season

Every assumption below is stated so you can swap in your own. Nothing here is a benchmark, it is arithmetic.

1. Start with a floor stretch of seven hours, which is what an eight hour shift leaves after a meal break and two rest breaks come out of it.
2. At a 45 minute interval that is roughly nine positions per person across the shift, and nine moves, counting the walk from the base out to the first position.
3. Nine moves at 12 minutes each is 108 minutes per person per shift in transit. Against 405 minutes of interval time, just over a quarter of the shift is spent walking.
4. Across a day team of 60 people that is 6,480 minutes, or 108 hours. Divided by the 6.75 hour floor stretch, it is the equivalent of sixteen people who clocked in and spent the whole shift in motion.
5. Over a 120 day operating season, 108 hours a day is 12,960 hours of paid transit. A site that runs year round multiplies accordingly.

The reflex on seeing that number is to eliminate it, which is the wrong reflex. A site large enough to need rotation is large enough to require walking. What the number does respond to is sequencing. Reorder the same nine positions so the average move drops from 12 minutes to 8, and each person saves 36 minutes. Across 60 people that is 36 hours a day, a little over five people's worth of floor time, and 4,320 hours over the season. Nobody walked faster. The order changed.

Why the plan breaks at the fifth handoff, not the first

Rotations do not swap everybody at once. They cascade. One relief enters the chain, displaces someone, that person moves on and displaces the next, and the chain runs through the area position by position. This staggered relief is what keeps every position staffed while people move, and it is also what makes lateness compound.

In a synchronised swap, a late arrival costs three minutes at one position. In a staggered chain, every link waits on the one before it, so three minutes lost at the first handoff is still lost at the fifth, with company. Two or three small overruns and the last person in the chain is a quarter of an interval behind, which usually lands on somebody's break.

That is the moment the plan dies. The floor can see it is wrong, so the lead stops reading it and starts calling moves over the radio, and everything the plan was carrying goes with it: certification requirements on safety critical positions, heat exposure limits, break entitlements, and the variety the rotation existed to produce. The practical test is to ask a lead whether the second half of the shift ever runs to the sheet. If they stop looking after the first break, walk time is a strong candidate for why.

The shortest public path is not the staff path

This is where plans built from a site map go wrong. The distance a guest walks between two points and the distance a staff member walks are frequently different numbers, in both directions.

• Sometimes the staff path is much shorter. Service roads and back of house corridors cut straight across a site while the public route curves around whatever the site is built to show off.
• Sometimes it is much longer. Staff in costume or full character cannot cross a guest area, so a position two hundred metres away on the map is a six hundred metre backstage loop in practice.
• Access control adds fixed overhead. Badge doors, secure areas, and anywhere requiring an escort put a constant on top of the distance, and that constant does not shrink when someone walks faster.
• The same crossing changes length through the day. A route that takes six minutes before opening takes eleven once the crowd arrives, and the moves you most need to be quick fall in the busy stretch.
• Who is walking matters. Someone carrying equipment, in heavy costume, or crossing a wet floor is not moving at the pace a map assumes.

The fix takes an afternoon. Time a handful of real routes with a stopwatch, once at open and once at peak, walking them the way staff walk them. Two or three measured crossings per area is usually enough to reorder a rotation into something that runs on time.

Proximity aware assignment

Proximity aware assignment means the schedule holds the distances, not just the names. Once the plan knows that position 3 is ninety seconds from position 4 and eleven minutes from position 9, it can order a position rotation so that consecutive assignments sit near each other, and save the long crossings for the moves that have slack around them.

The same data sets a floor under the interval. If heat or costume rules push the interval down to 15 minutes and the moves inside that area take 10, most of the labour is in transit and the rotation is close to pointless. The answer is not a faster walk. It is a relief pool living inside the exposed zone, so the moves are ninety seconds instead of ten minutes.

Proximity is a preference, though, not an override. A ride dispatch console needs a certified operator or the ride does not run. Nearest available person is the right tie breaker among people who are qualified, and the wrong answer when it is not. Any assignment engine worth using treats certification as a hard constraint and distance as a cost to minimise underneath it.

Measured distances also expose neighbourhoods: clusters of positions within two or three minutes of each other, separated by expensive crossings. Once the clusters are visible, a rotation ring can stay inside one for most of the shift.

Route sequencing for cleaning and maintenance teams

Cleaning, maintenance, grounds, and park services teams do not sit in a fixed position at all. They travel between jobs all day, so for them the sequence is the schedule. These teams almost always have a route sheet already, which is the existing manual practice and a good one. The flaw is not the sheet. It is that the sheet is static, written once, and rarely tested against the order it lists.

Two route sheets can hold the same jobs and differ by an hour of productive time purely in sequence. Backtracking is the usual culprit: a sheet organised by job type or by priority sends someone across the site and back repeatedly, while the same jobs sequenced by zone, then by time window inside the zone, remove most of the crossings.

Sequencing also makes the plan honest about capacity. Add up the job durations on a route sheet and it looks like eleven jobs fit in a shift. Add the travel between them and it is eight. Planners who only add durations promise eleven, and the team runs short every day for reasons that look like slowness and are actually geometry.

Mobile work also changes most during the day. A spill call or a broken fixture is not a task appended to a list, it is a re-sequencing problem, because inserting a job at the wrong point in the route costs two crossings instead of one. That is the same class of decision as any other intraday reallocation, applied to distance instead of demand.

The trade-off: least travel against most variety

Here is what gets missed once travel becomes a metric. Tell a solver to minimise walking and it gives you exactly what you asked for: park each person in a tight cluster of two or three neighbouring positions and leave them there. Almost no transit. Also eight hours on the same register, which is precisely the outcome rotation exists to prevent.

Variety across the shift is a first class objective, not a nicety. It is why the rotation exists at all in most operations, alongside the safety case for getting people off exposed or repetitive positions. It is also why the highest value moves are the long ones: someone homed to one area who works three locations in a day has crossed cost centre boundaries, and those are exactly where the walks are longest.

So the objective is not the minimum. It is a transit budget, spent deliberately:

• A per person transit ceiling. Decide what share of the shift can go to travel, for example ninety minutes, and let the plan spend it rather than silently exceeding it.
• Cheap moves as the default. Most of the shift runs inside one neighbourhood at ninety second moves, which costs almost nothing and still changes the task.
• Expensive moves bought on purpose. One or two long crossings per person, placed where they buy a genuinely different job or a different area.
• Break boundaries as free crossings. Someone walking to a break room is already in motion, so a return to a different area costs far less than a mid interval crossing.
• Quiet periods for the long walks. Schedule the crossings that get slow at peak for the parts of the day when the site is empty.

It also changes the argument on the floor. A lead who can show where ninety budgeted minutes went has a concrete case for a closer relief pool or one more person in the area. A lead with no number has an opinion.

What the plan actually needs to hold

None of this requires a mapping project. A rotation plan that respects walk time needs a small, boring set of facts kept current:

• Measured travel time between position pairs that actually appear in the rotation, not every possible pair.
• Two versions of the numbers where it matters: quiet and busy, and a wet weather variant if the site has one.
• A fixed overhead per handoff, covering the relief conversation and anything that has to be checked or signed at the position.
• Access constraints: badge doors, escorted areas, routes that costumed or uniformed staff cannot use.
• Which positions are safety critical and certification gated, so proximity never overrides qualification.
• A transit budget per person per shift, so the trade-off against variety is made on purpose.

Those inputs separate a rotation that survives a busy Saturday from one abandoned by 11am. They are also what makes automated assignment worth having, because auto-scheduling that does not know the distances just produces impossible plans faster.

Where to start

Pick one area, time five real routes at two points in the day, and re-run the arithmetic above with your own numbers. If a quarter of your interval turns out to be transit, you can decide what to do about it rather than watching the plan drift and calling it a discipline problem.

The rest of the mechanics, including how intervals interact with certification, heat rules, and a deviceless workforce, sit under intrashift scheduling, and the rotation schedule generator will do the interval subtraction on a printable sheet if you want to test an order before publishing it.

If the walking is a symptom of thin cover rather than bad sequencing, it is a headcount question, and the coverage staffing scenarios work out how many people a continuously staffed position needs before any rotation arithmetic applies.