On this page: Key takeaways · What is talent pipeline management in frontline hiring? · What makes a past applicant placeable? · How do you keep availability current without chasing everyone? · What does data protection law ask of a talent pipeline? · Which checks should you redo before a past applicant starts? · How big is your pipeline really? A worked example · What changes for staffing agencies? · How Radius helps · What should you do first? · FAQ
Key takeaways
- A past applicant is placeable only when availability, permission and checks are current and dated.
- Separate stable evidence from perishable facts, and refresh only the perishable ones.
- The GDPR asks for accurate data, kept no longer than necessary, with the period stated.
- Recheck anything with an end date before a returning applicant starts. A recruiter decides every placement.
What is talent pipeline management in frontline hiring?
It is the routine that keeps past applicants ready for the next shift.
Frontline roles reopen every week or season, so the person you could not place last month is often right for next month.
In the second quarter of 2026 the Netherlands had 95 vacancies for every 100 unemployed people, according to provisional, seasonally adjusted figures from Statistics Netherlands (CBS, 30 July 2026). In a market that tight, an applicant you have already interviewed is hard to replace.
This blog covers past applicants you did not hire or could not place, not temporary workers moving between assignments.
What makes a past applicant placeable?
Three facts, each with a date: availability, permission and valid checks.
Stable evidence, such as what a candidate showed in a structured interview, changes slowly. Perishable facts, such as availability, permission and document dates, expire on their own. Most pipelines treat both the same, so old availability looks as solid as last year's interview. Dating the perishable facts turns a list into a pipeline.
What to record for each past applicant
| Fact | Kind | Goes out of date when | How to refresh |
|---|---|---|---|
| Shifts, hours, earliest start date, travel area | Perishable | Their plans change | A short message before each hiring peak |
| Permission to keep and contact them, with the period you stated | Perishable | The period ends, or they withdraw | Ask at the end of each process, then renew or delete |
| Answers per requirement from a structured interview | Stable | The role's requirements change | Ask only the new or changed requirements |
| Identity and right to work, with any document end date | Perishable | A document expires, or a new start is due | Check again before the first shift |
| Certificates, such as forklift or VCA, with expiry date | Perishable | The expiry date passes | Compare the date with the end of the assignment |
See how interviews, checks and their dates sit on one candidate record in the Radius ATS.
How do you keep availability current without chasing everyone?
Ask on a schedule tied to your hiring calendar, not at random.
A few weeks before each peak you can predict, such as the holiday rush in logistics, send the past applicants for that role two or three questions: can you work from this date, which shifts suit you, and do you still want to hear from us. Keep it short enough to answer on a phone.
Record each answer with its date, and keep two habits:
- A reply has a shelf life. "Available from 1 December, nights only" is a fact for a few weeks, not a year.
- Silence is unknown, not available. Do not count silent people as capacity, and remove those who have found steady work.
What does data protection law ask of a talent pipeline?
Accurate data, kept no longer than necessary, with the period stated.
Four provisions of the GDPR matter most here:
- Accuracy: personal data must be accurate and, where necessary, kept up to date (Article 5(1)(d)).
- Storage limitation: data may be kept no longer than necessary for its purposes (Article 5(1)(e)).
- Transparency: when you collect the data, tell people how long you will keep it, or the criteria for deciding (Article 13(2)(a)).
- Withdrawal: where you rely on consent, people may withdraw it at any time, and withdrawing must be as easy as giving it (Article 7(3)).
In practice: at the end of each process, ask whether the person wants to hear about future roles, say for how long, and store the answer with its date. The Dutch Data Protection Authority (AP) says it is customary to delete an unsuccessful applicant's data no later than four weeks after the procedure ends, and that up to one year is reasonable if the applicant consents, for example for a future vacancy. This is regulator guidance, not a fixed legal limit: the GDPR requires that data are kept no longer than necessary. Agree your period with your privacy adviser.
Which checks should you redo before a past applicant starts?
Anything with an end date, and identity before every first shift.
Dutch government guidance tells employers to check a new worker's identity against an original, valid identity document before they start working, and then to make sure the person is allowed to work for them (business.gov.nl). Do this for every past applicant you place, rather than relying on a check from an earlier application. For certificates, compare the expiry date with the end of the assignment, not with today. See which checks can happen before the offer.
How big is your pipeline really? A worked example
Illustrative example. An agency needs 20 reach truck drivers for a client's peak in three weeks. Its records hold 80 past applicants for that role. Counting only what is current:
| Step | People left | What it tells you |
|---|---|---|
| Past applicants for the role | 80 | The size of the list |
| Permission still within the stated period | 56 | 24 records to renew or delete |
| Replied to the availability message | 31 | 25 people are unknown |
| Available for the shift pattern | 19 | 12 cannot work these shifts |
| Reach truck certificate valid to the end of the assignment | 14 | Ready for a recruiter to review; 5 need a renewed certificate first |
80 past applicants, 14 ready for a recruiter to review
Illustrative agency that needs 20 reach truck drivers for a client's peak in three weeks
The useful number is 14, and each drop is a task. Start sourcing for the other 6 drivers now. A recruiter still reviews each of the 14 and decides.
What changes for staffing agencies?
One pool serves many clients, so dates and context matter more.
- Tie evidence to its source. Record which client and role each answer or check came from, and when. A requirement met for one site may not cover another, and a client may ask how a placement was screened.
- Match the promise to the use. What you told candidates about future roles should match how you use the pool across clients.
How Radius helps
Radius Hire is the AI hiring platform for frontline roles. Interviews, checks and notes sit on one candidate record, so a past applicant's evidence is ready when a role reopens.
- The AI Interviewer runs a short, structured voice interview in the language set for the role. For each requirement, Radius shows whether it is backed by a document or a check, rests only on what the candidate said, or is still missing.
- Where the employer uses Radius Passport, identity and right to work are checked with a trusted verification partner and certificates are recorded with their expiry dates.
- Candidate data is hosted in the EU and processed under a data processing agreement, and the employer sets how long it is kept (Trust and compliance).
- Radius never rejects a candidate on its own. A recruiter reviews the evidence and makes every hiring decision. See how this fits staffing agencies.
What should you do first?
Start with one recurring role. Date everything that can change for its past applicants, refresh availability before the next peak, store permission with its period, recheck anything with an end date, and let a recruiter decide.