The sample pay period.

Two weeks of time entries, with five earlier pay periods of history so the repeated rules have something to remember.

Hours over

555.6h

≈ $7,223 estimated potential over-payment

Hours that need an answer

52.7h

20 flags where only the student knows the right time, so no dollar figure yet

Timesheets to review

210

on the supervisors’ lists

Small one-offs

221

53.2 h over: counted in the findings report, but not put in front of a supervisor

Hours under

88.8 h

on 53 entries where the recorded time is shorter than expected: counted the same way, never listed

Dollars at $13 an hour, the department default wage.

Every check the engine runs, and what it found in the sample. Each check’s name links to its rule.

Reading the table

• Each check counts its own minutes, so the rows add up to more than the totals above, where a minute that two checks describe is counted once.
• Two of the repeated rules, “Repeated forgotten clock-outs or missed punches” and “Repeated meal deductions removed”, mark flags already counted in the rows of the checks they repeat.
• “Counted” includes small one-offs that are not shown.
• The weekly cap’s hours are a policy figure, so its row has no hours over and no dollars.

For each of the 263 flags on the lists, here is what it took to find it.

The timekeeping system’s side

161

Something the university runs would have listed it: one of its own reports alone, or a sort of the base report.

HourFlag’s side

102

Nothing the university runs would have listed it: everything it needed was the schedule file, the opening hours, two reports read together or memory of earlier pay periods.

What the 102 on HourFlag’s side needed (a flag can need two):

• 21 the department’s opening hours
• 71 the schedule file
• 51 memory of earlier pay periods

The free check prints the same split for your own pay periods.

By source

Counting a flag once for each source it needed:

• 81One of the university’s own reports alone
• 122The time entries report alone (a sort, filter or sum of the base report)
• 21The department’s opening hours (a setting)
• 71The schedule file
• 0Two reports merged (a row from one matched to a row from another)
• 71Memory of earlier pay periods (shown because it repeats)20 of them a report alone would also have listed, so 51 in the split above.
• 30Forgotten clock-outs found in the base report with no row in the automatic clock-out report

One file per report, as the free check reads them. Column names are HourFlag’s assumption until a real export arrives.

The review file, with what HourFlag remembers from the five earlier pay periods, travels with the free check.

• time-entries.csvTime entries. Every entry: the base file.CSV
• automatic-clock-outs.csvAutomatic clock-outs. Entries the system closed on its own after 24 hours.CSV
• missed-punches.csvMissed punches. Every time typed in by hand.CSV
• auto-approved-missed-punches.csvAuto-approved missed punches. Typed times nobody reviewed.CSV
• corrections.csvCorrections. Every edit, with who made it.CSV
• approvers.csvApprovers. Who approves which work area.CSV
• schedule.csvThe schedule. From the scheduling tool.CSV
• timesheet-notes.csvTimesheet notes. Students’ own explanations.CSV

1. A seeded generator (seed 20260920) writes the pay period and the five before it.
2. The HourFlag engine runs every rule on them.
3. The site’s build regenerates the numbers from the engine, and refuses to finish if anyone has edited one by hand.

So if a rule changes, every number here changes with it. Read the rules the engine runs.