Overtime Approval Process for Hourly Employees: An 8-Step Workflow

What is the overtime approval process for hourly employees?

Hourly and other non-exempt employees request written authorization before overtime begins. UC Riverside HR and University of Washington HR state that if overtime-eligible employees work the time anyway, every hour must still be recorded and paid. A sound process separates permission to incur a future labor cost from the employer’s timekeeping and payroll duty, then reconnects both records during supervisor review and payroll reconciliation.

1. Identify the need: record the date, task, business reason, and estimated hours.
2. Submit a written request to the designated supervisor before work begins.
3. Verify non-exempt status, the applicable workweek, and any state or contractual rules.
4. Review coverage alternatives, budget, deadlines, workload, and fatigue.
5. Route the request to an approver with delegated authority.
6. Record and communicate the decision, permitted scope, and timestamp.
7. Record every hour actually worked, whether authorized or not.
8. Have the supervisor verify actual time, then let payroll calculate, pay, and reconcile it.

ChangeEngine’s overtime policy guide describes the federal baseline as a fixed, recurring 168-hour workweek that can start on any day and does not need to match the calendar week. HiveDesk’s overtime policy guide states that employers cannot average hours across multiple workweeks and notes that some states impose daily overtime requirements. Weekend or holiday work is not automatically federal overtime, although state rules, collective bargaining agreements, employment programs, and company policies can add daily thresholds or other requirements.

Why should overtime authorization and overtime pay use separate tracks?

Authorization and pay address different control failures. The authorization track decides whether planned work should proceed, who owns the cost, and which manager has authority to approve it. The pay track captures what happened, even when approval is missing. This reflects the distinction in UC Riverside HR and University of Washington HR guidance between requiring authorization and paying for all overtime worked. That separation keeps a policy violation from turning into an off-the-clock payroll error.

Keep both tracks in one operating design, even when separate systems execute them. A documented approval workflow should reference the timekeeping record. The timecard review should show whether authorization existed, but authorization must never become a condition of payment.

What should an employee include in an overtime request?

A useful request gives the approver enough detail to decide without another email or chat thread. Capture the worker, fixed workweek, requested date, task, business reason, estimated hours and cost, staffing alternatives, deadline, and charge code. Include an emergency flag and the employee’s acknowledgment that all actual time must be recorded.

Do not assume estimated cost always equals base hourly pay multiplied by 1.5. The employer’s payroll rules should define how the estimate treats remuneration that must be included in the regular rate. The request remains a planning estimate. The timecard and payroll calculation are the final records.

Who should be authorized to approve overtime?

Approval authority should follow a written matrix, not whoever answers first. Supervisors handle requests within their delegated scope. Department leaders or finance review budget exceptions, HR owns classification and policy interpretation, and payroll owns pay calculations and corrections. Give every role a named backup and a clear escalation route for absences or delays.

The matrix must name who acts when the usual approver is unavailable. Pair it with an approval escalation process that identifies the backup, escalation trigger, and final decision owner. Escalation cannot become informal approval by someone who lacks delegated authority.

How should a manager evaluate an overtime request?

Before approving overtime, a manager checks employee eligibility, the fixed workweek, state or contractual rules, staffing alternatives, budget, schedule impact, and fatigue. The decision must stay within delegated authority. Record the reason and timestamp, then specify the permitted date, task, and estimated hours without limiting the employee’s right to report actual time.

A denial needs an operating decision, not just a red mark. Reschedule the task, transfer it, reduce its scope, or escalate the deadline. Telling an employee to finish the work without recording the time is never an acceptable alternative.

How should emergency and unauthorized overtime be handled?

Emergency overtime needs a fast exception path. Protect people and operations first, notify the designated manager immediately, record all time, and document the reason as soon as practical. Unauthorized overtime calls for a different response: consistent with UC Riverside HR and University of Washington HR guidance, preserve the time entry, pay what is due, investigate the control failure, and apply consistent corrective action when warranted.

Emergency exception workflow

