ATS for Collaborative Hiring: An Agency Test

Collaborative hiring for an agency means one thing: letting an external client act on a shortlist without giving away your whole database. Your client is a hiring manager at another company, not a colleague. They need to see the people you present, react to them and tell you who to advance.

Ask to test more than the look of a client portal in an ATS demo. Check what the client can see, change and lose access to. Those details decide whether the tool protects your confidentiality or leaks it.

This guide gives you a reproducible test. It uses two fictional client mandates and a five-part protocol scored pass, fail or unknown. No hands-on vendor tests, no rankings. Just a checklist you can run in any demo.

What collaborative hiring means for an agency desk

Start by drawing a line. Internal collaborative hiring is a team inside one company sharing an opinion on a candidate. Agency collaborative hiring is different. You present candidates to a client who works somewhere else.

That difference changes the software you need. Ask whether the tool can give an external client access to one search without exposing internal data. An agency tool must show a client one search and hide everything else. Your other clients, your wider pipeline and your notes all stay private.

This is also where candidate data and client data split apart. Your candidate records belong to you and follow you across mandates. Your client records track the company you serve. If you want the longer version of that split, read our breakdown of the difference between a candidate CRM and a client CRM. For this guide, keep the focus on the client view of a single search.

Meet Northgate Search and Vantage Talent, our two test mandates

To keep the test concrete, picture two fictional agencies. Both are made up for this guide. Use them as a script when you sit in a vendor demo.

Northgate Search is a retained executive search firm with four consultants. It runs one confidential mandate for a client: a new finance director. The client’s CEO wants to see a shortlist of five, read the profiles and reply with a shortlist of two. Confidentiality is the whole point. The CEO must never see other searches or other candidates.

Vantage Talent is a contingent agency with eight recruiters. It fills several mid-level roles for one client at once. Here the hiring manager is hands-on. They want to comment on each candidate, mark a clear yes or no and see the pipeline move in real time.

These two mandates test opposite needs. One wants quiet, tightly controlled view access. The other wants active feedback and decisions. A good ATS should serve both without a workaround.

The five things to test before you trust a client portal

Run the same five tests against every ATS you consider. Score each one pass, fail or unknown. Leave a score unknown until the vendor proves it live. A confident sales answer is not proof.

The rest of this guide walks through each test with our two mandates in mind.

Test 1: can the client see only the right project?

This is the test that protects your business. Ask the vendor to log in as a client and show you the screen. For Northgate Search, the CEO should see the finance director shortlist and nothing else.

Watch for leaks. Can the client search your wider database? Can they see the name of another client or another role? Can they open a candidate who is not on this shortlist? Any yes here is a fail.

Test project-scoped visibility at every price point. If the client view shares your workspace, ask the vendor to show how it keeps each client separate. A single leak can cost you a client.

Try one more thing in this test. Ask the vendor to invite a second fake client to a different search, then switch between the two client views. Neither client should ever glimpse the other’s mandate. If the two views blur together, the tool was not built for agency work.

Test 2: view access versus feedback access

Your two mandates want different things, so this test matters. View access lets a client read profiles and follow progress. Feedback access lets them also comment, rate or decide.

Northgate’s CEO may only want to view and reply by email. Vantage’s hiring manager wants to comment inside the portal and mark decisions. A strong ATS lets you set the level per client, per project.

Ask the vendor to show both modes. Then ask how you switch a client from one to the other. If the tool only offers a single access level, note it. That is not a dealbreaker for every desk, but you should know before you sign.

Test 3: who can move or reject a candidate

Now test what a decision actually does. In some portals, a client marks a candidate as interested or not a fit, and that decision shows up on your side. In others, the client only leaves a comment, and the recruiter moves the pipeline stage.

Both models work. The risk is assuming one and buying the other. For Vantage Talent, a clear yes or no from the hiring manager needs to be easy to give and easy for you to see.

Have the vendor show a client leaving a decision. Then watch where it lands in your view. Does it change the candidate record, or does it add a note you must action? Write down the answer. Guesswork here creates missed feedback and slow searches.

Test 4: revoking access cleanly when a mandate closes

A mandate ends. The client should not keep a live window into your work. This test is easy to skip and painful to get wrong.

Ask how you remove a client’s access to a project. Confirm it is per project, so revoking one search does not touch another. Then ask what record remains. Check whether the access log records who was granted access and when. Permission history does not prove someone viewed the pipeline. If you need viewing history, ask the vendor to demonstrate it separately.

