A temp worker was scheduled for Site North when their payroll packet was directed there. On Wednesday they are moved to Site West, where the supervisor assumes the packet will follow them. North plans to give the unopened envelope to a driver. West plans to request another. The first thing to stop is not the person’s shift. It is the two uncoordinated attempts to solve the same delivery problem.
Name the change without passing the record around
Record that an eligible shipment may be routed to an old worksite, identify it through the authorized program records, and preserve the last confirmed custody state. Give the dispatch coordinator the information needed to compare plans. Do not attach a worker profile, an address screenshot or an envelope photo to the discussion. The FTC’s business privacy guide suggests mapping who has access and keeping only necessary information. Treat that as a design constraint: most people in a site transfer only need to know whether to wait, hand off an approved task or refer the employee.
Keep the record that determines the work assignment separate from the record that determines the packet’s physical route. A scheduling tool can update instantly while the package is already on a truck. Do not assume an employee’s latest site assignment also edits a carrier’s destination or a third party’s dispatch file. An inaccurate “sent to West” label is harder to fix than an honest “North is the recorded destination; current custody unknown.”
Use three distinct paths
- Not yet sent: Ask the authorized sender whether its deadline permits an approved destination change. Confirm the update actually appears in that system before clearing the exception.
- In transit: Log the request and ask the sender or custodian which options are permitted. Do not promise an intercept, forwarding, or another packet unless the permitted route is confirmed.
- Arrived and sealed: Keep it with the named custodian. If the program allows a site transfer, confirm the approved receiving role, secure route and custody record. If not, keep it on the authorized exception path.
Never make a driver or supervisor an unplanned courier for payroll packets. A planned transfer may have a safe route under one agreement and be prohibited under another. The absence of a prohibition in a public brochure is not authorization. If there’s an unverified handoff, notify the owner under the established procedure rather than trying to reconstruct it in a general work chat. A fresh dispatch should not duplicate an unresolved packet state.
Schedule a deadline for the fallback decision
The shipping exception and the wage deadline belong on two clocks, not one. Payroll can determine whether it can still meet Friday’s deadline by an approved method while the logistics owner verifies the location of an envelope. The Department of Labor’s state payday overview shows why a site lead should not assume one rule applies throughout a multi-state operation. Short shipping estimates do not settle the employment obligation; a check goes to payroll and legal when rules or fallback choices are unclear.
Suppose fictional dispatch North confirms an envelope is locked in its cabinet at 4 p.m. Wednesday, West has no designated custodian on Thursday, and a Friday payroll review cannot wait until a Monday shift. The useful outcome may be to leave the current envelope secured, escalate to payroll before its Thursday cutoff, and agree on a different future handoff method. Ask the approved owner what should happen to the older packet if a new one is ever authorized. Count it in the right custody bucket until disposition is confirmed.
Confirm only what the receiving team needs
Use an appropriate channel for any employee-facing note and avoid promising more than the program can deliver. “The location for the packet handoff has not been confirmed; the payroll team will provide next steps through the normal company channel” gives people a safe point of contact. It does not tell them to collect an envelope from someone else’s front desk, identify another worker, or send personal data to a supervisor. If the route changes to direct mail, consult the remote shipping workflow rather than forwarding a packet as an informal favor.
Audit the transfer using a simple timeline: latest authorized site instruction, last verified packet location, decision owner, due time and disposition. Order those items by confirmation time instead of by who sent the most recent message. When the old and new operations teams read the timeline, they should see the same next step without needing a second copy of the employee’s financial records.