Research note
What share of overtime requests carry approval before the work starts?
A local method for measuring how often overtime requests are approved before the extra hours begin, with separate checks for the approval time and the time entry.
Published

Table of contents
Question and scope
The question covers extra hours worked by employees who are eligible for overtime and who submitted a request. It includes requests sent by message, form, or scheduling tool. It excludes hours worked without any request and cases handled by an external payroll provider. The review covers one employer, one window, and the teams that use overtime.
A case enters the sample when the time entry shows hours beyond the regular schedule and a request exists for the same date. If the request was created after the pay period, the case enters as a late record. Record the source of the schedule and the approval, such as the time system or the request tool. A request invented during the review should be marked as reconstructed.
The stop point is the first extra hour recorded in the time system. The approval must be dated and timed before that point to count. An approval on the same day but after the work does not meet the standard. Report same-day approvals separately so the result does not hide the sequence.
Definitions and evidence standard
Define on-time approval before reviewing any case. The approval must come from a named person with the authority to grant it and must state the hours approved. A general message that says use your judgment is not an approval. Record the definition with the case so a later reader applies the same rule.
Use the request record, the approval message, and the time entry as the primary evidence. A calendar note can add context but cannot replace a dated approval. If only a verbal yes is remembered, mark the case as unverified. Report the share of unverified cases with the result.
Separate the approval from the payment. An approved request can still be paid at the wrong rate, and a late approval can still be paid correctly. Measure the approval timing and the time entry match as two different checks. The two numbers answer different questions about the control.
Sampling and measurement
Freeze the list of overtime requests before reviewing any of them. Include more than one manager, more than one shift, and more than one request channel. Record the export date and the filter used. Do not remove a case because the approval is missing, since the gaps are part of the finding.
If the list is large, take a random sample and record the selection method. Keep the full count beside the sample so a reader can see the coverage. A replaced case should be reported as a deviation. The sample should be large enough to compare at least two teams.
Measure the number of requests, the share approved before the first extra hour, the share approved later the same day, and the share with no approval. Add the median gap between the approval and the work. Report the counts by manager and shift. A single percentage hides which team drives the gap.
Findings and interpretation
Present the distribution before suggesting a cause. A cluster of late approvals under one manager may mean the request reaches the wrong inbox. A cluster on one shift may mean the schedule changes after the approval. Read the cases behind the largest cluster before naming a reason.
Compare the result with the request channel. A form may produce a timestamped approval that a chat message does not. Record the channel and the first person who saw the request. The comparison can show whether the problem is the tool or the habit.
Check whether the late approvals were for genuine emergencies and whether the hours were still recorded accurately. A late approval for a real outage is different from a routine request that was never sent. Record the reason where the file supports one. The quality of the exception matters alongside its timing.
Limitations
The review measures the approval sequence, not whether the extra work was necessary or fairly assigned. A well-approved request can still reflect a planning failure. The result describes the control, not the workload. Report it beside the staffing pattern so a reader does not overread the number.
The approval rule may change during the window, and an older case may follow a rule that was appropriate at the time. Record the policy version rather than applying the current rule retroactively. A case that missed an old standard may not be a current defect. Keep the version note with the case file.
Hours worked without any request are invisible to this method. The count may understate the problem if some extra time is never submitted. Pair the review with a comparison of scheduled and recorded hours. The answer can reveal a gap the request record cannot show.
Practical next step
Use one request form with fields for the task, the estimated hours, the stop time, and the approver. Send the form before the extra work starts. A single form makes the sequence measurable. Keep the form to one screen so it is used in the moment.
Record the approval time in the same system as the request and link it to the time entry. A shared reference lets a reviewer follow the case without searching three tools. Tell the employee the approved stop time. The link should take minutes to create.
Test the process for one pay period and compare the share of on-time approvals with the baseline. Keep the change if it improves the sequence without blocking urgent work. If the form or the approver causes delays, fix that step. The goal is a clear answer before the work begins, not more control.
Sources
References supplied with this research note.
| Source | Publisher | Context |
|---|---|---|
| U.S. Department of Labor, Overtime | dol.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, Fair Labor Standards Act | dol.gov | Primary reference supplied with this article. |
| U.S. Department of Labor, FLSA Recordkeeping Fact Sheet | dol.gov | Primary reference supplied with this article. |