Operations

The last-minute shift coverage checklist every dispatcher needs

Published May 2, 2026 · 5 min read

A guard calls out two hours before their post. You have a client expecting coverage, a list of workers somewhere in a spreadsheet, and a growing text thread. Here is the checklist that keeps it from becoming a crisis.

Step 1: Confirm the post details before contacting anyone

Before you send a single message, make sure you have the correct site name, address, start time, end time, required credentials, and any client-specific restrictions. Contacting the wrong guard or providing the wrong shift time creates a second problem on top of the original one.

Step 2: Pull the eligible worker list — not your full roster

Contacting every worker on your roster is the fastest way to create chaos. You need a filtered list: workers who hold the right credentials, are not on a rest period, are not already assigned to another shift, and have not been flagged for this specific site.

If your roster is in a spreadsheet, filter by credential column first. If you are using a staffing tool, apply the site rules before building your outreach list. The goal is to contact fewer people, faster, with confidence that any one of them can legally take the post.

Step 3: Reach out in controlled rounds, not all at once

Sending the same message to 30 workers simultaneously creates a race condition: multiple workers may believe they accepted the shift, leading to confusion, double-staffing, or a late complaint from a guard who showed up unnecessarily.

Step 4: Record every step as you go

Manual texting feels fast, but it leaves no trace. If the client asks who was contacted, when, and why a particular guard was assigned, you need to be able to answer. Disputes about overtime, fair offer practices, or missed coverage can surface weeks later.

At minimum, log these in a shared doc or your staffing tool in real time:

Step 5: Notify the assigned guard and confirm receipt

Assignment is not complete until the guard acknowledges the details. Send a confirmation message with the site address, start time, point of contact at the site, and any special instructions. Ask for a reply confirming they received it — not just a claim acknowledgment.

Workers who claim a shift via text but do not receive a proper confirmation are more likely to show up at the wrong time or wrong location.

Step 6: Notify workers who responded too late

Workers who replied after the shift was filled should receive a message letting them know. Ghosting late replies damages trust and increases the chance they ignore future offers. A simple "This post has been filled — thank you for responding" takes seconds and protects the relationship.

Step 7: File the record before closing out

After the shift is assigned, make sure the record is complete: the open post, who was contacted, who claimed it, and when. This becomes your audit trail if the client ever questions how coverage was handled. For agencies running 10 or more open posts per month, this documentation is the difference between a professional operation and a reactive one.

What makes this hard to do manually

Every step above is achievable with a spreadsheet, a phone, and discipline — until you are doing it at 10 PM for the third time that week. The friction is cumulative: filtering eligibility by hand, tracking who replied and when, logging it all in a shared doc while juggling texts. The manual process works until it does not.

The agencies that handle last-minute coverage consistently well are the ones that have reduced the number of decisions a dispatcher has to make in the moment. That means structured outreach, a predefined order of contact, and automatic logging — not more steps in a text chain.

Want a tool that handles steps 2–7 automatically?

RosterRounds was built for exactly this workflow. Create the open post, set your rounds, and the system handles outreach, coded reply matching, eligibility checking, and audit logging — without a worker app.

Join the pilot waitlist →