Duplicate job advertising: controls for branch recruitment teams

Duplicate job advertising should be controlled through vacancy identity and campaign ownership, not by deleting every repeated title. Separate genuinely different openings from repeated representations of the same opening, then decide which team owns the campaign and where candidates should apply.

Key facts

• Two jobs with the same title can be legitimate separate vacancies.
• One vacancy can appear under different titles or identifiers across systems.
• Duplicate advertising and duplicate applicant records are different problems.
• Resolve ownership before merging campaigns or removing destinations.

What counts as a duplicate vacancy?

Define a vacancy in operational terms: the employer or client, requisition, workplace, role requirements and hiring decision it represents. A title alone is a weak identity key. Several branches can recruit warehouse operatives for different sites, while two feeds can describe the same site under different names.

Distinguish a duplicate record from an intentional multi-channel campaign. Advertising one approved vacancy on several platforms is not automatically duplication. The concern is uncontrolled overlap: multiple owners promoting the same opening without shared identity, budget responsibility or applicant handling.

Also distinguish one requisition with several hires from several requisitions. A campaign for multiple identical openings can be appropriate when the source record and application route explain that structure. Do not combine roles with different shifts or requirements simply because a consolidated report would look tidier.

How do you find duplicates without blocking legitimate roles?

Start with stable source identifiers and add contextual checks. Where systems use different IDs, create a mapping rather than replacing both with a title-based guess. Keep the original values so an operator can trace the campaign back to its source.

Use similarity as a review signal, not an automatic verdict. Similar title, location and client names can identify candidates for inspection. A recruiter should confirm whether they represent the same hiring requirement before anything is merged or stopped.

Pattern	Possible explanation	Safe next check
Same source ID in two feeds	Repeated export	Identify the authoritative feed
Same title, different site	Separate genuine openings	Compare workplace and requisition
Different titles, same requisition	Local naming variation	Confirm one vacancy owner
Same client, different agency briefs	Separate assignments or overlap	Review the actual approved briefs
Reopened role with a new ID	New hiring cycle or duplicate creation	Ask the source-system owner
One vacancy, several channels	Planned distribution	Check shared campaign ownership

Give each reviewed pair a decision and reason. Otherwise the same ambiguous records will return to the exception list every week.

Who should own advertising when branches overlap?

Choose the owner closest to the hiring responsibility, with a documented exception for central campaigns. The owner should approve the destination, maintain current role facts and decide when the campaign stops. Other teams can contribute creative or distribution without becoming competing sources of truth.

For staffing agencies, clarify the relationship between the agency brand, client assignment and recruiting branch. A shared client name does not establish that two branches are advertising the same assignment. Use the authorised client brief and vacancy references rather than making assumptions from public job descriptions.

Record who can make urgent changes when the primary owner is unavailable. Ownership that exists only in a spreadsheet can fail during leave, branch transfers or a role closure. Keep a backup and make the escalation route visible to campaign operators.

The closed-vacancy workflow is especially important here: stopping the central campaign does not close an independently managed branch campaign.

What does a practical reconciliation exercise look like?

Consider a hypothetical employer with three branch exports and six campaign records. Two records share requisition R-41 but use different titles. Two more have the same title but different sites. The remaining pair refers to a reopened role with an old and a new identifier.

The team confirms that the first pair represents one opening and selects the authoritative record. It retains the second pair because the workplaces and hiring decisions differ. For the reopened role, it checks whether the old campaign should remain closed and maps the new hiring cycle explicitly.

Nothing in this example establishes wasted spend or a performance improvement. The exercise produces a controlled inventory: known identities, known owners and explainable campaign relationships. Any effect on applications or costs must be measured after implementation.

Keep the before-and-after mapping. Removing a duplicate without retaining its history can make earlier reports appear to lose a vacancy. Historical campaign records should remain traceable even when future advertising uses a single approved identity.

How should duplicates affect reporting and applications?

Report at a defined level: vacancy, campaign, branch or hiring cycle. If one vacancy has several campaigns, aggregate them through the mapping while retaining the underlying records. Do not add vacancy counts and campaign counts together as if they described the same unit.

Applicant deduplication needs its own decision. The same person applying to different vacancies is not automatically an invalid duplicate. A repeated technical delivery of one submission is different from two intentional applications. Confirm the relevant ATS behaviour through the application handoff acceptance test.

Check that candidates still reach a suitable destination after consolidation. If one branch’s ad promises a specific workplace, redirecting everyone to a generic national vacancy list can undermine that promise. The campaign identity fix should preserve the candidate’s understanding of the opportunity.

Which controls should remain after the cleanup?

Introduce a pre-launch check for existing active campaigns against the same authoritative vacancy. Keep a review queue for ambiguous matches and a clear rule for reopened roles. Re-run the mapping check when a branch, feed or supplier is added.

Track unresolved identity exceptions and their owners. Review changes to the naming convention, but avoid asking recruiters to remember a complex manual code when stable source identifiers already exist. A naming convention helps people read a campaign; an identity mapping helps systems and reports relate it correctly.

Adway describes Always-On Job Ads as turning vacancy information into social recruitment campaigns. Use a demonstration to inspect how your proposed source identifiers, branch responsibilities and campaign records relate. Do not infer duplicate controls or cross-account behaviour from that general description.

For a structured discussion, bring two genuinely different roles and one confirmed duplicate to the walkthrough. Those examples reveal more than a clean sample containing only unique openings. Book a demo to examine the workflow with Adway.

Sources

• Adway Always-On Job Ads, product description checked 2 November 2026.
• The identity matrix and branch example are original operational recommendations, not measured customer outcomes.

Give every real opening a clear identity and every campaign a clear owner.