An experienced maintenance engineer emails his CV with a short note: no vacancy fits right now, but he would like to work for you or your clients. The message lands in a shared inbox, someone forwards it to a recruiter who is on leave, and three weeks later a client asks for exactly this profile. Nobody remembers the email, and the engineer has since accepted a role elsewhere. Open applications are one of the cheapest sources of motivated candidates, but only if they are handled as carefully as applications for a vacancy. This article explains how to handle open applications without a vacancy in your Applicant Tracking System: what goes wrong without a fixed route, how to set up intake and ownership, how to review and tag them, how to deal with consent and retention, how the approach differs per segment and how to check with your own data whether open applications lead anywhere.
Open applications arrive in every segment. Recruitment agencies receive CVs from professionals who want to be considered for future client roles. Staffing desks receive registrations from flexible workers who simply want work in their region. Secondment firms hear from specialists who are open to an assignment. Executive search firms receive unsolicited CVs from senior candidates who are quietly exploring the market. In-house recruitment teams receive open applications via the careers page from people who want to join the organisation. In every case the question is the same: does each open application get a recorded answer and a place in your pipeline, or does it disappear into someone’s mailbox?
What goes wrong without a fixed route
- Open applications sit in personal or shared mailboxes and never become a candidate record
- Nobody feels responsible, so the candidate never hears back
- The same person applies again later and is entered as a new candidate
- A suitable candidate is overlooked when a matching vacancy opens, because the profile was never tagged
- Personal data is kept without a clear agreement on how long and for what purpose
The result is lost candidates, a weaker employer or agency reputation and data that is hard to justify when a candidate asks what you keep about them.
One intake route into the system
Start by making sure every open application ends up in the same place. Keep it practical:
- A dedicated open application form or pool — the careers page and website offer one route for applications without a vacancy, linked to a general pool instead of a fake vacancy
- Emailed CVs are entered, not forwarded — whoever receives an open application by email creates or updates the candidate record and attaches the message
- Check for an existing record first — merge with an existing candidate instead of creating a second record
- Record the source — note that the candidate came in through an open application, so you can later see what this source delivers
- A few basic questions — desired type of work, region and availability, asked through short screening questions rather than a long form
This way every open application becomes a findable candidate record from the first day.
A named owner and a first-review deadline
A general pool without an owner fills up quickly and is rarely looked at. Assign one recruiter or a small rota as owner of open applications and record that owner in the system. Give every new open application the same first-review deadline as a regular application, so the candidate receives an answer within a predictable time. The owner decides per candidate: add to a current vacancy, keep in the talent pool with tags, or decline with a short, respectful message. A shared message template helps here, as long as the recruiter adds a personal sentence when it matters.
Tag for later, not for show
An open application is only useful later if you can find it. Use the shared skills and tag list instead of free text, record the preferred work location and travel radius and give every candidate in the pool a next-action date, for example a check-in after a few months. When a new vacancy opens, search the pool before you start external sourcing, in the same way you would re-engage runner-up candidates.
Consent and retention
A candidate who applies without a vacancy expects you to keep their details for future roles, but not indefinitely. Tell the candidate how long you keep their data and for what purpose, in line with your own privacy statement, and record that agreement on the candidate record. Set a retention date and ask before the date passes whether the candidate wants to stay in your pool. Ask for consent before every submission to a client, and make sure you can answer a data access request from the same record.
Differences per segment
Agencies use open applications mainly to build a pool per specialism and region, and decide per candidate which recruiter or desk follows up. Staffing desks treat open registrations as the start of a flexible pool and combine them with confirmed availability, so candidates can be scheduled quickly. Secondment firms record which type of assignment and which start period a specialist is open to, so the profile appears when a client asks. Executive search firms handle unsolicited senior CVs with extra discretion, record any off-limits agreements that apply and keep the profile visible only to the people who need it. In-house teams answer every open application on behalf of the organisation and decide with hiring managers which departments want to see open applications at all.
Let the system help
Much of the handling repeats and suits automation: confirming receipt to the candidate, assigning the application to the owner, flagging applications that pass their review deadline, reminding the owner of next-action dates and retention dates and alerting a recruiter when a new vacancy matches tags in the pool. An artificial intelligence helper can suggest tags from a CV or propose pool candidates for a new vacancy. The recruiter checks the suggestion and decides what happens next; artificial intelligence does not replace recruiters and does not decline or submit candidates on its own.
Common mistakes to avoid
- A fake vacancy as a catch-all — reports on time-to-fill and close reasons become unreliable
- No reply at all — the candidate assumes the application was lost and does not apply again
- Free-text notes only — the profile cannot be found when a matching vacancy opens
- Keeping data without an agreement — the pool grows, but you cannot explain why you still hold each record
- One owner without cover — open applications stall during holidays and busy periods
Questions teams ask
- Should every open application receive a personal answer? — Every candidate should receive an answer; a template is fine, with a personal sentence for candidates you want to keep in touch with
- Who owns open applications? — One named recruiter or a small rota, recorded in the system, with a stand-in for absences
- Do open applications count in pipeline reports? — Report them separately as a source and as a pool, and count them in vacancy pipelines only once they are added to a vacancy
- How long do we keep the data? — As long as your privacy statement and your agreement with the candidate allow; record the date and ask before it passes
- What if a candidate applies openly and for a vacancy at the same time? — Keep one record and follow the approach for one candidate in several vacancies
Check it with your own data
Count from your own records, per team and per segment: how many open applications came in, how many received an answer within the review deadline, how many were added to a vacancy later, how many led to a placement and how many records passed their retention date without a decision. Discuss these figures in your weekly pipeline review and report the number of candidates behind each figure. Do not compare with industry averages; your own trend is the number that matters.
A practical start
- Create one intake route and one general pool for open applications
- Name an owner and a stand-in and record them in the system
- Apply the same first-review deadline as for regular applications
- Tag every pool candidate and set a next-action date and a retention date
- Search the pool first whenever a new vacancy opens
Every open application deserves an answer
Candidates who apply without a vacancy have already chosen you. Give them one intake route, a named owner, a prompt answer, clear tags and a recorded retention agreement, search the pool before sourcing elsewhere and check your own figures. Explore the product or book a demo — we show how candidates, talent pools and the pipeline work together in BoldATS for your segment.