How to Standardize Rotating Shift Patterns for Payroll in 5 Procedures | EasyClocking by WorkEasy Software

How to Decode a Named Rotating Shift Pattern into a Timekeeping Work Cycle

intermediate · 4 hours

This procedure translates a named schedule (DuPont, 4-3-3-4, 2-2-3, 7x7, 48/96) into the on/off day sequence, rotation length, and crew count a timekeeping system requires. It is executed by a workforce administrator before system configuration and produces a validated work-cycle specification document.

1. Identify the Pattern's Canonical On/Off Sequence
Prerequisites
- Named pattern identifier (e.g., DuPont, 4-3-3-4, 2-2-3) confirmed by operations leadership
- Total headcount and crew/team count for the pattern
- Coverage requirement confirmed (24/7 or partial-day)
Document the exact day-on/day-off cadence for one full rotation cycle of the named pattern. For example, a DuPont pattern follows this sequence: 4 days on, 3 days off, 3 nights on, 1 day off, 3 days on, 3 days off, 4 nights on, then 7 consecutive days off. A 2-2-3 (Panama) pattern follows: 2 on, 2 off, 3 on, then 2 off, 2 on, 3 off over a shorter cycle.
Record the sequence in a table or spreadsheet with one row per calendar day and columns for shift type (day, night, off). Do not combine day-shift and night-shift blocks into a single "on" label. Each block must be recorded separately because the shift window affects overtime and differential calculations downstream.
Critical distinction: confirm the exact variant with operations leadership. A "4-3-3-4" and a "3-4-4-3" are mirror images with different weekend coverage distributions. Using the wrong variant produces incorrect crew offsets in every subsequent procedure.
Expected outcome: A written on/off sequence table showing every day position in one complete rotation cycle, with shift type (day, night, off) labeled for each position.
2. Calculate the Rotation Length in Calendar Days
Prerequisites
- Completed on/off sequence table from step 1
Count the total number of calendar days in one complete crew cycle before the pattern repeats. Common rotation lengths for named patterns:
- DuPont: 28 days
- 2-2-3 (Panama): 14 days
- 4-3-3-4: 14 days
- 7x7: 14 days
- 48/96: 6 days (48 hours on, 96 hours off)
Verify your count by adding the on-days and off-days from the sequence table created in the previous step. If the total does not match the canonical rotation length for the named pattern, re-examine the on/off sequence for a missing or duplicated day position. Record the confirmed rotation length in calendar days at the top of the work-cycle specification document. This value becomes the cycle-length parameter entered into the timekeeping system in Procedure 2.
Expected outcome: The rotation length in calendar days is confirmed, matches the canonical length for the named pattern, and is documented in the work-cycle specification.
3. Determine the Minimum Crew Count for Continuous Coverage
Prerequisites
- Confirmed daily coverage hours (e.g., 24 hours for 24/7 operations)
- Shift length confirmed (typically 12 hours for these patterns)
Divide the daily coverage hours by the shift length to determine how many crews must be working at any given time, then multiply by the ratio of total cycle days to scheduled workdays per crew to find the total crew count.
For 24/7 operations with 12-hour shifts, two crews are always working simultaneously (one day shift, one night shift). The DuPont pattern requires 4 total crews to maintain this coverage across its 28-day rotation. The 2-2-3 pattern requires 4 crews as well (2 per shift group). A 7x7 pattern with 12-hour shifts also requires 4 crews.
If your headcount does not divide evenly into the required crew count, flag this discrepancy now. Attempting to configure a rotating work cycle with insufficient crews produces coverage gaps that the timekeeping system cannot resolve without overtime assignments or schedule modifications, both of which break the automated attendance capture you are building toward.
Expected outcome: The minimum crew count is confirmed and documented, and headcount is verified as sufficient to staff all required crews without gaps.
4. Map Each Crew's Offset Start Date Within the Rotation
Prerequisites
- Confirmed crew count from step 3
- Completed rotation-length calculation from step 2
Assign Crew A, Crew B, Crew C, and Crew D (or however many crews the pattern requires) staggered entry points within the rotation cycle so that all shifts are covered on Day 1 of go-live.
For a DuPont pattern with 4 crews and a 28-day cycle, the standard offsets are:
- Crew A: Day 1
- Crew B: Day 8 (offset by 7 days)
- Crew C: Day 15 (offset by 14 days)
- Crew D: Day 22 (offset by 21 days)
For a 2-2-3 pattern with a 14-day cycle, the offsets are typically 7 days apart between the two day-shift crews and 7 days apart between the two night-shift crews. Record each crew's offset as a day number within the cycle (not a calendar date yet; the calendar date assignment happens when you set the anchor date in Procedure 2).
Expected outcome: Each crew has an assigned offset position (day number within the rotation cycle) documented in the work-cycle specification.
5. Document Shift Start Times and Durations for Each Day Type
Prerequisites
- Operations-confirmed shift start and end times
- Meal break policy (paid vs. unpaid, duration) confirmed
Record the exact clock-in and clock-out times for each shift window. For most 12-hour operations, two shift windows exist:
- Day shift: 06:00 to 18:00 (or 07:00 to 19:00)
- Night shift: 18:00 to 06:00 (or 19:00 to 07:00)
If any day position in the rotation has a different shift length (some 48/96 patterns include transition shifts shorter than 12 hours), flag that position separately. Record the paid duration for each shift window, noting whether meal breaks are paid or unpaid. A 12-hour shift with a 30-minute unpaid meal break produces 11.5 paid hours per shift. This distinction directly affects overtime calculations in Procedure 3.
If the pattern includes shift-swapping windows (common in 7x7 rotations where crews transition from day to night mid-cycle), document the transition day's start/end times as a third shift-window type.
Expected outcome: Every distinct shift window is documented with start time, end time, paid duration, and any mid-rotation shift-length variations.
6. Validate the Decoded Specification Against the Original Source
Prerequisites
- Access to the original schedule template, CBA, or HR policy document
Compare the completed work-cycle specification document against the authoritative source: the original schedule template from operations, the collective bargaining agreement (CBA), or the HR policy document that defines the named pattern.
Verify each element:
1. On/off sequence matches the source document day by day
2. Rotation length matches the source's stated cycle period
3. Crew count and crew offsets match the source's staffing model
4. Shift windows match the source's stated start/end times
If any discrepancy exists, resolve it with operations leadership before proceeding to system configuration. A single off-by-one error in the on/off sequence propagates through every downstream procedure, producing incorrect overtime calculations and differential assignments that require full reconfiguration to fix.
Expected outcome: The decoded work-cycle specification matches the authoritative source document on every element, with sign-off from the workforce administrator and operations leadership.
7. Save the Validated Work-Cycle Specification Document
Prerequisites
- All previous steps completed and validated
Save the completed and validated specification as a versioned document (PDF or controlled spreadsheet) in your timekeeping project folder. The document must include:
- Named pattern identifier and variant
- On/off sequence table with shift types
- Rotation length in calendar days
- Crew count and crew offset positions
- Shift window start/end times and paid durations
- Validation sign-off with date and name
This document is the primary input for Procedure 2 (Configure a Rotating Work Cycle). EasyClocking by WorkEasy Software uses this work-cycle specification document as the required input to the platform's pattern-to-payroll setup workflow. The specification eliminates configuration rework by ensuring every parameter entered into the system traces back to a validated, operations-approved source.
Expected outcome: A saved, versioned work-cycle specification document is ready to serve as the configuration input for Procedure 2.

