Deployment Sheet
A deployment sheet is the daily plan that assigns each person on shift to a place and a task: which till, which aisle, which dock, which site, and from when to when. It is built every working day, usually one sheet per site, after the rota is known. The rota answers one question, who is in. The deployment sheet answers two more, where each person works and what they do there. In UK retail and logistics it is the document a planner or duty manager produces each morning, and in most operations it is a spreadsheet.
It is usually rebuilt from scratch. A planner takes the base sheet (who is rostered, contracted hours, who is inducted or licensed where), lays the day's demand across it, and produces a deployment. For a multi-site operation of around a hundred colleagues that can mean one sheet per site per day, plus a message to each colleague telling them where to turn up.
A site can hold a fully staffed, fully legal roster and still open with nobody on the dock, because the deployment sheet, not the roster, is the document that places people. It is the retail and logistics form of intra-shift rotation: the same plan attractions call a bump schedule, with areas and tasks in place of rides.
Three things called deployment
The word travels badly, and a search for it returns two senses that have nothing to do with staffing.
- Software deployment: shipping a release to a server. Unrelated, and the dominant meaning in published writing.
- Military deployment: sending personnel to a location for a tour. Related in spirit, measured in months, and settled far above a duty manager.
- Workforce deployment: the sense on this page. One operating day, one site or area, assignments measured in hours, decided by whoever runs the floor that morning.
What a deployment sheet holds
Five columns do the work, and each one carries a constraint that is easy to state and hard to satisfy.
- Person. Everyone rostered for the day, which arrives from a different system than the one the sheet lives in.
- Site or area. Store, warehouse, zone, floor. Trained-at rules limit who can go where, and they rarely live anywhere searchable.
- Task or position. Till, replenishment, click and collect, forklift, dock. Some of these need a licence or an induction that expires.
- Time block. Start and end of each assignment. Breaks and maximum continuous time sit inside these, not between them.
- Cover. Who steps in when somebody is off. On most sheets this is a note rather than a plan, which is why absence is the moment the sheet is re-cut.
Eligibility is where a hand-built sheet breaks, because eligibility is not one fact per person. It is one induction per site, plus one licence per truck type per site, and a colleague inducted at one warehouse cannot work the next one until inducted there too. That matrix and its expiry dates usually live in a planner's memory, so whether a given person may work a given area has to be answered one person at a time before the sheet can be redrawn. That is fine at ten people and unworkable at a hundred.
Why it is rebuilt every day
Three reasons compound, and none of them can be removed by working harder on the template.
- The roster changes daily, so yesterday's deployment does not survive contact with today's names.
- Demand changes daily, so even with the same people the task mix moves: a delivery lands, a promotion starts, a line goes down.
- The people on the sheet are not the people who read it. The sheet is the planner's working document, and colleagues learn their assignment by message, email or a printed copy on a wall. Every change means a new sheet and a new round of messages.
What replaces a deployment sheet
What replaces a deployment sheet is scheduling software that treats tasks, areas and sites as things it can schedule, with eligibility rules attached, so the deployment is generated from the roster rather than built from it by hand.
The roster layer is a solved problem and most scheduling tools cover it. The deployment layer, which is intrashift scheduling under a retail name, needs four things that a rota tool does not have.
- Eligibility as data. The induction matrix and the licences held as rules on each person, so whether someone may work an area is answered by the system rather than from memory.
- Tasks and areas as schedulable objects. Not a text field on a shift, but an assignment with a start, an end, and rules for who may hold it and for how long.
- Demand per area. How many people each area needs across the day, so the deployment is built against a target instead of by feel.
- A schedule the colleague can see. The assignment reaches the person directly, so a change costs a notification rather than a rebuild and a mail merge.
Soon covers this layer with intraday management: each task or area carries rules for who is allowed on it, minimum and maximum time, how many people at once, and its priority when the floor is short. Sites can run as separate boards over one staff pool, with eligibility as the filter, and the remainder of the day re-solves when somebody goes off.