From Application to Shortlist Overnight: Introducing Workflows
A candidate applies at 9pm on a Tuesday.
By Wednesday morning, they've completed a screening questionnaire, finished an async AI interview, and landed on your shortlist, without a single recruiter lifting a finger.
That's not a future state. That's what a well-built hiring workflow looks like today.
For teams hiring at scale, especially in hourly, high-volume, or multi-location environments, speed and consistency aren't nice-to-haves. They're the difference between filling a shift and losing it. Between landing a great candidate and watching them accept an offer from whoever moved faster.
The problem isn't effort. It's architecture. Most recruiting teams are stuck coordinating screening steps manually: sending one email, waiting, sending another, chasing a response, then finally booking time with a hiring manager, only to find out the candidate dropped off two days ago.
Today, we're introducing Workflows: a new way to automate candidate progression through every stage of your hiring process, from the moment someone applies to the moment they're on your shortlist.
What Is Workflows?
Workflows is Humanly's configurable, multi-step candidate screening system. It lets you define a structured sequence of steps — screener questionnaires, AI interviews, async video, scheduling — and automatically advance candidates through each one based on their performance.
When a candidate applies to a job with an associated workflow, they're automatically enrolled. From there, the system handles progression. Your team stays in control of the criteria. The follow-through handles itself.
A few key terms worth defining upfront:
- Workflow template: A reusable, named screening sequence you can apply to many jobs at once.
- Job family: A grouping of similar roles (e.g., "Warehouse Associate" or "Customer Service") that share a common workflow.
- Step: A single stage within a workflow — a questionnaire, an interview, or a scheduling invite.
Why It Matters
Speed. Every hour a qualified candidate waits for the next steps is an hour they're weighing other offers. Workflows eliminates the lag between "applied" and "moving forward."
Consistency. Every candidate for a given role moves through the same sequence. No variation based on who's covering that day, which recruiter got to it first, or whether it was a Monday or a Friday.
Quality. Score thresholds act as automatic gates: only candidates who meet your requirements advance. By the time a hiring manager sees someone, they've already demonstrated they can do the job.
Candidate experience. Candidates get clear, prompt communication at every step — not silence. A structured journey feels like a responsive employer, not a black hole.
How It Works
Here's what the end-to-end experience looks like, from configuration to candidate completion:
- Create your steps. In Humanly, build the interviews, questionnaires, and scheduling links you want to use as building blocks. These can be reused across multiple workflows.
- Build a workflow. In Settings → Customization → Screening Workflows, create a named workflow and arrange your steps in sequence. Define any score thresholds or requirements a candidate must meet before advancing to the next step.
- Attach the workflow to jobs. Apply your workflow to individual jobs, a job family, or both. Job-level overrides let you customize for specific roles while keeping your templates intact.
- A candidate applies. The moment they submit their application, they're automatically enrolled in the workflow associated with that job.
- Invites go out. The candidate receives a step-by-step invitation — either all at once or staged with deliberate delays between each step, so it feels like genuine review is happening between stages.
- Candidates progress (or don't). As each step is completed, the system evaluates the result against your thresholds. Candidates who meet the bar move forward automatically.
- Qualified candidates land on your shortlist. By the time your team reviews the queue, the work is done. You're looking at candidates who've already passed your screening criteria, not a pile of raw applications.
Example Workflows
Example 1: Hourly / High-Volume Role (e.g., Warehouse Associate)
| Step | Type | Gate |
|---|---|---|
| 1 | Screening questionnaire | Must meet minimum score threshold |
| 2 | AI screening interview | Must meet minimum score threshold |
| 3 | Hiring manager scheduling | Auto-invited upon passing Step 2 |
Result: Candidates who aren't a fit never reach the calendar. Hiring managers only meet candidates who've already cleared two rounds of screening.
Example 2: Professional / Salaried Role (e.g., Customer Success Manager)
| Step | Type | Gate |
|---|---|---|
| 1 | Application questionnaire | Required completion |
| 2 | Async video interview | Score threshold |
| 3 | Practice/skills interview | Score threshold |
| 4 | Scheduling with hiring manager | Auto-invited upon passing Step 3 |
Result: A structured four-step sequence that mirrors the quality bar of your best manual processes, fully automated.
Configuring Workflows: Templates, Job Families, and Overrides
Workflows is built for teams managing many jobs across many locations. Here's how the configuration layer works:
Templates are your starting point. Build a screening sequence once, name it, and apply it wherever it fits. If you hire for a role in 40 locations, you configure it once, not 40 times.
Job families let you assign a template to an entire category of roles. Every job tagged "Retail Associate" or "Call Center Agent" automatically inherits the right workflow without individual setup.
Per-job overrides give you flexibility when a specific role needs something different. A flagship location might add an extra step. A specialized role might have a higher score threshold. You can override the inherited workflow at the job level without touching the template.
Precedence rules are simple: a per-job override takes precedence over a job family assignment, which takes precedence over the default template. From the job detail view, you can always see which workflow is active and where it came from.
The Candidate Experience
Candidates don't see the machinery. What they see is a clear, responsive hiring process.
When they're enrolled in a workflow, they receive step-by-step invitations either delivered together or staged with a delay between them, so each invite feels purposeful rather than automated. Each message tells them what's next and how long they have to complete it.
The interview and scheduling experiences they encounter are the same ones Humanly already powers, familiar, mobile-friendly, and purpose-built for a candidate who might be applying from their phone at 9pm.
Candidates never see a status like "advancing" or "passed." They simply receive a clear next step when they've earned one, or a respectful close if they haven't.
The Recruiter Experience
For recruiters, Workflows shifts the work from coordination to oversight.
From the job detail view, you can see:
- Which workflow is attached to this job and where it came from (template, job family, or per-job override)
- Where each candidate is in the sequence
- Which candidates are progressing and which have stalled or dropped off
Overrides are accessible directly from the job view. If a role needs a different flow, you can edit or reset the workflow without touching your master templates.
The result: instead of shepherding individual candidates through manual steps, your team is monitoring a pipeline that largely runs itself and stepping in where their judgment actually matters.
FAQ
What's the difference between a Workflow and an automation? An automation is a single-action trigger — "when X happens, do Y." A workflow is a multi-step sequence that carries a candidate through multiple stages over time, with gating logic between each step. Think of automations as individual actions and workflows as the full journey.
Can I use different workflows for different jobs? Yes. You can assign workflows at the job level, the job family level, or both. Per-job overrides let you customize individual roles without changing your broader templates.
What if I want some steps to require human review? Today, workflows advance candidates automatically based on score thresholds and completion signals. We're actively building toward more granular manual review gates, the ability to pause progression at specific steps until a recruiter explicitly approves or rejects. Stay tuned.
Does this work with my ATS? Yes. If your ATS is integrated with Humanly, jobs can be automatically imported and associated with workflows. Screener questionnaires and application questions can be attached during setup.
What does the candidate receive at each step? Candidates receive a step-by-step invitation for each stage of their workflow, either immediately or with a deliberate delay. Each message includes what they need to do, a link to complete it, and how long it's available.
Can I stage invites instead of sending everything at once? Yes. Staged delivery is built into Workflows. You can configure delays between steps so the experience feels like a genuine review is happening between stages, not a single automated blast.
Can I reuse workflows across roles and locations? That's the point. Workflow templates are reusable across any number of jobs. Apply one template to multiple roles in a single action.
How do score thresholds affect progression? Each step can have a required score or completion threshold. Candidates who meet it advance automatically. You set the bar; the system enforces it.
How do job families and job overrides work? A job family is a grouping of similar roles that share a workflow template. A job override lets you deviate from that template for a specific role. Override settings are visible from the job detail page, along with the source of the active workflow, so you always know what's running and why.
See Workflows in Action
Workflows is rolling out now. If you're hiring at scale and want to see what a well-built screening sequence looks like end-to-end, we'd love to show you.