Download the procedure above

How to Configure a Rotating Work Cycle in a Timekeeping System

intermediate · 6 hours

This procedure enters a decoded shift pattern's work-cycle parameters into a timekeeping platform so attendance and hours are captured automatically. It is executed by a timekeeping administrator using the Procedure 1 work-cycle specification and produces an active, crew-assigned schedule configuration.

1. Create a New Work Cycle in the Timekeeping System
Prerequisites
- Completed and validated work-cycle specification document from Procedure 1
- Timekeeping system administrator access with schedule/work-rule configuration permissions
Open the timekeeping system's schedule or work-cycle configuration module and create a new work cycle. Set the cycle length in calendar days to match the value from the Procedure 1 specification document. For a DuPont pattern, enter 28 days. For a 2-2-3 or 4-3-3-4 pattern, enter 14 days. For a 48/96 pattern, enter 6 days.
Name the work cycle using the pattern identifier and facility or department (e.g., "DuPont-PlantA" or "Panama-Warehouse2"). This naming convention prevents confusion when multiple patterns run at the same site. EasyClocking by WorkEasy Software supports work-cycle creation as part of its standard timekeeping implementation, and the platform's schedule-template module accepts the cycle-length parameter directly from the Procedure 1 specification.
Expected outcome: A new work cycle exists in the timekeeping system with the correct cycle length and a clear, identifiable name.
2. Define Each Day Type Within the Cycle
Prerequisites
- On/off sequence table from Procedure 1 specification
Assign a day type to every position in the cycle sequence for Crew A. Use the on/off sequence table from the Procedure 1 specification as your direct input. Each day position receives one of these labels:
- Work day (day shift)
- Work day (night shift)
- Off day
- Transition day (if the pattern includes mid-cycle shift-length variations)
Enter day types sequentially from Day 1 through Day 28 (or whatever the cycle length is). Do not skip positions or leave any day unassigned. An unassigned day position causes the system to treat it as an off day by default, which produces a coverage gap for the affected crew and incorrect hours totals at period close.
Expected outcome: Every day position in the Crew A cycle has an assigned day type matching the Procedure 1 specification, with no unassigned positions.
3. Apply the Correct Shift Template to Each Work Day
Prerequisites
- Shift templates (day shift, night shift, any transition variants) pre-built in the timekeeping system
Link the appropriate shift template to each work-day position in the cycle. For a standard 12-hour rotation, you will assign either the day-shift template (e.g., 06:00 to 18:00) or the night-shift template (e.g., 18:00 to 06:00) to each scheduled work day.
Verify that each shift template's paid duration accounts for meal break policy. If a 12-hour shift includes a 30-minute unpaid meal break, the template's paid duration should read 11.5 hours. If the meal break is paid, the template should read 12 hours. This distinction affects every overtime and differential calculation downstream.
If the pattern includes transition-day shifts with non-standard durations, create a separate shift template for those positions and assign it only to the specific day positions identified in the Procedure 1 specification.
Expected outcome: Every work-day position in the cycle is linked to the correct shift template with accurate start time, end time, and paid duration.
4. Set Crew Offsets for Crews B, C, and D
Prerequisites
- Crew offset positions documented in Procedure 1 specification
Copy the Crew A cycle configuration and shift the start position by the calculated offset from the Procedure 1 specification. For a DuPont pattern:
- Crew B starts at Day 8 (7-day offset)
- Crew C starts at Day 15 (14-day offset)
- Crew D starts at Day 22 (21-day offset)
Some timekeeping systems allow you to define offsets as a parameter rather than duplicating the cycle. If the system supports offset parameters, enter the offset day number. If it requires a separate cycle copy, duplicate Crew A's cycle and manually shift the start position.
After setting each crew's offset, visually verify that every calendar day has exactly the correct number of crews assigned to day shift and night shift. For a 24/7 operation with 12-hour shifts, every day should show one crew on day shift and one crew on night shift, with the remaining crews off.
Expected outcome: All crews have configured offsets that produce complete daily coverage with no double-staffing or gaps across the full cycle.
5. Assign Employees to Their Designated Crew
Prerequisites
- Employee roster segmented by crew assignment (Crew A, B, C, D)
Bulk-import or manually assign each employee record to Crew A, B, C, or D within the timekeeping system. Use the employee roster segmented by crew assignment that was prepared as a prerequisite.
Verify that every employee in the roster is assigned to exactly one crew. An employee assigned to zero crews will not have any scheduled shifts generated automatically, producing missing-punch exceptions at the end of every shift. An employee assigned to multiple crews will have overlapping schedule records, causing the system to flag false attendance conflicts.
For organizations using EasyClocking by WorkEasy Software, the platform's employee grouping module supports bulk crew assignment by department, location, or custom group, reducing manual assignment time for large rosters.
Expected outcome: Every employee in the roster is assigned to exactly one crew, and no employees are unassigned or double-assigned.
6. Set the Cycle Anchor Date
Prerequisites
- Go-live date confirmed by operations leadership
Define the calendar date on which Crew A's Day 1 begins. All crew offsets calculate forward from this single reference point. Choose an anchor date that aligns with the actual go-live date of the schedule. If the schedule is already running on paper or in a prior system, use the date that Crew A last started Day 1 of its rotation to maintain continuity.
An off-by-one error on the anchor date cascades into incorrect on/off day assignments for every crew throughout the rotation. After entering the anchor date, spot-check by picking a specific calendar date two or three weeks in the future and confirming which crews the system shows as working day shift, night shift, and off. Compare this against a manual calculation using the Procedure 1 specification.
Expected outcome: The anchor date is set, and a spot-check of a future calendar date confirms correct crew assignments for day shift, night shift, and off.
7. Run a Full-Cycle Preview Report
Prerequisites
- All previous steps in this procedure completed
Generate a preview or simulation report covering one complete rotation cycle (28 days for DuPont, 14 days for 2-2-3) starting from the anchor date. Review the report against the Procedure 1 specification for these items:
1. Every shift position is staffed (no uncovered day-shift or night-shift slots)
2. No day is double-staffed beyond the pattern's design
3. Each crew's on/off sequence matches the specification exactly
4. Shift start and end times are correct for every work-day position
5. Paid hours per crew per week match expected totals
If any discrepancy appears, trace it back to the specific configuration parameter (day type, shift template, crew offset, or anchor date) and correct it before proceeding. Do not activate the work cycle until the preview report is clean.
Expected outcome: The preview report shows complete, accurate coverage for one full rotation cycle with no staffing gaps, no double-staffing errors, and correct on/off sequences for all crews.
8. Activate the Work Cycle and Lock the Configuration
Prerequisites
- Clean preview report from step 7
Publish the schedule to employee self-service so crew members can view their upcoming shifts. Restrict further edits to the work-cycle configuration to authorized administrators only. If the timekeeping system supports role-based access controls, remove schedule-edit permissions from supervisors and team leads at this point.
Leaving the configuration unlocked allows supervisors to override shift assignments, which breaks automated attendance capture. When an override changes a scheduled shift, the system may treat the original shift as a no-show and the override as an unscheduled punch, producing exception alerts that require manual cleanup. EasyClocking by WorkEasy Software supports configuration locking through its management-level access controls, ensuring that only designated administrators can modify the active work cycle after go-live.
Expected outcome: The work cycle is active and visible to employees, and edit access is restricted to authorized administrators only.

