Confirm that a new starter reached the right site and was received by the right person. Keep conflicting arrival reports open until someone resolves the handoff.
A temporary worker texts “I’m here.” The client supervisor reports that the new starter has not arrived. Both messages may be accurate: the worker is waiting at a side entrance, while the supervisor is watching the main reception desk.
A temporary worker first-day check-in workflow should reconcile those reports before the agency marks the placement as started or escalates an apparent absence. This guide is for staffing coordinators and host supervisors handling a new onsite assignment. It covers the receiving handoff at Ready → Assign → Manage, not the entire onboarding process.
Separate an arrival report from a completed handoff
“Scheduled,” “worker reports arrival,” “host received worker,” and “work began” describe different events. A message, a clock-in or a completed onboarding packet does not establish all four.
The staffing agency onboarding process prepares the placement. This narrower workflow starts when a first-day arrival is expected and ends when the receiving outcome is documented, with any remaining issue assigned to its next owner.
Actual agency practices demonstrate why the receiving step needs its own attention. Dean’s Professional Services’ assignment instructions ask workers to notify their staffing coordinator upon first-day arrival. That is the provider’s own instruction, not a universal reporting deadline. On the host side, Pacific University’s temporary staffing guide includes first-morning introductions and checks that the worker can use required systems.
The operating design below joins those two perspectives. It is a recommended coordination process, not a determination of attendance discipline, safety clearance, payable time or employment rights.
Give the receiving handoff a named owner
The agency coordinator owns reconciliation. The worker reports their situation through the agreed channel. A named host contact confirms receipt at the intended location and identifies the person taking over supervision. The coordinator’s backup handles unresolved cases when the primary coordinator is unavailable.
Before the first day, carry forward the approved assignment reference, start time and time zone, address, entrance, receiving contact, backup contact and communication route. Do not collect another full onboarding packet. Confirm that the host contact actually knows a new starter is expected.
Safar Staffing’s workplace preparation guide recommends a first-day contact and a backup, along with clear entrance and reporting instructions. Those concrete arrangements make a receiving plan actionable; “ask for the manager” does not identify who will respond.
- Trigger: a scheduled first-day start enters the team’s agreed arrival-check window, or an arrival message arrives sooner.
- Input: the approved placement details and current worker/host reports.
- Decision: receipt confirmed, discrepancy being resolved, or another documented outcome.
- Evidence: who reported what, when the event occurred, when it was recorded and who accepted the next action.
- Next state: received by host, or an open exception handed to a named owner.
Set the check window and escalation timing with the client for the actual shift. This article supplies no default grace period. Do not borrow another agency’s published timing and present it as a legal or contractual requirement.
Use a paired-report arrival register
Keep one record per worker, placement and first-day start. Record the source of each fact instead of combining everything into one “arrived” checkbox. The register below is a reusable field specification, not a prescribed legal form.
| Record part | What to capture | Owner and progression rule |
|---|---|---|
| Expected handoff | Placement reference, worker reference, approved site/entrance, local start time and zone, receiving contact and backup. | Coordinator confirms the current assignment version before comparing reports. |
| Worker report | Reported arrival location and event time, message/call receipt time, channel and any immediate receiving difficulty. | Coordinator records the worker’s account as reported, not independently verified presence. |
| Host receipt | Named host confirmer, where and when the worker was met, receiving supervisor and any unresolved start condition. | Host confirms the actual handoff; silence is not acceptance. |
| Discrepancy | Conflicting facts, last contact attempts, action needed, assigned resolver and next update point. | Coordinator keeps the case open until the difference is resolved or accepted by the next responsible owner. |
| Outcome and linked records | Received, unresolved exception, revised start or other confirmed outcome; actual chronology and references to attendance, timekeeping or readiness follow-up. | Coordinator closes only the receiving case; separate decisions remain with their authorized owners. |
Use restricted references for personnel information. The receiving supervisor needs the assignment and contact instructions, not the worker’s entire file. Avoid adding sensitive personal explanations to a general coverage register.
Resolve the discrepancy before choosing the outcome
The worker reports arrival but the host cannot find them
Contact the worker and named host receiver. Confirm the assignment reference, entrance and meeting point using the approved instructions. Ask the host backup to take ownership if the primary receiver is unavailable. Do not direct a worker into a restricted or unsafe area to prove arrival.
Keep “worker-reported arrival” visible while receipt is pending. If the worker is at the wrong location, record the correction and the actual subsequent handoff. Do not overwrite the earlier report or change its time to make the story look simpler.
The host confirms receipt but there is no worker message
Record who at the host met the worker, where and when. Resolve the missing agency notification separately through the established communication process. A missed text does not, by itself, mean the person was absent.
If a device or clock-in problem remains, route it to the timekeeping owner with the known chronology. Do not invent a clock event or silently substitute the scheduled start time for an observed event.
Neither side can confirm receipt
Record contact attempts and ask the designated host contact to check the receiving location. Keep the outcome unconfirmed until there is evidence for a different state. Apply the agreed escalation path rather than waiting indefinitely for one more reply.
If the facts establish a missed start, hand the case to the existing no-show response process. That process owns absence review and coverage recovery. This arrival register supplies the verified facts; it should not create a competing discipline or replacement policy.
The worker is received but cannot begin the assigned work
Close neither the readiness issue nor the timekeeping question merely because the worker reached the site. Identify the blocker and responsible host or agency owner. Receiving a person is different from confirming that access, instruction, equipment and the approved work conditions are ready.
Use the established temporary-worker safety responsibility process for safety questions. If proposed duties differ from the approved placement, route that change separately. An arrival acknowledgement is not authorization for different work.
Work through a side-entrance mismatch
Illustrative scenario: a new starter is scheduled for 08:00 local time. At 07:57, the worker texts the agency that they are at the building. At 08:03, the host supervisor reports that nobody has checked in at reception.
The coordinator opens a discrepancy rather than recording a no-show. The worker explains that they followed an old side-entrance instruction. The coordinator checks the approved placement details with the host, and the host backup arranges to meet the worker at the correct receiving point. The backup confirms receipt at 08:09.
The record preserves 07:57 as the worker’s reported arrival event, 08:03 as the host’s report and 08:09 as confirmed receipt. It also identifies the obsolete instruction for correction by its owner. The coordinator does not backdate receipt to 08:00 or decide payable time from these messages.
The receiving case can now close as “received by host,” with any readiness or timekeeping questions linked to separate owners. A brief end-of-day follow-up can check that the handoff problem did not leave a practical issue unresolved. RHO Hiring’s onboarding service description similarly distinguishes early check-ins with the worker and supervisor, but the exact follow-up cadence should fit the actual assignment.
Where Workhint fits
Workhint’s Shifts & Field Visits describes shift assignment, attendance and location verification at clock-in and clock-out. It explicitly distinguishes that verification from live GPS tracking. A clock event can be relevant evidence, but the product page does not establish that the host received the worker or that work was ready to begin.
The Workflow Engine describes configurable steps, role-routed approvals and required details, files or notes before progression. Those building blocks are relevant to an agency-owned receiving case with a host acknowledgement and an exception owner. The Staffing Managers solution provides the matching staffing context: worker profiles, availability, assignments and reviewed hours.
Treat the paired-report register as a configuration requirement to review, not a claim of a ready-made arrival-reconciliation module. Test worker-only, host-only, conflicting-report and inaccessible-contact cases. Confirm what the setup can support and which actions remain manual. Do not assume a status automatically calls a client, changes payroll or prevents work on site.
Close the receiving case without closing unrelated decisions
Before closure, the coordinator should be able to answer: Which placement was involved? What did each party report? Who actually received the worker? What remained unresolved, and who accepted that follow-up?
If the outcome is not receipt, retain the confirmed alternative and its owner: a revised start, a missed-start investigation or an unresolved exception with an accepted escalation. “No reply” is a pending fact, not a successful handoff. Review repeated mismatches for instruction or receiving-contact failures rather than automatically assigning blame to workers.
FAQ
Does a clock-in prove the first-day handoff is complete?
No. It records a timekeeping event according to that system’s rules. Confirm separately that the designated host received the person and owns the next step. Do not infer readiness or payable time from a single arrival signal.
Should every shift use this full record?
This design is for the first day of a new onsite placement. Use the established attendance process for routine shifts. Decide whether a site transfer or other material receiving change needs another explicit handoff.
What if the receiving supervisor is unavailable?
Use the named host backup and agency escalation route. Keep the case pending until a responsible person accepts the handoff or a different outcome is confirmed. An unanswered message should not silently become an acknowledgement.
Who decides whether waiting time is payable?
The authorized payroll or employment owner applies the relevant rules and terms. The coordinator supplies accurate event and communication records without treating this operational register as a pay decision.
Leave a Reply