Documentation Index
Fetch the complete documentation index at: https://mintlify.com/chamals3n4/OpenATS/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Pipeline stages define the journey candidates take through your hiring process. OpenATS provides flexible, customizable stages that adapt to your unique workflow while automating key actions along the way.Understanding Pipeline Architecture
Global Stage Templates
OpenATS includes system-wide pipeline stage templates that serve as blueprints:- Applied: Initial stage when candidates submit applications
- Screening: Review resumes and responses
- Interview: Various interview rounds
- Assessment: Technical or skills testing
- Offer: Extending job offers
- Hired: Successful candidates
- Rejected: Declined applications
Stage templates are reusable across all jobs, ensuring consistency while allowing per-job customization.
Job-Specific Pipelines
Each job has its own pipeline instance based on templates:Stage Configuration
Basic Properties
Stage Name
Display name shown in the UI (e.g., “Phone Screen”, “Technical Round”)
Position
Order in the pipeline (lower numbers come first)
Stage Type
Special behavior: Assessment, Offer, Rejection, or None
Deletable
Whether stage can be removed from job pipelines
Stage Types & Special Behaviors
Stages can have special types that trigger specific actions:- None
- Assessment
- Offer
- Rejection
Standard stage with no special behavior. Used for general workflow steps like “Screening” or “Interview”.
Offer Stage Configuration
Offer stages have additional settings to control the offer process:Offer Template
Select a pre-built template that defines:- Email subject and body
- Offer letter format
- Variable placeholders (salary, start date, etc.)
Offer Mode
Manual
HR reviews and approves before sendingBest for: Executive roles, complex negotiations
Automatic
System generates and sends immediatelyBest for: High-volume hiring, standard offers
Offer Expiry
Set the number of days until the offer expires:Rejection Stage Configuration
Rejection Template
Assign an email template that:- Thanks candidates for their time
- Provides closure on their application
- Maintains positive employer brand
- Optionally encourages future applications
Assessment Stage Configuration
When configuring an assessment stage:Only one assessment can be attached per stage, but you can have multiple assessment stages in a pipeline.
Managing Pipeline Positions
Ordering Stages
Stages are ordered by their position number:Unique Positions
Each job can only have one stage at each position number, ensuring:- Clear linear progression
- No ambiguous ordering
- Predictable candidate flow
Hiring Teams
Assign team members to jobs to control access and collaboration:Adding Team Members
Team Member Permissions
Hiring team members can:- View all candidates for the job
- Move candidates between stages
- View assessment results
- Create and send offers
- Access stage history and analytics
Team assignments are job-specific. Users can be on multiple hiring teams across different jobs.
Stage Templates vs. Job Stages
Key Differences
| Feature | Stage Templates | Job Pipeline Stages |
|---|---|---|
| Scope | System-wide | Job-specific |
| Reusability | Used across all jobs | Unique to one job |
| Modification | Admin only | Per-job configuration |
| Deletion | Restricted for core stages | Configurable |
Using Templates Effectively
Create role-specific templates
Create role-specific templates
Define templates for Engineering, Sales, Operations, etc. to speed up job creation.
Standardize common stages
Standardize common stages
Use identical stage names across jobs for better reporting and analytics.
Allow flexibility
Allow flexibility
Let hiring managers customize stage names while maintaining the template structure.
Version control
Version control
Track template changes to understand how pipeline evolution affects metrics.
Stage Linking & References
Job stages maintain relationships:Source Template Reference
Each job stage optionally links back to its source template:- Tracks which template was used
- Helps update multiple jobs when templates change
- Maintains consistency across jobs
Template Relationships
Stages reference:- Offer Templates: For offer stage email/document generation
- Rejection Templates: For rejection notification emails
- Assessments: For technical testing triggers
Best Practices
Keep pipelines simple
Keep pipelines simple
Aim for 5-7 stages. Too many stages slow down hiring and confuse candidates.
Name stages clearly
Name stages clearly
Use descriptive names that hiring managers and candidates understand (avoid internal jargon).
Position assessments strategically
Position assessments strategically
Place technical assessments after initial screening but before time-intensive interviews.
Standardize across similar roles
Standardize across similar roles
Use consistent pipelines for similar positions to enable better hiring analytics.
Review and optimize
Review and optimize
Regularly analyze where candidates drop off and streamline bottleneck stages.
Next Steps
Create Assessments
Build technical screening tests
Design Offer Templates
Prepare offer letter templates
Build Email Templates
Create candidate communication templates
Track Candidates
Start managing applications