# How to organize rotating shifts without losing track of hours https://techy.eus/en/resources/organize-rotating-shifts Updated: 2026-09-20 A shift schedule is more than a list of names. It should show who works, what rest comes next and how the pattern affects the people using it. Techy · Editable offline copy. Examples are illustrative, not customer results. Review the guide's limitations before applying it. ## Start with the rotation, not the month A usable schedule starts with the pattern that repeats: for example, four workdays followed by four days off. Write down the shift names, start and end times, and the date the cycle begins. The monthly calendar is only a view of that source pattern. Once the rotation is clear, you can move its start date, compare teams and forecast coverage without rebuilding a spreadsheet every month. - Give every shift a plain name. - Record start and end time, including overnight shifts. - Calculate the actual duration after unpaid breaks. - Keep the rotation rule and its starting date visible. ## Make the schedule answer three questions Someone should be able to open the schedule and immediately answer: when do I work, when am I off, and which shift is mine? If they have to count cells or ask a coworker, the format is doing too much work for too little clarity. Use labels and color as a quick guide, not as the only source of meaning. Important information should remain understandable when printed or viewed without color. ## Review hours before sharing it The common problem is not an individual shift — it is the accumulated total. Check duration, overnight transitions and the estimated total per person before the schedule goes live. That review prevents last-minute disputes over a difference that was already visible. Employment rules, overtime and required rest vary by location and agreement. Use this guide to organize the schedule, then confirm any legal or contractual requirements with the appropriate employer, representative or qualified adviser. ## Keep one version people can trust Avoid distributing multiple screenshots through chat. Share one clearly dated calendar, link or file, and log meaningful changes. When something moves, notify the people affected rather than restarting the whole conversation. ## Worked example: test the boundary, not just the first week Use this fictional eight-day cycle to test a calendar: two morning shifts, two evening shifts, then four days off. At eight counted hours per shift, one complete cycle contains 32 hours. If day one is 1 October, 9 October must return to the first morning shift. Check that boundary before extending the calendar for a year. This is an arithmetic exercise, not a staffing or legally compliant work-pattern recommendation. Next, add one approved absence in a copy. Keep the planned shift visible alongside the exception and the person covering it. Check each coverage interval separately: a correct personal rotation can still leave a team understaffed. Monthly hours must come from shifts inside that month, not from multiplying a cycle average. Ask another person to identify their first shift and first rest day without interpreting a color legend for them. ## Separate coverage hours from a weekly cost estimate Fictional small-team planning exercise: five people share the same hourly rate and weekly hours. The calculation below assumes a 40-hour threshold, a 1.5 overtime multiplier and a 10% additional-cost allowance. These are model inputs, not a statement of applicable US payroll law. The second scenario adds 20 coverage hours for $825, or $41.25 per additional hour under these assumptions. That is a marginal comparison, not the average hourly rate. Open the linked exercise, load the baseline, calculate, save it, then load the 44-hour variant. Keep the allowance unchanged in both runs so the comparison isolates hours. Worked example · fictional inputs | Scenario | Coverage hours | Regular + overtime | Including 10% | | --- | --- | --- | --- | | 5 people × 40 hours at $25 | 200 | $5,000 + $0 | $5,500 | | 5 people × 44 hours at $25 | 220 | $5,000 + $750 | $6,325 | ## Test the result and handle the exception Different pay rates, daily overtime, breaks, premiums or classification rules require a more detailed model. Do not treat a low estimate as permission to publish a schedule. A roster with the right total can still leave the busiest hour unstaffed. - The baseline has 200 coverage hours, not 200 hours per employee. - Only the hours above the assumed threshold receive the multiplier. - Review the actual calendar separately: 220 hours do not prove every required slot is covered. ## Your working sheet — fill in locally Situation and date: ____________________ Inputs and where they came from: ____________________ Decision / calculation: ____________________ Expected result: ____________________ Actual check and evidence reference: ____________________ Exception and next action: ____________________ Owner and review date: ____________________ Do not put passwords, patient details or other sensitive data in a shared worksheet. Downloading or checking a box does not verify real-world compliance.