# How do I track a value that changes at every meeting?

> For freelancers, consultants and project leads whose go-live dates, budgets and statuses move at every Google Meet or Microsoft Teams call: how to set up a TrackHeros tracker so one row follows the value, what its history looks like, how repeats and first values are handled, and how much of it waits for your review.

Canonical: https://trackheros.com/answers/track-a-value-that-changes-every-meeting/  
Author: Sami Kanafani  
Updated: 2026-11-04

**In short:** Make it a column in a TrackHeros tracker whose rows are named by a key column, such as the feature or the deal. Each Google Meet or Microsoft Teams meeting that mentions the row updates the same cell, and the cell keeps every earlier value with its meeting, speaker and words. A go-live date that moved from 3 March to 17 March to 2 April stays one row.

| Fact | Detail |
| --- | --- |
| Shape | The same rows, updated meeting after meeting |
| Default rule | Latest value wins; earlier values stay in the history |
| Same value said again | Recorded as a confirmation, not a change |
| Changes | Wait for your review by default |

A value that changes at every meeting is the one minutes handle worst: each set of notes has a different date, and the current one is whichever you happened to read last. This answer is for freelancers, consultants and project leads who need one place where that value is current, taken from their Google Meet and Microsoft Teams calls. In TrackHeros that place is a tracker, described in full on [trackers](/features/trackers/).

## How do I set up a tracker for a value that moves?

Choose the shape in which the same rows are updated meeting after meeting, and pick the key column that names each row: the feature, the deliverable, the deal. Then add the moving value as a column of the right type, with the rule "latest value wins".

| Setting     | For a moving go-live date                                    |
| ----------- | ------------------------------------------------------------ |
| Shape       | The same rows, updated meeting after meeting                 |
| Key column  | Item: one row per feature or release                         |
| Column      | Go-live, of type date                                        |
| Description | "The date the release is planned to go live, as last agreed" |
| Rule        | Latest value wins                                            |
| Scope       | The client's weekly call, chosen as a recurring meeting      |

The description line matters most: it is what tells TrackHeros which date in a conversation belongs in this column and which does not. The project tracker template already has a deadline column set up this way; the others are in [tracker templates for freelancers](/blog/tracker-templates-for-freelancers/).

## What does the history of a changing value look like?

One row, one current value, and a history panel listing every earlier value with its meeting, its speaker and their words. Each entry links to the transcript at the moment it was said.

| Meeting                     | Value    | Said by | Their words                                      |
| --------------------------- | -------- | ------- | ------------------------------------------------ |
| Weekly call, Tuesday 17 Feb | 3 March  | Priya   | "We're aiming to go live on the third of March." |
| Weekly call, Tuesday 24 Feb | 17 March | Tom     | "Realistically, that's the seventeenth now."     |
| Weekly call, Tuesday 10 Mar | 2 April  | Priya   | "Let's say the second of April and hold it."     |

The table can be filtered to rows changed recently or changed several times, which is a quick way to see what keeps slipping. The [guide to a date that keeps moving](/blog/track-a-date-that-keeps-moving/) covers how to raise that with a client.

## What if someone repeats the same value?

It is recorded as a confirmation, not a change. The cell stays as it is, the history notes that a later meeting said the same thing, and nothing waits for review.

That keeps "changed several times" honest: a date confirmed at four standups has not changed four times.

## What if the value should never change?

Give the column the rule "keep the first value". A later, different value is then shown as a conflict for you to decide, rather than replacing the first one.

It suits facts that ought to stay put, such as the date a request was first made. What happens in each case is in [what happens when two meetings disagree](/answers/what-happens-when-two-meetings-disagree/).

## Does every change wait for my approval?

By default, yes. New and changed values wait in a review queue, grouped by meeting, until you accept, correct or reject them.

You can let a tracker apply confident values on its own instead. A value that contradicts a first value, a change to a cell somebody edited by hand, the removal of an item from a list and a possible duplicate row still wait for a person. Choosing between one row per meeting and rows that update is covered in [one row per meeting or one table that updates](/blog/one-row-per-meeting-or-one-table-that-updates/).

---

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