# Why is a meeting tracker value waiting for review?

> For anyone whose table, filled from Google Meet and Microsoft Teams meetings, shows values waiting: why TrackHeros reviews changes first by default, the changes that always wait even when confident values apply on their own, what accepting, correcting and rejecting do, where to find everything waiting, and how to let confident values through.

Canonical: https://trackheros.com/answers/why-is-a-tracker-value-waiting-for-review/  
Author: Sami Kanafani  
Updated: 2026-11-04

**In short:** Because a TrackHeros tracker reviews first by default: new and changed values from a Google Meet or Microsoft Teams meeting wait until a person accepts them. Even when a tracker applies confident values on its own, four kinds always wait: removing a list item, a value that contradicts a keep-the-first-value column, a change to a cell edited by hand, and a possible duplicate row.

| Fact | Detail |
| --- | --- |
| Default | Every new or changed value waits for review |
| Optional | Apply confident values automatically |
| Always waits | Removals, conflicts with a first value, changes to edited cells, possible duplicates |
| Grouped by | Meeting, with one action to accept them all |
| A rejected value | Does not come back when the meeting is read again |

A tracker in TrackHeros is a table that fills itself from your meetings, and by default nothing in it changes until a person has looked. A value waiting for review is that check doing its job. This answer is for anyone keeping a tracker on their Google Meet and Microsoft Teams calls who wants to know why a value is waiting and what to do with it. 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. The feature is on [trackers](/features/trackers/).

## Why do tracker values wait for review at all?

Because a wrong value in a table looks exactly as trustworthy as a right one. A misread date in a paragraph of notes gets noticed; the same date in a tidy cell gets copied into an invoice. So every tracker starts in review-first mode, where new and changed values wait until somebody accepts them.

Checking is quick because every value is cited. It shows the meeting it came from, who said it, when, and the words they used, rebuilt from the stored transcript rather than written by the model, with a link to that moment. [Where a tracker value comes from](/answers/where-does-a-tracker-value-come-from/) explains the citation; [review before a value changes](/blog/review-before-a-value-changes/) explains the habit.

## Which changes always wait, even with automatic updates on?

A tracker can be set to apply confident values on its own. A value the model was unsure of still waits, and so do four kinds of change, however confident:

| What waits                    | Example                                                  | Why a person decides                                  |
| ----------------------------- | -------------------------------------------------------- | ----------------------------------------------------- |
| Removing a list item          | "The VPN access is sorted" closes a blocker              | A removal hides something; a wrong one goes unnoticed |
| A conflict with a first value | A later meeting gives a different "date first requested" | That column's first value only moves if you say so    |
| A change to an edited cell    | A meeting disagrees with a value you typed               | Your correction outranks a meeting                    |
| A possible duplicate row      | "the auth endpoint" arrives while "Login API" exists     | Rows are never merged automatically                   |

## What do accept, correct and reject do?

- **Accept** puts the value in the table. If a newer meeting has already set that cell, the accepted value goes into its history instead and the table keeps the newer one.
- **Correct** lets you fix the value, such as a misheard figure, and accept your version. The reading you corrected does not come back when that meeting is read again.
- **Reject** discards it. Reading the same meeting again does not bring it back.

A possible duplicate asks whether it is the same as the existing row or a new row. A conflict asks whether to keep the first value or use the new one. Values are grouped by the meeting they came from, and a whole meeting's can be accepted at once. More on conflicts in [what happens when two meetings disagree](/answers/what-happens-when-two-meetings-disagree/).

## How do I find everything that is waiting?

Open the tracker's Review tab, where waiting values are listed meeting by meeting with each meeting's date. On the table, a filter shows only rows with something waiting, and each affected cell is marked. The person who made the tracker gets an alert in the app when changes are waiting, and each meeting's page has a "What changed" panel listing what that meeting gave every tracker. On a shared tracker, if a colleague reviews a value first, your list refreshes rather than letting you decide it twice.

## Can I stop values waiting for review?

Partly. The tracker's creator, or an admin on a company account, can switch it to apply confident values on its own, and anything it applies can be undone later, as [undoing a tracker change](/answers/undo-a-tracker-change/) shows. The four kinds in the table above, and values the model was unsure of, still wait. That is deliberate: they are the changes a person should own.

---

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