# How to keep client meeting notes separate when you work with several clients

> A practical guide for freelancers and consultants who run several clients on Google Meet and Microsoft Teams: why blended notes leak, how to give every client its own container and naming rule, what to do when a tool has one workspace, how to delete at the end of a contract, and what to tell clients. Ends with how TrackHeros keeps each client in a sealed workspace.

Canonical: https://trackheros.com/blog/keep-client-meeting-notes-separate/  
Updated: 2026-09-02

Keep client meeting notes separate by giving each client its own container, whether that is a folder, a notebook or a workspace, and by never creating a note outside it. Add a naming rule that carries the client's code into every file name, and when a contract ends, delete rather than archive. The danger is rarely theft. It is the ordinary slip: the wrong summary pasted into the wrong email, one search box that returns two clients, an AI assistant that carries one client's context into another client's call. This guide is for freelancers and consultants who run several clients on Google Meet and Microsoft Teams.

## Why is blending client notes a real risk?

Three failures account for most of the damage, and none of them needs a villain.

The first is the paste. You write up a call for Client A, open your email, and the clipboard still holds Client B's summary. Or the notes app's "recent" list puts the two side by side and you attach the wrong one. It takes a second and it cannot be taken back.

The second is the search box. A notes app with one workspace has one index. Type "invoice" or "deadline" or a first name that both clients share and you get both clients' notes in the same list. That is fine while you are the only reader. It is not fine when you screen-share, when you export "everything tagged March", or when the app's AI feature reads the whole index to answer a question.

The third is memory. Meeting assistants and AI notetakers increasingly "remember" your earlier meetings so their answers improve over time. Inside one client that is useful. Across clients it is a leak with a friendly interface: ask about the API deadline and the tool helpfully mentions the one you agreed with someone else. It does not know that the two projects are not the same project. It only knows that they look alike.

The consequence is not usually a lawsuit. It is a client who sees another company's name in something you sent and quietly stops trusting you with the interesting work. The confidentiality clause in your contract was the easy part. The habit is the hard part.

## Give every client their own container

The rule is simple and the discipline is the whole job: a note is created inside the client's container, never in an inbox to be filed later. Later does not arrive.

What the container is depends on your tools:

| Tool                                 | The container                                                       | What "separate" means there                                                     |
| ------------------------------------ | ------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| A file system or cloud drive         | One top-level folder per client                                     | Nothing lives at the root except the client folders                             |
| A notes app with notebooks or vaults | One notebook or vault per client                                    | Search, tags and AI features are scoped to the notebook, or you do not use them |
| A meeting notetaker                  | One workspace per client                                            | Transcripts, summaries and the assistant's memory are scoped to the workspace   |
| Email                                | The account the client gave you, or a label you never search across | Sent items stay with that client's account                                      |

Two things belong outside all of the containers: your own admin (invoices, contracts, time tracking) and your templates. Nothing else. If you find yourself creating a "General" folder, ask which client it belongs to.

## Use a naming convention you can search by

Files leave their folders. They get attached, exported, dragged into a chat and forwarded. So the client's code has to be in the file name, not only in the path.

A convention that works:

`YYYY-MM-DD CLIENT topic.md`

`2026-09-02 ACME kickoff.md`

`2026-09-02 NORTH sprint-review.md`

The date first, so files sort themselves. Then a short client code that cannot be confused with another client's; avoid initials, because two clients called Northwind and Northgate will both end up as "NW". Then the topic, in one or two words.

Put the same code in the first line of the note, in the subject line of the email you send, and in the calendar event title if the client did not. When the code is everywhere, the wrong-paste failure becomes visible before you press send.

## What if the tool only has one workspace?

Most notes apps and most meeting tools assume one company, one workspace, one team. Tags are the usual answer, and tags are not walls. A tag changes what you see; it does not change what the search index or the AI feature reads.

You have three honest options:

1. **One account per client.** A separate login, in a separate browser profile, with the client's own notes inside it. Clumsy, but it is the only way a single-workspace tool becomes a multi-client tool. If the client gave you an account of theirs, this happens naturally; [managing several Google accounts](/blog/multiple-google-accounts-freelancer/) is its own discipline.
2. **Separate the storage, not the app.** Some apps let you open a different vault, database or notebook that has its own index. Use one per client and keep the app pointed at one at a time.
3. **Turn the clever features off.** If the app must hold every client in one place, switch off cross-workspace search and AI summarising. Then treat it as a filing cabinet, not an assistant.

