# What field types can a meeting tracker have?

> For anyone designing a table that fills itself from Google Meet and Microsoft Teams meetings: the ten column types a TrackHeros tracker offers, what each one accepts from a meeting, which column names a row, the rules for how a new value meets an old one, the two columns that fill themselves, and what happens when a column's type changes.

Canonical: https://trackheros.com/answers/what-field-types-can-a-tracker-have/  
Author: Sami Kanafani  
Updated: 2026-11-04

**In short:** A TrackHeros tracker has ten column types: text, number with a unit, money with a currency, date, status with options you define, person, list of people, yes / no / unclear, list, and link. After each Google Meet or Microsoft Teams meeting it reads, a value is written only if it fits its column's type; one that does not fit is dropped, never forced into shape.

| Fact | Detail |
| --- | --- |
| Column types | Text, number, money, date, status, person, people, yes / no / unclear, list, link |
| Filled automatically | Last discussed, and the meeting date |
| A value that does not fit | Dropped, never repaired |
| Changing a column's type | Convert the values, or keep the old ones as a separate column |

A tracker in TrackHeros is a table that fills itself from your meetings. You name its columns, give each a type and a one-line description, and choose which meetings feed it. This answer is for anyone designing one for 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 whole feature is on [trackers](/features/trackers/).

## Which column types can a tracker have?

Ten. Each holds a different kind of value, and the type decides what a meeting may write into the column.

| Type     | What it holds                         | Example                    |
| -------- | ------------------------------------- | -------------------------- |
| Text     | A short piece of wording              | "Login API", "two days"    |
| Number   | A figure, with a unit if you set one  | 12.5 h                     |
| Money    | An amount and a currency              | 1,200 USD                  |
| Date     | A calendar date                       | 17 March 2026              |
| Status   | One of the options you define         | In progress, Done          |
| Person   | One name                              | Maria                      |
| People   | Several names                         | Maria, Tom                 |
| Yes / no | Yes, no or unclear                    | In original scope: unclear |
| List     | Items added and removed one at a time | Blockers                   |
| Link     | A web address                         | A ticket or document link  |

The description under each column matters as much as its type: it is what TrackHeros reads to decide what goes in the cell, so "the date the client agreed, not estimates" fills better than "date". [Designing the columns of a meeting tracker](/blog/design-the-columns-of-a-meeting-tracker/) goes further.

## What does each type accept from a meeting?

Only a value it can hold. One that does not fit is dropped rather than repaired, because a cell nobody can rely on is worse than an empty one.

- **Date.** A relative date such as "next Thursday" is worked out against the date of the meeting it was said in, not the day the tracker happens to read it.
- **Money.** An amount needs a currency. If a meeting gives a figure with no currency and the column has no default currency, the value waits for your review instead of being given one.
- **Status.** Only one of your options. You can mark some as final, such as Done or Lost, to tell TrackHeros the row is finished.
- **Person and people.** Names as they were heard. An email address is only ever taken from the meeting's invitation, never written by the AI.
- **Yes / no.** "Unclear" is a real answer, and the right one when nobody said.
- **List.** Items are added when they are raised and removed when someone says they are resolved.

## Which column names a row?

In a table whose rows carry on from meeting to meeting, a key column names each row: a candidate, a feature, a change request, a deal. It can be a text, person or link column, and a row can be named by more than one, such as candidate and role. A table with a new row for every meeting, like a standup log, needs no key, because the meeting is the row. [One row per candidate or one per interview](/answers/one-row-per-interview/) shows the difference.

## How does a new value meet the one already there?

By the column's rule, of which there are four:

- **The newest meeting wins** (the default): the latest value is current and older ones stay in the cell's history.
- **Keep the first value**: a later, different value is shown as a conflict for you to settle. It suits "date the request was first made".
- **Add and remove items**: the rule for lists.
- **Only people fill it**: the AI never writes the column.

Two columns fill themselves: "last discussed", the last meeting that mentioned the row, and the meeting date in a one-row-per-meeting table. More in [what happens when two meetings disagree](/answers/what-happens-when-two-meetings-disagree/).

## Can I change a column's type later?

Yes, and nothing is lost. TrackHeros asks what to do with the values already there: convert them, keeping and flagging any that do not fit the new type, or keep the old values as a separate column and start the new type empty; a list column can only do the second. Renaming a column keeps its values, and removing one hides it rather than deleting what it held. Whether your plan lets you design your own columns or start from the templates only is on [the pricing page](/pricing/).

---

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