Small-business outsourcing research

How often do payroll timesheets reach approval with a missing manager sign-off?

A protocol for measuring how many weekly timesheets reach the pay run without the manager approval the written policy requires.

How often do payroll timesheets reach approval with a missing manager sign-off?

Research question and scope

This protocol asks how often a weekly timesheet reaches the pay run without the manager sign-off required by the written policy. The unit is one employee-week submitted for payment, not one employee and not one pay period. The study measures the share with a missing approval, the time the approval arrives, and the pay that was released before it arrived. It does not judge whether the manager was right to approve the hours.

Set the scope to one business, one payroll schedule, and one approval rule. Record the timekeeping system, the approval method, and the cutoff time for each weekly run. If the approval rule changes during the window, keep the original rule for the weeks already collected and analyze the later weeks separately. A new reminder system can reduce missing approvals without any change in manager behavior.

Define the population as every employee-week included in the pay run during the window, including weeks with no hours and weeks paid at a fixed salary. Include corrections and off-cycle payments, because those often bypass the normal approval path. State any exclusion, such as an owner who is also the approver, and apply it to every week. Test the unit definition on two completed pay runs before collection begins.

Definitions that make the measure reproducible

Define approval as the recorded action of the named manager in the timekeeping or payroll system, not a verbal okay or an email that says the hours look fine. Define missing as no recorded approval at the moment the pay run is locked. If the approval arrives after the lock but before payment, record it as late rather than missing. The distinction matters because a late approval still leaves the pay run exposed.

Record the time the timesheet was submitted, the time the manager approved it, and the time the pay run was locked. These three timestamps show whether the delay belongs to the employee, the manager, or the payroll schedule. A timesheet submitted after the cutoff cannot be approved before the run, so report it separately. Do not count a system-generated reminder as an approval.

Use the same payroll export for every week and keep the export time beside each record. A queue that changes while the analyst works can make the missing count unreliable. Record any manual override, because an override may release pay without the normal approval. If the business uses a delegated approver, record that person and the delegation date.

Evidence standard and data dictionary

For each employee-week, capture the employee identifier, the week ending date, the scheduled hours, the submitted hours, the approved hours, and the approval timestamp. Add the approver name, the pay code, and the amount paid. Record whether the week included overtime, a correction, or an off-cycle payment. Keep the export and the approval log linked to the same record.

Capture the reason for any missing approval when the reason is documented: manager leave, a new supervisor, a system error, or a late submission. Do not infer a reason from the absence of a record. If the reason is unknown, mark it unknown and report the count. A guessed reason makes the pattern look cleaner than the evidence allows.

Record the number of reminders sent and the channel used. A reminder that reaches the manager on the morning of the cutoff is different from one sent two days earlier. Note whether the business has a written escalation rule and whether it was followed. A policy that exists but is never used is a different finding from no policy at all.

Sampling and collection

Collect every pay run in the window rather than a sample of employees, because the approval rule applies to the whole run. If the business has several locations or entities, collect each one separately and record the entity. A combined rate can hide one location with a persistent problem. Report the number of runs and the number of employee-weeks behind every percentage.

Draw the approval data from the system audit log, not from a spreadsheet the manager maintains after the fact. If the audit log is incomplete, say so and reduce the claim. Record the export date, the filters, and any records that could not be matched. A missing audit trail is itself a finding about the control.

Ask the payroll owner to identify the weeks when the run was moved earlier or later than usual. A shortened week can produce missing approvals that have nothing to do with manager behavior. Record the schedule change and analyze those weeks separately. The reader should be able to tell whether the rate reflects the rule or the calendar.

Analysis and reporting

Report the share of employee-weeks with no approval at lock, the share with a late approval, and the share with a documented override. Show the median and range of the approval delay in hours. Present the results by location, manager, and week so the reader can see whether the problem is concentrated. Use the same denominator for every rate.

Separate the weeks that were paid before approval from the weeks that were held. A missing approval that stops the pay run is a delay, while a missing approval that releases pay is an exposure. Report both because they lead to different fixes. A business may accept a delay but should not accept an unapproved payment without a documented decision.

Inspect the slowest cases and describe which stage dominated without naming the employee. A late submission, an absent manager, and a system error each point to a different repair. Compare the delay with the reminder schedule and the cutoff time. Report the cases with incomplete timestamps rather than dropping them from the denominator.

Limits of the evidence

The record can show whether an approval was recorded, but it cannot show whether the manager actually reviewed the hours. A quick click and a careful review look the same in the audit log. The protocol also cannot capture a verbal approval that was never entered, so a missing record may not mean a missing conversation. State that limitation before presenting the rate.

A small business may have too few pay runs to support a stable trend. Describe the runs and the employee counts instead of ranking managers. If the same owner approves every timesheet, the result may reflect one person's availability more than the control design. Do not use the rate as a performance score without the context of leave, turnover, and schedule changes.

Do not compare a business that holds pay until approval with one that pays and corrects later. The two operate different controls even when the missing-approval rate looks similar. Report the pay-release rule beside the rate. A target that can be met by delaying everyone's pay is not a good target.

What to change

Give the result to the payroll owner and the manager and ask them to choose one observable change. The change might be an earlier submission deadline, a named backup approver, a daily approval check, or a hard stop at the pay run. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions after the change.

If the missing rate falls but the late rate rises, the approvals may be arriving closer to the deadline without improving the control. If both fall but overrides rise, the team may be routing around the rule. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Ask the manager which timesheet was hardest to approve and why. A concrete answer often reveals a missing schedule, a new pay code, or an employee who submits at the last minute. Use that answer to improve the process rather than to blame the manager. The next measurement should test whether the same delay shrank.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research