1. Address the urgent safety, customer, equipment, or operational need.
2. Notify the designated manager through the fastest approved channel.
3. Record the actual start, end, task, and hours worked.
4. Submit the normal request fields with the emergency reason marked clearly.
5. Have the supervisor verify the facts and payroll process any pay due.

Unauthorized overtime response

UC Riverside HR states that overtime worked by non-exempt employees must be compensated whether approved or not. University of Washington HR also separates the duty to pay from possible corrective action. Keep the time entry intact, document the violation, pay correctly, find out why the employee worked without approval, and apply policy consistently when corrective action is warranted.

How do actual overtime hours reach payroll correctly?

Actual hours move from timekeeping to the supervisor’s factual review and then to payroll, regardless of the authorization decision. The supervisor verifies dates, tasks, missed punches, and work across positions. Payroll applies the governing weekly or daily rules, calculates the regular rate, corrects discrepancies, and confirms that all compensable time was paid.

This review covers more than scheduled shift time. University of Washington HR guidance identifies required travel, training, meetings, and sufficiently restricted on-call time as situations that can count as hours worked. It also directs organizations to combine hours across multiple positions when calculating a non-exempt employee’s weekly overtime.

Compare approved estimates with actual time, but never force the actual entry to match the estimate. Investigate missing entries under a written missed punch policy, correct factual errors, and record the reason for material differences. Payroll then confirms the hours, applicable rate, pay period, and correction status.

What policy language supports the overtime authorization process?

Put both rules in the same policy paragraph: advance authorization is required, and all hours worked must be reported and paid. Workstream’s overtime policy guidance supports defining covered employees, pay rules, approval procedures, hour limits, and communication methods. The policy should also define the fixed workweek, approvers, request method, emergency handling, timekeeping duties, review steps, corrective action, and any state, contractual, or program-specific provisions.

Non-exempt employees must obtain written approval from an authorized manager before working overtime, except when an emergency makes advance approval impractical. Employees must accurately record all hours worked, including unauthorized or emergency overtime. The company will pay all compensation due under applicable rules. Failure to follow the authorization procedure may result in consistent corrective action.

Use this as starter language, not as a substitute for review. HR should adapt it to applicable state rules, collective bargaining agreements, employment programs, pay practices, and the company’s real approval structure.

How should employers implement and monitor the process?

Implementation fails when policy, workflow, timekeeping, and payroll use different definitions or owners. Start with classification and workweek rules. Configure alerts, assign authority, train managers, collect employee acknowledgments, and run weekly exception reviews. On a set cadence, inspect turnaround, unauthorized overtime, estimate accuracy, team cost, emergencies, and payroll corrections.

1. Confirm classifications, workweeks, state rules, contracts, and regular-rate practices.
2. Publish the request form, approval matrix, emergency path, and escalation route.
3. Configure alerts when reported or scheduled hours approach a governing threshold.
4. Train managers never to permit, encourage, or ignore off-the-clock work.
5. Require employees to acknowledge the request and time-reporting rules.
6. Review pending requests, actual hours, exceptions, and discrepancies each week.
7. Recheck policy language and workflow configuration whenever governing rules change.

Measure approval turnaround, unauthorized-overtime frequency, estimated versus actual hours, overtime cost by team, emergency usage, and timecard corrections. Keep the definitions consistent in your approval workflow metrics so leaders can tell a slow approval process from weak scheduling, unexpected demand, or inaccurate timekeeping.

How Cogniver helps run overtime approvals for hourly employees

Cogniver turns pre-work overtime authorization into a routed process instead of a chain of messages. Employees submit the required fields, and the visual builder sends each request through the correct approval path. A mandatory default branch catches anything that does not match a rule, so no request sits without an owner.

The directed-graph builder handles branching, merging, and multi-step approval chains. Standard requests can go to the supervisor, budget exceptions to finance, and policy exceptions to HR. A step can require supporting documents or ask an approver to enter a verified value that later routing uses.

Every workflow also has its own isolated AI agent, trained by organization admins on that workflow’s rules. The agent answers request questions, routes cases, and chases approvers. Attendance exceptions run through the same approval engine, and each workflow’s agent remains isolated from other workflows and companies.