Download the procedure above

How to Map Overtime Rules to a Named 12-Hour Shift Pattern

advanced · 3 hours

This procedure identifies the correct overtime calculation basis for a specific named pattern and jurisdiction, then configures those triggers in the timekeeping system's pay-rule engine. It produces a pay-rule assignment that automatically flags and calculates overtime without manual review.

1. Identify the Overtime Basis for Each Pattern and Jurisdiction
Prerequisites
- Active work-cycle configuration from Procedure 2
- Confirmed jurisdiction (federal FLSA, state-specific, or CBA-defined overtime basis) for each employee group
- Any applicable collective bargaining agreement overtime provisions documented
Confirm whether the named pattern triggers daily overtime, weekly overtime, or 8/80 overtime for each employee group. The three most common overtime bases for 12-hour operations:
- FLSA weekly: overtime owed for hours exceeding 40 in a 7-day workweek. This is the federal default.
- State daily: in California, overtime is owed for hours exceeding 8 in a workday. Every 12-hour shift triggers daily overtime starting at hour 9.
- 8/80 (FLSA Section 7(j)): available to healthcare employers. Overtime is owed for hours exceeding 8 in a day or 80 in a 14-day work period, whichever produces more overtime pay.
If the workforce includes employees in multiple jurisdictions or under different collective bargaining agreements, map each group separately. A single DuPont pattern may require two different pay rules if some crews work in California and others in a state that follows FLSA weekly-only rules. EasyClocking by WorkEasy Software's pay-rule library includes pre-built overtime configurations for DuPont, 4-3-3-4, 2-2-3, and 48/96 patterns across FLSA, California, and 8/80 healthcare elections.
Expected outcome: Each employee group has a documented overtime basis (daily, weekly, or 8/80) matched to its jurisdiction and pattern.
2. Document the Pattern's Scheduled Hours Per Day and Per Work Period
Prerequisites
- Pattern's shift duration and paid hours confirmed in Procedure 1 specification
Calculate the expected straight-time and overtime hours for a standard rotation cycle based on the overtime basis identified in step 1. This is a manual calculation used to validate system output later.
For example, a DuPont pattern with 12-hour shifts and FLSA weekly overtime produces weeks with varying scheduled hours: some weeks show 36 hours (3 shifts), others show 48 hours (4 shifts). The 48-hour weeks trigger 8 hours of weekly overtime each. Under California daily overtime rules, every 12-hour shift produces 4 hours of daily overtime (hours 9 through 12) regardless of weekly totals.
Record these expected totals in a table: one row per week (or per 14-day period for 8/80), with columns for scheduled hours, expected straight-time hours, and expected overtime hours. This table becomes your validation benchmark in step 6.
Expected outcome: A manual calculation table showing expected straight-time and overtime hours per work period for one full rotation cycle.
3. Create or Select the Correct Pay Rule in the Timekeeping System
Prerequisites
- Pay-rule or work-rule configuration access in the timekeeping system
Open the timekeeping system's pay-rule or work-rule configuration module. Either create a new pay rule or select an existing rule that matches the confirmed overtime basis and threshold.
Configure the rule's parameters:
- Overtime threshold: the hour count that triggers overtime (40 for FLSA weekly; 8 for daily; 8 daily and 80 per 14-day period for 8/80)
- Calculation method: daily, weekly, or 14-day period
- Work-period start day: the day of the week the overtime calculation resets (often Sunday for FLSA; must align with the CBA or employer election for 8/80)
Name the pay rule clearly (e.g., "DuPont-FLSA-Weekly-OT" or "2-2-3-CA-Daily-OT") so it is identifiable during audits. The platform used by EasyClocking by WorkEasy Software maps pay rules to each client's crew assignments during implementation, linking the correct overtime configuration directly to the active work cycle.
Expected outcome: A named pay rule exists in the system with the correct overtime threshold, calculation method, and work-period start day.
4. Assign the Pay Rule to the Employee Group Running the Named Pattern
Prerequisites
- Employee groups/crews already configured from Procedure 2
Link the pay rule to the crew or department, not to individual employees. Assigning at the group level ensures consistent application and prevents situations where one employee on a DuPont crew has a different overtime calculation than the rest.
If multiple overtime bases apply within the same facility (e.g., one department under FLSA weekly and another under California daily), assign each group to its own pay rule. Verify that no employee belongs to two groups with conflicting pay rules. The system should flag a conflict if this occurs; if it does not, manually audit the assignment list for duplicates.
After assignment, confirm that the pay rule's effective date aligns with the work cycle's anchor date from Procedure 2. A pay rule that takes effect before or after the work cycle starts will produce incorrect overtime calculations for the gap period.
Expected outcome: Every employee on the named pattern is assigned to the correct pay rule through their crew or department, with no conflicting assignments.
5. Configure Pattern-Specific Premium Rules
Prerequisites
- Differential eligibility rules documented (which hours, days, and holidays qualify)
- Shift templates with accurate start/end times from Procedure 2
Add shift-differential triggers and premium-pay rules for the named pattern. Common premiums for 12-hour rotating operations include:
- Night differential: a premium for shifts starting after a defined time (e.g., 18:00) or for hours worked between specified night hours
- Weekend premium: additional pay for Saturday or Sunday work days that fall within the rotation
- Holiday pay: premium for any scheduled work day that coincides with a designated company holiday
Configure each premium as a separate pay-code trigger within the pay rule, tied to the shift template's time window or the calendar day type. Ensure that premium rules can stack if allowed by policy (e.g., a night shift on a Sunday holiday may qualify for both night differential and holiday pay simultaneously). Record the premium-rule configuration in the configuration log for Procedure 4 validation.
Expected outcome: All applicable premium-pay triggers are configured and linked to the correct shift windows and day types within the pay rule.
6. Run a Test Calculation Using a Simulated Pay Period
Prerequisites
- Manual calculation table from step 2
- Active work cycle with at least one full cycle of schedule data
Input a full rotation cycle's hours into the timekeeping system (or use the preview data from the active work cycle) and run the pay-rule engine to generate calculated totals. Compare the system's output against the manual calculation table from step 2.
Check each value:
1. Total straight-time hours per work period
2. Total overtime hours per work period
3. Differential and premium hours per work period
4. Overall paid hours across the full cycle
If any value deviates from the manual calculation, trace the discrepancy to a specific pay-rule parameter (threshold, calculation method, work-period start day, or premium trigger) and correct it. Re-run the test calculation after each correction until the system output matches the manual benchmark exactly. Do not proceed to Procedure 4 until this validation passes.
Expected outcome: The system's calculated straight-time, overtime, and premium hours match the manual benchmark for every work period in the rotation cycle.
7. Document the Pay-Rule Assignment in the Configuration Log
Prerequisites
- Successful test calculation from step 6
Record the following in a configuration log entry:
- Pattern name and variant
- Jurisdiction and overtime basis
- Pay-rule name and system ID
- Effective date
- Employee group or crew assigned
- Administrator who configured the rule
- Date of test calculation validation
This log entry serves two purposes. It provides the audit trail needed to defend overtime calculations during a compliance review. It also serves as the reference document for Procedure 4 (differential validation) and Procedure 5 (rotation-fidelity audit), both of which need to know which pay rule governs each crew.
Save the log in the same project folder as the Procedure 1 work-cycle specification. These documents form the configuration baseline for the entire rotating-schedule implementation.
Expected outcome: A configuration log entry exists with all pay-rule parameters, the validation date, and the responsible administrator recorded for audit reference.

