DDNNOO schedule
Two days, two nights, two off: a six-day cycle so compact that three teams cover the clock, at an average of 56 hours a week each.
Also known as: ddnnoo rotation, 2-2-2 schedule, two days two nights two off
- Shift length
- 12h
- Rotation cycle
- 6 days
- Teams
- 3
- Avg hours/week
- 56
- Longest stretch
- 4 days
- Longest break
- 2 days
The full 6-day rotation
One complete cycle for all 3 teams. Coverage is 24/7: every day has exactly one team on each shift.
| Team | Week 1 | |||||
|---|---|---|---|---|---|---|
| Team A | D | D | N | N | ||
| Team B | D | D | N | N | ||
| Team C | N | N | D | D | ||
- Each row is one team across the six-day cycle: two day shifts, two night shifts, two days off, staggered so the clock is always covered.
- Every day of the cycle has exactly one team on days and one on nights; the third team is off.
- There is no long break anywhere in the cycle: the longest rest is the same two days, every time, and one of them is spent recovering from nights.
Build your DDNNOO calendar
Pick the date your rotation starts (day 1 of the grid above) and a team to see the next six weeks as real dates. Download the result for your calendar app or as a spreadsheet.
Calendar exports cover 26 weeks from the start date. Shift times use this page's defaults and can differ from your operation's clock times.
How the DDNNOO schedule works
DDNNOO is the tightest continuous rotation in this library: work two 12-hour days, roll straight onto two 12-hour nights, take two days off, repeat. The cycle is six days long, three teams tile it perfectly, and the whole clock is covered with the smallest team count of any 12-hour rotation here.
The number most pages ranking for this pattern never print: each team works four of every six days at 12 hours, which averages 56 hours a week. Not 42, like 2-2-3 or Pitman or 4-on-4-off. Fifty-six. That is the direct arithmetic consequence of covering 336 weekly hours with three teams instead of four, and it makes DDNNOO a fundamentally different proposition: a high-hours pattern for operations that pay for the overtime or crew for the intensity, not a sustainable default.
The rotation itself is also the fastest here: days roll into nights with only the sleep between them, then two days off must absorb the recovery from both. The two-day break after night blocks is the patternโs pressure point, and the reason its sustainable sibling, the four-team 2-2-4, exists at all.
How many people you need
Every position staffed 24/7 on this pattern needs 3 employees, one per team, before you cover holidays, sick leave, and training. A planning buffer of around 25 percent on top is a realistic starting point; the exact number depends on your absence rates, which you can work out with our shrinkage calculator. The same worked arithmetic for other coverage windows and team sizes lives in the staffing math library.
| Positions per shift | Minimum headcount | With 20% shrinkage buffer |
|---|---|---|
| 1 | 3 | 4 |
| 2 | 6 | 8 |
| 3 | 9 | 12 |
| 5 | 15 | 19 |
| 10 | 30 | 38 |
Pros and cons of the DDNNOO schedule
Works in its favor
- Covers 24/7 with three teams instead of four: a quarter less headcount than 2-2-3, Pitman, or 4-on-4-off
- Forward rotation (days before nights) follows the direction the circadian evidence prefers
- Never more than two consecutive nights, well inside the usual fatigue guidance
- A six-day cycle is trivially easy to memorize: the same three states, always in the same order
- Suits short-term intensives (shutdowns, projects, seasonal peaks) where high hours are priced in
Watch out for
- Averages 56 hours a week per person, which most pages describing this pattern simply do not mention
- In the EU, a standing 56-hour average is above the Working Time Directiveโs 48-hour ceiling, so the pattern needs opt-outs or reference-period averaging to be lawful at all
- Sixteen hours of weekly overtime per person is the real cost basis: three teams are cheaper in heads but not automatically in wages
- Two days off must absorb recovery from nights every single cycle; there is no long break anywhere
- The cycle drifts against the calendar week, so working weekends land unpredictably and family rhythm suffers
Who runs DDNNOO
Mining and resources
Short-rotation camps use DDNNOO where crews are on site anyway and hours are contractual.
Plant shutdowns and turnarounds
Time-boxed maintenance events accept high weekly hours to compress the outage window.
Military and emergency operations
Watch systems under surge conditions run compressed three-crew rotations by necessity.
Small utilities
Control rooms that cannot field a fourth team sometimes run DDNNOO and pay the overtime, knowingly or not.
Whichever industry you plan for, the hard part is rarely the pattern itself but keeping it fair as people join, leave, and swap. That is worth reading up on before you commit a team to one; our guide on making shift schedules fair covers the rotation-fairness tradeoffs in depth.
Common variations
- 2-2-4 (DDNNOOOO)
- The sustainable sibling: add a fourth team and extend the break to four days. The average falls to 42 hours and the EU ceiling problem disappears.
- DNONDO shuffles
- Local reorderings of the same six-day mix, usually to fix which weekdays the off-days land on. The 56-hour average does not move.
- 8-hour DDNNOO
- Rare: with 8-hour shifts the average drops to 37.3 hours, but a third shift type is then needed to cover the clock, and the pattern stops being DDNNOO.
Compare with other patterns
4-on-4-off schedule
The simplest continuous pattern there is: work 4, rest 4, forever. Four teams on 12-hour shifts cover 24/7 with a cadence anyone can remember.
12h shifts · 16-day cycle · longest stretch 4 days
View pattern →2-2-3 schedule (Panama)
Four teams on 12-hour shifts work 2 days, get 2 off, work 3, in a 14-day cadence that gives every team a full weekend off every other week.
12h shifts · 28-day cycle · longest stretch 3 days
View pattern →Continental schedule
A fast-rotating 8-hour pattern: four teams move through mornings, afternoons and nights in short 2-3 day blocks across a 4-week cycle.
8h shifts · 28-day cycle · longest stretch 7 days
View pattern →Frequently asked questions
- How many hours a week is a DDNNOO schedule?
- Fifty-six on average: four working days of every six at 12 hours each, which is 48 hours per 6-day cycle, or 56 per calendar week. Most descriptions of DDNNOO skip this arithmetic. Any operation adopting it should price roughly 16 hours of weekly overtime per person into the comparison against a four-team pattern.
- Is DDNNOO legal in Europe?
- Not as a standing arrangement without extra steps. The EU Working Time Directive caps average weekly hours at 48 over the reference period, and DDNNOO averages 56. Running it lawfully requires individual opt-outs where the member state allows them, or confining the pattern to short periods inside a longer averaging window.
- How many teams does DDNNOO need?
- Three, and that is its entire appeal. The six-day cycle with two on days, two on nights, and two off tiles perfectly across three teams, covering 24/7 with 25 percent fewer people than the four-team 12-hour rotations. The saving in heads is paid for in hours: each team carries a third of the clock instead of a quarter.
- What is the difference between DDNNOO and 2-2-4?
- One team and one number. The 2-2-4 (DDNNOOOO) adds a fourth team and stretches the break to four days, which drops the average from 56 hours to 42 and brings the pattern inside normal working-time limits. If the operation can afford the fourth team, the 2-2-4 is almost always the better long-term choice; DDNNOO is what you run when it cannot.
Your next schedule could take 2 minutes.
Import your team, set your rules, hit auto-fill. Most teams are live the same day.
30 days free ยท No credit card required
Already have an account?Sign in
