Skip forward into hiring notes
RosterAcorn

Lever Hackett ATS badges: 3 areas to test yourself

Lever's 2026 Hackett Group badges recognize assessed strengths; small staffing teams should test analytics, flexibility, and applicant assessment before choosing an ATS.

Key takeaways

  • Turn badge areas into questions about your own workflows.
  • Have vendors demonstrate those workflows on your data.
  • Compare written quotes using the same growth assumptions.
  • Test data exports before you commit.

What did the 2026 Hackett assessment cover?

It does not tell you that the software will suit your recruiters. The assessment covered 12 talent acquisition software providers, and analysts assessed them across 28 criteria. The account this guide relies on comes from Lever, one of the vendors that was assessed, so treat it as Lever's own summary.

If weighting matters to your decision, put that question to the analyst firm or the vendor before you lean on any single result. A small staffing team rarely needs the full methodology, but it does need to know whether a ranking reflects the features you will use every day.

What do Lever's Top Performer badges cover?

Lever reports earning 10 Top Performer badges, naming analytics, platform flexibility, and applicant assessment among the areas recognized. Treat those three areas as examples, rather than the whole set.

A badge is a label for a result in a defined area. It cannot show how the product feels to a coordinator on a busy Monday, how many clicks it takes to move an applicant to the next stage, or whether hiring managers will log in at all. Those depend on your team, your roles, and your habits. Test them with your own recruiters.

If you compare a Hackett result with a different review, first check whether the two use the same criteria. A badge works best as a pointer toward areas worth checking. The checking itself is your job.

Why is a badge not enough for a small staffing team?

The basics are now expected. Lever's post describes posting jobs, tracking applicants, and moving people through hiring as basic requirements. The useful question becomes which system handles them the way your team works.

The same post argues that "Recruiting teams need their technology to do a whole lot more than keep everything organized." That is a fair test for any vendor. Can the tool help recruiters decide what to do next, or does it only store records you must organize yourself?

Small staffing teams feel this more than large in-house departments do. A handful of recruiters may be sourcing, screening, updating clients, and tracking placements in the same afternoon. A system that looks tidy on a slide but is slow to change can cost more in lost time than the subscription line suggests. The cost arrives as small delays that add up across a week.

Client reporting deserves the same attention. Staffing firms often answer to clients who want to know where their roles stand. A system that makes that answer hard to produce pushes the work back onto recruiters every week.

Small teams often have no dedicated systems administrator. When someone in the office is also doing the hiring, every setting that needs a vendor ticket becomes an obstacle. Flexibility you control yourself often matters more to a small firm than a feature only a specialist can switch on.

Which areas should you test yourself?

Start with the three areas Lever names, because each is concrete enough to test. Turn each label into a question about your own work, then ask the vendor to answer it on a live screen. These illustrative questions and success signs can guide a demo; they are not product claims.

AreaQuestion for the vendorSign of a good answer
AnalyticsCan you show open roles and the stage where applicants stall, using one of our real requisitions? The view makes sense without a long setup, and no export to a spreadsheet is needed.
Platform flexibility Can our own administrator change pipeline stages, scorecards, and email messages?Changes take minutes and do not need a support ticket.
Applicant assessment How is a skills check added to a role, who sees the results, and can an applicant finish it on a phone?Recruiters see results with enough context to act on them.

Look at the system from the applicant's side too. JazzHR puts the case plainly: "The average person checks their phone 150+ times per day, and 91 percent of people say they always have their phone within arm’s reach." To check the application experience yourself, apply to one of your own test roles on a phone and on a laptop. Note how long the process takes, what confirmation an applicant sees, and whether any automated message would make sense to someone who has never heard of your firm. Use the application form checks when reviewing that experience.

Then add areas beyond those badge labels. Your list should include how the system handles applicant messages, how it reports to client accounts, and what it costs when your team grows from a few users to a few more. Those points matter to a staffing business regardless of which product won which award.

How do you run your own comparison?

Write a short list of the workflows your team runs every week, then make each vendor show those workflows on your data. A standard sales demo is built to look good. A demo built from your own job orders shows what your recruiters will live with every day.

Next, score the options in a simple grid. List workflows down the side and vendors across the top. Give each cell a number from one to five, and have at least two people score independently before you compare. Write one sentence beside each score explaining why. Disagreements between raters are useful, because they show where your team has not agreed on what good looks like. Decide now how much each area should count. A team that places many temporary workers may weigh scheduling and applicant messaging more heavily than a team that hires mostly full-time professionals.

Illustrative example: compare the same workflow

Suppose a team tests 10 open roles with 2 vendors. Each vendor must show where applicants stall and how the team changes a pipeline stage. Recruiters record what they could do themselves and what needed help. Compare those observations before discussing badges; this example describes a test, not either vendor's performance.

Price the options against a realistic scenario, not the smallest plan on the page. Write down your expected users, open roles, and client accounts for the next year, then ask each vendor to quote that exact scenario in writing. Two quotes built on the same assumptions are easy to compare. Two quotes built on different assumptions are not. Growth changes the math, too. One Workable customer story describes a lean recruiting team with "a footprint that quintupled in six years." Price for where you expect to be, not only where you are today. For another comparison aid, see ATS prices by team size.

