# Notes for recurring client meetings: one running document or one per meeting?

> For freelance developers and consultants with weekly standups, status calls and reviews on Google Meet or Microsoft Teams: one running document against one record per occurrence, a template that carries action items forward, what to do when the series changes, and how to find things months later. Ends with how TrackHeros handles a series, including per-series auto-join and notes language.

Canonical: https://trackheros.com/blog/recurring-client-meeting-notes/  
Author: Sami Kanafani  
Updated: 2026-10-22

**In short:** For recurring client meetings, keep one dated record per occurrence and carry open action items to the top of the next one. A single running document is quicker to start but harder to send, search and delete. TrackHeros files each occurrence of a Google Meet or Microsoft Teams series under its client, with auto-join and the notes language settable for the whole series.

| Fact | Detail |
| --- | --- |
| Each occurrence | Its own meeting, notes and action items, filed under the client |
| Auto-join | This meeting, then the recurring series, then the account default; most specific wins |
| Notes language | Meeting, recurring series, client, then account; most specific wins |
| Open items across clients | One Action items page, each row labelled with its client and meeting |

Notes for recurring client meetings work best as one dated record per occurrence, with last week's open action items carried to the top of the next. This guide is for freelance developers and consultants with weekly standups, status calls and reviews on Google Meet or Microsoft Teams. It compares a running document with one record per meeting, gives a template that carries actions forward, covers what to do when the series itself changes, and shows how to find something from week nine in month six.

## Should you keep one running document or one record per meeting?

One record per occurrence, for anything a client will read. A running document is easier to start and pleasant for a few weeks; after that it is hard to send, hard to search by date and hard to delete cleanly.

| Question                                | One running document                               | One record per occurrence                |
| --------------------------------------- | -------------------------------------------------- | ---------------------------------------- |
| Sending this week's notes to the client | Copy a slice out, and hope you got the edges right | Send the record                          |
| Finding what was said on a date         | Scroll, or search for the date heading             | Open the file with that date in its name |
| Carrying actions forward                | Easy: they are just above                          | Needs a carried-forward table            |
| Size after six months                   | Long enough that nobody reads the top              | Each record stays short                  |
| Your private remarks                    | Sit beside client-facing lines                     | Kept out of what you send                |
| Deleting at the end of the engagement   | One file, which is easy                            | Many files, all in one client folder     |

A running document still suits two cases: an internal daily standup where nobody outside the team reads the notes, and a short series of three or four meetings with a fixed end. For a weekly client call that runs for months, one record per occurrence wins.

## How do you carry action items forward?

Open each record with a table of the previous occurrence's open items, and go through it in the first minutes of the call. That one table does the job a running document was doing.

```markdown
# [Client] weekly status: 2026-10-23

## Carried forward

| Action                          | Owner | Due        | Status        | First raised |
| ------------------------------- | ----- | ---------- | ------------- | ------------ |
| Send November sample files      | Tom   | 2026-10-20 | Done          | 2026-10-16   |
| Test account on accounting tool | Priya | 2026-10-17 | Open (2nd wk) | 2026-10-09   |
| Write up rounding rule          | Me    | 2026-10-22 | Done          | 2026-10-16   |

## Since last week

## Decisions

## New actions

| Action | Owner | Due | Notes |
| ------ | ----- | --- | ----- |

## Next meeting

2026-10-30, 10:00 (UK time)
```

Three rules keep the table honest:

- **Every item ends in one of three words:** done, open, or dropped. "Dropped" needs a date and who agreed, so an item never simply disappears.
- **Keep the "first raised" column.** An item open for three weeks is not an action any more; it is a conversation to have, and the date makes that visible without anyone having to say it.
- **Resolve vague dates.** "End of next week" means one thing on Monday and another when you read it on Thursday. Keep the phrase if you like, and write the date next to it. [How to write action items](/blog/how-to-write-action-items/) covers the line itself.

The weekly call that uses this template is described in [running a weekly client status meeting](/blog/weekly-client-status-meeting/).

## What should you do when the series changes?

Change it in the calendar deliberately, and split it when its purpose changes. A recurring meeting that moves time, gains people or turns into a different kind of meeting is where notes and tools lose track.

