Research question and scope
This protocol asks whether rest-day premium decisions can be reconstructed from the roster, the time record, and the approval note. The unit is one rest-day case that required a decision during the observation window. The study measures evidence completeness and decision traceability. It does not determine whether a particular premium was legally owed, which depends on the applicable rule and the facts of the case.
Set the scope to one site or one client and record the scheduling rule, the payroll code set. The approval authority in force at the start. If the policy changes during the window, keep the earlier definition for the full sample or analyze the change separately. A case that was resolved informally and never recorded is still relevant and should be counted as a traceability gap.
Population and unit of analysis
Define the population as all rest-day cases identified by the scheduling or payroll system during the window, including cases that were denied, approved, or corrected after payment. The unit is the case, identified by the worker, the shift date. The premium code. A case that is reopened after a payroll correction remains one unit with a revision history.
Record the shift type, the notice given, whether the work was voluntary or assigned. Whether the case involved a swap or an emergency. These strata matter because a voluntary swap and an unplanned emergency can follow different approval paths. Test the unit definition on one ordinary and one disputed case before collection begins.
Definitions that make the measure reproducible
Define a traceable decision as one where a reviewer can identify the rule considered, the facts relied on, the decision owner, and the effective date without contacting the worker or supervisor. Define a complete evidence packet as one containing the approved roster, the time record, the relevant policy version. The decision note. A payroll code alone is not a decision note.
Separate the existence of a decision from the correctness of that decision. The protocol can show that a note names an owner and a rule; it cannot show that the owner applied the rule fairly or that the rule itself is lawful. Use explicit codes for missing evidence, conflicting evidence. Evidence that exists but is unreadable.
Evidence standard and data dictionary
For each case, capture the roster entry, the time record, the policy version, the decision note, the approver, and the payroll disposition. Record the source link and the date observed. Code the decision note as complete, partial, or absent, and record whether it explains the facts rather than only the outcome. Keep restricted worker information out of the analysis file.
Add a field for the time between the shift and the decision, and another for whether the case was corrected after payroll. These fields show whether the process is proactive or repair-driven. If the decision note references a conversation, record that the evidence is fragile and note the retention limit. A second reviewer should reach the same classification from the same packet.
Sampling and collection
Draw the sample from the payroll and scheduling exports rather than from a list of disputed cases. Record the export date, filters, and selection rule. Include approved, denied, and corrected cases, because a denied case can reveal whether the reason was documented. If the site has few cases, review all of them and report counts instead of rates.
Collect the packet as it existed at the decision point and preserve later corrections as revisions. Do not fill a missing policy version with the current policy. The rule may have changed. If a supervisor gave approval verbally and the note was written later, record the delay and treat the note as reconstructed evidence rather than contemporaneous proof.
Analysis and reporting
Report the number of cases by outcome, the share with a complete decision note, and the share that required a post-payroll correction. Separate voluntary, assigned, and emergency cases, and show the time from shift to decision. If the sample supports it, report the distribution rather than only an average. A few late cases can carry most of the risk.
Inspect the cases with missing or conflicting evidence and describe the specific gap. Avoid presenting a high approval rate as evidence of good practice; it may simply mean that difficult cases were not recorded. Compare cases within the same rule set and note any change in policy during the window. The report should make the next review easier, not assign blame.
Limitations and sources of error
The record cannot show whether the worker felt able to decline the shift or whether the supervisor applied pressure. It also cannot resolve legal questions about rest periods, premiums, or working time. Those questions require the applicable rule, the contract, and advice from a qualified professional. The protocol is an evidence audit, not a legal compliance determination.
Payroll exports may use codes that combine several situations, and policy versions may be hard to retrieve. A complete note can still describe a decision that was wrong. An incomplete note can accompany a fair one. If the reviewer has a stake in the outcome, use a second coder and record disagreements rather than forcing consensus.
Review cadence and next action
Ask the payroll and workforce owners to choose one change: require a policy version in the decision note, add a pre-cutoff review for emergency cases, or create a separate code for voluntary swaps. Record the owner and the effective date. If the finding involves a possible legal violation, route it to the appropriate adviser rather than handling it as a template update. The owner should confirm in writing that the change is operational before the next review begins.
Repeat the protocol after the change and compare the same fields. If traceability improves but corrections do not fall, inspect whether the decision is being made too late. Close the review when the owner accepts the finding and the next check is scheduled. The goal is a record that explains the decision without exposing unnecessary worker information.
Sources
- [U.S. Department of Labor, Wage and Hour Division](https://www.dol.gov/agencies/whd) — primary guidance on hours, overtime, and recordkeeping.
- [Occupational Safety and Health Administration, recordkeeping](https://www.osha.gov/recordkeeping) — incident and exposure record requirements.
- [U.S. Small Business Administration, manage your business](https://www.sba.gov/business-guide/manage-your-business) — operating and workforce planning guidance.
- [NIST Cybersecurity Framework 2.0](https://www.nist.gov/cyberframework) — governance, access, and recovery language used in the access checks.
What the result can change
The result can change the decision note, the policy-version field, or the timing of the pre-cutoff review. It cannot decide whether a rest-day premium was legally owed or whether a supervisor applied the rule fairly. Those questions need the applicable rule, the contract. Advice from a qualified professional.
If notes are missing the rule version, add that field before adding more narrative. If corrections cluster around emergency cases, create a separate path for those cases rather than loosening the standard for every rest-day decision. The recommendation should be narrow enough to test in the next cycle.
A worked reporting example
Suppose eight rest-day cases are reviewed and five have a complete decision note. Two of the remaining three were approved verbally and written up after payroll. Report those counts with the case types and the time from shift to decision, then describe the specific evidence gap without naming the worker.
The example does not establish compliance or noncompliance. It shows how to separate a documentation gap from a legal conclusion. The next step should be a specific change to the note or the approval window, with an owner, an effective date. A follow-up sample.
Reporting the limitation beside the result
State that the review describes the evidence in the selected cases and does not determine legal compliance. Explain whether the policy version was available, whether the decision note was written at the time. Whether any case was excluded. A reader should be able to see the difference between a missing note and a wrong decision.
If the sample is small, report counts by case type and describe the specific gaps. Do not publish a compliance rate that the data cannot support. The owner can still act on a clear pattern, such as missing policy versions. Schedule a larger review if the risk warrants it.
What the result cannot settle
The protocol cannot decide whether a premium was owed, whether a worker freely accepted the shift, or whether the schedule complied with every applicable rule. Those questions depend on the contract, the jurisdiction, and facts outside the record. The audit can show only whether the decision is traceable and whether the evidence is complete.
That boundary should appear in the report and in any conversation with the owner. A traceable decision can still be wrong, and an untraceable one can still be right. The purpose of the review is to improve the evidence trail and route legal questions to the right adviser, not to substitute an operating protocol for legal analysis.
