The Applicant Tracking System Template That Moves Candidates Instead of Losing Them

Lead: Most ATS templates are spreadsheets that look like a hiring pipeline. You add candidates, drag them across columns, and feel organized for about two weeks. Then a candidate sits in "Phone Screen" for eleven days because nobody assigned the interviewer. Another one drops out because the hiring manager never saw their application. The pipeline looks full. The roles stay open. The template told you where candidates were, but it never moved them forward.

We pulled the recruiting and applicant tracking templates from Greenhouse, Lever, and Airtable. Each one gets part of the pipeline right. None of them ship all three things a small hiring team needs: automatic stage-transition alerts, interviewer auto-assignment, and a scheduled digest that tells you which candidates are stuck and which roles are falling behind.

We rebuilt all three into a Baserow template — free, open source, self-hosted, zero per-seat pricing. The alerts work the day you install it.

Why most ATS templates fail at the handoff

Hiring is a team sport with terrible handoffs. A recruiter screens a candidate, moves them to "Interview," and expects the hiring manager to pick it up. But the hiring manager does not check the ATS. They check email, Slack, and their calendar. The candidate waits. The template does not care.

No stage-transition notification. When a candidate moves from Applied to Phone Screen, who gets told? In most templates, nobody. The recruiter knows because they moved the card. The interviewer finds out when someone pings them on Slack three days later.

No auto-assignment. A candidate reaches the Technical Interview stage. Who conducts it? The template does not know. Someone has to manually assign an interviewer, check their calendar, and send the invite. Each manual step is a place where the process stalls.

No staleness detection. A candidate has been in "Hiring Manager Review" for nine days. Is that normal or is that a problem? The template cannot tell you because it does not compare the current date to the last stage transition. Stale candidates are invisible until they accept another offer.

No pipeline health view. How many candidates are in each stage? Which roles have a thin pipeline? Which have candidates bunching up at the interview stage? Most ATS templates show you individual candidate cards, not the aggregate health of your hiring operation.

What the competitors actually give you

Greenhouse: the right structure

Greenhouse is the gold standard for structured hiring. Scorecards, stage-specific interview kits, configurable approval chains — the workflow logic is comprehensive. For companies doing 50+ hires a year with a dedicated recruiting team, Greenhouse earns its price.

What it costs: Greenhouse does not publish pricing, but reported ranges start at $6,000/year. Implementation takes weeks. The system is designed for full-time recruiters, not a startup founder who is also the hiring manager, the interviewer, and the onboarding buddy. The power is real; the overhead is too.

Lever: the right candidate experience

Lever combines ATS and CRM into a single system, which means it tracks candidates across roles and over time. If someone applies, gets rejected, and applies again two years later, Lever remembers. The nurture campaign feature keeps passive candidates warm. For talent teams thinking long-term, Lever's relationship-tracking model is the right idea.

What it costs: Lever's pricing starts around $3,500/year for small teams. The CRM features that differentiate it from a basic ATS are in the higher tiers. For a five-person startup hiring three roles a quarter, the price-to-value math does not work.

Airtable: the right data model

Airtable's Applicant Tracker template separates Candidates, Positions, and Interviews into linked tables. The structure is correct — you can view candidates by role, by stage, by recruiter, and the rollup fields aggregate counts per position.

What it does not do: move things forward. No stage-transition alerts. No interviewer assignment logic. No staleness detection. The template models the shape of a hiring pipeline without modeling the motion. You still need a human to push every candidate through every gate.

Comparison: ATS features across platforms

| Feature | Greenhouse | Lever | Airtable | OSAI Pro | |---|---|---|---|---| | Candidate pipeline stages | Yes | Yes | Yes | Yes | | Stage-transition alerts | Yes | Yes | No | Yes (event alert) | | Auto-assignment to interviewers | Configurable | Configurable | No | Yes (rule-based) | | Stale-candidate flag | Partial | Partial | No | Yes (formula) | | Interview scheduling | Yes (with integrations) | Yes | No | Yes (linked table) | | Hiring pipeline digest | Yes (reports) | Yes (reports) | No | Yes (scheduled) | | Self-hosted / data ownership | No | No | No | Yes | | Pricing | ~$6,000+/yr | ~$3,500+/yr | $20/seat | $0 (self-hosted) |

