Standup tracker for developers: a row per standup, and the work that moves

A standup tracker is a record of what each standup said, kept where you can look it up later instead of scrolling back through chat or minutes. This guide is for freelance developers who join a client's daily or weekly standup on Google Meet or Microsoft Teams and want two things from it: a log of every standup, and a current picture of every piece of work that keeps coming up. It shows how to keep both with TrackHeros trackers, tables that fill themselves from your meetings. The wider picture for developers with several clients is on freelance developers.

What should a standup tracker record?

Two different things: what happened at each standup, and where each piece of work stands now. The first is a diary, one entry per meeting. The second is a status board, one entry per item, that changes as the work does.

Most standup notes try to be both and end up as neither. A diary answers "what did we say on Tuesday?" but not "is the login API done?", because that answer is scattered across ten entries. A status board answers the second question and forgets the first. Keep them as two tables fed by the same meeting.

Why is one table not enough for standups?

Because the two questions need different row shapes. A log adds a new row at every meeting; a status table keeps one row per item and updates it.

Question you ask later	Table shape	TrackHeros template
What was done, planned and blocked on Tuesday?	A new row for every meeting	Standup log
Where does the password reset stand today?	The same rows, updated every meeting	Project tracker
When did that blocker first come up?	Either, through the cell's history	Both

Put a moving status in a log and one item becomes a dozen rows you have to read in order. Put the diary in a status table and Tuesday disappears the moment Wednesday updates it. The choice is covered in more depth in one row per meeting or one table that updates.

What does the Standup log record?

One row per standup with five columns: the date, who attended, what was done, what is planned and what is blocked. The date comes from the meeting itself; the other four are filled from what people said, and the last three are lists with one item each.

Three days of a client's standup might read like this:

Date	Attendees	Done	Planned	Blockers
Mon 9 Mar 2026	Lena, Omar, Jo	Login API returns refresh tokens	Password reset emails	No access to staging mail server
Tue 10 Mar 2026	Lena, Omar	Reset email templates	Send reset emails from staging	No access to staging mail server
Wed 11 Mar 2026	Lena, Omar, Jo	Reset emails sent from staging	Rate limiting on login

Every cell carries the words it came from. Open the history of Tuesday's blocker and you see who raised it, when in the call, and the sentence they used, with a link that opens the transcript at that moment and a recording that jumps there.

What does the Project tracker add?

A row per piece of work that stays put while its status, owner, deadline and blockers change. Its columns are item, description, status, owner, deadline, priority, blockers and last discussed; the last fills itself with the most recent meeting that mentioned the item.

The same three standups give the password reset one row, not three:

Item	Status	Owner	Deadline	Blockers	Last discussed
Login API	Done	Omar	Fri 13 Mar 2026		Wed 11 Mar
Password reset	In progress	Lena	Fri 20 Mar 2026		Wed 11 Mar

Behind "In progress" sits a history: in progress on Monday, blocked on Tuesday when the mail server came up, in progress again on Wednesday, each with its quote. Rows are named by the item. If Wednesday's standup calls it "the password reset flow" and that arrives as a new row, it is flagged as a possible match for the existing "Password reset" row and you choose: same as, or new row. Rows are never merged on their own. Bugs fit the same shape; tracking bug status from standups is the guide for those.

How do you point both tables at the same standup?

Give both trackers the standup as their scope. Choose the recurring meeting itself, such as the Monday standup with one client, or take every meeting of that client whose title contains "standup". An upcoming standup already on your calendar can also be given a tracker from its own meeting page; see attach a tracker before the meeting.

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. That matters for standups because a developer with three clients sits in three of them, and each tracker belongs to one client's workspace. If you want one Project tracker definition across all of them, an all-clients tracker keeps a separate table for each client and shows them together with a client label on every row; project status across all clients explains how.

When you create a tracker you can have it read your recent past standups in scope, oldest first, so the table starts with history rather than empty.

What happens when a blocker clears or a deadline moves?

A blocker is a list item: it is added when someone raises it and removed when someone says it is resolved, and a removal always waits for a person to confirm it. A deadline follows the default rule, latest value wins: the newest meeting's date is current, and every earlier one stays in the cell's history with its quote.

Repeating a date is not a change. "Still Friday the 20th" at the next standup is recorded as a confirmation, so the filter for rows changed several times shows dates that actually moved. An older standup read late never overwrites a newer value; its reading lands in history, labelled as older. Dates that slide every week have a guide of their own: track a date that keeps moving.

Does the tracker fill in during the standup?

No. Trackers are filled after the meeting's notes are ready, not live during the call. A standup held in German, in Hindi, or switching between either and English goes through the audio pass first and is read once that pass is done, so the table comes from the same transcript as the notes.

Text values are written in the notes' language. A very short call is skipped, so a standup abandoned a minute in leaves no empty row. The spoken languages TrackHeros recognises are listed on languages.

How do you use the tables before the next call?

Open the tracker, not the minutes. Filter to rows changed recently, rows waiting for review or rows with conflicts, and you have what moved since you last looked. Each meeting's page also has a What changed panel listing what that standup gave each tracker.

By default, new and changed values wait in a review tab, grouped by meeting, until you accept, edit or reject them; why that is the default is in review before a value changes. The assistant reads trackers too, so "what is still blocked for Client A?" is answered from the table, with the meeting each value came from. It reads them only; changes are yours to make.

Before a sprint review or a weekly status call, the Project tracker is most of the agenda; the sprint review guide shows how to run one. The current table and its full history can be downloaded as CSV, which opens in Excel or Google Sheets, and pricing says which plans include export.