Meeting Notes for Digital Agencies: What to Capture and When

Notes are your defence against scope creep

Most agency disputes follow the same pattern. The client says "I thought that was included". Someone remembers a conversation, someone remembers it differently, and there is no record. Meeting notes are cheap insurance, provided they capture the right things at the right meetings.

The five meetings that matter

1. The kickoff

Capture: goals, audience, requirements, constraints, in-scope and out-of-scope items, who approves what, and the dates. Write the out-of-scope list explicitly and read it back to the client.

2. Requirements and design reviews

Capture: each piece of feedback with who gave it, whether it is a change or a preference, and whether the client approved the direction. "Approved the layout, pending logo update" is a precise record.

3. Weekly status calls

Capture: decisions, blockers, dependencies on the client (copy, access, feedback), and the next deadlines. Note what the client owes you.

4. Change requests

Capture: what was requested, the impact on scope and timeline, and the client's answer on cost. Never let a "quick addition" pass without writing it down.

5. The approval or handover meeting

Capture: what was delivered, what was accepted, and anything left open. This note closes the project.

A habit that works

After each meeting, write a five-line recap and send it to the client the same day: decisions, actions with owners and dates, what is still open. Ask for corrections. The email is your record and the client's reminder. See the meeting follow-up templates.

Make notes findable

Name meetings by client, project and date, and keep decisions apart from ideas. When a client asks about a past conversation, you should be able to find it in seconds. MeetMemo keeps a client and project name on each meeting and makes notes and transcripts searchable on your device, with sourced answers across meetings when you ask. See searchable meeting history and the agency solution page.

Requirements without chaos

Once requirements are clear, write them in a single document and share it. The project requirements template gives you the structure, including a source column that references the meeting each requirement came from.

Be realistic about tools

A note-taking tool does not replace project management software or a client portal. It helps you stop losing the conversations those systems depend on. MeetMemo is a personal app in early access, so each person's meetings stay on their own device today.

Sample notes from a design review

Design review - Northwind, 15 Oct 2026
Attendees: Priya (client), Dev (designer), Alex (account)

Feedback
- Homepage layout: APPROVED (Priya).
- Hero image: CHANGE - wants a lifestyle photo, not a product shot. (Change request, in scope: one revision.)
- Colour palette: PREFERENCE - likes the green, will confirm after seeing it printed.
- Members area: raised again - OUT OF SCOPE (see kickoff, 12 Oct). Priya will think about a phase two.

Actions
- Dev: revised homepage with lifestyle hero by Fri 18 Oct
- Priya: confirm colour palette by Mon 21 Oct

The labels APPROVED, CHANGE, PREFERENCE and OUT OF SCOPE take a few seconds to write and make the notes useful as a record.

Approval language that prevents disputes

Clients often say "looks good" without meaning "approved". Where an approval matters, confirm it in plain words: "To confirm, you have approved the homepage layout, and further changes would be a new request?" Write the answer down and repeat it in your follow-up. Approvals recorded this way are far easier to rely on later.

Handling change requests in writing

A simple three-line format keeps changes visible:

1. Request: what the client asked for, in their words
2. Impact: effect on cost, timeline and other work
3. Decision: accepted, declined or deferred, and who decided

Keeping the habit in a busy week

You will not write perfect notes after every call. Keep the minimum: decisions, actions with dates, what the client owes you, and anything out of scope. Four lines done every time beat a full template done sometimes.

Frequently asked questions