Cost per qualified applicant: a worksheet for fair campaign comparisons

Cost per qualified applicant divides a declared campaign cost by the number of applicants confirmed to meet an agreed role requirement. For a fair comparison, use the same qualification rule, deduplication method and review cutoff, and report applications still awaiting review separately.

Key facts

• Define qualification against the role before launch and name the person responsible for review.
• State whether the numerator includes only media or the full declared allocation of costs.
• Keep duplicates, reviewed applications and pending reviews visible in the same ledger.
• Use a stable application cohort and revisit it after the agreed review window.
• CPQA concerns the application stage; it does not measure employee performance or recruiting return on investment.

What counts as a qualified applicant?

Start with the job-relevant requirements that a recruiter can assess consistently. Record what evidence is needed, where the decision is stored and who owns the review. Agree this rule before launch so the campaign is not judged against a threshold selected after its results arrive.

An answer to an automated screening question is evidence for assessment; it is not automatically a recruiter-confirmed qualification decision. Keep the answer and the reviewed outcome distinct. If the team changes the requirement, record that change and explain which applications were assessed under each version.

Qualification at this stage also differs from performance after someone joins. An applicant can meet the agreed role requirement without yet providing evidence about retention or proficiency. Use the quality-of-hire measurement guide for those later employee outcomes. Keep the application ledger focused on what the team has actually reviewed.

Which cost should go into the numerator?

Choose the cost scope before calculating the ratio. Media-only CPQA = media spend / qualified applications. Fully allocated CPQA = included media, platform, service, creative and operations cost / qualified applications. Label these measures separately instead of presenting them under one unexplained cost figure.

Name the allocation period and the application cohort. Record which costs belong to that period and how any shared costs are assigned. Keep the same allocation method when comparing campaigns; otherwise the cost can change because of the accounting boundary you chose, even when the underlying applications are unchanged.

This worksheet uses qualified applications as the denominator, not hires. It does not calculate ROI. If no applicant has been confirmed as qualified, report the spend and zero qualified applications. The ratio is undefined: neither a zero cost nor a guessed denominator describes that situation accurately.

Keep the underlying amounts alongside the ratio. A reviewer should be able to reproduce the calculation from the declared cost and application count without having to infer what was included.

How should the application ledger be prepared?

Choose the cohort’s application dates, role scope and review cutoff, then preserve that cohort for later checks. State the unit being counted. For this worksheet, use unique job applications after removing repeat submissions under the declared rule. State explicitly whether a person applying to different jobs counts as one person or as separate job applications in your reporting.

The illustrative ledger below shows how the statuses reconcile. Copy the structure and replace the counts with your own reviewed records; these numbers are an example, not a benchmark.

Ledger field	Illustrative count	Interpretation
Submitted applications	100	Raw submissions in the chosen cohort
Duplicate submissions removed	10	Removed under the declared rule
Unique applications	90	Records eligible for review
Reviewed applications	60	Assessment recorded by the cutoff
Qualified applications	30	Subset of reviewed applications meeting the rule
Reviewed, not qualified	30	Remaining reviewed applications
Pending review	30	Outcomes still unknown

The 100 submitted applications include 10 duplicates, leaving 90 unique applications eligible for review. Of those 90, 60 have been reviewed and 30 remain pending. Within the 60 reviewed records, 30 are qualified and 30 are not qualified under the agreed rule.

Qualified records are a subset of reviewed records. Do not add all three figures together as if they were separate groups. Likewise, pending records sit within the unique application cohort; they are not additional submissions. Check these relationships before calculating a ratio. If the counts do not reconcile, resolve the ledger rather than burying the discrepancy in a cost metric.

How does review lag change the result?

Use the same illustrative cohort with media spend of 1,200 budget units and total included cost of 1,800 units. With 30 qualified applications, media-only CPQA is 1,200 / 30 = 40 budget units. Fully allocated CPQA is 1,800 / 30 = 60 budget units.

Both figures are provisional because 30 unique applications remain unreviewed. Pending applicants are not rejected, qualified or lost. Their outcomes are unknown at this cutoff. Include the pending count beside the result so the reader can see how much of the cohort still awaits assessment.

If later review adds 10 qualified applications and the costs for that cohort remain unchanged, the qualified denominator becomes 40. Media-only CPQA becomes 1,200 / 40 = 30 budget units; fully allocated CPQA becomes 1,800 / 40 = 45 budget units.

That change is arithmetic following additional review, not evidence that advertising improved the campaign. Revisit the same cohort at the planned review cutoff and record the remaining pending count. Do not silently replace the earlier applications with a newer cohort or classify every remaining record as rejected. Retain the earlier result as a dated, provisional observation so the change can be explained.

What makes two campaigns comparable?

Compare similar role requirements, markets, application windows and review practices. Align the cost scope and allocation period as well. A media-only result from one campaign cannot be compared directly with a fully allocated result from another without explaining and reconciling the difference.

Check how mature each cohort is. If one team has reviewed its applications and another is still working through them, their observed denominators represent different review stages. Show the reviewed, qualified and pending counts together. Where the number of applications is small, keep those counts beside any reported rate rather than letting a percentage conceal the sample size.

A changed qualification threshold can alter the denominator. A delay in recruitment review can also alter the result at a given cutoff. Neither observation alone establishes that advertising caused a change in candidate quality. Before interpreting a difference, ask whether the requirements, reviewers, deduplication rules and reporting boundaries stayed consistent.

Use the comparison to locate the difference that needs investigation. Keep separate explanations visible instead of collapsing them into a single verdict about the campaign.

How should the team use the result?

Review the ledger together with the people who own campaign delivery, application handling and qualification. Start by confirming that the costs and counts reconcile. Then ask where the workflows differ: the application route, the review timing, the agreed requirement or the recording of outcomes. CPQA provides a question to investigate; it is not an automatic instruction to stop a campaign.

Where applications move into an ATS, confirm that the fields needed for the ledger reach the intended record and can be interpreted consistently. Adway publishes an ATS and CRM integration directory. Buyers should verify the actual connection, field mapping and responsibilities for their configuration. A listing alone does not prove a tested bidirectional connection or universal support.

Keep the calculation, cutoff and unresolved records together when sharing the result. Agree when the same cohort will be reviewed again and who will update the ledger. The worksheet makes the comparison reproducible; it does not promise a lower cost or better hiring outcomes.

Book a demo to walk through one approved role, its application journey and the handoff to your recruiting system.

Sources

• Adway integrations: published ATS and CRM directory, checked 6 November 2026. Confirm the application-to-ATS mapping for the proposed configuration.
• The ledger and budget-unit calculations are illustrative Adway editorial examples. They are not customer results, vendor prices or evidence of an advertising improvement.

Start with one role. Verify the whole journey.