What is the difference between a rota and a deployment sheet?

The rota says who is working and when. The deployment sheet says what each of those people is doing, and where, during the shift. A rota is usually published weekly and a deployment is built daily, which is why the two rarely live in the same system.

Who builds the deployment sheet?

A planner, area manager or duty manager, each morning, from the roster and the day's demand. In a multi-site operation one person often builds several, one per site, before the first shift starts.

Can a deployment sheet be automated?

Yes, once three things are captured as data rather than held in a planner's memory: eligibility, meaning who is trained or licensed for what; demand, meaning how many people each area needs across the day; and time rules such as breaks and maximum continuous time on a task. A solver can then produce the deployment and rebuild it when the roster changes. Deciding the rules still takes a person.

Is a deployment sheet the same as a position rotation?

They are close relatives. A position rotation moves people between posts on a timer through the shift, which is typical in attractions and aquatics. A deployment sheet assigns people to areas and tasks for blocks of the day, which is typical in retail and logistics. Both are intra-shift assignment and both are usually a spreadsheet.

Why is the deployment sheet rebuilt from scratch every day?

Because both of its inputs move daily. The roster changes, so yesterday's names are wrong, and demand changes, so yesterday's task mix is wrong. A template can hold the shape of a deployment but not its contents, which is why the work repeats every morning.

What breaks a deployment sheet first?

Absence. The roster still shows enough people, so nothing upstream flags a problem, but a specific licensed or inducted person is missing from a specific area. Answering who else may cover it means checking eligibility one person at a time, which is the slowest step in the rebuild.

← Back to glossary

Deployment Sheet

A deployment sheet is the daily plan that says where each person already rostered for a shift will work and what they will do, broken into time blocks: which till, which aisle, which dock, which site, which task, and from when to when. It is the UK retail and logistics name for intra-shift assignment, and it is almost always a spreadsheet rebuilt by hand every morning.

The distinction that matters is the one against the roster. The roster settles who is in and between which hours. The deployment sheet settles what those people do once they arrive. A site can hold a fully staffed, fully legal roster and still open with nobody on the dock, because the second document is the one that places people.

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. The induction matrix and the licence expiry dates usually live in a planner's memory, so the question of 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

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.

Why this matters for planners and team leads

A deployment sheet is the document that decides whether a shift works, and it is usually the least supported document in the operation. The roster gets a system, an approval flow and an audit trail. The deployment gets a spreadsheet, a planner and an hour of their morning.

That imbalance shows up twice. It shows up in the planner's week, where building the sheet, sending individual assignments and answering eligibility questions can be the single largest block of time in a multi-site operation. And it shows up in the quality of the day, because a sheet built at seven in the morning is a forecast, and by mid-morning it is describing a site that no longer exists.

The fix is not a better template. It is holding eligibility, demand and time rules as data so the deployment can be rebuilt in the minute after someone calls in, rather than in the twenty minutes it takes to check who is trained on what.

Example in practice

A regional operation runs four sites off one staff pool. At 06:40 the planner opens the base sheet: who is rostered, contracted hours, and the trained-at grid. Demand for the day says one site needs an extra pair of hands on click and collect and another has a delivery landing at 10:00.

The planner cuts four deployments, one per site, and sends each colleague their area and time blocks. Two people are dual-sited, so their blocks have to leave travel time between the last assignment at one site and the first at the next.

At 09:15 a forklift-licensed colleague calls in sick at the site expecting the delivery. The roster still shows enough bodies, so nothing in the rota flags a problem. The deployment is the document that is now wrong: the dock has no licensed operator between 10:00 and 14:00. The planner works back through who else holds a current licence, finds one person on tills at another site, moves them, and re-cuts two of the four sheets. Two sites' worth of colleagues get a second message before ten o'clock.

Frequently asked questions

What is the difference between a rota and a deployment sheet?: The rota says who is working and when. The deployment sheet says what each of those people is doing, and where, during the shift. A rota is usually published weekly and a deployment is built daily, which is why the two rarely live in the same system.
Who builds the deployment sheet?: A planner, area manager or duty manager, each morning, from the roster and the day's demand. In a multi-site operation one person often builds several, one per site, before the first shift starts.
Can a deployment sheet be automated?: Yes, once three things are captured as data rather than held in a planner's memory: eligibility, meaning who is trained or licensed for what; demand, meaning how many people each area needs across the day; and time rules such as breaks and maximum continuous time on a task. A solver can then produce the deployment and rebuild it when the roster changes. Deciding the rules still takes a person.
Is a deployment sheet the same as a position rotation?: They are close relatives. A position rotation moves people between posts on a timer through the shift, which is typical in attractions and aquatics. A deployment sheet assigns people to areas and tasks for blocks of the day, which is typical in retail and logistics. Both are intra-shift assignment and both are usually a spreadsheet.
Why is the deployment sheet rebuilt from scratch every day?: Because both of its inputs move daily. The roster changes, so yesterday's names are wrong, and demand changes, so yesterday's task mix is wrong. A template can hold the shape of a deployment but not its contents, which is why the work repeats every morning.
What breaks a deployment sheet first?: Absence. The roster still shows enough people, so nothing upstream flags a problem, but a specific licensed or inducted person is missing from a specific area. Answering who else may cover it means checking eligibility one person at a time, which is the slowest step in the rebuild.

Related terms

Continue with closely connected glossary pages in the same operations cluster.

Put this into practice

See how Soon handles deployment sheet in your shift scheduling workflow.

See the product