Both calendars ask how far a change reaches. When you edit a recurring event, Google Calendar asks which events in the series the change applies to ([Google Calendar Help](https://support.google.com/calendar/answer/37115)). The new Outlook offers to edit one event, the whole series, or this event and all following ones; classic Outlook offers just this one or the entire series ([Microsoft Support](https://support.microsoft.com/en-us/outlook/calendar/change-an-appointment-meeting-or-event-in-outlook)). Pick on purpose. A time change applied to one occurrence by accident leaves next week's call at the old time.

Three habits help:

- **One series per kind of conversation.** A weekly slot that is a status call one week and a sprint review the next confuses everything keyed on the series: your notes, your template and any setting in a tool. Make two series.
- **After a change, check the next occurrence.** If you edited "this and following", open next week's event and check the time, the link and the guests.
- **Write a line for a skipped week.** "No meeting 2026-11-06 (client holiday)" in the client folder stops a gap in the dates looking like lost notes.

## How do you find something from a series months later?

By date and client, in the file name, and through a decision log rather than rereading thirty records. Name each record `YYYY-MM-DD CLIENT weekly-status` so it sorts and filters itself; [keeping client notes separate](/blog/keep-client-meeting-notes-separate/) explains the naming rule.

Nobody rereads six months of status notes to find when the release date moved. Copy decisions that will matter later into a [decision log](/blog/decision-log-for-client-projects/) as you write them, with the date of the meeting. Once a quarter, a five-line roll-up of decisions and milestone dates gives the client, and you, the series at a glance.

## What do you send the client from a recurring meeting?

This week's record, in the email body, under the same subject line every week: "Status: [Client] [project], [date]". Not the running document and not an attachment. The same subject keeps the thread searchable on both sides, and a body is read on a phone where an attachment is not.

## How does TrackHeros handle a recurring meeting series?

TrackHeros is an AI meeting notetaker that treats each occurrence of a Google Meet or Microsoft Teams series as its own meeting, with its own summary, decisions and action items, filed under the client whose calendar it came from. It does not merge a series into one running document.

Auto-join has three levels: this meeting, then the recurring series, then your account default ("Join meetings automatically" in Settings). The most specific one wins, and the app shows which level decided. The meeting page reads "The bot will join this meeting" or "The bot will not join this meeting". To skip a week, "Stop the bot joining this meeting?" offers "Just this meeting" or "Every meeting in this series", and "Reset to my account default" is there when you want the default back. [Stopping the notetaker joining a recurring meeting](/answers/stop-the-notetaker-joining-a-recurring-meeting/) has the detail.

The notes language can be set for a single meeting, a recurring series, a client or the account, with the most specific winning; on paid plans ([pricing](/pricing/)) a weekly call with a client's team in Madrid can get Spanish notes while the client's other meetings stay in English. Separately, a series remembers the language it is spoken in, and re-checks that memory; see [why a notetaker should remember the language of a recurring meeting](/blog/recurring-meetings-remember-their-language/). If the same meeting sits on two calendars of the same client, it gets one bot. A recurring meeting from your own calendar waits under "No client" until you file it, and File it can remember the choice for the whole series.

Carrying forward is handled by the "Action items" page: everything committed to in your meetings across every client, with Client and From meeting columns, Open, Done and All filters, and items you can tick done as they close. Inside a client, ask "what did we decide about the release date in the last month of status calls?" and the answer is cited to who said it and when. More at [action items](/features/action-items/) and [ask your meetings](/features/ask-your-meetings/).

## Frequently asked

**Should I keep notes for every occurrence of a recurring meeting?**

For client-facing meetings, yes: a short dated record each time, even if it is five lines. For an internal daily standup, a running list of blockers and decisions is usually enough. The test is whether anyone will ever need to know what was said on a particular date.

**How do I stop action items being forgotten between weekly meetings?**

Start each occurrence's notes with a carried-forward table of last week's open items, and go through it in the first minutes of the call. Mark each one done, still open, or dropped by agreement, and never let an item disappear without one of those three words next to it.

**Should I send the client the running document?**

No. Send this week's record only, in the email body under the same subject line each week. A running document carries every earlier week, including notes you wrote for yourself, and it gets longer and less read with every occurrence.

**Can I stop TrackHeros joining one occurrence of a recurring meeting?**

Yes. On the meeting page, the dialog 'Stop the bot joining this meeting?' offers 'Just this meeting' or 'Every meeting in this series'. The most specific setting wins, so one skipped week does not change the rest of the series, and the app shows which level made the decision.

---

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