Private-Label ATS: What Recruitment Agencies Should Check
Candidate data ownership, per-client separation, what your branding actually reaches, and the exit clause that decides who keeps the database.
Overview
A private-label ATS is an applicant tracking system a recruitment agency sells or operates under its own brand rather than the vendor's. Agencies reach for it for two different reasons, and the reasons lead to different diligence. Some want their own delivery platform to look like theirs to candidates and clients. Others want to resell the ATS to their clients as a product, adding a revenue line to a placement business.
Both are workable. But recruitment carries a complication that other white-label software categories do not: the asset at stake is your candidate database, and the vendor is holding it. Everything below follows from that.
- Settle candidate data ownership and export before anything else — it is the only irreversible term.
- Check that per-client separation is architectural, not a permission setting someone has to remember.
- Test the artefacts candidates actually see: careers page, application form, and every automated email.
Candidate data ownership comes first
An agency's database is its balance sheet. Before branding, before pricing, before a demo, get three things in writing.
Who owns the candidate records. Not who "has access" — who owns them. Some vendor agreements are silent, which is not the same as favourable.
What export looks like, tested. Ask for the export format and schema, and run a real export on real data during evaluation rather than accepting a yes. Confirm whether it includes attachments — CVs, right-to-work documents, notes, and communication history — or only the structured fields. An export of names and emails without CVs and notes is not your database; it is a mailing list.
Whether the vendor may use the data. Aggregate analytics, benchmarking, or model training across tenants. Ask directly, get the answer in the contract, and be specific about whether "anonymised" means anything you would recognise as anonymised.
Candidate data also carries obligations of its own. Applicants have rights over their personal data in most jurisdictions — access, correction, and in many regimes erasure — and unsuccessful applicant records typically have a defined retention limit. You need to know which of those requests you can service yourself in the product, and which require a ticket to the vendor, because response deadlines are measured in days.
Multi-client separation, if you are reselling
If you are operating one ATS for your own delivery, this section is simpler. If you are reselling to clients, or running embedded recruitment for several of them, separation is the question that decides what you can promise.
Establish whether each client is a genuine tenant with its own isolated data, or whether you are expected to keep clients apart using permissions and record ownership inside a single tenant. The second arrangement is a standing risk in recruitment, because the failure mode is not abstract: it is one client seeing which candidates you are also submitting to their competitor.
Then check the adjacent questions. Can tenants carry different workflows, stages, and scoring criteria, since no two clients hire the same way? Can a candidate exist in more than one tenant, and if so, is that duplication or a deliberate shared-pool feature? Do you get a cross-tenant view for support, and is your access to it recorded? These are the same architectural questions any partner should ask, which we set out more generally in the white-label buyer's guide.
What your branding actually reaches
Recruitment is unusual in how much of the product faces people outside your business. A candidate may never log into the ATS, but they will see the careers page, the application form, the acknowledgement email, the interview invitation, and the rejection. Those artefacts are your brand or they are not.
Check each one individually: the careers or job-board page and whether it sits on your domain; the application form, including any vendor branding in the footer or on the file-upload widget; every automated email, and specifically the sender address and name rather than just the template body; the calendar invitation for interviews; and anything exported and forwarded — candidate summaries, shortlists, scorecards — since those circulate inside your client's business with whatever branding they carry.
- Distribution and integrations:
- Which job boards can you post to from the system, and are they included or separately contracted?
- Does posting carry your brand or the vendor's on the board listing?
- Can the careers page be embedded into an existing site, or does it have to be hosted by the vendor?
- Operating at agency scale:
- How long does it take to stand up a new client tenant, and can you do it without raising a ticket?
- Can a configured pipeline be saved as a template and reapplied?
- Is there an API, and does it cover the objects you would need to sync into your CRM or billing?
- The exit:
- Full export including attachments and notes — tested, not promised.
- Non-solicitation covering the clients you introduced.
- Notice period on both sides, and what happens to live tenants during it.
Where private-label ATS deals go wrong
Buying an ATS to run an agency. Most applicant tracking systems are built for an employer filling its own roles: one company, one pipeline per job, one hiring manager. An agency works the other way round, with many clients, candidates shared across searches, and a commercial layer — fees, splits, placements, rebates — that a corporate ATS has no concept of. Some products handle both; many do not, and the gap shows up after migration. Ask to see the agency workflow specifically, not a generic hiring demo.
Underpricing support. The same trap as any reseller arrangement: your brand on the login screen makes you the support desk, at a cost that scales with users rather than clients. We covered how that reshapes reseller margin in how the white-label reseller model actually works.
Assuming automated screening is a differentiator you control. If the ATS ranks or scores candidates, you inherit responsibility for how it does so — including under the growing set of rules on automated decision-making in hiring. Understand what the scoring uses before you sell it as a feature. Our explainer on how applicant tracking systems actually work covers what these systems do and do not evaluate.
Questions we get asked
An applicant tracking system operated or resold under your own brand instead of the vendor's — your logo, colours, domain, and sender identity across the interface and the candidate-facing artefacts. The vendor builds and hosts the platform; you own the client and candidate relationship.
Where to go next
If you want to see what the hiring side of our suite covers — positions and applicants, structured resume scoring, LinkedIn job posting, and onboarding packets that carry a hire past the offer — Hirepacket is the product page. Agencies running embedded or outsourced HR for clients may also want the HR teams view of the suite, since hiring feeds onboarding and the people record directly.
For per-tenant branding, domains, and partner terms across the whole suite rather than the ATS alone, see the white-label page. Terms are quoted rather than published — ask and we will send them.
Want to see how this works in practice?
Tell us how your team runs today and we'll walk you through the parts of Workefy that apply.
Prefer email? Write to contact@workefy.io