Picture the HR lead at a 120-person company with seven requisitions open across four departments. Engineering wants updates daily but hasn't logged interview feedback since May. The sales director keeps candidates warm over text and tells no one. Finance asks for time-to-fill numbers that would take an afternoon of spreadsheet archaeology to produce. And somewhere in that mess, a candidate who interviewed twice is waiting on an answer nobody remembers owing them.
The vendor solution is a full ATS, and the quote lands hard — Greenhouse comes in around $6,500 a year, which is a genuine line item for a mid-sized company that also needs the budget for the actual salaries. Worse, an expensive tool doesn't fix the real failure mode: hiring managers who won't open it. If the system of record requires a login people avoid, the record stops being real.
There's a quieter route. Most HR teams already run recruitment out of a spreadsheet anyway — the trick is promoting that spreadsheet into a proper hiring system with AI: a careers page feeding it, resume scores landing in it, and views each hiring manager will actually use. Cost: nothing.
Build a Roles tab first — one row per requisition with title, department, hiring manager, requirements, and status. The Applicants tab captures the pipeline and fills automatically once live:
| Column | Example |
|---|---|
| Candidate | Priya Nair |
| Role | Financial Analyst |
| Department | Finance |
| Hiring manager | T. Whitfield |
| Stage | Panel interview |
| Score | 91 |
| Interview feedback | Strong modeling; light on forecasting tools |
| Days in stage | 6 |
Days in stage is the column HR dashboards are made of. Once it exists per candidate, time-to-fill stops being archaeology and becomes arithmetic.
Register at lovespreadsheets.com — building and operating both the public page and the tracking layer costs nothing. You move to the paid plan when you want individual logins for every hiring manager or the careers site on your company domain.
Select the Website template and write the recruitment process as your team actually runs it:
"Publish our open requisitions from the Roles tab as a careers page, grouped by department. Applicants go through a brief guided flow — contact details, resume upload, plus two screening questions specific to the role. Each submission becomes a row in Applicants. Evaluate every resume from 1 to 100 against the requisition's stated requirements and record the score with a short written rationale. Acknowledge every applicant by email immediately."
Then ask for the pieces HR teams are usually missing:
Expect a clarifying question or two from the AI Optimize step; the build itself wraps in the 15–20 minute range.
You end up with a public careers page and an internal pipeline view over one sheet. Every application arrives pre-scored with reasoning tied to the requisition's own requirements — useful triage when a popular posting pulls a hundred resumes. Stages, feedback, and dates accumulate into exactly the defensible record HR needs: who applied, who was seen, what was assessed, and when each decision happened.
To be precise about the scoring: it ranks the reading pile against criteria you authored, and it explains itself in writing. No candidate is filtered out by a number — humans advance and decline, and the sheet remembers that they did.
Adoption stops being a battle. Hiring managers won't learn an ATS, but they'll click a link showing only their candidates and fill a 60-second feedback form. Lower friction, better data.
Metrics come free with the structure. Because stage changes and dates live as cells, time-to-fill, source quality, and pipeline conversion are queries — not a quarterly project.
The audit trail is yours forever. Scores with rationale, feedback with timestamps, decisions with dates — exportable, filterable, and not held hostage by a vendor contract you might cancel.
Is an AI score defensible in our process? More defensible than an unexplained gut call: the criteria are the requisition's published requirements, the rationale is written down, and every advance-or-decline decision is made and recorded by a person.
Can hiring managers see each other's pipelines? Only if you want them to. Scoped views mean each manager gets their requisition; HR and leadership get the cross-department picture.
Where does this hand off to onboarding? Once the offer is signed, onboarding is its own checklist — that's covered in our employee onboarding tracker for HR teams.
Draft the Roles tab from your open reqs, head to lovespreadsheets.com, and write down the process you keep describing in kickoff meetings. The general-purpose build is documented in the Google Sheets ATS walkthrough, and there's a recruiting-agency edition if you work with external partners. Next quarter's time-to-fill report can be a filter, not a favor.
The team turning other people's spreadsheets into software they actually trust — one sheet at a time.