Who counts as an applicant
| Person | Applicant? | Why it matters |
|---|---|---|
| Submitted an application for an open role | Yes | The base case |
| Sent a CV speculatively with no role | No, in most definitions | Counting these inflates volume and depresses conversion |
| Sourced by a recruiter and expressed interest | Only if they then applied | Otherwise sourcing effort looks like inbound demand |
| Referred by an employee | Yes, once the person themselves applies | A referral without the candidate's involvement is a lead |
| Submitted by an agency | Usually yes, on acknowledgement | Ties to the fee ownership rule |
| Applied and withdrew | Yes, historically | Withdrawal by stage is a signal about the process |
| Rediscovered from the database | No, until they respond to the new role | Otherwise the same person is counted repeatedly across years |
The definition is arbitrary. What is not arbitrary is using the same one everywhere. Where sourcing counts profiles as applications and the careers page counts only submissions, the two channels cannot be compared, and the channel that counts more generously will look cheaper per applicant and worse per hire.
What the numbers are for
- Applications per opening tells you whether the role is attracting interest. A very low number is a sourcing or positioning problem; a very high one usually means the requirement is too loosely stated.
- Applications per hire, by channel, is the honest measure of channel quality. A board that produces four hundred applications and no hires is a cost.
- Screening pass rate shows whether the applications are relevant. Consistently low rates point at the job advertisement rather than the market.
- Time to first response is the applicant-facing number and the one that predicts withdrawal among candidates who have options.
- Withdrawal by stage identifies the round that is losing people.
- Application completion rate, for anything requiring a form, is usually the largest single loss and the cheapest to fix.
All of these depend on the applicant definition holding still. Changing it mid-year, which usually happens when a new system is introduced, breaks every comparison with the previous period and is worth stating explicitly when the numbers move.
What is owed to an applicant
Applying creates a relationship, thin but real, and it carries obligations from the moment of submission.
- Notice at collection: what the data will be used for, how long it will be held, and who else will see it, including verification and assessment vendors.
- Collection limited to what the decision needs. Date of birth, marital status, community and photographs are collected out of habit and each is a field you must then justify.
- An outcome. Everyone who applies should be told, including at the CV stage, where an automated but clear message is far better than silence.
- A process that does not exclude people for reasons unrelated to the role, including a form or assessment that a disabled applicant cannot use.
- Retention with a stated end. Holding applications indefinitely against a future opening is a purpose beyond the one notified.
- An answer if they ask what happened to their data, which requires knowing where it is, including the copies with agencies and vendors.
Verify the data fiduciary obligations, the notice requirements and the erasure position under the Digital Personal Data Protection Act, 2023 and the rules made under it before setting a retention rule. Note the timing before building anything around it: those duties are not yet in force. Sections 3 to 17 of that Act, which carry the grounds for processing, notice, consent, the obligations of a data fiduciary and the data principal rights, take effect on 13 May 2027 under the commencement notification of 13 November 2025. The definitions, the Data Protection Board and the penalty machinery commenced in November 2025.
The rejected majority
A role with two hundred applicants and one hire produces one hire and a hundred and ninety-nine rejections. Whatever reputation the organisation has as an employer in that market was mostly formed by the second group, and it is formed cheaply or expensively depending on three things.
- Whether they were told at all. Silence is what applicants complain about most, and it costs nothing to fix.
- How long it took. A rejection two days after an interview is respectful; one six weeks later, after two chases, reads as contempt.
- Whether anyone who reached an interview received a reason specific enough to be believable. Generic wording is transparently generic and is worse than being brief.
The commercial argument is straightforward: in consumer businesses the applicant is frequently also a customer, rejected applicants who were treated well refer others, and the strong candidate rejected this year is often the right hire in two years, if they will still take the call.
Statutory reference
- Act
- Digital Personal Data Protection Act, 2023
- Section
- Digital Personal Data Protection Act, 2023 and the rules made under it: obligations of a data fiduciary in respect of applicant personal data, including notice at the point of collection, purpose limitation, accuracy, security safeguards, erasure once the purpose is served, and responsibility for a processor such as an agency or verification vendor. Code on Wages, 2019: prohibition of discrimination in recruitment in respect of the same work or work of a similar nature. Rights of Persons with Disabilities Act, 2016: non-discrimination in recruitment and accessibility of the application and assessment process. In force 21 November 2025 for the Code on Wages
- Key limits
- Obligations to an applicant's personal data begin at submission, not at shortlisting, and retaining applications for future openings is a purpose beyond the one notified. An application form or assessment a disabled applicant cannot use is a selection barrier. Under notification G.S.R. 843(E) dated 13 November 2025, sections 3 to 17 - the grounds for processing, notice, consent, the general obligations of a data fiduciary and all of the data principal rights - take effect eighteen months from that date, on 13 May 2027. Only the definitions and the Data Protection Board and penalty machinery are in force now. Separately, processing for employment purposes runs on the section 7(i) legitimate use and not on consent, and the erasure duty in section 8(7) yields where retention is necessary for compliance with any law, which is the position for statutory payroll and register retention. Section 20 non-discrimination in employment, the section 20(2) duty to provide reasonable accommodation and a barrier-free environment, the section 20(4) protection of an employee who acquires a disability in service, the section 23 Grievance Redressal Officer and the section 34 four per cent reservation all bind government establishments only. What binds every establishment, private included, is section 21, notifying an equal opportunity policy and registering it with the Chief or State Commissioner, and section 22, maintaining records of persons with disabilities open to inspection. For the private sector section 35 provides government INCENTIVES towards a five per cent workforce target, not a quota. The general prohibition that does reach private conduct is section 3(3), and it carries a defence where the act or omission is a proportionate means of achieving a legitimate aim. Reasonable accommodation is defined in section 2(y) as excluding what would impose a disproportionate or undue burden. Sections 3 to 17, which carry the duties described here, commence on 13 May 2027 under G.S.R. 843(E) of 13 November 2025. In force now are the definitions, the Data Protection Board and the penalty provisions.
Frequently asked questions
What is an applicant?
A person who has submitted an application for a specific role. The word is often stretched to cover anyone whose CV is in the system, which is why application volume and conversion rates frequently mean different things in different reports within one organisation.
Does a sourced candidate count as an applicant?
Only once they actually apply, in most workable definitions. Counting sourced profiles as applications makes outbound effort look like inbound demand and destroys any comparison between channels.
How many applicants per hire is normal?
It varies too much by role and channel for a benchmark to help. The number is useful compared against your own channels on a single definition, where a source producing hundreds of applications and no hires is visible as a cost.
Do we have to respond to every applicant?
There is no statutory duty to, and silence is the most common complaint applicants report and the cheapest thing to fix. An automated but clear rejection at the CV stage is far better than nothing, and anyone who reached an interview deserves a specific reason.
How long can we keep applications?
Only as long as the purpose you gave notice of requires. Keeping applications indefinitely against future openings is a further purpose that needs its own basis and notice, so set a retention period and apply it rather than accumulating an archive.
How Engage counts applicants
Engage applies one applicant definition across every channel, so applications per hire compares a job board against a referral rather than comparing two counting conventions. Every applicant carries the date and purpose their data was collected for, and rejections can be issued in bulk with a clear message instead of being left as silence.
See recruitment in Engage