# Does an interview tracker keep one row per interview or one per candidate?

> For interviewers and recruiters running several rounds on Google Meet and Microsoft Teams: why the TrackHeros interview scorecard keeps one row per candidate rather than one per interview, how a later stage updates that row while every cell keeps its earlier values, how a standup log differs, how to get one row per interview instead, and what happens when a name is spelled two ways.

Canonical: https://trackheros.com/answers/one-row-per-interview/  
Author: Sami Kanafani  
Updated: 2026-11-04

**In short:** One per candidate. The TrackHeros interview scorecard is keyed by the candidate's name, so a second or third interview on Google Meet or Microsoft Teams updates that candidate's row instead of adding another. Every cell keeps its earlier values with their quotes, so the screening's answer is still there. A standup log is the other shape: a new row for every meeting.

| Fact | Detail |
| --- | --- |
| Interview scorecard | One row per candidate, named by the candidate column |
| Standup log | A new row for every standup |
| Earlier rounds | Kept in each cell's history, with the quote |
| Same candidate, two spellings | Flagged as a possible match; never merged automatically |
| Shape of the table | Chosen when the tracker is created |

A tracker in TrackHeros is a table that fills itself from your meetings, and it comes in two shapes: the same rows updated meeting after meeting, or a new row for every meeting. The interview scorecard is the first kind. This answer is for interviewers, recruiters and hiring managers who run several rounds per candidate on Google Meet and Microsoft Teams. TrackHeros is an AI meeting notetaker that connects every Google and Microsoft calendar you hold, recognises close to 100 spoken languages on its own, writes the notes in nine of them, and keeps every client's notes in a sealed workspace of its own. The feature is on [trackers](/features/trackers/); interviewing with it is on [AI notes for interviewers](/for/interviewers/).

## Why does the interview scorecard keep one row per candidate?

Because the questions you ask afterwards are about candidates, not calls: where is Maria in the process, what does she expect to be paid, what did the panel worry about. The scorecard's rows are named by its candidate column, so when a later interview mentions the same candidate, that row is updated rather than duplicated. Its columns are candidate, role, stage, interviewers, strengths, concerns, technical assessment, salary expectation, availability and recommendation.

Which meetings feed it is up to you. Narrowing it to meetings whose title contains "interview" keeps a project call that mentions a hire out of it. [Building an interview tracker from meeting notes](/blog/interview-tracker-from-meeting-notes/) walks through the set-up.

## What happens to a candidate's row at the second interview?

The row moves on and its history fills in. Say Maria has a screening on Tuesday 10 February 2026, a technical interview on Tuesday 17 February and a final on Tuesday 24 February:

| Column             | After the screening   | After the final                      |
| ------------------ | --------------------- | ------------------------------------ |
| Stage              | Screening             | Final; history: Screening, Technical |
| Salary expectation | The figure she gave   | The latest figure she gave           |
| Concerns           | None raised           | Each concern raised, until resolved  |
| Interviewers       | The screening's panel | The final's panel                    |
| Recommendation     | Empty                 | What the panel said, if they said it |

Each change keeps the quote that made it. If she repeats the same figure, that is recorded as a confirmation; if she gives a new one, the earlier one stays in the cell's history. Interviewers shows the latest round's panel, with earlier panels in the history. Comparing candidates side by side is in [comparing candidates across interviews](/blog/compare-candidates-across-interviews/).

## When does a tracker add a new row for every meeting instead?

When the meeting itself is the record. The standup log template adds one row per standup, with the date, who attended, what was done, what is planned and what is blocked, and nothing in it is matched or updated by a later meeting. The rule of thumb: if the thing outlives the meeting, as a candidate or a feature does, use rows that update; if each meeting is its own entry, use a row per meeting. [One row per meeting or one table that updates](/blog/one-row-per-meeting-or-one-table-that-updates/) goes further.

## Can I have one row per interview instead?

Yes, by designing a tracker with a row per meeting and a candidate column, so every interview is its own line. You lose the single row where a candidate's whole process sits, which is why the template does not do it, but nothing stops you keeping both. The shape is chosen when a tracker is created and does not switch afterwards, so this means a second tracker. Whether your plan includes designing your own trackers is on [the pricing page](/pricing/).

## What if a candidate's name is spelled two ways?

A new row that looks like an existing one, such as "Sam" in one interview and "Samir" in the next, is flagged as a possible match for you to settle: same as the existing row, or a new row. Rows are never merged automatically. Answering same as keeps the new row's history under the existing candidate's row. When two candidates may share a name, name rows by candidate and role together, and decide that before the first rows arrive: the columns that name a row can only change while the table is empty.

For one interview written up on its own, the meeting's notes can also be summarised as an interview; [interview notes instead of minutes](/answers/interview-notes-instead-of-minutes/) covers that.

---

TrackHeros is in early access: https://trackheros.com/#early-access