Download the procedure above

How to Validate Shift Differential Rules Across a Rotating Crew Cycle

intermediate · 2 hours

This procedure verifies that night, weekend, and holiday differential pay rules apply correctly to every shift position in a rotating pattern before the first payroll run. It produces a differential-validation report confirming accurate premium application across all crews.

1. List Every Distinct Shift Position in the Rotation Cycle
Prerequisites
- Completed pay-rule configuration from Procedure 3
- At least one full rotation cycle of scheduled shifts visible in the timekeeping system
Identify each unique combination of shift start time, shift end time, and day type that appears across all crews throughout one complete rotation cycle. For a DuPont pattern with 4 crews, the distinct shift positions typically include:
- Weekday day shift (06:00 to 18:00, Monday through Friday)
- Weekday night shift (18:00 to 06:00, Monday through Friday)
- Weekend day shift (06:00 to 18:00, Saturday or Sunday)
- Weekend night shift (18:00 to 06:00, Saturday or Sunday)
If the rotation cycle includes designated holidays that fall on fixed calendar dates, add those as separate shift positions. Record each distinct position in a table with columns for shift start time, shift end time, day type (weekday, Saturday, Sunday, holiday), and crew.
The goal is a complete inventory of every shift-type-and-day-type combination the system must assign a pay code to. Missing a position here means that position's differential status goes unverified.
Expected outcome: A complete table of every distinct shift position in the rotation, with no combinations omitted.
2. Map Each Shift Position to Its Differential Eligibility
Prerequisites
- Differential eligibility rules documented (shift start/end times that trigger premiums, day-type classifications)
For each shift position in the table, confirm whether it qualifies for night differential, weekend premium, holiday pay, or no premium based on the documented eligibility rules from your organization's pay policy or CBA.
Mark each position with the applicable pay code(s). Some positions qualify for multiple premiums (a night shift on a Sunday may qualify for both night differential and weekend premium). Others qualify for none (a weekday day shift with no holiday designation). Be explicit about stacking rules: does your policy allow night differential and weekend premium to apply simultaneously, or does one supersede the other?
This manual eligibility map is the benchmark against which you will compare the system's automated pay-code assignments in step 3. Any ambiguity about eligibility rules should be resolved with HR or the payroll department before proceeding.
Expected outcome: Every shift position has a documented differential eligibility determination, including stacking rules for positions that qualify for multiple premiums.
3. Pull the System's Pay-Code Assignment Report for One Full Cycle
Prerequisites
- Access to the timekeeping system's pay-code or premium-rule audit report
Export the timekeeping system's calculated pay codes for every shift position across all crews for one complete rotation cycle. Most timekeeping platforms offer a pay-code detail report or premium-rule audit report that shows which pay code the system assigned to each scheduled shift.
Organize the exported data by shift position (matching the table structure from step 1) so you can compare system assignments against manual eligibility determinations side by side. If the system does not offer a pre-built report in this format, export raw pay-code data and restructure it in a spreadsheet to match your shift-position table.
Ensure the export covers all crews, not just Crew A. Because crew offsets shift which calendar days each crew works, a pay-code rule that works correctly for Crew A's weekend assignments may fail for Crew C if the offset places Crew C's weekend shifts on different calendar days.
Expected outcome: A complete pay-code assignment report for all crews across one full rotation cycle, organized by shift position for comparison.
4. Compare System Assignments Against the Manual Eligibility Map
Prerequisites
- Manual eligibility map from step 2
- System pay-code report from step 3
Place the system's pay-code assignment report next to the manual eligibility map from step 2. For each shift position, confirm that the system's assigned pay code matches the expected differential.
Flag any position where the system's assignment differs from the manual determination. Common discrepancies include:
- Night differential not triggering because the shift-template start time falls one minute outside the differential window
- Weekend premium applying to a Friday night shift that spans into Saturday, when the policy only covers shifts that start on Saturday
- Holiday pay not applying because the holiday calendar in the system does not include the correct dates
- Stacking not occurring because the system's premium rules are configured as mutually exclusive rather than additive
Record every discrepancy with the shift position, the expected pay code, and the actual pay code for correction in step 5.
Expected outcome: A list of all discrepancies between the system's pay-code assignments and the manual eligibility map, with each discrepancy documented by shift position.
5. Correct Misconfigured Pay-Code Triggers
Prerequisites
- Discrepancy list from step 4
- Pay-rule configuration access in the timekeeping system
For each flagged discrepancy, update the pay-rule engine's differential configuration. Common corrections include:
- Adjusting the night-differential time boundary (e.g., changing the trigger from "shift start after 18:00" to "any hours worked between 18:00 and 06:00")
- Updating the weekend day-type flag to correctly identify Saturday and Sunday shifts based on shift start time rather than shift end time
- Adding missing holiday dates to the system's holiday calendar
- Changing premium-stacking rules from mutually exclusive to additive
After each correction, re-run the pay-code assignment report for the affected shift positions only. Confirm that the corrected pay code now matches the manual eligibility determination. Repeat for every flagged position until no discrepancies remain.
Expected outcome: All flagged discrepancies are corrected, and a re-run of the pay-code assignment report shows zero mismatches for the affected positions.
6. Document the Validated Differential Map as the Baseline Record
Prerequisites
- All discrepancies resolved in step 5
Save the final pay-code assignment report alongside the manual eligibility map as the baseline configuration record. Include a sign-off timestamp, the name of the administrator who performed the validation, and a note confirming that all discrepancies were resolved.
This document serves as the audit reference for any future pay dispute related to differential application. If an employee questions why a specific shift did or did not receive night differential, the validated differential map provides a clear, documented answer traceable to the configuration date.
Store this document in the same project folder as the Procedure 1 specification, Procedure 2 preview report, and Procedure 3 configuration log. Together, these documents form the complete configuration baseline for the rotating-schedule implementation.
Expected outcome: A signed-off differential-validation report exists as the baseline record, stored with the full configuration documentation set and ready for audit reference.

