Records to Keep

General orientation, not legal advice; retention periods differ by jurisdiction.

Scheduling records are examined in wage claims, ordinance enforcement and inspections. Most of what decides those cannot be produced retrospectively.

What to retain

Published schedules, as published, with the publication timestamp.

Every version, so what changed and when is visible.

Who initiated each change — the distinction the whole premium mechanism rests on.

Predictability pay calculated and paid, per instance.

Good-faith estimates issued, with dates.

Offers of additional hours to existing staff, and the responses.

Availability records with their dates.

For how long

Commonly three years under US fair workweek ordinances.

Payroll retention separately, which is usually longer.

Availability and estimates for the duration of employment plus the statutory period.

Write the numbers down per category, because "as long as necessary" is not a period.

The four that cannot be reconstructed

The publication timestamp. Without it, advance notice is an assertion.

Which version a person actually received.

Who initiated a change, which after a few months nobody remembers and which determines whether a premium was owed.

Whether extra hours were offered internally first, which is a compliance requirement with no trace unless it was recorded at the time.

Each costs nothing to capture as habit and is impossible to assemble later.

What an enforcement investigation looks at

A multi-year lookback across a chain, in the larger cases.

Published schedules against actual worked hours, which is where undocumented changes surface.

Predictability pay owed against paid.

Penalties are typically per employee per violation, which is why a small systematic gap becomes a large number.

The self-audit

Take one site and one month.

Produce: every published version, every change with its initiator, every premium calculated.

Time it.

Whatever you cannot produce is what an investigation would also not find, which means the matter turns on the other side's records rather than yours.

Where the records live

In the scheduling system, ideally, with versioning.

Not in a spreadsheet that gets overwritten, which is the commonest arrangement and destroys the version history by design.

Check whether your product retains versions — several do not, and that is a procurement question rather than a detail.

Check whether versions are retained

A procurement question rather than a detail.

A spreadsheet that gets overwritten destroys the version history by design.

Several scheduling products do the same, showing only the current state.

Which means what was published, and when, cannot be evidenced — and that is the first thing an enforcement investigation asks for.

Connect policy to configuration

The choices in this note can be compared with time tracking for accountants. Enable only the data required for the stated purpose and confirm who can see and change it.

Independent reference

For a thematic point of reference, see the Information Commissioner's Office. Consult the source directly because technical and legal details can change.