Using applicant quality feedback to improve recruitment advertising

Applicant quality feedback is useful when the team can connect a consistent review reason to a specific campaign decision.

Adway 7 min read
A closed neon loop linking a campaign card, reviewed records and one precise creative adjustment.

Applicant quality feedback is useful when the team can connect a consistent review reason to a specific campaign decision. Separate missing job requirements, unclear messaging, delivery errors and unreviewed applications before changing targeting or creative; a rejected or pending application is not automatically evidence of poor advertising.

Give the advertising team a reason it can investigate. A general statement that applications are poor does not identify whether the problem is the role description, the application route or a review that has not happened yet. The useful feedback connects an agreed hiring requirement with evidence from a defined set of applications and a specific next action.

Key facts

  • Share approved, role-related reasons and aggregate counts rather than full candidate notes.
  • Keep reviewed outcomes, clarification needs and pending reviews separate.
  • Use a fixed application period and an agreed review window before judging a cohort.
  • Match one verified issue with one campaign change to test.
  • A before-and-after improvement is an observation, not proof that the edit caused it.

Which feedback should reach the advertising team?

Start with the requirements recruiters and hiring managers have agreed for the role. Use the candidate qualification rubric to distinguish essential criteria, trainable preferences and information that still needs clarification. Feedback becomes difficult to interpret when reviewers use the same label for different reasons.

Keep four review states visible: reviewed and meets the agreed criteria, reviewed and does not meet them, needs clarification, and pending review. These states describe what the team knows at the reporting cutoff. A record awaiting review does not carry the same evidence as a completed review, and a clarification request is not a confirmed mismatch.

Share the minimum approved information needed to diagnose the campaign issue. Aggregate counts and consistent role-related reason codes can describe a pattern without copying full candidate notes into a marketing report. Follow the organisation’s access and data-handling rules. Keep sensitive personal details out of the advertising feedback worksheet.

Ask the receiving team to explain the reason definition before acting on it. Confirm that the reviewer applied the approved role criteria and that the application belongs to the intended vacancy. If the record reached the wrong job, the immediate issue is the delivery route. Changing the advert’s audience would not repair that mapping problem.

When is the cohort ready for a decision?

Fix the application period and reporting cutoff. Record which unique applications belong to the cohort, which review window has been agreed and how many outcomes remain unresolved. This makes it possible to distinguish a completed review from a changing snapshot of work still in progress.

Allow the agreed review window to pass before drawing a conclusion that depends on completed reviews. If the window closes with applications still pending, show that limitation rather than assigning those records to the unsuccessful group. Name the review owner and the next step for resolving the backlog.

Do not compare a mature cohort with another that is still being reviewed as though their labels were equally complete. Preserve the application dates, review timing and pending counts for both. If reporting has to happen before completion, describe the figures as provisional and retain a later checkpoint for the outstanding outcomes.

Reconcile the application source separately from the review decision. The recruitment advertising attribution guide explains how to compare ad reports with ATS applications. Establish which records belong in the campaign cohort before interpreting their quality; a source label alone does not establish that two reports count the same people.

How should a review reason become a campaign change?

Use the table to connect a reviewed signal with a verification step and a candidate intervention. The proposed change follows the diagnosed issue. It is not an instruction to change targeting whenever an application is rejected, and it does not assume that advertising caused every mismatch.

Reviewed signalVerifyCandidate change to test
Shift misunderstoodApproved shift and actual ad wordingMake the shift explicit before the application
Required skill unclearRole-related requirement and reviewer agreementClarify the task and evidence requested
Record reaches wrong vacancyATS mapping and source IDRepair the delivery route
Many reviews pendingOwner and available review timeComplete reviews before judging quality

Confirm the underlying role fact with the hiring manager before revising the creative. For a misunderstood shift, check both the approved shift and the wording candidates saw. If the advert omitted that information, a clearer message is a specific change the team can test. Do not change the role requirement to make the campaign figures look better.

For an unclear skill requirement, establish what the task requires and what evidence reviewers expect. Make the request understandable before candidates apply. If reviewers disagree about the requirement, resolve that disagreement before turning their reasons into a campaign instruction. An ambiguous review standard cannot reliably explain an advertising problem.

