How to Add AI Screening to Your Existing ATS
Published
Your ATS may already manage applications, approvals and offers well. The bottleneck can still be the work between receiving a CV and giving a manager useful first-interview evidence. Adding AI screening is worth considering when that boundary is clear.
An integration is useful when it transfers the right candidate, role, evidence and next action reliably. A vendor logo does not answer those questions. Neither does the phrase “two-way sync” without a list of supported operations.
The distinction matters for Skill Society: its applicant-tracking scope excludes requisition approvals, offer letters, e-signature and onboarding. Those needs may continue to sit in an existing ATS. Published workflow scope.
This guide gives HR operations, recruiters and system owners a practical way to evaluate an additional screening workflow without creating conflicting records or duplicate candidate messages.
Keep your current ATS working for your team. Bring its name and your screening stages to a Skill Society integration discussion.
Should you improve the ATS, add screening or replace the system?
Describe the bottleneck before looking at connectors. If the issue is unclear role requirements, another system will inherit the ambiguity. If nobody owns manager follow-up, generating more interview reports may increase the backlog.
| Situation | First option to evaluate | Evidence needed |
|---|---|---|
| Existing ATS has an unused feature that addresses the task | Configure and test that capability | Recruiter effort and manager evidence after a realistic trial |
| ATS works well but repeated first calls consume capacity | Add a scoped screening workflow | Reliable invitation and result handoff with less total work |
| Fundamental workflow requirements are unmet across several stages | Evaluate a broader replacement | Complete requirements, migration effort and downstream dependencies |
| Hiring process is inconsistent between managers | Clarify ownership and criteria | Agreed decisions, evidence and response expectations |
For background on the screening stages themselves, use the AI screening workflow guide. Keep that process decision separate from whether a specific connector supports it.
Draw a one-role boundary map
Use one actual vacancy and write five steps: application arrives, first-screen invitation is authorised, candidate completes the screen, evidence becomes available, reviewer decides the next stage.
For each step, name the system where the authoritative record lives and the person responsible when something goes wrong. “The integration handles it” is not an owner.
| Record or action | Proposed owner | Question to resolve |
|---|---|---|
| Job requirements and active version | HR role owner in an agreed system | How does the screening workflow receive a changed brief? |
| Application identity | ATS application record | How are the same person's applications to different jobs distinguished? |
| Invitation permission | Approved stage or named reviewer | What prevents an invitation after withdrawal or closure? |
| Interview completion | Screening workflow | How are partial and failed attempts represented? |
| Returned evidence | Agreed review destination | Is the output a link, attachment, note, field or combination? |
| Progression decision | Authorised recruiter or manager | Which system sends candidate communication? |
These are proposed responsibilities to agree with the vendor. They are not a description of every connector's available functions.
Specify the data you need to exchange
A useful field map names the source, destination, purpose and expected failure behaviour. Include only information required by the workflow, and have the responsible privacy and system owners review the proposed movement of candidate data.
Start with the application identifier, role identifier, candidate contact information, approved question set, invitation state, completion state and evidence location. List any additional CV or application answers separately rather than treating an entire profile export as the default.
For every returned field, establish whether it is an observation, a status or a decision. An interview summary should not silently become a rejected status. A missing result should not appear as a failed assessment. A reviewer must be able to distinguish incomplete information from an unfavourable answer.
The OAIC recommends examining commercial AI data flows and access. Use your field map in both operations and privacy review. OAIC guidance.
Test the invitation trigger before testing the report
Write the intended rule in plain language. For example: “An authorised recruiter selects the approved screening stage for an open role; an eligible application receives one invitation.” This is an illustrative requirement, not a promise that a particular product uses that trigger.
Then deliberately challenge it. Move the test application into the stage twice. Withdraw it before processing. Close the role. Correct the email address. Use the same test candidate for another role. Record what actually happens to the invitation and application history.
Decide which system sends reminders and rejection messages. Two individually reasonable workflows can create a poor experience if both communicate about the same event. Keep one accountable owner for each message type.
Make the connector demonstration specific. Book a handoff walkthrough using your proposed trigger, returned evidence and review destination.
Use this handoff acceptance checklist
Run the checklist with authorised test records before inviting real applicants. Ask the vendor to demonstrate gaps rather than marking them as supported based on a presentation.
| Test | What a reviewer needs to observe |
|---|---|
| Normal completion | Result reaches the intended application and a person can inspect it |
| Two applications by one candidate | Evidence remains associated with the correct role |
| Repeated event or manual retry | No unintended duplicate invitation or result |
| Incomplete interview | Clear unfinished state and an assigned next action |
| Failed transfer | Visible failure, named owner and a documented recovery path |
| Candidate withdrawal | Future actions follow the agreed withdrawal process |
| Removed reviewer access | The former reviewer cannot open restricted evidence |
| Role question change | Team can establish which questions produced the evidence |
Define the expected result before each test. Some acceptable solutions involve manual steps. Record their frequency and workload so the procurement decision includes them.
Who handles failures after launch?
Agree where someone checks exceptions, how often that review happens and whom they contact. A small integration with a clear recovery procedure may be more useful than an ambitious flow whose failures disappear into an unattended inbox.
For a missed result, establish whether the candidate needs to do anything again. Avoid making applicants repeat an interview solely because an internal transfer failed if the original evidence remains available. Preserve the original record and use the agreed recovery process.
When the issue changes what a candidate should expect, the recruiter owns the update. The candidate follow-up SLA guide can help define that responsibility.
How should you evaluate Skill Society with an existing ATS?
Skill Society lists integration destinations, including dedicated pages for several ATS products. Confirm the connector, permitted operations and account scope for your environment; directory presence alone does not establish complete synchronisation. Integration directory.
Use the checklist to ask what starts the screen, what comes back and where managers work. For a concrete example of the questions to ask, read the Lever handoff guide.
Measure reconciliation work as part of the pilot: correcting records, finding missing reports, sending duplicate-message apologies and helping managers obtain access all count. Reduced interview scheduling is valuable only if the complete workflow is manageable.
FAQ
Q: Do we need to replace our ATS to use AI screening?
A: Not necessarily. First establish whether the existing system meets broader requirements and whether a supported screening handoff solves the identified gap.
Q: Does an integration mean all data synchronises both ways?
A: No. Ask for the exact objects, fields, triggers and actions supported, along with exclusions and recovery steps.
Q: Can a manual pilot be useful before integration?
A: Yes, when authorised data handling and candidate communication are clear. Track the manual work and do not present that pilot as proof that the future integration works.
Q: Who should attend the integration demo?
A: Include the recruiter who operates the process, the ATS owner and a manager who will review evidence. Bring privacy or security colleagues when their requirements need examination.
Map your screening handoff before choosing a connector
Bring one vacancy, its stage names and a blank field map. Book a Skill Society demo to identify supported operations, open questions and the tests required before launch.
Sources
Primary sources reviewed 16 September 2026. Tables are buyer requirements and proposed tests, not connector guarantees.
