How to create a staff rota, step by step
Build your first staff rota with a worked example, the role and availability checks to make yourself, a publishing checklist and a clear process for later changes.
By The TeamZap Team · · Updated · 3 min read
In this guide
Create a staff rota by defining the work that needs cover, checking who can do it and assigning clear shifts before publishing one current version. Begin with roles and times, then add people. That makes gaps easier to see.
This is a practical starter tutorial. The UK rota guide covers the wider management and working time context.
1. Define the shifts before choosing names
List opening, service, preparation and closing work. Include the role or skill each period requires. Customer opening hours are not necessarily the same as staff working hours.
For a fictional shop open from 10:00 to 18:00, the opening keyholder may need to arrive at 09:30 and the closing team may finish at 18:30. Build those tasks into the plan instead of treating them as invisible extra time.
2. Check people and constraints
Gather approved leave, current availability and contracted arrangements. Check relevant skills and the surrounding shifts, including those in the previous rota period.
TeamZap staff can record weekly availability in the app. It is not currently shown or checked in the normal rota builder, so the manager must review it separately. Availability guidance explains how to keep that step reliable.
3. Build a small worked day
| Role | Example shift | Planning check |
|---|---|---|
| Opening keyholder | 09:30 to 17:30 | Opening responsibility and break cover |
| Sales assistant | 10:00 to 16:00 | Customer service and delivery work |
| Closing keyholder | 12:30 to 18:30 | Closing responsibility and handover |
This example is a planning sketch, not a staffing recommendation. The business still needs to specify breaks, assess demand and check the rules applying to its employees.
Notice the overlap. It can support a handover and break cover, but it is only useful if the work requires it. Add or reduce hours based on actual operational needs.
4. Review the whole week
Check hours by person and role. Look at the previous finish and next start, approved absences and whether the same people repeatedly receive particular shifts.
TeamZap's scheduling checks warn as shifts are added or edited about clashes, approved leave, short rest, long weeks and skills mismatches. These are useful checks, not a complete legal or suitability assessment.
Use staffing history alongside bookings, opening plans or other demand information. Attendance shows when people worked; it does not automatically measure how many customers needed service.
5. Publish a version staff can find
Confirm that every shift has a date, start, finish, role and location where needed. Tell staff where the current rota lives and how to raise a query.
If a paper copy is needed, mark its publication date and explain how staff check subsequent changes. A screenshot cannot update itself.
6. Have a route for changes
Use manager approved swaps and open shift claims where appropriate. Keep proposed cover distinct from confirmed assignments. Follow the rota change checklist so the affected employee understands the revised details.
After the week, compare planned and reviewed actual hours. Investigate differences before adjusting the next plan.
Start with the free rota template, or explore TeamZap scheduling to connect the rota with attendance, leave and staff communication.
Frequently asked questions
What information do I need before building a rota?
Start with opening hours, required roles, contracted arrangements, approved leave, availability and any relevant training or rest requirements.
How far ahead should I publish?
Use the applicable contractual and legal requirements, then agree a reliable publication rhythm with the team. Do not treat an arbitrary number of days as a universal rule.
