How to track what matters across meetings

Some questions are never answered by one meeting. Where does the go-live date stand? What did each candidate ask for? Which of the client's requests fell outside the original scope? This guide is for freelancers, consultants and project leads whose answers are spread across many calls on Google Meet and Microsoft Teams. It explains how to track a subject across meetings, by hand or with a TrackHeros tracker, and points to a detailed guide for each part.

Why do meeting notes lose track of things?

Because notes are written one meeting at a time, and the facts that matter change between meetings. A date, a status or an amount appears in several sets of notes, each one right on its day, and none says which is current.

Finding the current value means reading the notes backwards until you hit the last mention, then hoping nobody revised it in a meeting you skipped. That works for one project. It does not work for four clients, each with a weekly call, a standup and the occasional steering meeting. What is missing is a second record, organised by subject rather than by meeting.

What is a tracker?

A tracker is a table that fills itself from your meetings. You define the columns, give each one a type and a one-line description of what belongs in it, and choose which meetings feed it; after each of those meetings is summarised, TrackHeros reads it and fills or updates the table.

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. A tracker sits beside the notes, read from the same transcript, inside one client's workspace. The full description is on the trackers feature page.

Which of the two shapes do you need?

If the meeting itself is the record, add a new row for every meeting. If the thing you care about outlives any one meeting, keep the same rows and update them meeting after meeting.

Shape	Each row is	Example
A new row for every meeting	One meeting	A standup log: attendees, done, planned, blocked
The same rows, updated	One thing, named by a key column	A project tracker, keyed by item

In the second shape, a later meeting that mentions the same thing updates its row rather than adding a duplicate, and a row that only looks new ("the auth endpoint" next to "Login API") is flagged for you to decide. Worked examples of both are in one row per meeting, or one table that updates.

Which meetings should feed a tracker?

As few as will answer the question. A tracker can read all your clients, one client, chosen recurring meetings, specific meetings picked before they happen, or only the meetings you send it by hand.

• All your clients suits a definition you want everywhere, such as a project tracker. Each client gets a separate table, shown together with a client label on every row, and rows from two clients are never merged.
• One client reads every meeting of that client, skipping any plainly unrelated to the subject, or only the meetings whose titles contain words such as "interview" or "standup".
• Chosen recurring meetings suit a standup log or a weekly status call; see tracking a recurring client meeting.
• Specific meetings, chosen before they happen, are attached from the upcoming meeting's page; see attach a tracker before the meeting.
• By hand only: the tracker's creator or an admin sends it finished meetings from each meeting's page.

How do you choose the columns?

Choose the facts you keep looking up, and write each column's description as a rule. The description is what decides what goes in the cell, so say what counts, what does not, and when to leave it empty.

"Deadline" on its own invites guesses. "The date the item is due, when a date is stated or agreed; not estimates given as durations" does not. Each column also has a type (text, number, money, date, status, person, list of people, yes / no / unclear, list or link) and a rule: the latest value wins, keep the first value, a list that grows and shrinks, or fill by hand only. Six templates give you a starting point; design the columns of a meeting tracker and tracker templates for freelancers go into both.

How do you review what a tracker found?

In its review queue. By default every new and changed value waits there, grouped by meeting, and you accept it, edit then accept it, reject it, or accept everything one meeting proposed.

A tracker can be set to apply confident values on its own. Some changes still always wait for a person: removing an item from a list, a value that contradicts a column set to keep the first value, a change to a cell somebody edited by hand, and a possible duplicate row. A rejected value does not come back when the same meeting is read again. The tracker's creator gets an in-app alert when changes are waiting. More in review before a value changes.

What does a cell's history show?

Every value the cell has held, each with the meeting it came from, who said it, when in the meeting and the words they used. A link opens the transcript at that moment, and the recording jumps there.

A go-live date reads like this: 3 March, then 17 March, then 2 April, each change with its quote. Two rules keep the history honest. An older meeting never overwrites a newer value: if last week's call is read after this week's, its value lands in history, labelled as older. And saying the same value again is recorded as a confirmation, not a change. A history of every change, with the quote walks through one cell.

How do you use the table once it fills?

Open it instead of the minutes. The tracker's page has search and filters for values that changed recently, changed several times, conflict, or wait for review; each meeting's page has a "What changed" panel listing what it gave each tracker.

You can also ask. The assistant reads trackers, so "what salary did each candidate this month ask for?" is answered from the table, with the meeting behind each value; it never changes a tracker. The current table and its full history download as CSV for Excel or Google Sheets, on the plans that include export, listed on pricing.

What is a tracker not for?

Anything that was not said in a recorded meeting, anything you need during the call, and anything better read as prose. A tracker reads meeting transcripts after the notes are ready; it does not read email, phone calls without a recording, or a meeting while it is happening.

One-off commitments with an owner and a date belong in action items, and a running account of where a topic stands, in prose, belongs in a notebook. Tracker or notebook? and tracker or action items? draw the lines.

Where should you start?

With the question you ask most often. Each of these guides starts from one:

• Hiring for a client: an interview tracker from meeting notes.
• Daily standups: a standup tracker for developers.
• Dates that slip: track a date that keeps moving.
• Decisions that get reopened: track decisions across meetings.
• Requests outside the agreed work: a scope change tracker.
• Several clients at once: project status across all clients.