The Schedule Audit report is complex; we put together this article to explain the columns, logic (business rules) and parameters used.
Role
Role is the security role assigned to the employee’s user account; it is not derived from schedule entries or work position.
Days Sch
The count of distinct calendar dates in the report period where the employee has at least one scheduled shift at the selected store(s), excluding days marked "OFF" on the schedule.
Notes:
- Multiple scheduled shifts on the same date count as 1 scheduled day.
Days Wkd
The count of distinct scheduled calendar dates in the report period where the employee had at least one Clock-In segment on that date, and was scheduled that day, subject to Count Work Across Stores (see below).
- If Count Work Across Stores is True (if enabled):
“Worked” = any Clock-In on that date at any store. - If Count Work Across Stores is False:
“Worked” = any Clock-In on that date at one of the selected store(s).
Important: The report displays worked days only for dates that exist as scheduled dates (because the report is schedule-driven). This means:
- It counts “scheduled dates that had at least one Clock-In” (the Clock-In can be at any store if Count Work Across Stores = True). It does not include days with at least one Clock-In where the employee was NOT scheduled.
The system may have punches on unscheduled days, but those dates don’t appear in this schedule-driven report.
Days late
The count of scheduled dates where the employee was scheduled (non-OFF) and was late by tolerance (Number of minutes considered late) for at least one scheduled shift that day.
Late by tolerance for a shift means:
- Find the First Clock-In matched to that scheduled shift (see “Matching rule” below)
- If First Clock-In > Scheduled Start + Number of minutes considered late, then that shift is late by tolerance
- If any shift is late by tolerance on that date → the day is late
% Late
Number of Late Days/Number of Days Scheduled
Missed Days
Scheduled dates (non-OFF) where the employee had no Clock-In at all on that calendar date (based on Count Work Across Stores rule).
Formula: Number of Days Scheduled - Number of Days Worked (computed per scheduled date)
% Missed
Number of Missed Days/Number of Days Scheduled
Total Minutes Late
The sum, over all scheduled shifts in the report period, of lateness minutes (positive only) based on the matched First Clock-In:
Important: This is independent of Number of minutes considered late.
If someone is 3 minutes late and Number of minutes late is 5, those 3 minutes still count toward Total Minutes Late.
Avg Minutes Late
Total Minutes Late / Number of Late Days
It’s the average lateness minutes per late day, not per late shift.
Late/Miss %
(Number of Late Days + Number of Missed Days) / Number of Days Scheduled
Gain/Loss Start (not shown)
Sum over scheduled shifts of:
- The difference in minutes between the Scheduled Start time and the First Clock-In time
- early Clock-In ⇒ positive (gain)
- late Clock-In ⇒ negative (loss)
If no matched Clock-In exists for the shift, contributes 0.
Gain/Loss End (not shown)
Sum over scheduled shifts of:
- The difference in minutes between the Scheduled End time and the Last Clock-Out time
- early Clock-Out ⇒ negative (loss)
- late Clock-Out ⇒ positive (gain)
Where the Last Clock-Out is the maximum Clock-Out across all punch segments matched to the shift window.
If no matched Clock-Out exists, contributes 0.
Gain/Loss
Gain/Loss Start + Gain/Loss End
This produces:
- Negative net = overall loss against schedule
- Positive net = overall gain against schedule
Count Edited Time
Total number of punch segments that are marked edited (Clock-In or Clock-Out edited) that fall inside the matching windows for scheduled shifts.
- If an employee has 3 edited segments on one shift day and 2 on another shift day within the report period, Count Edited Time = 5.
Number of Minutes Considered Late (parameter, default = 5)
This provides a tolerance for employees clocking in late (after their scheduled time). See above where this is used in calculations.
Early Grace Minutes (parameter, default = 120)
In order to match schedules with Clock-Ins, the report creates a "window" of time that begins with the Scheduled Start time minus Early Grace Minutes (for each scheduled shift). This allows the report to detect early Clock-Ins up to the Early Grace Minutes before the Scheduled Start time.
After Shift Minutes (parameter, default = 240)
This is similar to Early Grace Minutes but is applied to the shift's Scheduled End time. This allows the report to detect late Clock-Outs up to the After Shift Minutes beyond the shift's Scheduled End time OR the next scheduled start time on that day. That is the "window" ends at the next scheduled start time (same day) if another scheduled shift exists; otherwise, it is the scheduled end time plus After Shift Minutes.
Shift Matching Window (logic)
For each scheduled shift:
- Window Start = Scheduled Start - Early Grace Minutes (for that shift)
- Window End =
- Next Scheduled Start time (same day) if there is another scheduled shift that day, otherwise
- Scheduled End time + After Shift Minutes (for that shift)
This prevents overlap between two scheduled shifts on the same day.
Which punch segments are included?
A punch segment is included in the shift match if:
- Punch Clock-In date equals scheduled date, AND
- Clock-In >= Window Start, AND
- Clock-In < Window End
Matched punch time for calculations
Within the included punch segments:
- First Clock-In = minimum Clock-In among punch segments that fall inside the shift's matching window.
- Last Clock-Out = maximum Clock-Out among punch segments that fall inside the shift's matching window.
This correctly handles lunch breaks / job switching (multiple segments) because:
- First Clock-In reflects the day’s arrival for that shift window
- Last Clock-Out reflects final departure for that shift window
Count Work Across Stores (parameter, default false)
Some entities prefer a “worked day” to mean worked at the selected store(s), not anywhere. If you want to calculate a worked day no matter which store the employee worked at (e.g. not count a day as missed if they worked at a store outside the selected store(s), set this to True. Normally the rules filter punches to the selected store(s). If this is set to True, the rules remain identical except punches are NOT filtered by store at all.
False = punches are limited to the selected store(s)
True = punches are allowed from any store (a cross-store punch can prevent a "missed" day).
Examples
Example 1 — “Days late” uses tolerance, but “Total Minutes Late” does not
Parameters: Number of Minutes Considered Late = 5
Scenario: One scheduled shift in a day.
- Scheduled shift: 8:00 AM – 4:00 PM
- Clock-In: 8:03 AM (3 minutes late)
Report impact:
- Days Sch: 1 (scheduled that day)
- Days Wkd: 1 (at least one Clock-In on that scheduled date)
- Days late: 0 (3 minutes late is within the 5-minute tolerance)
- % Late: 0 / 1 = 0%
- Total Minutes Late: 3 (late minutes still count even if within tolerance)
- Avg Minutes Late: 0 (because Days late = 0)
- Late/Miss %: (0 + 0) / 1 = 0%
Key takeaway: A person can have 0 Days late and still show Total Minutes Late > 0.
Example 2 — Two shifts in one day; late once → the day counts as late
Parameters: Number of Minutes Considered Late = 5
- Scheduled shift 1: 8:00 AM – 12:00 PM
- Scheduled shift 2: 1:00 PM – 5:00 PM
- Clock-Ins: 8:02 AM and 1:09 PM
Report impact (for that date):
- Days Sch: 1 (still just one scheduled day, even with two shifts)
- Days Wkd: 1 (clock-in exists on that scheduled date)
- Days late: 1 (because at least one shift is late by tolerance: 1:09 > 1:05)
- % Late: 1 / 1 = 100%
- Total Minutes Late: (2 + 9) = 11
- Avg Minutes Late: 11 / 1 = 11
- Late/Miss %: (1 + 0) / 1 = 100%
Key takeaway: Days late is day-based: if any shift that day is late by tolerance, the day is late.
Example 3 — Lunch break (multiple punch segments) and why Gain/Loss is based on First/Last within the window
This example shows why the report uses:
- First Clock-In (minimum Clock-In in the shift matching window)
- Last Clock-Out (maximum Clock-Out in the shift matching window)
Parameters: Early Grace Minutes = 120, After Shift Minutes = 240
- Scheduled shift: 8:00 AM – 5:00 PM
- Punch segments (break/job switch):
- 7:55 AM → 12:00 PM
- 12:30 PM → 5:10 PM
Report impact for that shift:
- Gain/Loss Start: clocked in early by 5 ⇒ +5
- Gain/Loss End: clocked out late by 10 ⇒ +10
- Gain/Loss: 5 + 10 = 15 (gain)
Key takeaway: With breaks, using only the first punch row’s clock-out would be wrong; the report uses the last clock-out in the window, which makes Gain/Loss accurate.
Example 4 — Gain/Loss sign rules (easy to remember)
Scheduled shift: 9:00 AM – 6:00 PM
Scenario A: late in + early out = loss
- Clock-In: 9:12 AM
- Clock-Out: 5:50 PM
Report impact:
- Gain/Loss Start: clocked in late by 12 ⇒ -12
- Gain/Loss End: clocked out early by 10 ⇒ -10
- Gain/Loss: -22 (net loss)
Scenario B: early in + late out = gain
- Clock-In: 8:50 AM
- Clock-Out: 6:08 PM
Report impact:
- Gain/Loss Start: clocked in early by 10 ⇒ +10
- Gain/Loss End: clocked out late by 8 ⇒ +8
- Gain/Loss: +18 (net gain)
Key takeaway:
- Clock In Early = positive (gain)
- Clock Out Late = negative (loss)
Example 5 — Missed Days is tied to Days Wkd and Count Work Across Stores
Scheduled day: Employee is scheduled at a selected store on 3/10.
Scenario A — Count Work Across Stores = False (default)
Employee clocks in on 3/10, but at a store not included in the report’s store selection.
Report impact:
- Days Sch: includes 3/10
- Days Wkd: does not count 3/10 as worked (clock-in not at selected store(s))
- Missed Days: counts 3/10 as missed
Scenario B — Count Work Across Stores = True (enabled)
Same situation, but now any-store punches qualify.
Report impact:
- Days Sch: includes 3/10
- Days Wkd: counts 3/10 as worked (cross-store clock-in allowed)
- Missed Days: does not count 3/10 as missed
Key takeaway: Enabling Count Work Across Stores can prevent a scheduled day being marked missed when the employee worked at a different store.
Example 6 — Count Edited Time counts edited segments, not just “edited day”
One scheduled day has three punch segments inside the matching windows:
- 8:00 → 10:00 (edited)
- 10:15 → 12:00 (not edited)
- 12:30 → 5:00 (edited)
Report impact:
- Count Edited Time: 2 (two edited punch segments)
If a second day has 1 edited segment, then for the report period:
- Count Edited Time = 3
Key takeaway: Count Edited Time is useful for spotting employees/timecards with frequent manual adjustments.
Comments
0 comments
Please sign in to leave a comment.