How to run a structured interview without an ATS

You can run a structured interview without an applicant tracking system (ATS) if four things live in writing: the same questions for every candidate, an anchored scorecard each interviewer fills in alone, a tracker that shows where every candidate stands, and a record of why you decided. A shared folder, a spreadsheet, a form and a calendar cover all four for a team that hires a handful of people a year.

This page is for hiring managers at small companies, often without a recruiter: what structure actually requires, the folder and files to set up in an afternoon, how to keep scores independent, what records to keep, and a checklist per role.

What structure needs, and what an ATS was doing for you

The US Office of Personnel Management's structured interview guide sums up a structured interview in three points: every candidate is asked the same questions in the same order, evaluated on a common rating scale, and interviewers agree on what acceptable answers look like. None of that needs software. An ATS makes some of it easier, and each part has a plain substitute:

Set up the folder in 15 minutes

One folder per role, in whatever your company already uses: Google Drive, OneDrive, SharePoint or Dropbox. Share it only with the people interviewing for that role.

Hiring/
  2026-10 Operations Coordinator/
    00 Role brief
    01 Interview kit
    02 Scorecard form (link) and responses sheet   [process owner only]
    03 Tracker
    04 Email and invite templates
    05 Decision notes
    Candidates/
      Brennan, Casey/
        Resume
        Work sample
      Novak, Riley/
        Resume

• Resumes stay in the folder. Do not forward them by email or paste them into team chat, where they outlive the process and reach people outside it.
• The responses sheet is locked to the process owner until the debrief, so nobody reads a colleague's score before writing their own.
• Discuss candidates in the debrief, not in chat. Chat threads are written records, easy to forward, and usually full of first impressions.

The role brief and interview kit

Write the role brief before posting the job. It is one page: what the person will achieve in the first six months, four to six competencies with a line on what strong looks like, which are must-haves, and the pay range and location facts candidates will ask about. The OPM guide notes a structured interview typically assesses four to six competencies. Add more and each one gets a single shallow question.

The kit turns the brief into stages. A shape that works for a small team:

INTERVIEW KIT: [role]
Competencies: C1 [must], C2 [must], C3, C4, C5
Scale for every stage: 4 strong / 3 meets the bar / 2 below / 1 no evidence / - not assessed

STAGE 1  Screen, 20-30 min, video or phone, hiring manager
  Knockouts (same wording for everyone): [license, schedule, location]
  Q1 [C1]  [question]   Strong answer includes: [...]
  Logistics: pay range shared, availability, notice period

STAGE 2  Structured interview, 60 min, hiring manager + one colleague
  Q2 [C1]  Q3 [C2]  Q4 [C2]  Q5 [C3]  Q6 [C4]
  Each question: probes + strong answer includes
  Who asks what: [name] Q2-Q4, [name] Q5-Q6

STAGE 3  Work sample, 45 min, scored on the same scale
  Task: [small, realistic, same for every finalist]
  Scored by: [name], rubric written before anyone takes it

STAGE 4  References, 2 calls, questions tied to C1 and C2

RULES
  Same questions, same order, same time for every candidate.
  Scorecard submitted through the form within the hour.
  No discussion of a candidate before all scorecards are in.

For writing the questions and anchors, see the interview scorecard template. If this is your first time running interviews, the first-time hiring manager interview guide covers the hour itself and the questions you must not ask.

Scorecards as a form, so scores stay independent

The weak point of a spreadsheet-only process is the shared scorecard. When everyone types into the same document, the second interviewer reads the first interviewer's 2 before writing their own. A form fixes that with tools you probably already have. Google Forms and Microsoft Forms both collect each submission separately and put the responses where the form owner can see them.

Fields to include

• Candidate (dropdown, so names are spelled one way) and stage.
• Interviewer name.
• For each competency: rating 1–4 or "not assessed" (required), and evidence as a paragraph (required). Making evidence required is what stops a bare number.
• Recommendation: strong yes, yes, no, strong no. No "maybe".
• What the next interviewer should probe.

Settings to check

• Respondents must not be able to see a summary of other people's responses. Google's Forms help page explains that response summaries, when turned on with the "View results summary" setting, are visible to anyone who can respond, so leave it off. Check the equivalent setting in Microsoft Forms.
• Allow people to edit a response after submitting only if you are comfortable with scores changing after the debrief.
• Link the responses to a sheet in the role folder that only the process owner can open.

