Starting honest: spreadsheets are not the wrong answer for everyone

Spreadsheets are free. Flexible. Everyone knows how to use them. And they're genuinely fine for a company that hires 5 people a year. This article is not for that company.

This article is for the company that's hiring 20+ people per year and still wondering if an ATS is worth it. For the recruiter who's managing 15 open roles in a spreadsheet and spending Sunday evenings on follow-up emails. For the HR manager who just lost a great candidate because the interview scheduling took too long and a competitor moved faster. For the team where one person owns the spreadsheet, and everyone else is asking them for status updates they don't have time to give.

That's right: you already know the spreadsheet is a bottleneck. The question is whether the ATS solution is worth the cost and disruption of switching. That's the calculation this article makes honestly, including naming the scenarios where spreadsheets remain perfectly adequate.

The time cost that rarely gets calculated

The most significant cost of managing hiring in spreadsheets at 20+ hires per year is time — and it almost never gets calculated explicitly because it doesn't appear on any invoice. Let's make it explicit.

For a company hiring 25 people per year with a single recruiter, consider the spreadsheet-based workflow for each hire:

  • Initial CV processing: Reading each application, copying key data to the tracking spreadsheet, deciding whether to advance. At 40 applications per role and 25 roles, that's 1,000 CVs. Even at 2 minutes per CV for the tracking step alone (not including the actual read), that's 33 hours per year in data entry.
  • Interview scheduling coordination: For each candidate invited to interview, there's an average of 4–6 email exchanges to find a time that works for the candidate, the recruiter, and the hiring manager. At 3 interviews per hire and 25 hires, that's 75 multi-email scheduling threads — conservatively 15 minutes each. That's 18.75 hours per year.
  • Status management and stakeholder updates: Hiring managers asking for status, candidates following up, internal updates to team spreadsheets. At 30 minutes per week per active role, with an average of 8 roles simultaneously, that's 4 hours per week, 200 hours per year.
  • Follow-up and rejection emails: Each rejected candidate deserves a timely response. Managing this manually at volume — checking who has been followed up with, drafting appropriate responses, sending, tracking — takes 5–10 minutes per candidate. At 1,000 applications and a 97.5% rejection rate (25 hires from 1,000 applications), that's 975 rejection emails, at 7 minutes each, which is 113 hours per year.

Adding the conservative estimates: 33 + 18.75 + 200 + 113 = 364 hours per year in spreadsheet-based hiring administration. At a fully-loaded recruiter cost of $35 per hour, that's $12,740 per year in labour spent on tasks that an ATS would automate — before accounting for the cost of hiring manager time on scheduling, the cost of delayed decisions, or the candidate experience cost of slow follow-up.

That's right. The spreadsheet is not free. It's $12,000–$15,000 per year in invisible labour cost at a hiring volume that many growing companies consider modest.

The compliance risk no one talks about

Spreadsheets carrying candidate personal data create compliance exposure that most companies managing hiring this way have not fully assessed.

GDPR and data protection law: Under GDPR (and most equivalent data protection frameworks), candidate personal data has retention limits — you cannot keep a rejected candidate's CV and personal details indefinitely. Spreadsheets have no automated retention enforcement. Candidate data sits in shared drives indefinitely, often with access controls that don't reflect the actual permission structure for personal data. Auditing who has access to candidate data in a spreadsheet environment is effectively impossible.

EEO and diversity reporting: US employers with 100+ employees (or federal contractors with 50+) have reporting obligations under EEOC that require demographic data collection from applicants. Collecting this data manually and correctly in a spreadsheet — ensuring the right questions are asked, in the right way, in a separate voluntary section — is difficult to implement consistently and nearly impossible to audit.

Audit trail absence: When a hiring decision is challenged — by a rejected candidate, by a regulatory body, in an employment discrimination claim — the question is: what was the basis for the decision, and was it consistently applied? A spreadsheet tracking "advanced / rejected / pending" provides no evidence of consistent process. An ATS creates a documented timeline of every action, every decision, every communication — the audit trail that turns a challenging legal conversation into a manageable one.

Data breach exposure: A spreadsheet emailed to a hiring manager, or shared in a cloud drive with broad access permissions, or downloaded to a personal laptop, creates data breach exposure at every step. Candidate personal data (name, contact details, often salary expectations) sitting in uncontrolled spreadsheets is a GDPR data handling issue, not a theoretical one.

The candidate experience cost

It seems like every company talks about candidate experience in their employer brand content — and then runs a hiring process that candidates experience as slow, disorganised, and impersonal. The correlation between spreadsheet-based hiring and poor candidate experience is not accidental.

The specific failure modes of spreadsheet-based candidate experience:

Response time. In a spreadsheet workflow, nothing happens automatically. Every response — acknowledgement of application, status update, interview invitation, rejection — requires a human to notice it needs to happen, find time to do it, and execute it manually. In practice, this means days-long delays at each step. The best candidates — the ones with multiple options — withdraw from slow processes first.

