Meeting Minutes Template for UK Small Teams

A good set of minutes is not a transcript. It is a short, dependable record of what a small team decided, who agreed to do what, and by when. Done well, it takes fifteen minutes and saves a week of half-remembered conversations. The template below is deliberately plain. It suits a five-person team in a shared office, a family firm in a converted barn, or four freelancers on a monthly call. Copy it, cut what you do not need, and keep the structure — the shape of the document is what makes it useful.

Why a fixed structure beats free-form notes

When you take notes freehand, you naturally capture the interesting parts of a conversation and skip the ordinary ones. Unfortunately the ordinary ones — the date something was agreed, the name attached to a task, the client who must be told before Friday — are usually the parts people need afterwards.

A template fixes that in two ways. It tells you where each item goes while you are still listening, and it tells everyone else where to look when they read it later. It also applies a little healthy pressure: if the decisions heading is still empty at the end of a long discussion, that is worth noticing.

The template

Keep the whole thing to one side of A4. If it runs longer, the meeting probably covered too much, or the note-taker is recording discussion rather than outcomes. The skeleton looks like this:

• Header: meeting name, date, start and finish time, venue or platform, chair, minute-taker.
• Attendees: full names on first mention, initials afterwards. Apologies, and any guests.
• Agenda item: a short heading for each point discussed.
• Decisions: numbered, one line each, written as a statement.
• Actions: owner, task, deadline — three pieces of information, nothing vague.
• Carried forward: anything unresolved that will come back next time.

Header details

Record the meeting name, the date and both the start and finish times. The finish time is handy when someone later asks whether an item was properly discussed or squeezed in at the end. Note who chaired and who took the minutes, because people will have questions and it helps to know who to ask. Mark the document draft until it has been checked, and approved once the group has accepted it at the following meeting.

Attendees and apologies

List everyone present, then anyone who sent apologies. This is not box-ticking: if a decision was taken while half the team was away, the record should show it. Use initials in the body of the minutes — "AB raised the issue of supplier lead times" — and keep a key at the top so the initials are never ambiguous. If two people share initials, add a second letter.

Decisions

Number them. "D1: The weekly update email moves from Monday to Tuesday, starting 7 April." That is a decision. "The team discussed the timing of the update email" is not; it describes a conversation and will cause an argument in three weeks. Write each decision as a single-line statement and keep the numbering running across meetings so people can refer to D14 or A32 without confusion.

Actions and deadlines

Three pieces of information per action: who, what, when. One owner per action, even when others will help. If you write two names, you have written no name. Deadlines should be dates — "Friday 14 March", not "soon", "next week" or "before the end of the month". If a task genuinely cannot be dated yet, mark it "date to be agreed" and put it on the next agenda so it cannot quietly disappear.

Items carried forward

Some things get discussed and neither decided nor assigned. That is fine, as long as they are listed. A short carried-forward section stops the same topic being reintroduced from scratch every month.

Filling it in while the meeting runs

Sit where you can hear everyone, and accept that you will miss the occasional sentence. Capture the outcome, not the debate. Abbreviations and initials are fine; complete sentences are not required. Type the exact figures, dates, product names and client names the moment they are said, because those are the details people misremember. If a name is unclear, leave a gap and fill it in afterwards rather than guessing.

If you are chairing as well as taking minutes, say so at the start and keep the last three minutes free. Read the decisions and actions back aloud and ask whether anything is missing. It also helps to ask "who is doing that, and by when?" while everyone is still in the room. That question can feel blunt the first few times; it is still far less trouble than four chasing emails the following week.

A short example

Present: Priya (chair), Tom, Aisha, Ben. Apologies: Ruth.

D2: Sample orders stay free for the first month, reviewed in June.

A1: Tom — remove the postage charge from the order form. Deadline: 20 June.

A2: Aisha — email the three affected customers before Friday 13 June.

Carried forward: whether to offer the same terms to trade customers (Priya, next meeting).

Notice how little there is. No summary of the twenty-minute debate about postage, no attribution of clever remarks. Just the decision and the two things that now need doing.

Send it out, then close the loop

Circulate within a working day, ideally the same afternoon. Send it to the same list every time and label it clearly as a draft, with a note that corrections are welcome for 48 hours. After that, treat it as the record. Late corrections tend to be about who said what rather than what was agreed, and they are rarely worth reopening.

The habit that makes minutes genuinely valuable is the first item on the next agenda: reviewing the actions from last time. Go through them one by one — done, not done, dropped. Teams that skip this end up with minutes nobody reads and tasks nobody owns. Keep the documents in one running file per year, or a folder per meeting series, so that "what did we agree about the supplier in March?" takes seconds to answer rather than an afternoon.

Common mistakes in small teams

• Recording discussion instead of outcomes. A summary of who said what is a story, not minutes.
• Actions without an owner. "The website needs updating" is a wish. "Ben will update the pricing page by 4 July" is an action.
• Fuzzy deadlines. "Next week" is not a date, and it means something different to everyone reading it.
• Opinions logged as decisions. If nobody agreed, write "no decision reached; item carried forward".
• Circulating too late. Week-old minutes invite edits, second-guessing and arguments.
• No record of apologies. Absences matter when a decision is queried months later.

One caution: if a meeting touches on employment matters, contracts or money, keep sensitive detail out of the version you circulate widely and check what your business is obliged to keep on file. For anything with legal or financial consequences, take proper professional advice rather than relying on meeting notes.

Make the template your own

Adjust the headings to fit how your team actually works. A design studio might add a client sign-off line; a shop might want a staffing section. What matters is that the same four things appear every time — who was there, what was decided, who is doing what, and by when. Agree on one person to keep the master copy and one place to keep it. Then use it for every meeting, including the short ones. The fifteen-minute habit is what turns a template into a record you can trust.

Photo: Startup Stock Photos / Pexels