TL;DR:
How do you find what is delaying candidate submissions?
Before replacing your recruiting agency’s ATS, trace one candidate from initial review to client submission. Record the work performed, waiting time, repeated data entry, missing information, and owner of each next step. Then classify the bottleneck: unclear process, insufficient capacity, or a software limitation. Use that diagnosis to test a specific fix—and require any new ATS to demonstrate the relevant workflow before you commit.
A candidate has been screened.
You think they are worth presenting.
Your client still has not seen them.
What happened in between?
Maybe a recruiter is rewriting the candidate summary. Maybe compensation expectations were never confirmed. Maybe the profile is waiting for the agency owner to approve it.
Or maybe your system genuinely makes a routine task harder than it needs to be.
Those problems call for different solutions. Before you buy another ATS, identify which one is slowing your agency down.
Start with the workflow, not the software complaint
“Our ATS is slowing us down” may describe a real limitation. It may also describe a process that has never been made explicit.
Turn the complaint into an observable task:
- “We enter the same candidate information in two places.”
- “We cannot tell which profiles are ready for client submission.”
- “Every summary waits for the owner to review it.”
- “We repeatedly reopen records because screening notes are incomplete.”
Now you have something to investigate.
If you need a refresher on the software’s role, our applicant tracking system guide explains the basics. For an agency owner, the evaluation should go further: does the system support the way your team needs to deliver client-ready candidates?
Define what “ready to submit” means
You cannot measure a consistent submission process if each recruiter has a different definition of a finished profile.
Agree on a submission standard appropriate to the role and your client’s requirements. That might include:
- An up-to-date resume or agreed candidate profile.
- Evidence against the role’s required qualifications.
- Relevant screening notes.
- Confirmed interest in the opportunity.
- Availability and compensation expectations, where appropriate.
- Open questions the client should evaluate.
- A clear recommendation for the next step.
Follow your agency’s applicable privacy, consent, confidentiality, and client-agreement requirements when handling or sharing candidate information.
The aim is not to create a longer checklist for its own sake. It is to prevent repeated work caused by discovering missing essentials at the last moment.
Our article on the recruiter–hiring manager handoff covers what makes a submission useful to the person receiving it. This audit focuses on the agency work required to get it ready.
Map one candidate from screening to client submission
Start with a recently completed submission. Choose an ordinary case rather than your easiest success or most unusual problem.
Reconstruct the steps using available records. If you cannot see when an activity happened, note the gap instead of inventing a timestamp.
| Stage | What to record | Question to ask |
|---|---|---|
| Initial review | When the candidate was reviewed and what criteria were applied | Did the reviewer have enough information to decide the next step? |
| Screening | Scheduling, conversation, notes, and missing details | Was the screening completed once, or did someone have to repeat part of it? |
| Profile preparation | Summary writing, formatting, and information transfer | Which work adds useful context, and which work merely copies information? |
| Internal review | Who reviewed the profile and how long it waited | Did the review improve the submission, or mainly move it through a queue? |
| Client submission | When and how the profile was sent, plus where that activity was recorded | Can another authorized team member confirm what was sent and what happens next? |
Then compare a few more submissions. One case can expose a problem, but it cannot tell you how frequently that problem occurs.
Measure working time separately from waiting time
A submission can take several days to move through a process without requiring several days of recruiter work.
Separate these two measures:
- Working time: the time someone actively spends reviewing, screening, preparing, checking, or sending the submission.
- Waiting time: the time the submission sits between actions.
This distinction changes what you should fix.
If preparing a profile requires substantial repeated entry, investigate the task and the tools supporting it. If preparation is quick but the profile waits for approval, investigate the approval process.
Define elapsed time consistently. Decide whether your internal measure uses business hours or calendar hours, and note candidate availability or other factors outside your agency’s direct control.
These are diagnostic measures, not universal recruiting benchmarks. Establish your own baseline and compare similar work before drawing conclusions.
Five candidate submission bottlenecks to check
1. Screening information is incomplete
A recruiter begins preparing the submission and realizes an important requirement was never discussed.
The profile goes back into follow-up. Someone contacts the candidate again. The summary waits.
Possible first fix: use a consistent, role-specific screening guide and record the relevant evidence before moving the candidate forward.
An ATS may help organize the information. It cannot recover a question nobody asked.
2. Candidate information is repeatedly copied
Look for transfers between screening notes, candidate records, internal summaries, and client-facing formats.
Some rewriting may be necessary to explain fit clearly. Other work may duplicate information without improving the submission.
Possible first fix: agree on a reusable submission structure, then test what your current system can support. If evaluating another ATS, ask the vendor to demonstrate the exact preparation steps rather than assuming the capability exists.
3. Every submission waits for the agency owner
Owner review may be valuable for a complex search, a new client, or a recruiter who is still learning the account.
But if every routine submission requires your approval, inspect whether your standards are documented well enough for someone else to apply them.
Possible first fix: clarify which cases need review, what reviewers check, and when a recruiter should escalate uncertainty.
For a broader look at owner-dependent delivery, read why a growing recruiting agency can still leave its owner doing the heavy lifting.
4. Nobody knows who owns the next action
A profile marked “in progress” does not tell your team whether it needs a screening call, a summary, an approval, or a client email.
Possible first fix: make the next action explicit. Record the responsible person, what they need to do, and the agreed timing.
When evaluating software, test whether authorized users can easily identify those details in the relevant workflow. Do not settle for a status label that still requires someone to explain the situation in another message.
5. The process is clear, but the team has no capacity
Sometimes the workflow is not mysterious. The work is simply waiting for someone who is already handling other searches.
Possible first fix: review priorities, active commitments, and which activities could be supported by another qualified person.
Software may remove certain steps, but it does not automatically supply the people needed to perform screening or other recruiting work. Our guide to on-demand recruiting explains one support model worth evaluating against a defined workload.
Classify the problem before choosing the fix
| What you observe | What to investigate first | What not to assume |
|---|---|---|
| Recruiters use different submission standards | Documentation, training, and client requirements | That a new system will create agreement automatically |
| Profiles wait for the same approver | Decision rights, review criteria, and approval capacity | That faster data entry will remove the approval queue |
| The same information is entered repeatedly | Templates, configuration, integrations, and relevant product capabilities | That every transfer can or should be automated |
| The team cannot locate current information | Recordkeeping habits and the system’s usability for the task | That the problem is entirely user behavior or entirely software |
| Defined work waits because everyone is occupied | Workload, priorities, and support capacity | That purchasing software supplies recruiting labor |
You may find more than one cause. The purpose of this exercise is to identify the first constraint worth testing—not force every problem into a single category.
Make an ATS demonstration follow your actual workflow
If your audit identifies a software limitation, turn it into a demonstration request.
Use fictional or properly de-identified sample information. Give the vendor a scenario that resembles the work your team needs to perform.
For example:
We have completed a screening conversation and need to prepare a client submission. Show us how a recruiter records the relevant evidence, identifies missing details, prepares the agreed information, and records the next action. Then show what another authorized user can see.
During the demonstration, ask:
- Which steps happen inside the system?
- Which steps still require another tool or manual work?
- What must be configured before the workflow works this way?
- Which capabilities are included in the proposed plan?
- How are access and permissions handled?
- What happens to existing records during migration?
- How can the agency export its information later?
For GateKeeper, use the same standard. HRmango’s ATS should be evaluated against your agency’s requirements, not selected simply because it is part of a broader recruiting offer.
Calculate the economics without claiming every saved minute becomes revenue
Use your own audit to estimate the direct labor involved in a repeatable task.
A basic calculation is:
Monthly task hours = average working minutes per submission × monthly submissions ÷ 60.
Estimated labor allocation = monthly task hours × your chosen hourly labor-cost assumption.
Keep the assumptions visible. Use comparable submissions, avoid counting the same work twice, and include review time where relevant.
Then separate three possible outcomes:
- Capacity: the team has time available for other work.
- Cash savings: the business actually spends less.
- Additional revenue: the business wins and delivers additional paid work.
They are not interchangeable. Removing administrative work may create capacity without reducing payroll. Additional capacity may support more searches without guaranteeing another placement.
If you want to examine the wider cost picture, read how to reduce recruiting costs without sacrificing quality.
Test one change before replacing the whole system
Choose the bottleneck your audit made most visible.
- Define the specific problem.
- Record a baseline from comparable work.
- Change one part of the workflow.
- Document who owns the new process.
- Review working time, waiting time, and submission completeness.
- Decide whether to keep, adjust, or reject the change.
Do not improve speed by removing information the client needs. A faster incomplete submission can simply move the work downstream.
If your review reveals problems beyond candidate preparation, use HRmango’s guide to auditing a hiring process as a broader starting framework.
Frequently asked questions about recruiting agency workflow bottlenecks
How do I know whether our ATS is the problem?
Identify a specific task your agency cannot perform effectively, check the system’s current configuration and available capabilities, and test the workflow. A general feeling that the software is frustrating is a reason to investigate—not enough evidence by itself to justify migration.
What should we measure first?
Start with working time, waiting time, repeated entry, and whether submissions meet your agreed completeness standard. Define the start and end of each measure so your team compares the same activity consistently.
Should we replace our ATS or add recruiting support?
Evaluate replacement when a verified system limitation prevents a required workflow and cannot reasonably be resolved in the current setup. Evaluate support when qualified work is waiting because the team lacks capacity. Some agencies will need a combination, but the audit should explain why.
Can faster submissions improve placement results?
Timeliness is one part of delivery, but submission speed alone does not establish placement success. Track whether the candidates meet the agreed requirements and what happens after submission, including client review, interviews, offers, and completed placements.
Bring the bottleneck—not just the software wish list
You do not need to arrive at an ATS conversation with every answer.
You do need a clear example of the work that is getting stuck.
HRmango offers GateKeeper ATS and recruiting support options for agencies. Explore HRmango’s software and recruiting support, then use the site’s contact options to explain your current workflow, the step causing difficulty, and what you need to improve.
Ask to evaluate the relevant process. If additional support is part of the discussion, confirm its scope, pricing, client-contact boundaries, confidentiality, and candidate-data access before committing.
The next purchase should solve a problem you can describe—and produce an improvement you can check.