Disorganised communication. When email is the communication system, candidates receive messages from different email addresses, sometimes from the recruiter and sometimes from the hiring manager, with inconsistent information about timelines and process. Candidates interpret this disorganisation as a signal about how the company operates.

Interview coordination errors. Calendar confusion, double-bookings, and interview panel members who weren't fully briefed — these happen in ATS environments too, but they happen much more frequently when scheduling is done via email and spreadsheet. A single interview scheduling error costs the candidate's time and goodwill in ways that are disproportionately damaging for competitive roles.

The silence problem. In a high-volume spreadsheet environment, rejections often don't get sent at all — the recruiter intends to follow up but never gets to it. Candidates who never hear back mention it in Glassdoor reviews and to their networks. It's a measurable employer brand damage event at scale.

The collaboration and bottleneck problem

Spreadsheets are single-user tools pressed into multi-user service. The structural problems at team scale are predictable and consistent.

The single point of failure. One person owns the spreadsheet. They know where everything is, what it means, and how to interpret the colour coding they invented. When they're on annual leave, hiring slows to what everyone else can reconstruct from memory and email threads. When they leave the company, the institutional knowledge goes with them.

The visibility problem. Hiring manager A can't see what recruiter B did last week without asking. The recruiter can't share a clear pipeline view with the management team without exporting and formatting a spreadsheet snapshot — which is out of date as soon as they send it. No one has a reliable, current view of hiring status without synchronous conversation.

The concurrent editing problem. Two people trying to update the same spreadsheet produce version conflicts, overwrites, and the specific frustration of finding that the notes you added yesterday have been replaced by someone else's edit. This is not a workflow problem that better discipline solves — it's a structural limitation of the tool.

The scale cliff. Below 5 open roles simultaneously, spreadsheet collaboration is manageable with discipline. Above 10 open roles simultaneously — common for companies in a growth phase — the coordination overhead becomes untenable. The cliff is steep and the degradation happens faster than teams expect.

When spreadsheets are genuinely fine — be honest about this

It would be intellectually dishonest to recommend ATS to everyone. The situations where spreadsheets remain perfectly adequate:

  • Fewer than 10 hires per year with a single recruiter handling the process
  • 1–2 person company where the founders hire personally and infrequently
  • Very occasional, highly specialised hiring where each role is a bespoke executive search with a headhunter relationship — the ATS adds less value when the process is not high-volume and the management is relationship-based
  • Pure freelance or contractor engagement that doesn't involve permanent or long-term employment decisions

If this is your situation, the spreadsheet is the right tool. Don't buy an ATS to solve a problem you don't have.

The switching point: where the ROI math flips

Based on the time cost analysis above and market ATS pricing, the ROI calculation flips clearly at approximately 15–20 hires per year.

At 15 hires per year, the conservative time cost of spreadsheet administration is approximately $8,000–$10,000 annually. A mid-market ATS for a small team costs $300–$500 per month — $3,600–$6,000 annually. The net savings in year one: $2,000–$6,400, plus the compliance risk reduction, the candidate experience improvement, and the elimination of single-point-of-failure risk. Year two and beyond: the full $5,000+ savings with implementation costs already absorbed.

At 25 hires per year, the conservative time cost is $12,000–$15,000. The same ATS at the same price produces savings of $6,000–$12,000 annually — clear positive ROI from the first year even after implementation time.

The honest message: the question is not "is an ATS worth it?" The question is "at what hiring volume does my current invisible labour cost exceed the ATS price?" For most growing companies, the answer is somewhere between 12 and 20 hires per year. If you're past that, you're paying more to not have an ATS than you would pay for one.

See exactly what Treegarden costs

All features included. Public pricing. No demo required to see the numbers. Startup: $299/mo · Growth: $499/mo · Scale: $899/mo.

View full pricing →

Frequently asked questions

When should a company get an ATS?

The clearest indicator is hiring volume: consistently 15–20+ hires per year. Secondary indicators that should accelerate the decision: more than one recruiter working simultaneously, any legal compliance obligation for hiring records, a high-priority role where candidate experience matters, or any situation where the spreadsheet owner being unavailable would stop hiring from proceeding.

How much time does an ATS save?

For a company hiring 20–50 people per year, a well-implemented ATS typically saves 4–8 hours per hire in administrative time. At 30 hires per year, that's 120–240 hours of recruiter time annually — approximately $4,200–$12,000 per year in direct labour savings at a $35/hr fully-loaded rate, before accounting for reduced time-to-hire and improved candidate experience.

Is an ATS worth it for a 20-person company?

It depends on hiring velocity, not headcount. A 20-person company hiring 5 people per year does not need an ATS. A 20-person startup hiring 15–20 people per year absolutely does — because coordination complexity at that growth rate will consume disproportionate time, candidate experience will suffer, and the spreadsheet will become a bottleneck.

What are the risks of managing hiring in spreadsheets?

Four risk clusters: Compliance risk (no GDPR-compliant data handling, no EEO data collection, no audit trail). Operational risk (single point of failure when the spreadsheet owner is unavailable). Quality risk (candidate experience suffers with manual follow-up delays). Data risk (no version control, access permissions, or backup for candidate personal data).