# How to track a go-live date that moves at every standup

> For developers, project leads and consultants whose go-live date changes at every Google Meet or Microsoft Teams standup: how to keep that date in one table cell that TrackHeros updates after each meeting, with every earlier value, who changed it, when and in what words, why repeating a date is not a change, and why an older meeting never overwrites a newer date.

Canonical: https://trackheros.com/blog/track-a-date-that-keeps-moving/  
Author: Sami Kanafani  
Updated: 2026-11-04

**In short:** TrackHeros keeps a moving date in one tracker cell, filled from your Google Meet and Microsoft Teams meetings. The newest meeting's date is current, and every earlier date stays in the cell's history with the meeting, the speaker, the moment and the words used. Saying the same date again counts as a confirmation, and an older meeting read late never overwrites a newer date.

| Fact | Detail |
| --- | --- |
| Default column rule | Latest value wins; earlier values stay in the history |
| Same date said again | Recorded as a confirmation, not a change |
| Older meeting read late | Lands in the history, labelled as older; the table keeps the newer date |
| Each change records | The meeting, the speaker, the moment in the call and the words used |

A go-live date that moves at every standup is easy to say and hard to keep. This guide is for developers, project leads and consultants whose release, launch or delivery date changes in their Google Meet or Microsoft Teams standups, and who want one place that says what the date is now, what it was before, and who moved it. It covers keeping that date in one table cell that updates itself, and what happens to every value it replaces.

## Why is a moving date so hard to keep track of?

Because each change is spoken once, in passing, in whichever meeting it happened. The new date ends up in that meeting's minutes, the old one stays in the minutes before it, and nobody can say without reading them all when it moved or why.

The project plan does not help much either. Someone updates it later, or not, and it shows only the latest date. When the client asks "wasn't this meant to be March?", the honest answer is a search through three weeks of notes.

## How do you keep a moving date in one cell?

Use a tracker that keeps the same rows from meeting to meeting, with one row for each thing that has a date: the go-live, the payments release, the data migration. 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 is a table that fills itself from those meetings.

The Project tracker template already fits. Its Item column names each row, and its Deadline column is a date column described as "the date the item is due, when a date is stated or agreed. Not estimates given as durations." After each standup, TrackHeros reads the meeting, finds the row it talks about, and proposes the new date for that same row instead of adding a second one.

Every column follows a rule. The default is that the latest value wins: the newest meeting's value is current, and older ones stay in the cell's history. That is exactly what a moving date needs.

## What does the cell's history look like?

Each value the cell has ever held, in order, with the meeting it came from, who said it, when in the meeting, and the words they used. Here is the go-live row for a retail client's checkout rebuild:

| Meeting                          | Deadline      | Recorded as | Words used                                                                                   |
| -------------------------------- | ------------- | ----------- | -------------------------------------------------------------------------------------------- |
| Kickoff, Monday 2 February 2026  | 3 March 2026  | First value | Priya: "If staging is ready this week, we go live on Tuesday the third of March."            |
| Standup, Monday 23 February 2026 | 17 March 2026 | Changed     | Tom: "The payment provider needs two more weeks, so go-live is the seventeenth of March."    |
| Standup, Monday 9 March 2026     | 17 March 2026 | Confirmed   | Tom: "Still on for the seventeenth."                                                         |
| Standup, Monday 16 March 2026    | 2 April 2026  | Changed     | Priya: "The security review isn't done. Let's move go-live to Thursday the second of April." |

The table itself shows 2 April. The history shows 3 March, then 17 March, then 2 April, with the reason for each move in the words of the person who moved it. A link beside each entry opens the transcript at that moment, and the recording jumps there.

The quotes are not written by the model. Every value has to point at the transcript lines it came from, a value with no line behind it is dropped, and the quote you see is rebuilt from the stored transcript. [A history of every change, with the quote](/blog/a-history-of-every-change-with-the-quote/) covers what each entry holds.

## Is saying the same date again a change?

No. When a meeting repeats the current value, it is recorded as a confirmation, not a change. In the example, the standup of 9 March confirms 17 March: the history shows it was said again and by whom, and it is not counted as a change.

That difference matters when you are deciding how worried to be. A date that has been confirmed at four standups in a row is a different date from one that has moved four times, even if both read 2 April today.

## What happens when an older meeting is read after a newer one?

It never overwrites the newer value. Its date lands in the history, labelled as older, and the table keeps the date from the more recent meeting.

This comes up more often than it sounds. You might send last week's planning call to the tracker by hand after this week's standup has already been read. A meeting held in another language, or in two, is read after its audio pass, which can finish after a later meeting has already been read. When you create a tracker and have it read your recent past meetings, they are read oldest first so the history builds in order, but the rule holds either way: the newest meeting decides what the table shows.

## How do you keep the original date as well as the current one?

Add a second date column with the rule "keep the first value". A later, different value for that column is not applied; it is shown as a conflict for you to decide, and the table keeps the first date until you do.

With "Original go-live" kept first and "Deadline" left on latest wins, the row shows the slip at a glance: 3 March beside 2 April. Adding a column to a template counts as designing your own tracker; [pricing](/pricing/) says which plans include that. More on how conflicting values are handled is in [what happens when two meetings disagree](/answers/what-happens-when-two-meetings-disagree/).

## Which meetings should update the date?

The meetings where the date is actually discussed. For most projects that is one recurring call, so choose the recurring meeting itself, such as the Monday standup with one client, as the tracker's scope.

Other scopes work too: every meeting of the client, with plainly unrelated ones skipped; only meetings whose titles contain words such as "standup" or "planning"; a single upcoming meeting you attach the tracker to before it happens; or meetings you send by hand. The tracker fills after each meeting's notes are ready, not live during the call, and very short meetings are skipped.

A standup held in German moves the date the same way as one held in English. Trackers read meetings in any of the close to 100 spoken languages TrackHeros recognises, through the same transcript as the notes; the [languages page](/languages/) lists them.

## What if the tracker records the wrong date?

Reject it in review, or correct it there and accept. By default every new or changed value waits in a review queue, grouped by meeting, and a rejected value does not come back when the same meeting is read again.

If you edit a cell by hand, it is protected: later changes from meetings go to review instead of replacing your value. You can also restore an older value from the history, or undo a change that was applied. A tracker can be set to apply confident changes on its own, and a change to a cell somebody edited still waits for a person.

## How do you spot the dates that slip most?

Filter the table. You can show rows that changed recently, rows that changed several times, rows with conflicts, and rows waiting for review. A row that has changed several times is usually the one to raise at the next client call.

You can also ask the assistant in the client's chat, "when did go-live move to April, and why?", and the answer comes from the tracker, with the meeting each value came from. For other values that change from meeting to meeting, such as a rate, a headcount or a budget, see [track a value that changes every meeting](/answers/track-a-value-that-changes-every-meeting/) and the [Trackers feature](/features/trackers/).

## Frequently asked

**Does the date change while the standup is still running?**

No. A tracker is filled after the meeting's notes are ready, not during the call. The new date appears in the tracker's review tab, or in the table if confident changes are applied automatically.

**What if someone says 'two more weeks' instead of a date?**

The Project tracker's Deadline column asks for a date that is stated or agreed, not an estimate given as a duration, so the tracker is told to leave the cell as it was. Say the date back on the call, 'so that's the seventeenth?', and the answer is what gets recorded.

**Can I see every date that moved this month?**

Yes. Filter the table to rows changed recently, or to rows changed several times, and open a cell's history to see each date with the quote that moved it. The assistant can also answer from the table, naming the meeting each value came from.

---

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