Keep remedies within the authorised recruitment process. Do not change audience eligibility based on protected or inferred personal traits. This workflow is not a legal or automated fairness guarantee. A delivery error calls for a routing repair; a pending-review problem calls for review ownership and time. Neither is evidence that a different audience should be excluded.

How should the team verify whether the change helped?

Record the exact change, its implementation date, the verified issue it addresses and the person responsible for the later check. Preserve the previous message so the team can explain what was altered. Avoid changing several unrelated parts of the campaign and then treating the result as evidence for one particular edit.

Review suitable later cohorts using the same reason definitions. Show their application dates, volumes, review windows and unresolved outcomes. Check whether the diagnosed issue appears again and whether the later cohort has had a comparable opportunity to be reviewed. Keep the outcome counts visible rather than relying on a single percentage.

Record other changes that affect the interpretation, such as a revised role requirement or different review timing. A before-and-after difference can be useful operating evidence, but it does not isolate the cause. Report what changed and what remains uncertain without promising that clearer creative will produce a particular hiring result.

If the team also wants to compare cost, use the cost per qualified applicant worksheet with consistent criteria and the appropriate cost scope. Keep that calculation separate from diagnosing the review reason. This workflow does not establish that an advertising platform automatically receives ATS outcome labels or uses them to optimise delivery.

What does a worked example show?

Illustrative cohort of 40 unique applications: 20 meet the agreed criteria, 10 do not, 5 need clarification and 5 are unreviewed. Six of the 10 reviewed mismatches concern a shift absent from the creative. The proposed intervention is to show the verified shift, not to label all 20 remaining candidates unqualified. Evaluate a later cohort using the same definitions and show unresolved outcomes separately. These are invented teaching numbers, not Adway results.

First retain all four groups in the report. The team has a reviewed group meeting the criteria, a reviewed mismatch group, a clarification group and a pending group. Combining the last three would erase the difference between a known mismatch and a result the team has not established.

Next, investigate the shift reason within the reviewed mismatches. Check the approved shift with the hiring manager and confirm that it was absent from the creative. The proposed change is then specific: show the verified shift before the application. Keep the other mismatch reasons and unresolved reviews visible instead of assuming that the same change addresses them all.

After the change, review a suitable later cohort with the same definitions and reporting discipline. Record its counts and pending outcomes, along with any other changes. The example intentionally supplies no later result, improvement rate or expected hiring benefit. Its purpose is to show how a reviewed reason can lead to a testable decision without mislabelling candidates.

Where should the team go next?

Choose one approved role and agree the review states, reason definitions and reporting cutoff with the hiring manager. Then identify one verified campaign or delivery issue, assign its owner and record the proposed change. Keep the worksheet small enough that the receiving team can maintain it alongside its normal reviews.

Adway’s Social Apply describes an application workflow with role information and configurable screening questions. A demonstration can help you inspect the proposed candidate journey and ATS handoff for your role. Confirm what information is collected, where it arrives and who reviews it rather than assuming the qualification worksheet or feedback loop is automated.

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

Sources

  • Adway Social Apply: supplier description of role information and configurable screening questions in the application workflow, reviewed 20 November 2026.

This guide is published by Adway. The feedback table and numerical cohort are original teaching examples, not customer results or a measured campaign test. Product documentation does not establish a conversion advantage, guaranteed candidate quality or an automated feedback integration.

Start with one role. Verify the whole journey.

Frequently asked questions

Should pending applications count as unqualified?

No. Report them separately until the agreed review is complete.

Can rejection reasons guide recruitment advertising?

They can support a decision when reasons are consistent, role-related and connected to a verified issue in the campaign or application journey.

Should marketers receive full candidate notes?

Use the minimum approved information needed for the task, such as aggregated role-related reasons. Follow the organisation’s access and data-handling rules.

Does improved quality after an edit prove the edit caused it?

No. Other changes, cohort differences and review timing can affect the result. Record them and describe the limits of the comparison.