Why not just use a spreadsheet for hiring?

Spreadsheets fail in five predictable ways: nobody knows which copy is current, the same person appears twice under different rows, there is no shared notion of who owes a reply, stage history is overwritten silently, and nothing connects a row to the interview that was actually run. Each of those costs candidates rather than time.

Is a lightweight ATS enough for a growing team?

It is enough while your process is screen, interview, decide, and while nobody needs to search a large resume pool or run different stages per role. Once structured scorecards, candidate email sequences, offer letters or compliance reporting become requirements, you need a full ATS. Moving on is cheap here because there are no stored resumes and no hosted job pages to unwind.

How do I move from a spreadsheet to an ATS?

Export the spreadsheet as CSV with a name column and an email column, create your open jobs, then import the file against the right job, up to 500 rows at a time. Every row is reported individually so you can see exactly which lines failed. Then point your career page at the apply API so new applicants stop arriving in a spreadsheet at all.

Simple ATS: A Lightweight Alternative to the Hiring Spreadsheet

Q: What is a simple ATS?

A lightweight applicant tracking system that does the core job and nothing else: a list of open roles, every applicant against those roles, and a fixed set of stages showing where each person is. No resume parsing, no configurable workflows, no candidate email automation, no compliance module. The InterviewWatch built-in ATS uses six fixed stages and can be learned in one sitting.

Q: Why are the stages fixed instead of configurable?

Because configurable stages are the point where an ATS starts needing configuration, training and an owner. Six fixed stages, Applied, Phone screen, Onsite, Offer, Hired and Rejected, cover the shape of nearly every small-team process, and fixing them is what keeps setup at zero minutes.

Short answer

A simple ATS holds your open roles, every applicant against them, and a fixed set of stages, and stops there. The InterviewWatch built-in ATS uses six fixed stages (Applied, Phone screen, Onsite, Offer, Hired, Rejected), stores a name and an email per candidate, and needs no configuration before first use.

Moving off a spreadsheet takes one CSV import. Moving off this later takes one CSV export, because nothing about it is designed to hold you.

Five ways spreadsheets fail

The problem with a hiring spreadsheet

People usually justify moving off a spreadsheet with efficiency. The real reason is that a spreadsheet cannot represent the things hiring depends on.

1. There is no current copy

Someone downloaded it, edited it, and mailed it round. Two versions now exist and neither is wrong, which is worse than one being wrong.

One board

A single pipeline per company, read and written by everyone with a seat. There is no copy to fall out of date.

2. The same person appears twice

They applied to two roles in March and June, spelled their name differently, and now their history is split across four rows.

Deduplicated by email

One candidate per email address per company, with one card per job. Their whole interview history stays on one identity.

3. Nobody owes anything

A cell says "waiting on hiring manager" and has said so for nine days. There is no notion of time in a stage, so nothing surfaces.

Time in stage on the card

Every card shows how long it has been where it is, which is what makes a stalled candidate visible without a report.

4. History is overwritten

Someone typed over "phone screen" with "rejected". What happened, and when, is gone with no trace.

Stage moves are recorded

The card carries its last move, and any interview run against it keeps its own timestamped, signed report permanently.

5. Rows are not connected to interviews

The spreadsheet says an interview happened. What happened in it lives in someone's memory, or a doc nobody can find.

Interviews attached to the card

Scheduled from the card, with the join link, the interviewer, and afterwards an integrity score on the same card.

Spreadsheet, light, full

Three options to compare

Two of the three columns below are not our product, and both are the right answer for some teams.

Question	Spreadsheet	Light ATS (this)	Full ATS
Cost	Free	$0 to $19 / month	Usually per seat, often annual
Setup time	Minutes	Minutes	Days to weeks
Shared, single source of truth	No	Yes	Yes
Duplicate candidates	Constant	Prevented by email	Prevented, with merge tools
Applications arrive automatically	No	Yes, via apply API	Yes, hosted careers page and job boards
Resume storage and search	Folder of files	None by design	Yes, with parsing and search
Custom stages and scorecards	Whatever you type	No, six fixed stages	Yes
Candidate email automation	No	No	Yes
Compliance reporting	No	No	Yes
Interview integrity evidence	No	Yes, built in	Usually a separate vendor
Cost of leaving	Nothing	A CSV export	Migration project

