Why time-to-redeploy is the only number that matters

What does time-to-redeploy actually measure?

It measures idle bench in days. The clock starts the moment a contract ends and stops when the consultant confirms a start date on the next one. Nothing in between counts as progress.

That framing matters because it is denominated in money. A consultant billing $65 an hour on a 40-hour week is roughly $2,600 of gross revenue per idle week. Ten benched consultants sitting an extra nine days is not a reporting problem — it is a five-figure hole.

Why are utilization and submittals the wrong scoreboard?

Utilization is an average over a period. It tells you what already happened and smooths over the exact thing you want to see: which consultant is sitting, and for how long. By the time utilization dips, the margin is gone.

Submittal counts are worse — they reward activity, not outcome. A desk can double its submittals and lengthen time-to-redeploy at the same time by spraying the same three candidates at a dozen duplicate requirements.

Fill rate has the same defect in reverse: it looks at roles filled, not people redeployed. An agency can post a healthy fill rate while its own bench rots.

Where do the days actually go?

When we instrument a desk, the idle days rarely disappear into sourcing. They disappear into coordination.

• De-duplicating the same role blasted by a dozen vendors, by hand, in a shared inbox.
• Re-typing a résumé into a client-ready format for each submission.
• Chasing a vendor for status on a submission from nine days ago.
• Waiting on a screening call that needs one recruiter and one candidate in the same half hour.
• Re-checking work authorization because the last person to touch the record did not log it.

How do agents compress it?

Each agent removes a waiting state rather than speeding up a human. Iris collapses duplicate requirements the moment they land, so nobody triages the same role twice. Maya keeps a work-authorization-filtered shortlist standing before the requirement is even routed.

Theo runs outreach continuously instead of in evening batches, and Aria can screen by AI voice when a recruiter is not free. Sam packages and submits without a copy-paste step, and Noor chases status so no submission sits unanswered.

The wins are individually unglamorous. Compounded across a bench, they are days.

How should you start measuring it?

You do not need a platform to begin. Record two timestamps per consultant — last billable day, and confirmed start date on the next assignment — and take the median across the quarter. Use the median, not the mean; one pathological bench case will otherwise flatter or wreck the average.

Then split the median by cause: days waiting on a shortlist, days waiting on a screen, days waiting on a client decision. That split tells you which agent, or which human process, is worth fixing first.