Planning employer branding software requirements

What to take away

Define the outcomes your employer branding software must report on, including candidate attraction, talent community activity and careers-site performance.
Compare platforms against the same requirements and demonstration tasks rather than feature claims.
A written, weighted requirements list stops a polished demo turning into a decision you regret.

Why selection changed recently

If early talent activity is in scope, decide whether the software needs to track cohorts, placements and outcomes. The government's announcement about work and training placements for young people can prompt questions about the data your programme needs to report.

Recruitment tooling has consolidated. Sourcing, pipeline management and reporting can sit in one platform, so buyers should compare suite coverage rather than single features. This guide covers the requirements and the procurement method; it does not shortlist named vendors. Our guide to employer branding tools and suppliers covers the supplier market itself.

Budget cycles matter too. Software bought mid-year often lands outside the agreed plan, so start scoping two quarters before your renewal date.

What to put in your requirements

Start with outcomes, not a feature list. Write one sentence for each of: candidate attraction, talent community nurture, careers site content, reporting and compliance.

Requirements checklist

Write one outcome sentence per area
Map each sentence to measurable test
Separate must-haves from preferences
Demo identical task across vendors
Ask data protection questions in writing

Then map each sentence to a measurable test. A team paying £400 a month for a careers site tool should expect a monthly report showing source-to-application conversion by channel. If the vendor cannot show that in a sandbox, the requirement is unmet.

Separate must-haves from preferences. Must-haves are pass or fail, such as UK data residency, a documented export route and reporting against the outcomes you named. Specify where data may be stored and accessed, which fields must be exportable, the export format and what happens to data at exit. UK data residency is not a blanket requirement for every organisation; if data is stored or accessed outside the UK, ask how the supplier handles international transfers under UK GDPR. Preferences carry scores. Mixing the two lets a weak vendor survive on a good presenter.

Ask each vendor to demonstrate the same task: load a candidate, tag them to a talent pool, and show where that action appears in reporting. Identical tasks make demos comparable.

Requirement lines you can copy

Each line below is written as a test the vendor passes or fails in the sandbox. Delete the ones outside your scope and weight the rest.

Careers site:pages can be edited by the in-house team without a developer, and job pages publish JobPosting structured data (schema.org) so roles can be picked up by job search features.
Applicant tracking link:new applications and talent pool tags pass to and from your applicant tracking system through a documented API or scheduled file export, with field mapping shown in the demo.
Talent community:candidates can join without applying, choose the topics they hear about, and withdraw consent in one step.
Multi-brand use:separate brands, locations or business units can run their own pages and campaigns while reporting rolls up centrally.
Access:single sign-on with your identity provider, role-based permissions and an audit trail of who changed what.
Reporting:source-to-application conversion by channel, exportable without asking the vendor.
Data exit:full export of candidate, consent and content records in a common format such as CSV or JSON, with the deletion route at contract end confirmed in writing.
Data protection:a named list of sub-processors, the storage location, and retention settings the employer controls.

Include data protection early. Ask where candidate data is stored, how long it is kept and who can export it. The Information Commissioner's Office (ICO) is the UK's data protection regulator, and the Data Protection Act 2018 sits alongside the UK GDPR. Your organisation will usually be the controller for candidate data it decides to process, while a supplier may act as processor; document those roles and any international transfer arrangements in writing. A supplier who cannot answer in writing is a risk you carry.

How to run the procurement

Score each vendor out of five on fit, integration, reporting, support and total cost. Weight the scores before you see any demo, so a polished presentation cannot move the numbers.

Keep one scoring sheet for every vendor, and give each panel member the same weightings. Review recorded demos against that sheet the same day. Decisions left a week drift towards the slickest demo.

For wider channel context, consult IAB UK's digital advertising research alongside your own campaign data. It can inform assumptions about formats and spend, but it is not a software price benchmark or evidence for a vendor's reach claims.

Decision table

Choose

Small in-house team, one careers site: Modular tool with clear pricing per seat
Early talent programme with cohorts: Software with cohort tracking and placement reporting
Multiple brands or regions: Platform with role-based access and shared reporting
Limited marketing budget: Tool with native analytics and export
Strict data protection review: Supplier with UK data residency and audit trail

Avoid

Small in-house team, one careers site: Enterprise suite with unused modules
Early talent programme with cohorts: Tools that only track applications
Multiple brands or regions: Single-user licences shared by email
Limited marketing budget: Add-ONS charged per report
Strict data protection review: Vendors who cannot name a sub-processor

Once the requirements are scored, our employer branding supplier comparison for England is the place to test them against suppliers.

What to do in the first 90 days

Sign nothing until the pilot is complete. A 30-day pilot with real candidates and one live campaign exposes integration gaps faster than any reference call.

Budget for implementation time, not just licence fees. Assume a fortnight of marketing time for content migration and a day a week from IT during onboarding. Vendors rarely price that in, and it lands on your team.

Agree success measures in the contract: time to shortlist, cost per application, and the share of roles filled from your talent community. Set a review date at 90 days.

Nominate one owner for the tool after go-live. Shared ownership is often why adoption stalls in month three.

Keep an exit plan. Ask for a data export in a common format and confirm the notice period, because leaving cheaply matters more than any roadmap promise.

Common questions

How long should selection take?

Eight to twelve weeks from scoping to a signed contract for most in-house teams. Compressing it below six weeks usually means skipping reference checks or the pilot.

Do we need a recruitment marketing suite or a point tool?

It depends on channel count. Teams running three or more channels get less manual reporting from a suite, while single-channel teams often get better value from a focused tool.

Who should own the decision?

HR owns candidate experience, marketing owns content and channels, IT owns integration and security. One named person should hold the budget and the final call.

What is the biggest cause of failed implementations?

Unclear requirements before demos. Teams that write and weight criteria first report fewer surprises during onboarding.