Meeting Minutes and Action Registers

Information only — not legal advice.

Meeting minutes preserve what was discussed and decided. An action register follows commitments until they are completed, cancelled or replaced. Keep a stable reference between them so that the reason for an action remains understandable after the meeting.

Capture the minimum useful context

• Meeting title, identifier, date, time and location or meeting method.
• Chair, minute taker, attendees and apologies where relevant.
• Agenda item, concise discussion summary and the evidence considered.
• Decision, responsible authority, conditions and unresolved questions.
• Action, one accountable owner, due date and expected result.
• Review or approval state, version and intended distribution.

Write facts and outcomes without attributing unnecessary personal details. Minutes are usually a concise record rather than a transcript. Formal governance meetings may have additional legal, constitutional or organizational requirements.

Separate a discussion, a decision and an action

Fictional example: a team is considering a replacement air-handling unit.

Discussion: the supplier's delivery date may delay commissioning. The team considered an alternative model and its maintenance implications.

Decision `DEC-014`: retain the specified model, subject to written delivery confirmation by 9 October. The project sponsor confirms the decision within their authority.

Action `ACT-028`: the procurement lead obtains written confirmation by 9 October and links the supplier's response. If the date cannot be met, the lead escalates to the sponsor.

“Discuss supplier” is a weak action. “Obtain the supplier's confirmed delivery date and attach the response” gives the owner and reviewer a clear result to check.

Use a simple action lifecycle

1. Open: agree the action, owner, deadline and completion evidence.
2. In progress: record the next step and any changed assumptions.
3. Blocked: state the dependency, who can resolve it and the escalation date.
4. Ready for review: link the output and identify the reviewer.
5. Closed: record who accepted the result and when.

Use a cancelled or superseded state when appropriate, with a reason and replacement reference. Preserve the original due date when recording a revised commitment. Closed should mean the agreed completion test was met, not merely that somebody changed a dropdown.

Before, during and after the meeting

Beforehand, circulate the purpose, agenda and decision papers. During the meeting, read back decisions, owners and dates so participants can correct misunderstandings. Afterwards, issue the draft promptly, gather corrections and record the agreed version. Do not silently rewrite approved minutes; issue an identifiable correction.

At the next review, discuss exceptions: overdue actions, blockers, changed dates and items awaiting acceptance. Reference existing actions instead of creating new duplicates every week.

Choose a template

There are four minutes templates and four action-register templates below. Each is available as a printable PDF, an editable XLSX workbook and a native .ts workbook for TableStudio. Download the .ts file, then use TableStudio's Open command to select it. XLSX files can be edited in compatible spreadsheet applications.

• Weekly team minutes: concise agenda, outcomes and follow-up for routine coordination.
• Project coordination minutes: decisions, affected deliverables and responsibility across disciplines.
• Site coordination minutes: work areas, observations, constraints and inspection references. Use the appropriate separate process for urgent hazards and statutory reporting.
• Governance decision minutes: authority, conflicts, quorum where applicable, resolution and approval details. Adapt to the organization's governing rules.
• Team action register: everyday commitments, owners and evidence.
• Project action register: deliverables, dependencies, acceptance criteria and changes to commitments.
• Corrective-action register: finding, immediate correction, cause, action and effectiveness review.
• Handover action register: asset or location, missing information, acceptance and operator sign-off.

Use the files well

The PDFs are printable blank forms. Editable files contain a blank working sheet and a separate, clearly labelled fictional example. Replace the example with your own situation; it is not evidence of a real meeting or acceptance. The templates are original educational forms, not certified compliance documents.

Review the fields before collecting personal data, assign appropriate access and retain completed records according to your organization's policy. Save each approved meeting record separately; keep the action register live across meetings.

Related reading: Project Workspace Setup, GDPR and Collaboration Platforms and COBie and Structured Handover Data.

Important information

This article provides general information and does not constitute legal advice or replace a qualified professional's assessment of your circumstances. Laws, official guidance, standards and product features can change. Check current primary sources and the requirements applicable to your jurisdiction, contract and project before making decisions. Examples illustrate the discussion; they are not official rulings or instructions for a particular case. For legal decisions, consult a qualified lawyer; for technical or other specialist matters, consult the responsible professional.