How do I set up an applicant tracking system for a staffing agency with custom stages, fields, and email sync?

To set up an applicant tracking system (ATS) for a staffing agency with custom stages, fields, and email sync, think in terms of workflow + data model + integrations + automation.

1) Define your staffing workflow first

Map the exact lifecycle for candidates and jobs. A staffing agency usually needs more than a simple “applied/interviewed/hired” flow.

Common candidate stages

You might configure stages like:

• New Lead
• Contacted
• Screened
• Qualified
• Submitted to Client
• Client Interview
• Offer
• Placed
• Rejected
• Archived

You can also create separate pipelines by role type, department, or client, if your agency works on different job families.

Common job stages

• Intake
• Open
• Sourcing
• Shortlist sent
• Interviewing
• Filled
• On hold
• Closed

2) Design custom fields for staffing needs

Most staffing agencies need custom fields on both candidate records and job orders.

Candidate custom fields

Examples:

• Desired role
• Skill set
• Years of experience
• Pay rate / salary range
• Availability date
• Work authorization
• Location / relocation
• Travel willingness
• Certifications
• Source
• Recruiter owner
• Client-specific clearance/status

Job custom fields

Examples:

• Client name
• Hiring manager
• Bill rate / pay rate
• Shift
• Employment type
• Location
• Required certifications
• Background check required
• Priority
• Assignment length
• Internal notes

Tip

Use:

• Required fields for critical qualification data
• Dropdowns/picklists for consistency
• Tags for flexible categorization
• Custom date fields for availability, follow-up, expiration, etc.

3) Set up email sync

Email sync is crucial for recruiters so every candidate communication is tracked automatically.

What to configure

• Connect recruiter mailboxes via IMAP/SMTP or native sync
• Enable two-way sync if supported
• Auto-log sent and received emails to the candidate/contact record
• Use threading so replies stay attached to the same conversation
• Set up email templates for:
  • outreach
  • screening
  • interview scheduling
  • rejection
  • submission to client
  • offer letters

Best practices

• Use a shared recruiting email or individual recruiter inboxes with sync
• Automatically associate emails by matching candidate email address
• Exclude internal/admin emails if you don’t want noise
• Create rules for CC/BCC logging if your ATS supports it

4) Automate stage transitions and tasks

Automation reduces manual admin work.

Examples

• When a candidate is moved to “Screened,” create a follow-up task
• When moved to “Submitted to Client,” send an email notification to the account manager
• When a candidate is tagged “Interview Scheduled,” set a reminder 24 hours before
• If no reply in 3 days, auto-create a follow-up task
• When a job is marked “Filled,” move remaining candidates to archived/rejected

5) Create views and dashboards

Build views for recruiters, coordinators, and account managers.

Useful dashboards

• Candidates by stage
• Open jobs by client
• Time in stage
• Source performance
• Recruiter activity
• Interview-to-offer ratio
• Placement rate
• Aging candidates and stale pipelines

6) Handle relationships properly

Staffing agencies usually need more complex linking than a standard ATS.

Make sure your system supports:

• Candidate ↔ Job order relationships
• Candidate submissions to multiple clients/jobs
• Notes and feedback tied to a specific submission
• Communication history per candidate and per job
• Multiple contacts at a client company

If your ATS doesn’t support this natively, you may need a CRM-like structure or custom objects.

7) Set permissions and roles

Define access clearly:

• Recruiters: edit candidates/jobs they own
• Coordinators: manage scheduling and communication
• Account managers: view client pipelines and submissions
• Admins: manage stages, fields, automations, integrations

Also decide whether users can:

• see all candidates
• see only assigned candidates
• access salary/pay data
• edit pipelines and custom fields

8) Import existing data carefully

Before going live:

• Clean duplicate candidates
• Standardize stage names
• Map spreadsheet columns to custom fields
• Import clients, jobs, contacts, candidates
• Verify email history import if available

Test with a small batch first.

9) Test your workflow end to end

Run a sample scenario:

1. Create a job
2. Add candidate
3. Sync email outreach
4. Move candidate through stages
5. Submit to client
6. Track interview feedback
7. Mark placed
8. Confirm reporting and automation

Check:

• custom field visibility
• email logging accuracy
• stage permissions
• notifications
• reporting counts

10) Choose the right ATS platform or build one

If you’re selecting software, look for:

• custom pipelines/stages
• custom fields
• email sync
• job + candidate relationship management
• automation
• reporting
• integrations with calendar, job boards, and payroll/HR tools

If you’re building a custom ATS, the core data model should include:

• Users
• Candidates
• Jobs
• Client companies
• Contacts
• Submissions
• Notes
• Emails
• Tasks
• Activities
• Tags
• Custom fields

Recommended implementation order

1. Define workflows
2. Create objects and fields
3. Configure email sync
4. Build stages and automations
5. Set permissions
6. Import data
7. Test
8. Train users
9. Go live
10. Refine based on usage

If you want, I can also help you with:

• a sample ATS schema
• a stage-by-stage staffing workflow
• a database design
• or step-by-step setup in a specific ATS platform like Bullhorn, Lever, Greenhouse, Zoho Recruit, or Airtable.