Check one worker’s complete week before confirming another client assignment, with a clear path for missing hours, competing bookings and payroll review.
A client asks for an extra shift. Its own schedule shows plenty of room, but the worker has already completed assignments elsewhere through your agency. Approving each client’s hours separately can hide the total that matters.
An overtime across clients check brings those assignments together before the scheduler confirms more work. This operating guide is for staffing teams placing covered, nonexempt employees of the same employer. It is not an independent-contractor pay rule or a method for deciding whether separate businesses are joint employers.
The process sits between Ready and Assign: the worker is otherwise eligible, and the proposed placement needs an hours review. After work occurs, actual time goes through Manage and Pay. A scheduling projection informs a booking decision; it does not calculate final wages.
Use the worker’s week, not the client’s remaining budget
The Department of Labor’s overtime fact sheet explains the federal baseline: covered nonexempt employees generally receive at least one-and-one-half times their regular rate for hours above 40 in a fixed, recurring 168-hour workweek. Hours cannot be averaged across weeks. Different straight-time rates can require a weighted-average regular-rate calculation, subject to specified alternatives.
For one employee working assignments for the same employer, review the combined workweek rather than treating each client as a separate allowance. Ascen’s multi-client assignment guidance illustrates the operational distinction: assignments remain client-specific, while the employee’s overtime position spans them.
Have payroll or the qualified employment reviewer establish applicable rules, workweek boundaries and included time. State rules, exemptions, travel, bonuses and other circumstances may change the review. A client invoice period is not a substitute for the employer’s workweek, and a weekly total below 40 is not universal clearance.
Assemble three different views of hours
Name one coordinator to assemble the worker-week record. Client account managers provide their assignment evidence; payroll owns wage-rule questions; the authorized scheduling reviewer decides whether the proposed work can be confirmed.
Observed work so far
Collect actual time recorded for every relevant assignment in the workweek. Keep submitted, client-approved and unresolved time distinguishable. Do not omit a submitted shift because its approver has not responded. A missing clock-out is an unknown duration requiring investigation, not a zero-hour entry.
Match by the authoritative worker identifier and employer record. If two branches have created different profiles for the same person, resolve that identity question before claiming complete coverage. Do not merge records or expose client data without the appropriate authority.
Confirmed work still to come
Add the remaining expected work on already-confirmed assignments. Avoid counting a completed shift twice: use actual hours for the completed portion and expected hours only for work still ahead. Show the source and last refresh time for each assignment.
Map shifts to the established workweek using dates, times and time zones. Escalate a boundary-crossing shift or incompatible export grouping to the timekeeping owner. Do not move the workweek boundary simply to make the proposed booking fit.
The new request and other pending requests
Show the proposed assignment separately. List other unconfirmed requests too, but do not silently count every request as a commitment. Two account managers considering the same worker need to see that their proposals compete for the same capacity.
For planning, calculate: observed hours + remaining confirmed hours + this proposed assignment. Label the result a projection and show unresolved inputs alongside it. If a value is unknown, a precise-looking total does not make the underlying record complete.
Keep a worker-week booking register
Use one summary record per employee and workweek, with assignment-level rows underneath it. This is a recommended operating asset, not a statutory form or a promise that a spreadsheet enforces booking limits.
| Record group | What to capture | Owner and gate |
|---|---|---|
| Identity and week | Worker ID, employing entity, established week start/end and time zone, applicable-rule reference | Coordinator; payroll resolves identity or rule uncertainty |
| Assignment coverage | Every relevant client/assignment reference, reporting contact, actual time source and refresh timestamp | Account owners confirm included assignments; missing feed remains open |
| Hours position | Actual recorded hours, unresolved time, remaining confirmed hours and proposed hours in separate fields | Coordinator checks duplicates and completed-versus-remaining work |
| Competing requests | Pending proposal IDs, requester, planned dates and whether another decision has changed commitments | Scheduling reviewer resolves the order of decisions |
| Decision | Projection version, rule review, operational approval or return, conditions, reviewer and timestamp | Authorized reviewer; incomplete evidence does not become an unqualified pass |
| Release and follow-through | Final recheck, assignment confirmation, worker response, changed source records and payroll handoff reference | Coordinator confirms the decision still applies and hands actuals to time review |
Keep personal and commercial details in restricted source records. A client supervisor needs its own shift instruction and approval request, not another client’s rates or the worker’s entire employment file.
Make a decision, then recheck before confirmation
The reviewer should choose an explicit outcome rather than passing around a total without instructions.
- Return for evidence: an assignment feed, time interval, identity match or rule decision is unresolved. Name the missing item, owner and next review time.
- Approve this proposal: the evidence supports the defined assignment under the applicable review. Record which projection version and conditions the approval uses.
- Approve an hours or cost exception: an authorized owner accepts the scheduling proposal and associated commercial implications. This is not permission to disregard wage requirements.
- Do not confirm: use another qualified worker, revise the requested coverage or return to the client with a specific alternative. Confirm the replacement through its own readiness and hours checks.
The overtime request form guide supplies the broader authorization record when extra work needs approval. The cross-client register supplies the missing context: whose other assignments were included, how current they were and what changed before release.
Resolve two simultaneous booking proposals
At low volume, designate a single confirmation owner for the worker-week. That person checks the latest commitments immediately before releasing each booking and records the updated version. An approval prepared earlier in the day should return for review when its underlying hours change.
If your scheduling system supports reservations or concurrency controls, test their actual behavior. Otherwise use a clearly owned manual handoff; do not describe a shared sheet as an atomic lock. A detected double confirmation needs prompt worker/client coordination, corrected instructions and a preserved decision history.
Reopen the review when actual work runs longer
Use assignment changes, extended shifts and newly reported time as review triggers. Define a refresh cadence suited to how quickly your schedules change; there is no universal safe interval. Before the next assignment starts, the coordinator checks whether the decision still fits the latest known facts.
DOL also explains that a policy requiring advance authorization does not remove an employee’s right to compensation for compensable overtime already worked. Record the actual work and route any authorization issue separately.
Example: a late clock-out changes the answer
Illustrative scenario: an agency employee has 17 recorded hours at Client A and 12 at Client B. Four hours remain on a confirmed assignment. Client C requests another six hours. The initial projection is 39 hours, assuming all time is complete.
Client B then reports that a completed shift ended two hours later than recorded. The coordinator preserves the original value and correction evidence, updates observed time to 31 hours and recomputes the projection: 31 + 4 + 6 = 41. The old review no longer supports an unchanged confirmation.
The scheduling reviewer can seek the relevant approval or propose another qualified employee for Client C. Payroll reviews the actual week and applicable pay treatment; the account owner checks commercial terms separately. This example illustrates an information change, not a wage calculation or a recommendation to reduce recorded hours.
If Client C’s booking had already been confirmed, record the conflict and contact the responsible parties. Do not erase it from the register and assume the worker knows the new instruction.
Hand actual time to payroll without hiding billing questions
At period close, replace projections with the actual time record through the staffing timesheet approval process. Retain the booking decision, late corrections, rule questions and accepted payroll handoff. Preserve the dates on which work actually occurred.
Client charge allocation needs its own commercial decision. An unresolved invoice arrangement should remain a visible account-owner task, not a reason to remove hours from the employee’s record. Send wage questions to payroll with an owner and applicable deadline rather than waiting for the client billing discussion to finish.
Where Workhint fits
Workhint’s Workflow Engine describes request and assignment steps, role-based approval routing and required details, files or notes before progression. Those are relevant building blocks for collecting the projection and routing unresolved evidence.
The Staffing Managers solution describes worker availability, assignment matching with manager review and timesheet review. These provide context for discussing how the worker, assignment and hours-review records would connect.
Neither page establishes an automatic cross-client overtime calculator, payroll-feed integration or atomic booking lock. Test the proposed configuration with a missing time entry and two competing requests. Identify which steps it supports and which need a manual owner or separate payroll system.
FAQ
Should the scheduler wait for every client approval to include hours?
No. Keep reported work visible even when its approval is pending. Distinguish the approval state from whether work has been reported, and investigate disputed or incomplete intervals.
Is a projection an overtime pay calculation?
No. It supports a scheduling decision. Payroll needs actual time, applicable rules and relevant earnings information to determine final pay.
Can each client use its own invoice calendar?
A billing calendar does not establish the employee’s workweek. Have the responsible owners map dated assignment records to the established workweek and confirm what the actual systems support.
Does this check replace other assignment-readiness checks?
No. Availability, qualifications, site readiness, worker acceptance and any required safety review remain separate. A complete hours record does not establish that someone can perform the proposed work.
Leave a Reply