Does a meeting tracker read meetings that already happened?

A tracker does not have to start empty. When you set one up in TrackHeros, the meetings you have already held can fill it, so a table about a client's change requests opens with the requests made last month, not just the ones made from today. This answer is for anyone starting a tracker on their Google Meet and Microsoft Teams calls. 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 described in full on trackers.

What happens to past meetings when I create a tracker?

When you create a tracker you can choose to have it read your recent past meetings in its scope as well; the editor says how many it will read. They are read oldest first, so the table starts with its history in the order things happened. A go-live date that moved from 3 March to 17 March to 2 April arrives in that order: the cell shows 2 April, and its history holds the two earlier dates with the quote for each.

Unless the tracker applies confident values on its own, what those meetings give it waits in the Review tab, grouped by meeting, where a whole meeting's values can be accepted at once. Why a tracker value waits for review explains what you are looking at.

How do I make it read past meetings again later?

Use Check past meetings on the tracker's page. It reads the recent meetings in scope again and skips any already read with the same columns, so nothing is read twice for no reason. The moment it earns its place is after you add a column or rewrite a column's description: the meetings already read are read again for the new definition, and the new column fills from them.

A value you rejected stays rejected when its meeting is read again. Only the person who made the tracker, or an admin on a company account, can start a check, and it cannot be started again within a few minutes.

Can I add one older meeting by hand?

Yes. On a finished meeting's page, send it to a tracker. It is read the same way as any other meeting, whatever the tracker's scope says; sending is for the tracker's creator or an admin, like a check. That is the way in for a meeting the scope does not cover, such as a kickoff held before the client's meetings had a regular title, or one older than the recent meetings a check reads.

Which past meetings are never read?

• Very short meetings.
• Meetings without finished notes, such as one where the notetaker recorded nothing. A meeting held in another language, or in two, waits for its audio pass, so it is read once, from the final transcript.
• Meetings the tracker's creator could not open, on a company account.
• Another client's meetings. A tracker belongs to one client's sealed workspace; one that covers all your clients keeps a separate table for each, as tracking across all your clients explains.
• Unrelated meetings, in a tracker fed by every meeting of a client: those plainly unrelated to its subject are skipped.

Can reading old meetings overwrite newer values?

No. An older meeting never overwrites a newer value, whatever order the meetings are read in. Its value lands in the cell's history, labelled as older, and the table keeps the newer one. A meeting that repeats the current value is recorded as a confirmation, not a change, and a cell somebody edited by hand keeps that edit until somebody accepts a change to it. What happens when two meetings disagree covers the rest.