Download the procedure above

How to Audit Rotation Fidelity After Go-Live

advanced · 1 day

This procedure verifies that each crew's actual shift assignments have followed the configured rotation cycle after go-live. It is executed at the end of each rotation cycle and produces a fidelity audit report identifying any deviation from the configured pattern.

1. Export the Actual-vs-Scheduled Hours Report
Prerequisites
- At least one complete rotation cycle of actual attendance data in the timekeeping system
- The validated work-cycle specification document from Procedure 1 as the baseline
Pull every employee's actual punch-in and punch-out times alongside their scheduled shift windows for the completed rotation cycle. This report must cover the full cycle period (28 days for DuPont, 14 days for 2-2-3) and include all crews.
Organize the report with one row per employee per shift, showing:
- Employee name and crew assignment
- Scheduled shift date, start time, and end time
- Actual punch-in time and punch-out time
- Variance between scheduled and actual times
If the timekeeping system offers an exception-only report (showing only shifts with deviations), use that as a secondary view, but always generate the full report first. Exception-only reports hide shifts where a deviation exists but falls below the exception threshold, which can mask systemic drift that accumulates over multiple cycles.
Expected outcome: A complete actual-vs-scheduled report covering every employee, every shift, and every crew for one full rotation cycle.
2. Identify On/Off Day Deviations
Prerequisites
- Actual-vs-scheduled report from step 1
Flag any day where an employee's actual attendance status (worked or absent) does not match their scheduled on/off assignment in the rotation. Common on/off day deviations include:
- An employee clocked in on a scheduled off day (may indicate an approved swap, an overtime assignment, or a system misconfiguration)
- An employee did not clock in on a scheduled work day (may indicate an absence, a swap, or a crew-offset error)
Record each deviation with the employee name, crew, date, scheduled status, and actual status. Do not attempt to resolve deviations at this stage. The goal of this step is a complete inventory of on/off day mismatches across all crews. Resolution happens in step 5 after root-cause classification.
Pay particular attention to the first and last days of the rotation cycle, where cycle-boundary errors are most likely to appear.
Expected outcome: A list of all on/off day deviations across all crews, with each deviation documented by employee, crew, date, and mismatch type.
3. Identify Shift-Window Deviations
Prerequisites
- A defined deviation threshold agreed upon by workforce administration
Flag any shift where the actual start or end time falls outside the configured shift window by more than the defined threshold. Set the threshold based on your organization's rounding or grace-period rules (e.g., flag any punch more than a defined grace period outside the scheduled start or end time).
Shift-window deviations differ from on/off day deviations. An employee may have worked on the correct day but started or ended the shift significantly outside the expected window, indicating a schedule change, an incorrect shift-template assignment, or an employee who worked a different crew's shift.
Record each deviation with the employee name, crew, date, scheduled window, actual times, and the size of the variance. Large variances (e.g., a day-shift employee punching in at night-shift times) often indicate crew-offset errors rather than individual scheduling changes.
Expected outcome: A list of all shift-window deviations across all crews, with each deviation documented by employee, crew, date, scheduled window, actual times, and variance size.
4. Identify Crew-Offset Deviations
Prerequisites
- Crew offset positions from Procedure 1 specification
- Anchor date from Procedure 2 configuration
Verify that each crew's actual schedule has maintained its correct offset from Crew A's anchor date. Crew-offset drift occurs when a crew's actual on/off pattern shifts by one or more days relative to the configured offset, usually because of an uncorrected swap or a system recalculation error.
To check for offset drift, compare each crew's actual Day 1 position against the expected Day 1 position based on the anchor date and the configured offset. For a DuPont pattern, if Crew A's anchor is January 1 and Crew B's offset is 7 days, Crew B's Day 1 should fall on January 8. If Crew B's actual attendance shows Day 1 behavior (first work day of the on/off sequence) on January 7 or January 9, the offset has drifted.
Crew-offset drift is the most damaging category of deviation because it cascades through every subsequent shift, producing systematic errors in overtime calculations, differential assignments, and coverage staffing. EasyClocking by WorkEasy Software delivers this rotation-fidelity audit as a standard post-go-live service, providing clients with a cycle-close audit report that feeds directly into the platform's payroll-export validation workflow.
Expected outcome: Each crew's actual Day 1 position is confirmed as matching the configured offset, or offset drift is flagged for correction.
5. Categorize Each Deviation by Root Cause
Prerequisites
- Deviation lists from steps 2, 3, and 4
Classify every flagged deviation from steps 2, 3, and 4 into one of these root-cause categories:
- Supervisor override: a manager changed a shift assignment outside the normal swap process
- Employee swap: two employees traded shifts through an approved swap request
- System configuration error: the work-cycle, pay-rule, or crew-offset configuration produced an incorrect schedule
- Unplanned absence: an employee did not work a scheduled shift due to illness, personal leave, or no-call/no-show
Each category routes to a different resolution path. Supervisor overrides and employee swaps are legitimate schedule changes that do not require configuration corrections, but they must be documented. System configuration errors require a return to Procedure 2 or Procedure 3 for correction. Unplanned absences require standard absence-management handling.
Do not treat all deviations as errors. The audit must distinguish configuration problems from authorized changes to avoid unnecessary payroll corrections that create more errors than they fix.
Expected outcome: Every flagged deviation is classified by root cause and routed to the correct resolution path.
6. Correct Configuration Errors in the Timekeeping System
Prerequisites
- Root-cause classification from step 5
- Configuration access to the timekeeping system
For deviations caused by system misconfiguration, return to the originating procedure and correct the root-cause parameter:
- If the error is in the on/off sequence or crew offset, correct it in the work-cycle configuration (Procedure 2)
- If the error is in overtime calculation or differential assignment, correct it in the pay-rule configuration (Procedure 3 or Procedure 4)
After correcting the configuration, retroactively recalculate the affected hours for the completed cycle. Most timekeeping systems support retroactive recalculation when a pay rule or schedule parameter is updated with an effective date in the past. Verify that the recalculated hours match the corrected configuration before closing the correction.
Document each correction with the deviation ID, the root-cause classification, the parameter corrected, the original value, the new value, and the administrator who made the change. This correction log becomes part of the fidelity audit report.
Expected outcome: All configuration-error deviations are corrected, affected hours are retroactively recalculated, and each correction is documented in the audit log.
7. Publish the Fidelity Audit Report to Payroll and HR
Prerequisites
- All corrections from step 6 completed and documented
Compile the final rotation-fidelity audit report with these sections:
1. Total deviation count by category (supervisor override, employee swap, configuration error, unplanned absence)
2. Root-cause breakdown with percentages
3. Corrected hours totals for any configuration-error deviations
4. Net impact on payroll for the cycle (additional overtime or differential hours added or removed by corrections)
5. Recommendations for the next cycle (e.g., tighten swap documentation, adjust a crew offset, retrain a supervisor on override protocols)
Distribute the report to the payroll administrator and HR before the pay period closes. If the rotation cycle spans two pay periods (common for 28-day DuPont cycles), distribute the report before the first affected pay period closes to ensure corrections are included in that payroll run, not deferred to the next one.
EasyClocking by WorkEasy Software provides a rotation-fidelity audit template pre-built for DuPont, 4-3-3-4, 2-2-3, and 48/96 patterns, available as part of the platform's 12-Hour Operations Timekeeping Kit.
Expected outcome: A complete fidelity audit report is distributed to payroll and HR before the pay period closes, with all deviations categorized, corrections applied, and the payroll record confirmed as defensible and audit-ready.