For a retained firm like Northgate, this is a confidentiality promise you make to clients. You need to prove that access was scoped and then closed. If a vendor cannot show clean revocation and a log, mark it unknown and dig deeper.

Test 5: keeping the feedback handoff human

Software should support the client relationship, not replace it. The best portals make it easy for a recruiter to stay in the loop, not push the client into a silent tool.

When a client leaves feedback, you should know fast and be able to reply as a person. The conversation about why a candidate fits belongs to you, the consultant. That is what clients pay an agency for.

This is also where retention lives. A tidy feedback loop keeps clients coming back. We cover the wider operating rhythm in our guide to keeping clients through a clear feedback loop. Do not let a portal turn a relationship into a ticket queue.

Where Leonar fits, and where it does not

Leonar documents a built-in hiring manager portal where a client gets view or feedback access to a specific project’s pipeline. Clients can submit feedback on candidates. You can add or revoke access per project, and an access log records who was granted access and when. These documented features are relevant to tests one through four; they are not demonstrated test results.

Leonar also supports multi-owner projects, so several consultants can share ownership of a search. That alone does not establish how client feedback reaches the right recruiter. Keep all five scores unknown until your demo. For test five, ask who receives feedback, where they see it and how they reply.

Now the boundary. Leonar does not ship anonymous no-login links, a rating engine for clients to score candidates, credentialing checks or on-brand per-client report templates. If your desk needs them, put them on your test sheet and confirm them separately. Leonar is an ATS and CRM for recruitment agencies with transparent, public pricing you can see on the pricing page, not a client-branding studio.

Turning the protocol into your buying decision

You now have a script. Take Northgate Search and Vantage Talent into every demo. Ask the vendor to log in as each client and run all five tests in front of you.

Score each test pass, fail or unknown. Do not let a smooth answer fill an unknown. Make the vendor show the screen, then you write the score. This works whether you run permanent searches or a busy contingent desk, and it pairs well with the broader checklist in our guide to an ATS built for a staffing agency.

The tool that passes all five tests is the one that lets you collaborate with clients and still protect your database. That balance is the whole job. Test it before you buy, and you will choose with proof instead of hope.

Frequently asked questions

What does collaborative hiring mean for a recruitment agency?

For an agency, collaborative hiring means working a shortlist with an external client, not with an internal HR team. Your client is a hiring manager at another company. They need to see the candidates you present, react to them and tell you who to move forward. The job is to give that client a clear view of one search without handing over your whole database. Internal team collaboration is a different problem. This guide is about the client side, where confidentiality and access control matter most.

What is the difference between view access and feedback access in an ATS?

View access lets a client look at a shortlist. They can read profiles and track progress, but they cannot change anything. Feedback access lets a client also leave comments, ratings or a decision on each candidate. The right level depends on the client. A busy medical director may only want to view and reply by email. A hands-on hiring manager may want to comment inside the portal. Test both modes in a demo. Ask which one a client gets by default and how you switch between them.

How do you stop a client from seeing your whole candidate database?

Look for project-scoped access. A client should only see the pipeline for the search you invited them to, never your full contact list or your other clients. Ask the vendor to show you exactly what the client sees once they log in. Confirm that other projects, notes and contacts stay hidden. Also check that you can add and revoke access per project. When a mandate closes, you should be able to remove the client's access and keep an audit record of who was granted access and when. That permission record does not prove anyone viewed the shortlist.

Can a client reject or move a candidate in the ATS?

It depends on the product and the access level you grant. Some portals let a client leave a decision, such as interested or not a fit, on each candidate. Others only let them comment while the recruiter moves the pipeline stage. Neither is wrong. What matters is that you know which one you are buying. Ask the vendor to show a client marking a decision, then show where that decision lands on your side. Confirm whether it changes the record or just adds a note for you to action.

Does Leonar have a client portal for collaborative hiring?

Yes. Leonar includes a hiring manager portal where an external client gets view or feedback access to a specific project's pipeline. Clients can submit feedback on candidates, and you can add or revoke their access per project with an access log. Leonar runs multi-owner projects, so several consultants can share a search. It does not ship anonymous no-login links, a rating engine for clients to score candidates or on-brand per-client report templates. Confirm the exact setup for your desk in a demo before you decide.