The rebuild: an ATS that pushes candidates forward

The Applicant Tracking System template runs on Baserow and adds the motion layer that spreadsheet-based ATS templates miss.

Candidate pipeline stages with formula-driven flags. Candidates move through stages: Applied, Screening, Phone Interview, Technical Interview, Hiring Manager Review, Offer, Hired, Rejected. A formula field calculates Days_In_Stage by comparing the Stage_Entry_Date to today. When a candidate exceeds the stage threshold — five days is the default for early stages, ten for later stages — they are flagged as stalled. The flag is a formula. It does not rely on anyone checking.

Auto-assignment at stage transitions. When a candidate moves to a new stage, the template assigns the appropriate team member based on the role and stage. Technical Interview goes to the engineering lead. Hiring Manager Review goes to the department head. The assignment is rule-based and fires via event-triggered automation — no one has to remember who handles what.

Interview scheduling via linked tables. Interviews are a separate, linked table — not a text field on the candidate record. Each interview has a date, time, interviewer, type (phone/onsite/technical), and outcome. When an interview is logged, the candidate record updates automatically. The interview history is a first-class entity, not a note someone typed into a comment box.

Stage-transition alerts. When a candidate moves stages, the next person in the pipeline gets an email — the interviewer, the hiring manager, or the recruiter, depending on the stage. The alert includes the candidate name, the role, and a link to the record. It fires once per transition and re-arms automatically.

Scheduled hiring pipeline digest. A weekly email summarizes the health of every open role: candidates per stage, stalled candidates, interviews scheduled for the coming week, and roles with thin pipelines. The hiring manager gets this without logging into the ATS. It is the recruiting standup, automated.

Working sample data. The template ships with three open roles, fifteen candidates across all stages, and five scheduled interviews. Three candidates are deliberately stalled. One role has a thin pipeline. The system demonstrates its exception logic the moment you open it.

Who this is for

Startups hiring their first 10-50 employees. You do not have a recruiter. The founders are screening, interviewing, and closing candidates between product meetings. You need an ATS that moves candidates forward automatically, not one that requires a full-time operator.

Small HR teams at growing companies. You have one or two recruiters managing twenty open roles. Candidates get stuck because handoffs are manual. You need stage-transition alerts and stale-candidate flags, not a $6,000/year platform.

Hiring managers at any company. You are not in the ATS every day. You need to know when a candidate is waiting on your review without checking a dashboard. An email when a candidate enters your stage is worth more than a beautiful pipeline view you never see.

Any team where ATS pricing blocks access. If only the recruiter has an ATS seat and the hiring managers use email, the pipeline has a gap. Zero per-seat pricing means everyone involved in hiring is in the system.

What open source buys you here

Candidate data is personal data. Names, resumes, interview notes, evaluation scores — in most jurisdictions, this is regulated information. GDPR, CCPA, and similar frameworks have specific requirements about where personal data is stored and who has access.

Self-hosted Baserow means candidate data lives on your infrastructure, inside your compliance boundary. No vendor has access to your applicant pool. No third-party data processing agreement is required. And when a candidate requests data deletion under GDPR, you delete it from your server — not from a vendor's database where you hope they actually purged it.

Get the template

The Applicant Tracking System template is free, with working sample data, deployable to any Baserow instance.

[DOWNLOAD CTA: Get the free Applicant Tracking System template -->] (Email-gated download. You will also get our weekly pattern breakdown — one reusable workflow pattern, every week, no filler.)

Evaluation checklist for any ATS template

1. When a candidate moves stages, does the next person in the pipeline get notified automatically?
2. Is there a formula-driven flag for candidates who have been stuck in a stage too long?
3. Are interviews tracked as linked records with outcomes, or as notes on the candidate card?
4. Can you see pipeline health across all roles without building a custom report?
5. What does it cost to give every interviewer and hiring manager access?

---

OpenSource AI Pro ships self-hosted business templates with built-in automation — formula-driven flags, event-triggered alerts, and scheduled digests. Zero per-seat pricing, fully open source.