The tracker spreadsheet

One row per candidate per role. The columns below are enough to know who is waiting on whom and to reconstruct the process later. The example row is invented.

Use a dropdown for the stage column and conditional formatting to highlight rows with no contact in seven days. Those two features do most of what an ATS pipeline view does for a handful of roles.

Scheduling, debrief and decision

Scheduling with a calendar

A candidate invite template that answers the questions candidates otherwise email about:

Title: Interview for [role] at [company]

Hi [first name],

This is your [stage] interview for [role].
When: [date, time, time zone], [length] minutes
Where: [video link, or address and who to ask for at reception]
You'll meet: [name, title] and [name, title]
What we'll cover: [e.g. your experience running schedules and
handling supplier issues]. No preparation needed beyond [x].

If you need any adjustment or accommodation for the interview,
reply to this email and we'll arrange it.

If the link fails, call [phone number].
[Your name]

• The accommodation line is allowed and useful. The EEOC's guidance on pre-offer questions says employers may tell applicants what the hiring process involves and ask whether they will need a reasonable accommodation for it.
• The internal invite links the kit and the form, states "scorecard due within the hour", and is marked private, so the candidate's name is not visible on shared calendars.
• Book the debrief when you book the last interview, not after.

Debrief and decision on one page

Once every form response is in, hold a 30-minute debrief. The process owner opens the responses sheet at the start, the group goes competency by competency, and the hiring manager speaks last. The interview debrief template has the agenda. If you have more than one finalist, build the side-by-side view with the decision matrix in how to compare candidates after interviews. Save a short decision note in the role folder: who was selected, the job-related reason for each decision, and anything that changed from the role brief.

If typing notes is what slows you down, Interview Signal is a desktop app that captures the interview with no bot in the call and keeps transcripts and notes on your computer. The free plan includes 20 minutes of transcription, no card needed.

Records: what to keep, for how long, who can see it

Who is covered. The EEOC's small business page explains that the laws it enforces on race, color, religion, sex, national origin, disability and genetic information apply once you have 15 or more employees, age discrimination law applies at 20 or more, and the Equal Pay Act applies to employers with at least one employee. It also notes that state and local laws may apply.

How long to keep records. The EEOC's recordkeeping page says covered employers must keep personnel or employment records for one year, and that when a charge of discrimination is filed, relevant records must be kept until the charge and any lawsuit are finally resolved. The regulation, 29 CFR 1602.14, counts the year from when the record was made or the personnel action was taken, whichever is later, and names application forms and other records having to do with hiring.

What that means for your folder

• Keep: resumes and applications, scorecard responses, interview notes, work samples and their scores, the tracker row, decision notes, and emails about the decision.
• Set a delete-after date in the tracker for each candidate, at least a year after the decision date, or longer if your state or your own policy says so. Review before deleting, and never delete while a complaint or charge is open.
• Limit access to the people involved in the hire. Interview notes are records; write them as if the candidate might one day read them. See what not to write in interview notes.
• If you record or transcribe interviews, tell the candidate at the start and follow the consent rules for both locations. Our consent guide covers the wording.

A lightweight checklist per role

Before posting

• Role brief written: outcomes, four to six competencies, must-haves marked, pay range.
• Folder created and shared only with the interviewers.
• Interview kit written: stages, questions, probes, strong-answer lines, who asks what.
• Scorecard form built, summary visibility off, responses sheet restricted.
• Tracker created with stage dropdown and delete-after column.

For every candidate

• Invite sent from the template, with the accommodation line.
• Same questions, same order, same time as every other candidate at that stage.
• Each interviewer's form submitted within the hour, before any discussion.
• Tracker updated with next step, owner and last contact date.

At decision

• Debrief held after all scorecards are in; decision matrix built for finalists.
• Decision note saved with a job-related reason for each candidate.
• Every candidate told, and the date recorded.
• Delete-after dates set; folder access reviewed.

When the spreadsheet stops being enough

This setup works while one person can hold the whole process in view. These are the signs it has stopped working:

• Several roles are open at once, and the trackers disagree about who is where.
• More than one person schedules interviews and invites start to collide.
• Candidates email to ask for updates because no row had a named next step.
• Applications arrive faster than you can log them, so some never reach the tracker.

When that happens, the process you built moves into an ATS unchanged: the role brief becomes the requisition, the kit becomes interview plans, the form becomes scorecards. The structure was never in the software.