Tables that fill themselves from your meetings

Trackers turn your Google Meet and Microsoft Teams calls into tables that keep themselves up to date, with every value pointing back to the moment it was said. It is for freelancers, consultants and project leads who keep asking where a candidate, a feature or a go-live date stands now. 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.

What is a tracker in TrackHeros?

A tracker is a table that fills itself from your meetings. You define its columns, each with a type and a one-line description of what belongs in it, and choose which meetings feed it. You check the table instead of re-reading minutes.

Minutes record one meeting; a tracker records one subject across many, such as every candidate for a role or every request a fintech client made outside the original scope. The minutes and action items are still written for each meeting.

What shapes can the table take?

Two. A table either adds a new row for every meeting, or keeps the same rows and updates them meeting after meeting.

Shape	A row is	Good for
A new row for every meeting	One meeting	A standup log: done, planned, blocked
The same rows, updated	One thing named by a key column: a candidate	A project tracker, an interview scorecard

In the second shape, a go-live date that moves at every weekly call stays one cell. One row per meeting, or one table that updates helps you choose.

Where does each value come from?

From lines in the transcript, which the model has to point at. A value with no line behind it is dropped, and the quote shown beside a value is rebuilt from the stored transcript, never written by the model. Anything the meeting did not say stays empty.

Every cell keeps its history: the meeting each value came from, who said it, when, and their words, with a link to that moment in the transcript and the recording. A go-live date reads 3 March, then 17 March, then 2 April, each change with its quote. A history of every change, with the quote walks through one.

Do changes apply on their own?

Not by default. New and changed values wait in a review queue, grouped by meeting: accept, edit then accept, reject, or accept all from one meeting. A rejected value does not come back when the same meeting is read again.

A tracker can be set to apply confident values on its own. Even then, some changes always wait for a person: removing an item from a list, a value that contradicts a column set to keep the first value, a change to a cell somebody edited by hand, and a possible duplicate row.

Any cell can be edited by hand, and an edited cell is protected. You can restore an older value, undo an applied change and add rows yourself. The creator gets an in-app alert when changes are waiting.

How does a column decide which value is current?

Each column has a rule, and most use the default: the latest value wins.

• Latest value wins. The newest meeting's value is current; older ones stay in history.
• Keep the first value. A later, different value is shown as a conflict for you to decide, as for "date first requested".
• List. Items such as blockers or pain points are added when raised and removed when said to be resolved.
• Fill by hand only. Never filled from a meeting.

Two columns fill themselves: "last discussed" and "meeting date". An older meeting never overwrites a newer value; if last week's meeting is read after this week's, its value lands in history, labelled as older. Saying the same value again is a confirmation, not a change.

Capitals and a leading "the" are matched for you. A new row that may mean an existing one, "the auth endpoint" against "Login API", is flagged for you to mark as the same row or a new one, and rows are never merged automatically.

Which column types are there?

Ten: text, number with a unit, money with an amount and a currency, date, status, person, list of people, yes / no / unclear, list, and link. A status column takes options you define, and some can be marked final, such as Done or Lost. What field types a tracker can have explains what each accepts.

How do you start a tracker?

Three ways: pick a template, describe what you want in a sentence and edit the draft, or start blank. Before saving, you can preview it on one recent meeting.

The six templates are Project tracker, Change requests, Interview scorecard, Sales discovery, Decision log and Standup log, with their columns in tracker templates for freelancers. A new tracker can read your recent past meetings in scope, oldest first, so it starts with history.

Which meetings feed a tracker?

The ones you choose, from five scopes, and only after a meeting's notes are ready.

• All your clients. One definition, a separate table for each client, shown together with a client label on every row. A client added later gets its own table; the private "No client" space is not included.
• One client. Every meeting of that client, skipping any plainly unrelated to the subject, or only those whose title contains words such as "interview" or "standup".
• Chosen recurring meetings, such as the Monday standup with one client.
• Specific meetings, chosen before they happen, attached from the upcoming meeting's page.
• By hand only. The tracker's creator or an admin can send any finished meeting to it from the meeting's page.

A meeting held in another language, or in two, is read once, after the audio pass. Very short meetings are skipped, and rewriting the notes in another language does not read the meeting again. Each meeting's page has a "What changed" panel listing what it gave each tracker.

Who can see a tracker?

The person who made it, and on a company account its admins, until they share it with colleagues already assigned to that client. Those colleagues can review and edit cells; only the creator or an admin can change the columns or scope, share, archive, delete or re-read it.

Every tracker belongs to one client's sealed workspace and reads only meetings its creator could open. The all-clients view labels every row and never merges two clients' rows, even with the same name; client isolation explains the walls. Deleting a tracker deletes every value and quote in it, and deleting a client deletes its trackers. Backups are covered in the privacy section.

Can I ask about a tracker or take the table out?

Yes to both. The assistant reads trackers, so "what salary did each candidate this month ask for?" is answered from the table, naming the meeting behind each value; it never changes a tracker. The table and its full history download as CSV for Excel or Google Sheets. Export is not on every plan; what each plan includes, from tracker numbers to export, is on pricing.

Which languages can a tracker read?

Any of the close to 100 spoken languages TrackHeros recognises, through the same transcript as the notes, so a standup held in German and a call held in French feed the same columns. Text values are written in the meeting's notes language. Every language is listed on the languages page.