Applicant tracking system guide

Applicant tracking system guide: records, roles and rollout

Understand the records, decisions, roles, measures and implementation choices behind an ATS—then inspect those ideas in a populated Jodoo application.

An ATS is the operating record for active hiring. It should connect approved demand, candidate movement, interview evidence and offer decisions without turning the candidate database into a collection of disconnected status labels.

  • ATS definition and boundaries
  • Core records and operating controls
  • Implementation plan and measurable outcomes
ATS record model

Four linked records turn applicant status into an accountable process

The exact field list can change, but these connections are what let a hiring team answer who owns the next decision and what evidence supports it.

Job requisition

Captures

Business need, openings, manager, recruiter, priority, budget and target date

Connects

Candidate applications for one approved role

Approve, hold or close demand before recruiting work begins

Candidate application

Captures

Candidate, source, role, stage, owner, disposition and next action

Connects

Interview rounds, scorecards and offer decision

Advance, hold or close with a recorded reason

Interview scorecard

Captures

Round, reviewer, structured evidence, recommendation and completion status

Connects

The candidate application and approved role

Complete the panel, request more evidence or escalate overdue feedback

Offer and decision

Captures

Approval, compensation terms, response, start date and close reason

Connects

The selected application and requisition

Release, revise, withdraw or accept the offer
ATS versus adjacent systems

Use each system for the job it can govern well

The names overlap in vendor marketing. The more reliable boundary is the record and decision each system owns.

Process active applicants against approved roles

What Jodoo handles

A configurable ATS can own requisitions, applications, interviews and offers.

When another product may fit better

A packaged ATS may add native parsing, sourcing and job-distribution depth.

Nurture long-lived talent and client relationships

What Jodoo handles

Use linked recruiting CRM records for talent, clients, jobs and submissions.

When another product may fit better

Choose a recruiting CRM with the outreach and sourcing depth you require.

Manage the employee after hire

What Jodoo handles

Hand the accepted candidate into onboarding and people-operations records.

When another product may fit better

Keep payroll, benefits and authoritative employee data in the HRIS.

Publish jobs and generate applicant traffic

What Jodoo handles

Connect the source and resulting application to the hiring record.

When another product may fit better

Use job boards, careers sites and sourcing networks for candidate acquisition.

How people use an ATS

A useful ATS presents a different next-action view to each role

Adoption improves when people see the decisions they own instead of navigating the same administrator screen.

Recruiter

Starts with
Unreviewed applications, aging stages and missing next actions
Acts on
Screening, coordination, disposition and candidate follow-up
Hands off
Evidence-complete candidate to the hiring manager or interview panel

Hiring manager

Starts with
Approved roles, shortlisted candidates and decisions waiting for input
Acts on
Selection criteria, interview participation and advance or close decisions
Hands off
Documented decision to recruiter and offer approver

Interviewer

Starts with
Assigned interview, role criteria and candidate context
Acts on
Structured evidence and recommendation
Hands off
Completed scorecard without exposing unrelated candidate data

Recruiting leader

Starts with
Funnel, aging, source, feedback and offer signals
Acts on
Capacity, blocker and policy decisions
Hands off
Actionable exception to the accountable owner
ATS measures that support action

Define every recruiting metric with a denominator and a response

A dashboard is valuable when the number opens the records that created it and tells the team what to do next.

Application review coverage

Applications reviewed within the service targetApplications received
Rebalance ownership or change the screening rule

Stage aging

Candidates beyond the agreed stage durationOpen candidates in that stage
Resolve the blocker, schedule the next step or close the record

Interview feedback completion

Scorecards completed by the deadlineScorecards assigned
Remind the reviewer or escalate an overdue panel

Offer acceptance

Offers acceptedOffers released
Review role, compensation, timing and decline evidence
ATS implementation plan

Implement one hiring cohort before migrating every historical record

A bounded first cohort reveals workflow, access and reporting problems while the cost of correction is still low.

  1. Days 1–3

    Freeze the hiring decisions

    • Name the requisition, candidate, interview and offer owners
    • Agree required fields, stages, dispositions and service targets
    • Approve candidate privacy, retention and access rules
    A signed record and responsibility map
  2. Days 4–7

    Configure and test the record flow

    • Build forms, related records, role views and reminders
    • Load representative sample candidates
    • Test advance, return, hold, reject and offer paths
    Every branch preserves owner, evidence and next action
  3. Week 2

    Run one live role

    • Process a bounded candidate cohort
    • Complete an interview panel
    • Open each dashboard signal back to source records
    The team completes decisions without a parallel tracker
  4. Weeks 3–4

    Improve from evidence

    • Review aging, feedback and disposition quality
    • Change one field, rule, view and measure
    • Document the migration and integration decision
    The ATS administrator owns routine change safely
Why a configurable ATS matters

Change the hiring process while the policy is still evolving

When the hiring process is distinctive, the cost of a small change matters as much as the original feature list.

Typical queued change5–20 business days

A small ATS change can wait behind vendor services, development or a central systems backlog.

Focused Jodoo configuration30 minutes–4 hours

A trained administrator can often add a field, stage, role view, reminder or dashboard segment and test it with sample records.

  • Add a new interview evidence field and reviewer view
  • Create an overdue-feedback reminder and exception queue
  • Separate contractor and employee requisitions without duplicating the application
Applicant tracking system questions

Clear answers before you design or buy an ATS

What is an applicant tracking system?

An applicant tracking system is software that organizes active hiring demand, candidate applications, selection stages, interview evidence and offer decisions. A useful ATS also assigns ownership, records next actions and exposes exceptions for management review.

Is an ATS the same as a recruiting CRM?

No. An ATS primarily processes candidates against active jobs. A recruiting CRM preserves longer-lived talent, client and hiring relationships. Some products combine both, but the records and user tasks should still be distinguishable.

What information should an ATS store?

At minimum: approved role, candidate and source, stage, owner, next action, decision evidence, interview scorecards, disposition and offer outcome. Privacy, access, retention and deletion rules are equally important.

Can a small team build an ATS in Jodoo?

Yes. Jodoo can connect requisitions, applications, scorecards, offers and dashboards. If the team also needs built-in resume parsing, job-board distribution or sourcing networks, add a proven integration or compare specialist ATS products.

How should an ATS implementation be measured?

Measure whether the team completes hiring decisions without shadow trackers: review coverage, stage aging, feedback completion, disposition quality, offer outcomes and the effort required to change the process.

Turn the ATS guide into a working pilot

Test the record model with one role and a representative candidate cohort

Use real owners and decisions, but begin with bounded data. Prove the workflow, access and reporting before scaling the implementation.

Explore the working ATS