The test to apply to any AI feature is one question: when it answers, what does it read? If the honest answer is "everything you have ever put in here", it is the wrong tool for work with several clients, however good the answers are.

## Keep the AI's memory in the same box

Try this once with any assistant you use. Open Client A's notes and ask a question that only Client B's notes can answer. If it answers, you have your finding.

The right shape is an assistant that only ever sees the client you are asking about. If you want a view across clients, it should be a view: a list with a client label on every row, not a blended answer that has forgotten where each fact came from. Read-only across clients, editable inside one.

## What should you do when a contract ends?

Delete. Not archive.

Archives are the notes nobody protects. They sit in a folder called "Old clients" that is never looked at and never cleaned out, and they are still in the search index, still in the backup, still one wrong paste away from a new client's inbox. Recordings and transcripts of someone else's meetings are the last thing to keep for sentimental reasons.

Keep what you need for the business: the contract, the invoices, the final deliverables and the hand-over document. Delete the rest, and write the date you deleted it in the one place you keep for that. A short off-boarding checklist:

- Export anything the client asked to keep and send it to them.
- Delete recordings, transcripts and summaries from every tool that holds them, including the notetaker.
- Remove the client's account from your browser profiles and your phone.
- Delete the calendar subscription.
- Note the deletion date next to the contract.

Agree the retention period early, ideally in the contract or on the first call. "I delete recordings thirty days after the engagement ends unless you ask me to keep them" is a sentence clients like hearing.

## What do you tell clients?

Say it before they ask. Three sentences are enough: where the notes and recordings live, who can see them, and when they are deleted. If a notetaker joins your calls, name it in the meeting invitation and again at the start of the first call, and offer to leave it out of anything sensitive.

Clients rarely object to notes. They object to surprises. The freelancer who explains the system in the first meeting is the one who gets asked back.

## How TrackHeros does it

Every client lives in its own workspace, and the separation is how the product is built rather than a setting you switch on. Every query is scoped to one client before it runs; an unscoped query is an error, not a leak. Postgres row-level security sits behind that as a second layer. Each connected Google account belongs to exactly one client, enforced in the database, so a meeting can never belong to two clients, and a meeting that arrives without a client goes to an "Unassigned" workspace with the same rules.

The assistant answers from one client's meetings only, with citations back to who said it and when. There is a global view (dashboard, meeting list, calendar, action items, search and a read-only chat mode), and every row and every fact in it carries its client's label. Nothing is blended and nothing can be changed from there.

When a contract ends, you delete the client workspace with a typed confirmation. The cascade removes the database rows, the stored recordings and transcripts, and the copy held by the meeting-bot service. Backups expire on their normal rotation and are never restored into a live account. The privacy commitments are at [/#privacy](/#privacy), the isolation model is described at [/features/client-isolation/](/features/client-isolation/), and the developer's day-to-day is at [/for/freelance-developers/](/for/freelance-developers/).

## Not yet available

- Connect a Microsoft account for calendar sync — not yet available

## Frequently asked

**Is it really a problem to keep every client's notes in one notes app?**

It is fine until a search, an export or an AI feature reads across the whole app at once. Tags change what you see, not what the index or the assistant reads. If the app has one workspace, keep one account per client or turn the cross-workspace features off.

**Should I delete or archive a client's notes when the contract ends?**

Delete, once the agreed retention period has passed. Archives stay in the search index and the backups and are never looked at again, which makes them the least protected notes you hold. Keep the contract, invoices and final deliverables; delete recordings, transcripts and summaries.

**Do I need to tell clients how I store meeting notes?**

Say it before they ask. Three sentences cover it: where the notes and recordings live, who can see them, and when they are deleted. If a notetaker bot joins your calls, name it in the invitation and at the start of the first call.

**Can an AI notetaker mix up two clients?**

Yes, if its memory spans every meeting you have ever recorded. Test it by opening one client and asking a question that only another client's notes can answer. The safe design is an assistant that only sees the client you are asking about, with any cross-client view read-only and labelled.

---

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