Every candidate submission workflow staffing agency teams run has the same weak point: the handoff to the client. Recruiters find good people, then the process breaks into email attachments, reply chains and spreadsheets. Feedback arrives late or not at all. Candidates go quiet while they wait. This page shows how to run the agency candidate submittal process in ATS Mako, from the ranked shortlist to the client decision to the text message that tells the candidate what happens next.
Why emailing resumes to clients breaks down
Email feels quick because everyone already uses it. The cost shows up later, when the account manager has to piece together who was sent where, and what the client said.
- Versions drift. The resume a client reviews may not match the one in your records.
- Feedback lives in inboxes. When a recruiter is out, the client's notes go with them.
- Duplicate submittals happen. Two recruiters send the same person to the same client because nobody can see the full picture.
- Candidates wait in silence. Nobody owns the follow-up, so good people accept other offers.
- Nothing is measurable. You cannot track submit-to-interview ratios if submittals are scattered across inboxes.
The fix is not a new email habit. It is keeping the submittal, the client response and the candidate update in one system that both your team and your client can work from.
The submission workflow, stage by stage
Below is a practical sequence an agency can run in ATS Mako. Adjust the stage names to match how your clients think about their orders.
- 1 Capture every applicant in one place Applicants come from job boards, referrals and direct email. Inbound email application capture pulls emailed applications into the ATS so they land in the right job instead of a shared inbox.
- 2 Rank the pool for the order AI candidate ranking scores applicants against the job so recruiters start with the strongest matches. Recruiters still decide who gets submitted. The ranking just shortens the review.
- 3 Screen before you submit Use AI voice screening to ask the same core questions to every candidate. Recruiters review the results and only move qualified people forward. Clients see candidates who have already cleared the basics.
- 4 Build the submission packet Package the resume, screening notes and recruiter summary for each candidate on the shortlist. Keep the packet attached to the candidate record so the client and your team are looking at the same information.
- 5 Submit to the client Send the packet from the integrated email client or through a branded client-facing view. Either way, the submittal is logged against the candidate and the order.
- 6 Collect the client decision Move the candidate to the matching stage when the client approves, rejects or asks for an interview. Status changes stay in the pipeline, not in someone's inbox.
- 7 Tell the candidate, fast Text the candidate with native SMS as soon as the client decides. Schedule the interview, or close the loop politely and keep them warm for the next order.
Building submission packets from ranked candidates
A good packet answers the client's first questions before they ask. Start from the ranked shortlist so the recruiter's time goes to writing summaries, not sorting resumes. The ranked shortlist for each order gives a starting order; the recruiter adds judgement about fit, availability and pay expectations.
Submission summary template
Candidate: [Name] Role and client: [Job title] for [Client name] Why this candidate: [Two or three plain sentences on fit] Screening highlights: [Key answers from voice screening] Availability: [Start date, shifts, location] Pay expectation: [Range or rate] Recruiter: [Name and direct contact]
Keep the summary short. Clients skim. Put the strongest reason to interview in the first line.
Client feedback loops and status syncing
Approval is a loop, not a single email. The client reviews, asks a question, approves one candidate and passes on another. Each of those moments should move the candidate to a clear stage. When your team works from per-client pipelines, as covered in the guide to running a pipeline for each client account, account managers can see every open submittal for a client at a glance and chase only the ones that are stuck.
If you want clients to review candidates themselves, a branded client candidate approval portal keeps feedback in the system. The page on giving clients a branded view of their hiring explains how that view can work.
Texting candidates after client decisions
The gap between a client decision and the candidate hearing about it is where agencies lose people. Native SMS lets recruiters send the update from the candidate record, so the message is logged with the rest of the history. For repeatable messages, such as interview confirmations or a polite pass, automated engagement workflows can send the right text when a candidate moves to a stage.
When the client wants to meet someone, use interview scheduling to book the time without a back-and-forth thread. Once a candidate is placed, onboarding and the employee portal carry them into paperwork and their first day.
White-label client-facing views
ATS Mako is fully brandable. Clients see your agency's name and look, not a software vendor's. That matters for an agency because the client relationship is the business. Every submittal, interview request and status update reinforces your brand. Agencies that run several brands or divisions can review how to manage separate client brands from one ATS.
Outcomes to measure
No tool sets your numbers for you. What a single system does is make the numbers visible, so you can see where submittals stall. Track these by client and by recruiter.
| Metric | What it tells you | Where to look |
|---|---|---|
| Submit-to-interview ratio | Whether your shortlists match what the client actually wants | Candidates moved from submitted to interview stage |
| Time from submittal to client response | Which clients need a nudge or a different review process | Time candidates sit in the submitted stage |
| Time from client decision to candidate update | How quickly your team closes the loop | SMS and email history on the candidate record |
| Interview-to-placement ratio | Whether screening and packets set candidates up to win | Candidates moved from interview to placed |
| Duplicate or rejected submittals | Gaps in coordination between recruiters | Candidate history across client pipelines |
Review these with account managers on a regular cadence. A low submit-to-interview ratio for one client usually means the job brief needs work, not that recruiters need to send more people.
Common pitfalls
- Submitting volume instead of fit. Sending more resumes rarely fixes a weak brief. Tighten the requirements and let ranking and screening narrow the list.
- Skipping the summary. A resume alone makes the client do the work. A short recruiter summary gets faster decisions.
- Leaving status updates for later. If stages are not updated when the client responds, your metrics and your follow-ups are wrong.
- Letting candidates wait. Silence after a client decision costs you people. Set an expectation that every decision triggers a text.
- Mixing client pipelines. Keep each client's orders separate so submittals and feedback never cross accounts.
To see how this fits your agency's volume and client mix, review pricing or book a demo and walk through a real order.
Put every submittal in one branded system
See how ranking, screening, client review and SMS updates work together on a live order.