Many staffing agencies do not lose placements because a candidate was unqualified. They lose them because the candidate looked ready in the CRM but was not actually ready to start. The record said available. The recruiter assumed transport was sorted. The site expected one arrival window, the candidate understood another, and the problem only became visible when it was too late to recover calmly.
That is why candidate start readiness deserves its own checklist. It sits between candidate availability, document status, and first-day execution. A good process confirms whether the candidate can start in real life, not only on paper. If your team already uses candidate availability tracking and a cleaner document collection workflow, start-readiness is the next layer that protects placements from avoidable friction.
Why "available" is not the same as "start ready"
Availability is only one part of the picture. A candidate may still fail to start because:
- the reporting time was never clearly confirmed
- transport works for day shifts but not for a 06:00 start
- the candidate still expects a different location or branch
- one document, item of equipment, or registration step remains open
- nobody confirmed who the candidate should contact if plans change
This is why start-readiness should be treated as an operational checkpoint, not as a hopeful assumption.
Use a simple framework: START
One practical way to review readiness is to work through five headings:
- Schedule: exact date, time, and shift expectation
- Travel: how the candidate will actually get there
- Admin: what is still missing before the start can happen cleanly
- Readiness: whether the person understands the role and still intends to start
- Team contact: who the candidate reaches if something changes
This is a practical framework, not a universal standard. It helps recruiters check readiness without turning every pre-start call into a long interview.
1. Schedule
Confirm the details that remove ambiguity:
- exact day and reporting time
- site or meeting location
- whether this is interview, registration, induction, or first shift
- whether the candidate should arrive early for any reason
If the start still sounds vague after this step, the record is not ready.
2. Travel
Travel is one of the most common hidden blockers in staffing.
Useful checks include:
- how the candidate plans to travel
- whether that travel works for the actual shift time
- whether pickup, shared transport, or public transport timing is understood
- whether the candidate knows the location well enough to arrive reliably
Example: a candidate may sound fully available for warehouse work near Rotterdam, but only if the shift starts after the first workable bus connection.
3. Admin
This does not mean verifying every possible item again. It means confirming whether anything still blocks the start.
Examples might include:
- registration step still incomplete
- one key document still missing
- client-specific pre-start instruction not yet acknowledged
- role-specific item still to be arranged
These are examples, not universal requirements. The point is to separate "ready apart from one visible blocker" from "assumed ready because nobody rechecked."
4. Readiness
This step tests whether the candidate still intends to proceed under the actual conditions.
Useful questions often include:
- are you still available for this exact shift and location
- do you understand the type of work and the shift pattern
- has anything changed since the last conversation
- is there any reason tomorrow morning could still fail
This protects the agency from treating silence as confirmation.
5. Team contact
Candidates are more likely to follow through when they know who to contact and how.
That usually means confirming:
- recruiter or coordinator contact route
- what to do if the candidate is delayed
- when the next confirmation should happen if the start is not immediate
A start-ready record should not leave the candidate guessing whom to call.
A practical 24-hour pre-start check
Many agencies benefit from one short check the day before the start.
Example pre-start confirmation:
- candidate repeats back date, time, and location
- recruiter confirms travel plan is realistic for the shift
- any remaining document or instruction is closed out
- candidate knows what to bring or expect
- one named person owns first-day follow-up
This usually creates more control than a larger batch of vague reminders.
How to store start readiness in the CRM
The CRM should show more than "placed" or "booked."
A useful model often includes:
- start date and time
- readiness status
- active blocker if the start is not yet clean
- last confirmation date
- owner of the pre-start follow-up
That makes start risk visible in the same way candidate no-show reduction depends on visible confirmation logic. If the pre-start record stays vague, the team finds out too late.
What staffing teams should not do
Do not rely on one old availability note
Someone who was available on Monday may not be genuinely ready for Friday's shift under the same conditions.
Do not mix start-readiness with general candidate activity
A recruiter queue for live sourcing and a queue for first-day readiness are not the same thing. Separate them where possible.
Do not leave hidden blockers inside note text
If transport, equipment, or timing is uncertain, it should appear as a visible blocker, not as a sentence buried in the record.
Do not assume the candidate understood operational detail
"See you tomorrow" is not a start plan.
Common mistakes
Confirming the role but not the route
Candidates often say yes to the job before anyone checks whether the start time and travel reality still work together.
Treating the first-day plan as administration only
Start readiness is not just paperwork. It is a live operational handoff.
Forgetting ownership on the morning of start
If nobody owns the first live check, the team may only notice trouble after the client notices it.
Reusing one generic checklist for every desk
The core structure can stay the same, but logistics, production, hospitality, and office roles often need different examples.
Short checklist
- Confirm exact date, time, and location
- Check whether the travel plan works for the real shift
- Surface any open admin blocker visibly in the CRM
- Ask whether anything has changed since the last call
- Give the candidate one clear contact route
- Assign one owner for pre-start follow-up
FAQ
Is start readiness different from candidate availability?
Yes. Availability says the candidate may be free. Start readiness confirms whether the candidate can actually begin under the agreed conditions.
When should the start-readiness check happen?
Usually once the start is realistic and again shortly before day one if timing, travel, or instructions could still drift.
Should every candidate receive the same checklist?
No. Use one shared structure, then adapt the practical examples to the role, branch, and start type.
Does this only matter for large staffing teams?
No. Smaller teams often feel the benefit faster because one failed start has a larger impact on a tighter desk.
What is the easiest improvement to make first?
Add one visible start-readiness status with a blocker field and one owner. That alone makes weak pre-start records much easier to spot.
If your agency wants fewer lost starts and less last-minute recruiter chasing, review the solution options, compare the pricing section, or use the contact section to map where pre-start readiness is still breaking down.