An employee in customer service applies for an opening in the planning team. She sends her CV by email to a recruiter, who forwards it to the hiring manager. A week later her own team leader hears about it at the coffee machine before she has told him herself. The planning team chooses an external candidate, and she hears that by a short phone call without any explanation. Six months later she leaves the company. Nobody meant any harm; the internal application simply never entered the same process as every other application. This article explains how to handle internal applicants in your Applicant Tracking System: why internal applications go wrong, what makes them different, what to record, who may see them, how to assess them fairly against external candidates, how to give feedback and arrange a transfer, what agencies and search firms should record when a client has an internal candidate, and how to check with your own data how internal applications really go.
Internal applicants matter for every segment. In-house recruitment teams see employees apply for other roles, for promotions and for internal vacancies posted before external advertising. Secondment firms see their own consultants apply for a permanent role at the office or for a different track within the firm. Staffing agencies and recruitment agencies recruit for their own consultant and recruiter roles, where colleagues often apply as well, and they regularly work on vacancies for which the client is also considering an internal candidate. Executive search firms often assess an internal successor alongside the external shortlist. In every case the question is the same: does the internal applicant get the same careful process as an external one, without the whole organisation knowing about it?
Why internal applications go wrong
- The application arrives by email, chat or a conversation in the corridor and never becomes a record in the system
- Too many people can see that a colleague has applied, or the current manager hears it from someone else
- Internal applicants are assessed more loosely or more strictly than external candidates, because no shared criteria are used
- A rejection is passed on by a short message, while the person stays in the same organisation and keeps asking why
- Nobody can say afterwards how many vacancies were filled internally, because the source was never recorded
None of this is bad intent. Internal applications feel informal because everybody already knows each other, while that is exactly why they need more care: the applicant stays in the organisation whatever the outcome.
What makes an internal applicant different
An internal applicant applies for the same vacancy, enters the same pipeline and is measured against the same requirements as an external candidate. Three things are different. Confidentiality weighs more, because colleagues, the current manager and sometimes the current team are close by. The current manager has a role: at some point he or she has to know, and a transfer date has to be agreed. And the applicant stays after a rejection, so the way you reject affects engagement and retention, not only your employer brand. An internal applicant is also not an internal referral: when an employee recommends someone else, that is a source for an external candidate, recorded as a candidate source, not an internal application.
What to record
Keep the structure simple enough that the whole team fills it in the same way:
- Source internal — recorded at the first application, so internal and external applicants can be separated in every overview
- Current role and department — only what the selection needs; the personnel file stays in the HR system and is not copied into the candidate record
- Visibility — who may see this application, set when it is created and not afterwards
- Current manager informed — the date, by whom, and that the applicant agreed to it beforehand
- Assessment — the same scorecard and interview outcomes as for external candidates
- Outcome and feedback conversation — the decision, the reason, the date of the feedback conversation and who held it
- Follow-up — whether the applicant agreed to be considered for future internal vacancies, and any agreed development step
Restrict who can see the application
Set the visibility of an internal application as soon as it is created: the recruiter, the vacancy owner and the hiring manager of the new team, and nobody else by default. Use the user roles and access rights of your system for that, instead of agreeing it informally; a colleague in the same department who happens to be an interviewer on another vacancy should not see the name in a shared overview. Agree with the applicant at the start when and by whom the current manager will be informed, usually before the second interview or before references are discussed, and record that date. Internal applications follow the same retention period as other candidate records, and an employee who asks what has been recorded about the application gets the same answer as an external candidate in a data access request.
The same pipeline and the same criteria
Put internal applicants in the same pipeline as external candidates, with the same entry criteria per stage and the same shared scorecard. That protects both sides: the internal applicant is not waved through because people know him, and not judged harder because people know his weaknesses. Record a written outcome after every interview, also when the conversation was informal or the hiring manager already knows the applicant. When your policy is to advertise internally first, record the internal publication period in the job advert history, so it is clear when the vacancy was opened to external candidates and why. Base the requirements on the structured brief, not on what the current team expects of a colleague they already know.
When the client has an internal candidate
Agencies and search firms meet internal applicants from the other side: the client is also considering an employee for the vacancy. Record that on the vacancy as soon as you hear it, with the date and the client contact who told you, without the name or personal details of that employee unless the client shares them and they are needed for the assignment. It changes your approach: your shortlist is compared with someone the client already knows, the decision may take longer, and the vacancy is more likely to be put on hold or closed when the internal candidate is chosen. Check the agreed client terms for what was agreed about that situation, and let the vacancy owner keep candidates informed about the expected timeline with a next-action date.
Rejection and feedback
An internal applicant who is not selected deserves a conversation, not a message. Record the rejection with a reason from your standard rejection reasons, schedule the feedback conversation with a date and a name, and record that it took place. Base the feedback on the scorecards and interview outcomes, so it is specific and the same as what was decided. Agree with the applicant whether the current manager will hear the outcome, and from whom. Ask whether the applicant wants to be considered for future internal vacancies and record the answer, so the talent pool works for colleagues as well as for runner-up candidates. An internal applicant who withdraws gets a withdrawal reason like anyone else.
Offer and transfer
When an internal applicant is selected, the offer gets an acceptance deadline like any other offer, and the transfer date needs agreement between the new and the current manager. Record the agreed handover period, which plays the same role as a notice period for an external candidate, and the confirmed start date in the new role before the vacancy is closed. Record who agreed the transfer date on both sides, so there is no discussion afterwards about when the employee was expected to start.
Let the system help
Several steps around internal applications repeat every time and suit automation: setting the source to internal for applications through an internal careers page, applying restricted visibility automatically, asking for the date on which the current manager was informed, creating a task for the feedback conversation when an internal applicant is rejected, and a reminder when that conversation has not been recorded. An artificial intelligence helper can draft a summary for the feedback conversation from the recorded scorecards and interview outcomes. The recruiter or hiring manager checks it, decides what to say and holds the conversation; artificial intelligence does not replace recruiters and does not select or reject internal applicants on its own.
Common mistakes to avoid
- Applications outside the system — an email to a manager is not an application; without a record there is no process, no confidentiality and no feedback
- Open visibility — when everybody can see the pipeline, a colleague’s application stops being confidential
- Different criteria — internal applicants judged by reputation instead of by the scorecard feel the process was unfair, whatever the outcome
- Rejection by message — a colleague who hears no reason keeps asking, or stops asking and leaves
- Current manager informed by others — the relationship with the current team suffers before any decision has been made
Questions teams ask
- Should internal applicants get an interview by default? — Agree a policy and apply it to everyone; if internal applicants who meet the entry criteria always get a conversation, record that as the rule rather than deciding case by case
- When should the current manager be informed? — At a moment agreed with the applicant, usually before the second interview or before references; record the date and who informed the manager
- Do internal applications count in time-to-fill? — Yes, measured in the same way; report internal and external fills separately so the figures stay comparable
- Is an employee who recommends someone an internal applicant? — No, that is a referral and a source for an external candidate
Check it with your own data
Count from your own records, per department and per segment: how many internal applications were received, how many have no source internal or no visibility setting, how many internal applicants reached each stage, how many vacancies were filled internally, how many rejected internal applicants had a recorded feedback conversation, and how long internal and external fills took in your time-to-fill. Review open internal applications in your weekly pipeline review, starting with rejections that have no feedback conversation yet. Report the number of applications behind each figure. Do not compare with industry averages; how your own internal applicants are treated is the number that matters.
A practical start
- Agree that every internal application enters the system, whatever channel it came through
- Record source internal and restricted visibility at the moment the application is created
- Agree with each applicant when the current manager will be informed, and record it
- Use the same entry criteria and scorecard for internal and external candidates
- Require a recorded feedback conversation for every rejected internal applicant
A colleague stays a colleague
An internal applicant is a candidate today and a colleague tomorrow, whatever the outcome. Record the application in the same process, restrict who can see it, agree when the current manager is informed, assess against the same criteria, give feedback in a conversation and record the transfer date when the move goes ahead. Explore the product or book a demo — we show how internal applications, visibility and feedback are set up in BoldATS for your segment.