How to track client feedback across review meetings

A client feedback tracker keeps everything a client has said about your work in one table: which feature or screen it was about, what they said, how they felt, and what you agreed to change. This guide is for freelance developers, consultants and small agencies who show work to clients in sprint reviews, design reviews and check-ins on Google Meet or Microsoft Teams. It covers why feedback gets lost, the columns that keep it, and how TrackHeros fills the table from the reviews themselves.

Why does client feedback get lost between reviews?

Because it is spread across meetings and only part of it is ever written down. The client mentions the export button in one review, comes back to it two reviews later, and agrees a change in a third. The minutes of each meeting are correct; none of them tells the whole story of the export button.

Then the disagreements start. The client remembers asking for something; you remember them approving the version they now dislike. A table with a row per feature, and a history behind every cell with the words that were said, settles that in one click.

Which columns should a client feedback tracker have?

Five or six, with each row named by the thing the feedback is about.

Column	Type	Rule	What belongs in it
Feature	Text, names the row	Names the row	The feature, screen or deliverable discussed, by the name the client uses
Feedback	List	Add and remove items	Each specific point the client raises, one item each
Sentiment	Status	Latest value wins	Pleased, Mixed, Unhappy, only when the client says how they feel
Decided change	Text	Latest value wins	The change agreed, as said
First raised	Date	Keep the first value	The date of the meeting where the client first gave feedback on it
Last discussed	Automatic	Filled automatically	The last review that mentioned the feature

None of the six templates matches this exactly. Describe it in a sentence and edit the draft TrackHeros gives you, or start blank, and preview it on one recent review before saving. Whether your plan lets you design your own columns is on pricing.

How do you stop feedback points from piling up?

Make feedback a list column. A point is added when the client raises it and removed when somebody says it has been dealt with, so the list shows what is still open rather than everything ever said.

Removal always waits for you. If you say "we fixed the date picker" and the client agrees, TrackHeros proposes removing that point, and you accept it in the review queue. If only you said it, you may prefer to keep it until the client has seen the fix. Either way the cell's history keeps every point that was ever on the list, with when it was added and when it went.

How should a client's sentiment be recorded?

As a status with options you choose, filled only when the client says how they feel in words: "this is exactly what we wanted", "I'm not sure this works for our users". Say so in the column's description, and add that silence is not approval.

Over a project, the history becomes a record of the relationship. Sentiment on the onboarding screens might read Unhappy on Tuesday 6 October, Mixed on Tuesday 20 October and Pleased on Tuesday 3 November, with the client's own words beside each change. That is worth having before a renewal conversation, and it is honest: every value points at a line in the transcript, and a value with no line is dropped.

What if two people at the client disagree?

Let the history show both, with names. Every value in a tracker records who said it, so when the product owner says in one review that the dashboard is fine and the managing director says in the next that it is not, the cell's history holds both views, each with the speaker, the time and the words.

If that happens often, add a "Raised by" people column, so the table itself shows whose feedback a feature is carrying. Write the decided change's description to ask for changes the client agreed, not suggestions made in passing. The review queue is where you catch anything that slips through.

How do you track what was decided?

In a "decided change" column that follows the latest value, so the cell holds what was last agreed and its history holds every earlier version. "Move export into the toolbar" in one review and "keep it in the menu and add a shortcut" in the next is a change of plan, and the history shows who said each version and when.

If feedback often turns into new work, add an "In original scope" yes / no / unclear column, filled only when someone says so. That is where feedback becomes scope creep, covered in scope creep starts in meetings. For the requests themselves, the scope change tracker guide uses the Change requests template.

Which meetings should feed the tracker?

The reviews, and usually nothing else. A tracker reads one client's meetings, and you choose which: a recurring meeting such as the fortnightly sprint review, meetings whose title contains "review" or "demo", specific meetings attached before they happen, or any finished meeting sent to it by hand.

A recurring review is the natural fit; track a recurring client meeting and running a sprint review with a client cover the meeting itself. If you scope the tracker to every meeting of the client instead, meetings plainly unrelated to feedback are skipped. If the project is already under way, the tracker can read your recent past meetings in scope when you create it, oldest first, so the table starts with history.

What does a review look like with a feedback tracker?

It starts from the table rather than from memory. Filter to rows changed recently to see what moved since the last review, open the rows with conflicts, and take the client through the open feedback points one at a time.

After the meeting, its page lists what it changed in each tracker, and the new values wait in the review queue, grouped by meeting, until you accept, correct or reject them; you can also accept everything from one meeting at once. A rejected value does not come back if the meeting is read again. The tracker's creator gets an in-app alert when changes are waiting.

How does TrackHeros fill a client feedback tracker?

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 notetaker joins the review on Google Meet or Microsoft Teams. Once the notes are ready, not during the call, the tracker reads the meeting and proposes values.

Every value records the meeting it came from, who said it, when, and the words they used, with a link that opens the transcript at that moment. A review held in French is read through the same transcript as the notes, and text values are written in the notes' language; see the languages page. The assistant reads the table too: "what has Client A said about the onboarding screens?" is answered from it, with the meetings cited. Each tracker belongs to one client's sealed workspace, as described on client isolation, and deleting a tracker deletes its table and every value and quote.