Then get a trial with live work. Put a few real requisitions into the system, invite the people who will use it daily, and watch where they hesitate. Hesitation is data. Note the moments when someone reaches for a spreadsheet, a sticky note, or a second tool. Those moments are where a system will fail after you buy it.

Finally, speak with reference customers who look like you: a small team, a similar number of open roles, and a similar mix of client work. Ask what broke during setup, what they wish they had asked before signing, and how support responded the last time something went wrong. Ask about the second year, not only the first month, because the early weeks of any new tool tend to hide friction.

Lever's post says it covers "Features, pricing considerations, and what to look for in an ATS in 2026." That makes a reasonable starting checklist. Build your own version first, then check it against each vendor's claims, so the list reflects your work rather than the pitch.

Who should be involved in the decision?

The recruiting lead should own the decision, but should not make it alone. Ask one recruiter who will use the system every day, one person who handles client billing or reporting, and anyone who manages hiring managers or client contacts. Each of them sees a different part of the workflow, and each will notice problems the others miss. Keep the group small enough that decisions move quickly.

When recruiters disagree, write down the specific workflow where the disagreement happens and test that step again. Most arguments about a tool are really arguments about one step in the process, and one step is easier to settle with evidence than with opinion.

Bring your recruiters in before the trial ends, not after the contract is signed. People who had a say in the choice are more likely to use the system well once it goes live. Explain the problem you are trying to fix, not only which tool you like. A recruiter who understands the problem can judge whether a proposed fix actually solves it.

Document your current process before you change it. Trace how a role moves from intake to placement today, including the workarounds people have built. Those workarounds often reveal what the new system must support. Teams that skip this step can end up rebuilding their old problems inside a new tool.

Plan for an adjustment period. Some recruiters will adapt quickly, and others will keep their old habits for a while. That is normal. Name one or two internal champions who can answer everyday questions, and run short training sessions built around real open roles rather than a general tour of the menus.

What should you ask a vendor before you sign?

Put these questions in writing, so the answers can be compared later and checked against the contract:

  • Which features are included in the base price, and which ones cost extra?
  • How does pricing change as you add users, open roles, or client accounts?
  • Who owns applicant and client data, and how do you export it if you leave?
  • Which integrations are included, and who maintains them when another product changes?
  • What happens to your pipeline history and applicant notes during a migration?
  • What is the support process when an applicant cannot apply or a message fails to send?
  • How often do features change, and how much notice do you get before a change affects your workflow?

Vendors also add features faster than most teams can evaluate them. Workable announced that "Four AI recruiting agents are now available to every Workable customer globally." A launch like that is the vendor's own claim, so ask what each agent does, whether it can be switched off, and whether it is included in the base price.

Get the answers in writing, and ask whoever signs the order form to confirm them. If a vendor will not answer one of these questions in writing, treat that refusal as information. Ask a second time, and then decide.

What does switching cost later?

Switching is rarely free, even when the new system is better. Plan for the cost before you start, because it is easy to underestimate. The following are illustrative planning categories, not quoted charges or promised schedules.

CostWhen it shows upWhat to plan for
Subscription and setup feeAt signingThe full scenario quoted in writing
Moving applicant recordsDuring migration Which fields and history actually carry over
Rebuilding pipeline stagesFirst weeks after go-liveOne named owner who makes the changes
Retraining recruitersFirst weeks after go-liveShort sessions built on real open roles
Running two systemsDuring the overlap A scheduled overlap, not a hope that none is needed

Teams rarely switch from a clean slate. In a Workable case study, the Saskatchewan Roughriders described their earlier setup: "Before Workable, the Roughriders managed recruiting through Teamworks Online, which they had used for two years following an earlier era of inbox-based hiring." That history is what a migration has to carry. Ask what happens to older records before you commit.

Ask whether exports include notes, attachments, and activity history, or only the basic applicant fields. A file that holds names and emails but loses everything else can leave you with far less than you think you are keeping. Make sure you can read your key applicant and client data without the vendor's software.

Finally, pick a date by which you will have chosen, and sketch a rough plan for the first few weeks after go-live. A decision that drifts for months costs more than a decision made on imperfect information and then managed well.

Today, choose a current job order and write the workflow you want each vendor to demonstrate, including the report you need at the end.

Should a badge settle the decision?

No, a badge should narrow your list rather than settle your ATS choice. If Lever holds up in your workflow tests, its recognition is a reasonable reason to keep it on the shortlist. If another system fits your roles, your budget, and your recruiters better, that system should win, whatever badges appear in a vendor's marketing.

Use the 2026 assessment as one input among several. Check its claims against your own trial, and name the criteria you cared about most when you share the decision with partners. That way the reasoning travels with the decision, and the next person can see which features mattered and why.

A good ATS choice comes from your own work, tested honestly. A badge can help you start that work with better questions.

Sources