What happens when two meetings give a tracker different values?

Clients change their minds, and colleagues remember things differently. This answer is for freelancers, consultants and project leads using a TrackHeros tracker on Google Meet and Microsoft Teams meetings who want to know which value wins when two meetings disagree, and what happens to the one that loses. Either way, nothing is thrown away. The feature is on trackers.

Which value does the tracker keep?

The column's rule decides. By default the newest meeting's value wins and the older one stays in the history; a column can instead keep its first value, collect a list, or be filled by hand only.

Rule	When a later meeting says something different
Latest value wins (default)	The newer value becomes current; the older one stays in the history
Keep the first value	The first value stays; the new one is a conflict for you to decide
List	Items are added when raised and removed when said to be resolved
Fill by hand only	Meetings never write to the column

"Latest value wins" suits a status, a deadline or a budget that is expected to move. "Keep the first value" suits facts that should not, such as the date a request was first made: if a later call places it a month later, that deserves a look, not a silent change.

What if an older meeting is read after a newer one?

The table keeps the newer value. Values are placed by when their meeting happened, not by when TrackHeros read it, so a meeting from last week read after this week's lands in the history, labelled as older, without replacing the current value.

This happens more often than it sounds. A new tracker can read your recent past meetings, a meeting can be sent to a tracker by hand days later, and a meeting held in another language is read after its audio pass (the languages page lists the languages recognised). If the older value is the one you want, you can make it the current value from the cell's history.

How do I settle a conflict?

In the review tab, or by filtering the table to rows with conflicts. A conflict shows the first value and the new one, each with its meeting and quote, and you choose whether to keep the first value or use the new one.

Conflicts wait for a person even on a tracker that applies confident values on its own. More on the queue in review before a value changes.

What if two meetings say the same thing?

That is a confirmation, not a change. The history records that a later meeting said the same value again, the cell does not move, and nothing waits for review.

What if two meetings name the same thing differently?

The tracker flags a possible match rather than guessing. Capitals and a leading "the" are matched for you, so "the login API" updates the "Login API" row. A name that may mean an existing row without matching it, such as "the auth endpoint", is marked as possibly the same, and you choose: the same as that row, or a new row.

Rows are never merged automatically; answering same as keeps the new row's history under the existing row. To take back a change you accepted by mistake, see how do I undo a tracker change?, and for a value that moves at every call, track a value that changes every meeting.