Six meeting tracker templates for freelancers, and when to describe your own

A tracker template is a ready-made table definition: the columns, the type of each, and a line saying what belongs in it. This guide is for freelancers and consultants who want their Google Meet and Microsoft Teams meetings to fill a table, and are deciding which one. It walks through the six TrackHeros tracker templates, what each is for, and when you are better off describing your own.

Which tracker templates does TrackHeros offer?

Six: Project tracker, Change requests, Interview scorecard, Sales discovery, Decision log and Standup log. Five keep one row per thing tracked and update it meeting after meeting; the Standup log adds a new row for every meeting.

Template	One row per	Suits
Project tracker	Piece of work	Any build or delivery project
Change requests	Request outside scope	Fixed-price work, where scope is money
Interview scorecard	Candidate	Hiring for a client, or for yourself
Sales discovery	Prospect	Discovery calls and your own pipeline
Decision log	Decision	Projects whose decisions get reopened
Standup log	Standup	Daily or weekly standups

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. A template sets up a table on top of that; it does not change the notes. Every tracker belongs to one client's workspace, unless you scope it to all your clients, in which case each client gets a separate table of its own.

What is the Project tracker for?

Every piece of work a client's meetings discuss, with where it stands. Its columns are item, description, status, owner, deadline, priority, blockers and last discussed.

Status is a set of options, some marked as final, such as Done. Blockers is a list: an item is added when raised and removed when someone says it is resolved. Last discussed fills itself with the latest meeting that mentioned the item. It suits a freelance developer's build as well as the wider brief of a fractional CTO; the standup tracker guide pairs it with the Standup log, and project status across all clients shows one definition kept for every client.

When should you use the Change requests template?

When the work is fixed-price or tightly scoped, and every "could it also…" has a cost. Its columns are request, requested by, date requested, in original scope, estimated effort, cost impact, decision and decision date.

Two columns do the protecting. Date requested keeps the first value, so a later meeting that remembers the request differently shows up as a conflict for you to settle rather than quietly moving the date. In original scope is yes, no or unclear, and is left unclear unless someone says which. Cost impact is a money column, with an amount and a currency. Why requests like these matter is in scope creep starts in meetings, and the scope change tracker guide is about running one.

What does the Interview scorecard record?

One row per candidate, updated across every interview they have. Its columns are candidate, role, stage, interviewers, strengths, concerns, technical assessment, salary expectation, availability and recommendation.

Strengths and concerns are lists, so the second interviewer's concern joins the first's rather than replacing it. Salary expectation is a money column, filled only when a figure is actually said. Freelancers who run technical interviews for a client get a side-by-side view of candidates instead of six sets of notes; the interview tracker guide covers that, and recruiters will find more on recruiters. This is a table, separate from the Interview summary profile that shapes the notes of a single interview.

What does the Sales discovery template capture?

One row per prospect: company, contact, pain points, current tools, budget, timeline, decision makers, stage and next step. It suits freelancers selling their own services as much as people selling a product.

Pain points and current tools are lists, decision makers is a list of people, budget is money, and stage is a set of options with final ones such as Lost. Each discovery call adds to the prospect's row instead of starting a new page of notes. Building a sales pipeline from meeting notes has the detail.

How are the Decision log and Standup log different?

The Decision log keeps one row per decision and tracks whether it still stands; the Standup log is the only template that adds a new row for every meeting. One is a record of decisions, the other a record of days.

The Decision log's columns are decision, context, decided by, date and status, where status is active, reversed or superseded. A decision the client reopens keeps its row, and the history shows when and by whom it changed; the decision log guide explains why that record holds up. The Standup log's columns are date, attendees, done, planned and blockers, with the date taken from the meeting itself.

When should you describe your own tracker instead?

When what you track is not on the list, or a template needs more than a column or two changed. Describe the table in a sentence, such as "every vendor we evaluate, their price and the client's concerns", and you get a draft to edit; or start blank.

Common cases among freelancers:

• Vendor or tool evaluations, one row per option: vendor evaluation tracker.
• Client feedback on releases or designs: client feedback tracker.
• Rates and budgets across clients: budget and rate tracker.
• Risks raised in meetings: risk register from meetings.

Ten column types are available: text, number with a unit, money with a currency, date, status, person, list of people, yes / no / unclear, list, and link. Whether your plan includes designing your own trackers, rather than using the templates, is on pricing.

Which template should you start with?

The one that answers the question you ask most often between meetings. "Where is that piece of work?" is the Project tracker; "did they agree to pay for that?" is Change requests; "what did we decide, and is it still true?" is the Decision log.

Start with one, scoped to one client, and read the review queue after its first few meetings. If the values are right, add the next table; if they are not, the column descriptions usually need tightening before anything else. A freelancer with three clients might end up with a Project tracker kept for all of them, Change requests for the fixed-price one, and an Interview scorecard for the client they help hire. Tracking what matters across meetings covers the choice in general.

What should you check before saving a template?

Which meetings feed it, how values land, and whether it should read past meetings. A template's columns are a starting point; those three choices decide how well it fits your client.

1. Scope. All your clients, one client (optionally only meetings whose title contains words such as "interview"), chosen recurring meetings, specific upcoming meetings, or only meetings you send by hand.
2. Column rules. Latest value wins by default. Keep the first value turns a later difference into a conflict. Lists add and remove items. Fill by hand only keeps a column for you.
3. Review. Changes wait for you by default; confident ones can apply on their own instead.
4. Preview. Run the definition on one recent meeting to see what it would record. Nothing is saved.
5. History. Have it read your recent past meetings in scope, oldest first, so the table starts with what was already said.

Adding, removing or retyping a template's columns counts as designing your own tracker, which depends on your plan; pricing says which plans include it.

A tracker reads meetings in any of the close to 100 spoken languages TrackHeros recognises, whether a client meets in French, Spanish or German, and writes text values in the notes' language; the list is on languages. How to write column descriptions that keep values accurate is in designing the columns of a meeting tracker.