+1 (415) 612-6492

Build an Applicant Tracking System in Airtable: Pipeline, Scorecards, and Offer Approvals

Hiring is one of the most common processes that outgrows a spreadsheet. Candidates sit in three inboxes, interviewers forget to leave feedback, and nobody can say how many people are at the offer stage. Airtable handles this well because a hiring pipeline is a set of linked records moving through stages. This tutorial builds a lightweight applicant tracking system (ATS) from scratch.

1. Model the data first

Avoid one giant Candidates table. Use four tables:

  • Roles: Role Title, Department, Hiring Manager (collaborator), Status (Open, On hold, Filled), Target Start.
  • Candidates: Name, Email, Source (single select), Resume (attachment), Notes. Candidates are people, not applications.
  • Applications: Candidate (link), Role (link), Stage (single select), Stage Entered (date), Rejection Reason, Average Score (rollup). One candidate can apply for several roles, so the application is the junction record.
  • Interviews / Scorecards: Application (link), Interviewer (collaborator), Round, one rating field per criterion, Recommendation, Comments.

This follows the same junction pattern as any many-to-many relationship, and it keeps reporting honest: time-in-stage and conversion are measured on applications, not people.

2. Define stages and keep them few

Use a single select with a short list: New, Screen, Interview, Final, Offer, Hired, Rejected. Resist adding a stage for every nuance. Put detail in other fields. Make Rejection Reason required in practice by using an automation (below) that flags rejected records without one.

3. Capture applications with a form

Build a form on Applications or a staging table. Ask only for what you will use: name, email, role (prefilled from the URL), resume upload, and a short question or two. Keep demographic or sensitive questions out of the main form unless you have a legal reason and a separate, restricted place to store them.

4. Automate the stage changes

Three automations cover most of the value:

  1. Stage timestamp. Trigger: when a record matches conditions or when a record is updated (Stage). Action: update the record, setting Stage Entered to the current date. This gives you time-in-stage.
  2. Interviewer request. Trigger: Stage becomes Interview. Action: create the scorecard records (one per interviewer listed on the role) and send each interviewer an email or Slack message with a link to their interface page.
  3. Stale application alert. A scheduled automation each morning finds applications where Stage is not Hired or Rejected and Stage Entered is more than 7 days ago, then sends the hiring manager a digest.

Test each with a dummy candidate and check run history before relying on it.

5. Use structured scorecards

Free-text feedback is hard to compare. Give every scorecard the same criteria (for example Technical, Communication, Role fit) as rating fields from 1 to 5, plus a Recommendation single select (Strong yes, Yes, No, Strong no). On Applications, roll up the ratings with AVERAGE and count the scorecards submitted against the number requested. Add a formula such as:

IF({Scorecards Submitted} >= {Scorecards Requested}, "Ready to decide", "Waiting on feedback")

6. Build interfaces by audience

  • Recruiter view: a kanban grouped by Stage, filtered by role, with a record detail page.
  • Hiring manager view: only their roles, with scores and a decision button.
  • Interviewer view: a page filtered to scorecards where Interviewer is the current user, so each person sees only their own assignments and the resume.

Interface visibility is not the same as data security. If interviewers should not see salary expectations or other candidates' notes, keep that data out of the tables they can access, or use a separate base and sync only the fields they need.

7. Offers and approvals

Add Offer Amount, Offer Status (Draft, Pending approval, Approved, Sent, Accepted, Declined) and an approver. Use an automation to notify the approver when the status becomes Pending approval, and lock down who can edit Offer Amount through interface design and base permissions. When Stage becomes Hired, create a record in an onboarding table so nothing is retyped.

8. Report on the funnel

Useful metrics: applications per source, conversion between stages, median days per stage, offer acceptance rate, and open roles by age. A summary table or interface charts will cover these. Group by Stage and Source first, and refine later.

9. Privacy and retention

Candidate data is personal data. Decide how long you keep rejected applicants, record consent where required, and schedule an automation or monthly review to archive or delete records past the retention date. Limit base editors to those who need them and remove shared links you no longer use.

Common mistakes

  • One row per person instead of per application.
  • Too many stages, so nobody updates them.
  • Collecting feedback in email rather than scorecards.
  • Giving everyone base-level access because it is faster than designing interfaces.

Need help?

BaseBrainers designs and builds Airtable systems for operations, HR, and enterprise teams, including data models, automations, and interfaces. If your hiring process has outgrown its current setup, get in touch through our contact page.