People · Recruiting operations
Candidate screening and scheduling
Turn inbound applications into structured candidate briefs and scheduling proposals, while the recruiter controls shortlist decisions and candidate progression.
Illustrative product view
run_talent_acquisition_01
An application enters a configured role pipeline.
Trigger captured
Evidence is normalized
Evidence attached
Candidate briefs are prepared
Evidence attached
Human decision required
Terminal approval step
The operating problem
Where the process breaks.
Recruiters repeatedly read, compare, and schedule before a hiring manager can engage. Automated screening can hide weak criteria, so job-related qualification evidence and the recruiter’s decision must remain visible.
Governed execution
How the work runs.
Order remains explicit from trigger to decision. Every step runs inside the tools, data scope, and policy assigned to this workflow.
- 01Trigger
Application enters the role
The applicant record and approved role criteria start the workflow.
- 02Agent
Evidence is normalized
The agent extracts job-relevant evidence against configured qualification criteria.
- 03Agent
Candidate briefs are prepared
Each brief presents supporting evidence, missing information, and the criteria evaluated without ranking candidates autonomously.
- 04Human
Recruiter decides progression
The recruiter reviews the evidence and makes every shortlist and progression decision as the terminal workflow step.
Decision boundary
Human approval is the boundary.
The approval node is terminal today. A post-approval send or write happens only through a separate manual or newly triggered continuation.
Required decision
A recruiter makes every shortlist and progression decision; stage changes and scheduling require a separate manual or newly triggered continuation.
Approval recorded
Actor, decision, edits, and timestamp join the receipt.
Separate continuation
External write
Nothing resumes silently after the human decision.
Proof of execution
Execution receipt.
The output is not just a result. It carries the trigger, evidence, proposed actions, decision, and final workflow state.
Illustrative receipt
sample · run_talent_acquisition_01
- Role criteria and version
- captured · evidence_01
- Application fields evaluated
- captured · evidence_02
- Evidence-linked qualification summary
- captured · evidence_03
- Fields excluded from evaluation
- captured · evidence_04
- Recruiter decision and continuation status
- approved · continuation_not_started
Output · Structured candidate briefs, recruiter decisions, scheduling proposals, and receipt.
Connected work
Example systems in this workflow
These are illustrative system choices, not a claim that every one is a native connector. Configure supported native tools, MCP servers, OpenAPI imports, or approved HTTP tools for your environment.
Deployment boundary
Run the workflow in Zilionix Cloud, inside your VPC, or through the self-hosted deployment path while keeping organization-scoped data and credentials inside the selected boundary.
Zilionix Cloud
Your VPC
Self-hosted
Policy before autonomy
Guardrails for this run.
The workflow is configured to exclude protected-characteristic fields from evaluation.
Configured role criteria are versioned and visible to reviewers.
The workflow prepares briefs rather than autonomously ranking candidates.
No applicant can progress in the approval run.
Candidate data access is limited by organization role and workflow scope.
External evidence
Benchmark the opportunity.
This source illustrates the surrounding business problem. It is not a Zilionix deployment, customer result, or performance guarantee.
Related workflows
Keep following the work.
All 14 use casesBring this workflow into view.
Map the trigger, tools, approval boundary, and execution receipt against the way your team already works.