Read the last two rows together.

The one capability a light ATS has that a full ATS usually does not is verified interviews, because that normally means buying a second product and wiring it in. Everything else on the list is a genuine reason to pay for a bigger tool.

Moving across

How migration works

Tidy two columnsYour spreadsheet needs a name column and an email column. Everything else can stay, and will be ignored. Rows without a valid email will be reported rather than silently dropped.
Create the jobs firstOne job per role you are hiring for. Imported applicants land against a job, so the jobs have to exist before the import.
Import, up to 500 rows at a timePick the file, pick the job. The result tells you how many were created, how many were already there, and the line number and reason for anything that failed.
Set the stagesEveryone lands in Applied. Drag the people who are further along into Phone screen or Onsite, which takes a couple of minutes for a real pipeline.
Turn off the tapPoint your career page at the apply API so new applicants arrive on the board directly. This is the step that stops the spreadsheet coming back. Integration guide.

What we left out

What it leaves out, and why

Simplicity is easy to claim. Here is the actual list, and why each line is missing rather than merely unfinished.

The line is drawn on purpose, and it is drawn in the same place for everyone.

Configurable stages

The moment stages are configurable, someone owns configuring them, and new interviewers need training on what your stages mean. Six fixed stages need no explanation.

Resume upload and parsing

Parsed resumes are the largest pile of candidate personal data most companies never audit. A name and an email is enough to run a pipeline, and much easier to defend in a privacy review.

AI candidate scoring

Ranking applicants automatically is a different product with real fairness risk. Our AI-related work points at whether an interview was genuine, not at whether a person is employable.

A hosted careers page

Your careers page is marketing and SEO, and it should live on your domain. We take applicants through an API instead, so there is nothing to migrate later.

Candidate email automation

Templated rejection and nudge sequences are worth having at volume, and they are also the fastest way for a small team to sound like a machine. Below a certain volume, write the email.

Per-move audit history

The card records its last move rather than a full audit trail. A per-move history is the seed of compliance reporting, which is a product we are not building. Interviews keep their own permanent signed records.

FAQ

Simple ATS: frequently asked questions

What is a simple ATS?

A lightweight applicant tracking system that lists your open roles, holds the applicants against them, and shows a fixed set of stages. No resume parsing, no workflow builder, no email automation, no compliance module. This one has six fixed stages and needs no configuration before first use.

Why not just keep using a spreadsheet?

Because spreadsheets cannot represent a current shared truth, a single candidate identity, time spent waiting, what changed, or what happened in an interview. Those five gaps cost you candidates, not hours.

Is a lightweight ATS enough as we grow?

While your process is screen, interview, decide, yes. Once you need resume search across a large pool, different stages per role, structured scorecards, email sequences or compliance reporting, buy a full ATS. Leaving here is a CSV export, by design.

How do I move my spreadsheet in?

Create your jobs, save the sheet as CSV with name and email columns, then import up to 500 rows against a job. Every row reports back individually, so bad lines are visible rather than silent.

Why can't I add my own stages?

Because that is where configuration, training and an internal owner start. Applied, Phone screen, Onsite, Offer, Hired and Rejected fit the overwhelming majority of small-team processes, and fixing them is what keeps setup time at zero.

Can I track candidates without using the interview monitoring?

Yes. Use it as a pipeline and never schedule a monitored round, or ask us to configure the account as ATS-only, where scheduling records the meeting but issues no candidate join link and consumes no interview allowance.

Does it work on a phone?

The dashboard is a responsive web app, so the board is usable on a phone for moving cards and checking where people are. Wiring up the careers API is a desktop job, and only needs doing once.

Replace your hiring spreadsheet

Import it, set your stages, and let your career page fill the board from then on. Free with unlimited seats.

Start free See the built-in ATS

Keep reading

Careers page APIStop applications arriving in an inbox ATS for small teamsClosing the handoff gaps Free ATSThe free plan, with its real limits Verified interviewsThe one thing a spreadsheet cannot do