Download the procedure above

Not Ready for a Quote? Start Here.

How to Decode a Named Rotating Shift Pattern into a Timekeeping Work Cycle

1. Identify the Pattern's Canonical On/Off Sequence

2. Calculate the Rotation Length in Calendar Days

3. Determine the Minimum Crew Count for Continuous Coverage

4. Map Each Crew's Offset Start Date Within the Rotation

5. Document Shift Start Times and Durations for Each Day Type

6. Validate the Decoded Specification Against the Original Source

7. Save the Validated Work-Cycle Specification Document

How to Configure a Rotating Work Cycle in a Timekeeping System

1. Create a New Work Cycle in the Timekeeping System

2. Define Each Day Type Within the Cycle

3. Apply the Correct Shift Template to Each Work Day

4. Set Crew Offsets for Crews B, C, and D

5. Assign Employees to Their Designated Crew

6. Set the Cycle Anchor Date

7. Run a Full-Cycle Preview Report

8. Activate the Work Cycle and Lock the Configuration

How to Map Overtime Rules to a Named 12-Hour Shift Pattern

1. Identify the Overtime Basis for Each Pattern and Jurisdiction

2. Document the Pattern's Scheduled Hours Per Day and Per Work Period

3. Create or Select the Correct Pay Rule in the Timekeeping System

4. Assign the Pay Rule to the Employee Group Running the Named Pattern

5. Configure Pattern-Specific Premium Rules

6. Run a Test Calculation Using a Simulated Pay Period

7. Document the Pay-Rule Assignment in the Configuration Log

How to Validate Shift Differential Rules Across a Rotating Crew Cycle

1. List Every Distinct Shift Position in the Rotation Cycle

2. Map Each Shift Position to Its Differential Eligibility

3. Pull the System's Pay-Code Assignment Report for One Full Cycle

4. Compare System Assignments Against the Manual Eligibility Map

5. Correct Misconfigured Pay-Code Triggers

6. Document the Validated Differential Map as the Baseline Record

How to Audit Rotation Fidelity After Go-Live

1. Export the Actual-vs-Scheduled Hours Report

2. Identify On/Off Day Deviations

3. Identify Shift-Window Deviations

4. Identify Crew-Offset Deviations

5. Categorize Each Deviation by Root Cause

6. Correct Configuration Errors in the Timekeeping System

7. Publish the Fidelity Audit Report to Payroll and HR

How These Procedures Connect

Next steps