Redeployment: The Revenue Sitting in Contractors About to Roll Off
You already sourced them, vetted them and placed them once. Losing them at the end of an assignment is the most expensive thing a staffing agency does routinely.
A contractor finishes a six-month assignment on a Friday. On Monday they start somewhere else, placed by a different agency.
You sourced them. You vetted them. You built the relationship, ran payroll, handled the timesheets and answered the questions. And you handed all of that to a competitor because nobody called them three weeks before the end date.
Redeployment is the cheapest revenue in staffing and it's routinely the worst-run process in the agency.
Why it gets missed
Not because anyone thinks it's unimportant. Because of when it needs to happen.
The right moment to start is three to four weeks before roll-off. At that point the contractor is still working, still happy, and generating no problems. Nothing about them is on anyone's list, because staffing operations are driven by exceptions β the person who didn't show, the timesheet that's late, the client complaint.
A contractor doing well is invisible. Then they're gone.
Build the calendar backwards
Every assignment has an end date, known at placement. Everything else follows from it.
Four weeks out. System raises it. Recruiter checks with the client: extending or ending? Half the time this conversation alone produces an extension nobody had asked for.
Three weeks out. If it's ending, talk to the contractor. What did they like, what would they want next, are they open to a similar role, has their rate expectation changed. This is a good conversation to have β they're employed, unhurried, and it reads as you looking after them.
Two weeks out. Actively match. They should be on shortlists before their last day.
Final week. Confirm what's next, or set the check-in cadence if there's a gap.
After the end. If they haven't been redeployed, they stay on a warm list with real follow-up. A contractor between assignments is looking, and they'll take whatever comes first.
None of these steps are difficult. They just have to be triggered by a date rather than remembered.
The extension conversation is half of it
The best redeployment is the assignment not ending.
Clients extend constantly, and often it's a decision made late because nobody asked. Asking four weeks out gets you three things: extensions that would otherwise have lapsed, notice on the ones that are ending, and a reputation for being the agency that stays on top of things.
Worth capturing the reason when it does end. "Project finished" is normal. "Budget" is a signal about the account. "Performance" is something you need on the contractor record before you place them again.
What has to be in the system
- End date on every assignment, driving the sequence automatically
- Extension status, tracked as its own thing with its own follow-up
- Availability date on the contractor, updated as roll-off approaches
- Skills and assignment history, so matching is a search rather than a memory exercise
- Redeployment status β actively looking, placed elsewhere, taking a break, don't re-engage
- A bench view β everyone available in the next 30 days, in one place
That bench view is the operational artifact. It should be the first thing a contract desk looks at on Monday.
Numbers to watch
- Redeployment rate. Of assignments ending, what percentage went straight into another placement with you? This is the headline. Most agencies have never calculated it and are surprised, usually unpleasantly.
- Bench time. Average days between assignments for redeployed contractors. Shorter means you started earlier.
- Extension rate. What proportion of assignments extend at least once?
- Contractor lifetime value. Total margin across all assignments, per contractor. Reframes the whole conversation β a contractor you place four times is worth several multiples of a one-off, and it shows what losing one actually costs.
- Reason-for-ending breakdown. Where the account intelligence is.
Treat them like clients
The mental shift worth making: a contractor with a good assignment history is an asset with recurring revenue, not a placement that closed.
Which means:
- Contact between assignments, not only when you need something
- Knowing their situation β moving, wanting different hours, studying, done with contracting
- Being honest when you have nothing suitable, so they believe you when you say you do
- Asking for referrals, because good contractors know good contractors and this is the cheapest sourcing there is
Agencies that do this have contractors who've worked for them for years. Agencies that don't re-source the same population every quarter and wonder why margins are thin.
The honest caveat
Redeployment only works if the first placement went well. A contractor who had a bad experience β late payroll, a client that misrepresented the role, a recruiter who went quiet the day they started β isn't taking your call at week three no matter how good your reminder system is.
The automation makes sure you ask at the right time. Whether the answer is yes was decided months earlier.
We build assignment tracking, redeployment prompts and bench views for US staffing agencies. See how it fits together, or tell us what happens at roll-off today.