1
Problem Twenty-eight days to complete one full rotation
Each crew moves through the entire DuPont sequence over four weeks. Printing only one week hides who is entering a four-day work string or a seven-day rest.
DuPont schedule
DuPont shift schedule — a four-week 12-hour cycle built for industrial 24/7
The DuPont pattern strings together long work runs and longer rest blocks across a 28-day rotation—four crews, twelve-hour shifts, coverage that never stops. ShiftBox lets you generate this schedule honestly—build the cycle, publish it to crews, and track uneven weeks without pretending a static file will survive the month.
- Full four-week DuPont cycle in one calendar
- Four-crew offset and rest blocks visible
- Day and night 12-hour lanes together
- Swaps without rebuilding the 28-day grid
How DuPont works
The four-week rhythm behind the DuPont name
Twelve-hour shifts, staggered crews, and rest blocks long enough to matter—short enough that planning mistakes hurt immediately
2
Problem Long work runs, then deliberate rest
Typical DuPont patterns cluster three or four consecutive 12-hour shifts before shorter off periods, with a longer break before the cycle restarts. Fatigue policy and coverage math both depend on honoring those blocks.
3
Problem Four crews offset across the month
Continuous operations require staggered entry points. If offsets slip during manual edits, double coverage or dangerous gaps appear at plant or post handoffs.
4
Problem Day and night strings alternate by design
Many DuPont implementations rotate crews through day blocks and night blocks across the 28-day window. Premium rules and handover quality both suffer when day and night live in separate files.
5
Problem Uneven payroll weeks are built in
A week with four 12-hour shifts totals 48 hours; a week inside the long rest block may show zero scheduled hours. Templates that assume uniformity mislead planners and finance alike.
6
Problem Industrial 24/7 leaves no buffer for roster drift
Chemical plants, utilities, and security operations cannot tolerate a silent gap. When the master schedule drifts from reality, overtime and risk rise together.
DuPont setup
How teams generate a DuPont schedule in ShiftBox
Encode the four-week cycle once, align four crews, then operate swaps and leave on the live calendar
Most teams adopting DuPont already know their crew identifiers and which anchor date each crew uses to enter the 28-day pattern. ShiftBox turns that into a published industrial roster instead of a workbook that fractures after the first unplanned absence.
28 days
standard full DuPont cycle
4 crews
typical continuous coverage model
1
Add crews, 12-hour shift types, and roles for your operation.
2
Define the DuPont work-and-rest sequence for the anchor crew.
3
Offset remaining crews so the plant or site stays covered 24/7.
4
Publish the generated four-week calendar to staff.
5
Manage swaps, training days, and leave without redrawing the cycle.
Before and with ShiftBox
What changes when the DuPont cycle, exceptions, and hours live together
Building the 28-day grid is hard; keeping four crew offsets accurate through a month of swaps is where manual tools collapse
Spreadsheets and binders
Why a manual DuPont grid drifts apart
The four-week template is correct on launch day. Then call-outs, overtime fill-ins, and crew-offset mistakes accumulate—and nobody trusts which version reflects tonight's night block.
- Twenty-eight-day visibility truncated to one-week printouts.
- Crew stagger maintained manually after each swap.
- Long rest blocks confused with accidental time off.
- Night premiums tracked outside the master rotation.
- Overtime on 48-hour weeks discovered late.
- Supervisors reconcile three sources before every handoff.
With ShiftBox
What a controlled DuPont process looks like
The four-week pattern is generated once, four crews stay aligned in one calendar, and exceptions update the picture operations and payroll share.
- Full 28-day rotation visible to planners.
- Each crew reads their lane from one published source.
- Swaps and leave recorded without breaking offset logic.
- Day and night 12-hour blocks in a single roster.
- Hour totals follow the latest assignments through uneven weeks.
- Staff see upcoming work strings and rest blocks on mobile.
Industrial reality
Where DuPont fits—and where planning must be ruthless
The pattern rewards teams that treat the four-week cycle as an operating system, not a one-time drawing exercise
1
Solution Chemical and process plants
Continuous units need predictable crew strings and real rest between intense blocks. DuPont is a cultural default in many industrial environments for that reason.
2
Solution Security and guarded facilities
Twelve-hour posts with long rest periods help reduce chronic fatigue—if the rotation stays accurate through swaps and extra shifts.
3
Solution Utilities and infrastructure
Grid, water, and telecom operations run DuPont-style rotations when coverage cannot stop and headcount is fixed at four crews.
4
Solution Long rest blocks need protection
When a crew enters a seven-day rest sequence, unplanned call-ins can destroy the fatigue benefit. Visibility helps supervisors say no with data—or backfill deliberately.
5
Solution Training and audit days inside the cycle
Safety training and certification refreshers must sit in the calendar, not as sticky notes that collide with a four-day work string.
6
Solution Month-end hours follow the cycle—not the calendar month
Payroll periods and DuPont cycles rarely align cleanly. Hour trails tied to assignments reduce reconciliation pain when the month splits a work string.
What DuPont teams notice
Capabilities that matter on a live four-week roster
Concrete control points for industrial schedulers—not generic HR feature lists
Generated four-week DuPont cycle
Encode the work runs, short off periods, and long rest block once. Offset four crews across the 28-day window and publish continuous 12-hour coverage without rebuilding the grid every month.
Uneven weeks and hour roll-ups
See when a crew member is in a 36- or 48-hour week versus a rest-heavy week. Compare planned 12-hour blocks to worked time before overtime and premiums harden.
A roster industrial crews can trust
After publish, operators and guards open the latest four-week view—upcoming day strings, night strings, and approved swaps included—without a new attachment after every edit.
Interface
How DuPont scheduling looks inside ShiftBox
Calendar, crews, 12-hour blocks, four-week visibility, and hour reports share one workflow—no multi-tab Excel models, email chains, and manual offset fixes.
01Planning
A schedule grid without visual noise
Build shifts in a clear matrix calendar, assign people with drag-and-drop, and immediately see coverage gaps.
drag-and-drop shiftsfilters by role and siteconflict checks
02Time control
Timesheets you can trust
Actual hours, lateness, and overtime live in one place so managers are not reconciling spreadsheets at month-end.
ready timesheet viewslateness & overtimepayroll-ready summaries
03Team
A lightweight employee workspace
Staff open a browser link, see their shifts, mark unavailability, and request swaps without a heavy onboarding flow.
no extra apps requiredunavailability marksshift swaps
04Communication
Updates without chat ping-pong
When shifts change, people see the new plan in their workspace—managers do not re-explain every edit in side threads.
publish in one stepclear what changedfewer manual follow-ups
Who benefits most
One flow for the site manager, scheduler, and payroll lead
On a 28-day industrial rotation, each role needs the same cycle seen from a different angle
site or plant manager
Sees whether four-crew coverage holds across day and night strings and whether any work run chronically ends short before production or security SLAs slip.
- Spots coverage risk before a handoff gap opens.
- Compares crew load across the full rotation.
- Spends less time reconciling verbal shift reports.
28-day
cycle in one view
scheduler or shift captain
Operates from a generated DuPont base: records swaps, training, and emergency fill-ins without manually re-aligning four crew offsets after every change.
- Publishes updates once to all four crews.
- Protects long rest blocks with visible backfill rules.
- Keeps day and night lanes synchronized.
1 process
for pattern and exceptions
payroll and labor compliance
Gets assignment-linked hours through uneven weeks—especially when 48-hour work strings, night premiums, and call-out coverage intersect.
- Hours follow the latest published roster.
- Rest blocks and work strings stay distinguishable.
- Overtime signals arrive before payout lock.
Less
end-of-period reconstruction
Case: industrial 24/7 site
What transition looks like on a DuPont four-week rotation
What changes after leaving the laminated cycle chart and the "final" spreadsheet
DuPont teams rarely fail while the printed 28-day chart is fresh—they fail when swaps, training holds, and emergency overtime pull crews off their anchor dates. That is when a single live roster starts paying back the setup effort.
"We run DuPont on four crews—three or four 12-hour shifts, then the rest sequence, across a full month. The wall chart was sacred until someone covered a night string for training and Crew D was a day ahead for two weeks. Security handoffs got tense. Now the four-week cycle is generated in ShiftBox, offsets stay honest, and we see who is entering a 48-hour week before we sign another swap."
Before
Each supervisor kept correction notes, the long rest block was easy to misread as vacation, and payroll rebuilt hours from three exports at period end.
After ShiftBox
The DuPont cycle, crew offsets, swaps, and hour totals live in one process that survives a full 28-day rotation.
What changes day to day
The site stops fighting roster drift through parallel files and moves to one current picture of four crews, twelve-hour blocks, and industrial coverage.
1 system
for the full 28-day cycle
4 crews
aligned in one calendar
earlier
overtime visibility on heavy strings
Why industrial teams use ShiftBox
The DuPont chart on the wall is not a scheduling system
Value appears when the four-week cycle, exceptions, and hours share one workflow through every work string and rest block
The DuPont shift schedule emerged from industrial environments that needed continuous 24/7 coverage with recovery periods long enough to matter. Unlike simple weekly rotations, DuPont stretches across twenty-eight days. Each crew progresses through defined strings of twelve-hour shifts—often three or four consecutive workdays or nights—separated by shorter off periods and, at key points, a longer rest block before the cycle begins again. Four crews enter the pattern on staggered start dates so the operation never goes dark.
That structure trades planning complexity for fatigue management and predictable coverage. A supervisor can look at the full cycle and see who is heading into a demanding four-shift string versus who is entering a multi-day rest. Payroll, however, still faces uneven calendar weeks: one week may contain forty-eight scheduled hours for a person on a long work run, while another week inside the rest block may show little or no scheduled time. Spreadsheet templates that color cells but do not track assignments leave finance guessing which version was actually worked.
ShiftBox treats DuPont as an operating pattern—not a one-time download. You generate the four-week sequence, align crew offsets, publish the roster, and then manage the messy reality: call-outs, security overtime, training holds, and approved swaps. Because the cycle lives in one system, a substitution that pulls someone off a rest block or adds a fifth shift in a week updates the hour picture immediately. Day and night lanes stay together, which matters when premiums, handoffs, and safety briefings differ by block type.
Teams in chemical processing, utilities, manufacturing, and secured facilities often choose DuPont when union agreements or internal fatigue policies favor longer rest between intense runs. The pattern is not lighter to administer than Pitman 2-2-3—it is different. ShiftBox does not oversell magic automation. It gives schedulers an honest workspace to generate the DuPont schedule, keep four crews synchronized, and give payroll a defensible hour trail through the month.
What industrial crews get
A DuPont roster that survives the full four-week cycle—not just week one.
Especially useful where 12-hour strings, long rest blocks, and four-crew 24/7 coverage are fixed constraints—and manual grids keep breaking at offset boundaries.
• Generated 28-day DuPont cycle with crew offsets
• Work strings and long rest blocks visible per person
• Day and night 12-hour lanes in one calendar
• Swaps, training, and leave without redrawing the grid
• Hour trails through uneven payroll weeks
• Browser-based schedule access for field crews
• Less supervisor time lost to offset reconciliation
Generate your DuPont schedule in ShiftBox
Model the four-week 12-hour cycle, align four crews, and keep swaps and uneven weeks visible in one roster.
Ask for a walkthrough if your DuPont variant uses custom rest blocks—we can map your anchor dates together.
ShiftBox for DuPont schedules
ShiftBox helps industrial and 24/7 teams generate and operate the DuPont four-week 12-hour rotation—four crews, continuous coverage, uneven weekly hours, and one workflow instead of a wall chart and a broken spreadsheet.
FAQ — DuPont schedule
DuPont shift schedule and ShiftBox — quick answers
Four-week cycles, 12-hour blocks, and the planning discipline industrial crews need
What is the DuPont shift schedule?
A 28-day rotating pattern—usually four crews on 12-hour shifts—with structured work runs (often three or four consecutive days or nights), short off periods, and a longer rest block before the cycle repeats. Crews enter the pattern on staggered start dates to maintain 24/7 coverage.
How is DuPont different from Pitman 2-2-3?
Both use four crews and 12-hour shifts for continuous coverage. DuPont emphasizes longer work strings and a defined four-week cadence with extended rest at cycle points; Pitman uses the 2-2-3 block rhythm. Teams pick based on fatigue policy, union rules, and operational culture.
Can ShiftBox generate the full DuPont four-week cycle?
Yes: define the work and rest sequence for one crew, offset the other three crews, and publish the repeating 28-day calendar. Exceptions and swaps then layer on the generated base instead of redrawing the grid.
Why do DuPont weeks feel uneven for payroll?
Some calendar weeks include three or four 12-hour shifts (36–48 hours); others include only one or two workdays, and the long rest block may land entirely inside a single week. Rules and premiums depend on seeing actual assignments—not a flat 40-hour assumption.
Is DuPont common outside chemical plants?
Yes. Security, utilities, manufacturing, and other always-on operations adopt DuPont-style rotations when they want longer rest periods between intense work strings—provided they can manage the planning complexity.
Do crews need special access to read a four-week rotation?
No app install is required. Staff use a browser link to the published roster and see their upcoming work runs, rest blocks, and any approved swaps—important when the cycle spans a full month.
Related patterns
Often viewed next to DuPont
Neighboring schedules for continuous twelve-hour operations