What this is
What is a meeting and action log?
What is a meeting and action log?
It is a running record, kept per meeting series, that captures every decision and action item raised in an operational meeting alongside an owner and a due date. It is not a set of minutes describing what was discussed — it is the subset of that discussion that someone is now accountable for delivering.
How is it different from a CAPA record?
The log captures agreed actions as they arise; a CAPA record exists where an action needs its effectiveness verified after closure, typically because it responds to a nonconformity. Routine actions stay in the log. Anything that needs proof the fix actually worked gets raised to a CAPA and referenced back.
What counts as a meeting series for this log?
Any recurring operational meeting with a stable membership and cadence — a tier board, a safety committee, a shift handover review. Each series keeps its own continuous log rather than a fresh sheet per session, so an action opened in March and still open in June is visibly the same row, not a new one.
Scope
When is a meeting and action log required?
This log is one step in a larger daily management programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later, because the same information ends up scattered across two sheets that were never meant to be reconciled.
Use this template when
- An operational meeting has just taken place, or is about to, and decisions from it need an owner and a date
- A meeting series is being set up for the first time and needs its own continuous log
- An action from a previous meeting is still open and needs its status, due date or owner updated
- You are running the Daily Management System programme and this log is one of its steps
- A linked record needs this one to exist: links Tier Board Review and CAPA
Do not use it for
- Tier Board Review, which runs the daily management meeting against a fixed agenda and records what was agreed and by whom — the meeting record itself, not the action tracker underneath it.
- Gemba Walk Record, which records a structured walk of the process by a manager and what was raised on the floor, not in a meeting room.
- Layered Process Audit, which checks that specific process steps are being done as specified, on a schedule, rather than tracking meeting outcomes.
- A CAPA record, once an action needs its effectiveness verified after closure — that action should be raised to CAPA and the reference logged here, not carried indefinitely as an ordinary row.
- Anything outside KnowOps, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.9.3 requirements does this satisfy?
ISO 9001 cl.9.3 sets management review as a planned, recurring event whose outputs are decisions and actions, not just a discussion. The clause map below shows which field carries which part of that requirement.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.9.3.1 | Management review shall be planned and carried out at planned intervals | Header |
| ISO 9001 cl.9.3.3 | Outputs shall include decisions and actions related to opportunities for improvement | Actions |
| ISO 9001 cl.5.3 | Responsibilities and authorities for relevant roles shall be assigned and communicated | Actions |
| ISO 9001 cl.9.3.3 | Outputs shall include any need for changes to the quality management system | Actions |
| ISO 9001 cl.10.2.1 | Where a nonconformity recurs, the organization shall take action and evaluate whether the response was effective | Actions |
| ISO 9001 cl.9.1.3 | The organization shall analyse and evaluate results, including trends, arising from monitoring | Log health |
| ISO 9001 cl.7.5.3 | Documented information shall be retained as evidence and be available when and where needed | Log health |
| ISO 9001 cl.5.1.1 | Top management shall demonstrate leadership by taking accountability for the effectiveness of the quality management system | Header |
What it does not cover
- An action logged with no due date, which cannot be marked overdue and so never surfaces on any exception report until someone remembers to chase it.
- A carried-over action re-entered as a fresh row, which resets its history and hides how many meetings it has actually survived unresolved.
- An action marked Raised To A CAPA with no CAPA ID against it, which breaks the link the moment anyone tries to trace effectiveness back to the log entry that started it.
- A Category field left blank on every row, which makes it impossible to see whether the same theme — maintenance, say — keeps generating actions nobody is fixing at the root.
- A signature applied before the open and overdue counts are checked against the actual rows, which puts a name to a health summary nobody actually verified.
Global
Meeting and Action Log requirements by country
ISO 9001 is a voluntary, internationally recognised standard, so what makes a meeting and action log defensible depends less on statute and more on who is going to ask to see it — a certification auditor, a customer, or a court.
ISO 9001:2015 under IAF MLA-accredited certification bodies
Auditors sampling management review outputs expect to trace a decision from the meeting to a named owner, a due date, and eventually a closed status — a log with gaps in any of those is treated as an open finding, not a formatting issue.
A poorly kept log can cost a minor nonconformity at surveillance audit and, if actions are shown to recur unaddressed, can escalate to a major one against clause 9.3 or 10.2.
UKAS-accredited third-party certification, plus customer second-party audits
UK customers in food, pharma and automotive supply chains routinely request meeting logs as evidence during supplier audits, particularly where a customer complaint traces back to an action that was supposedly closed.
A log that shows the action closed with no evidence of what changed undermines the supplier's position in a commercial dispute over a recurring defect, independent of certification status.
ANAB-accredited certification, and discovery in product-liability litigation
In litigation following an incident, meeting logs are discoverable and are read for whether management knew about a risk, discussed it, and then failed to close the resulting action.
An open action left unaddressed for months with no escalation is the kind of paper trail that turns a defence of reasonable care into evidence of prior knowledge.
How to complete it
How to complete a meeting and action log, step by step
Filling in the fields is mechanical. The judgement calls below are what decide whether the finished log actually holds up when someone other than the chair reads it later.
Not everything discussed deserves a row — the log stays useful only if a row means someone is now accountable for a deliverable by a date, not that a topic was mentioned. The chair has to draw that line consistently, meeting to meeting, or the log drifts into minutes.
Keeping the original date shows the true age of the delay and should be the default; resetting it on every carry-over hides exactly the pattern — Actions Carried Over Three Times — the log health section exists to expose.
The Raised To A CAPA field is the decision point: once effectiveness needs verifying, ownership of that evidence moves to CAPA and the log keeps only the reference. Leaving it in the log because raising a CAPA feels like extra process defeats the reason CAPA exists.
Open Actions, Overdue Actions and Actions Without An Owner are only trustworthy if someone recounts them against the rows rather than trusting whatever number was there last meeting — the two signatures on the record should mean two people looked, not two people who both assumed the other did.
What auditors find
Most common meeting and action log findings
These are the failures that show up when a meeting and action log is audited months after it was kept, not the day it was filled in.
| Finding | Clause | What fixes it |
|---|---|---|
| Actions logged with no due date, treated as open-ended | ISO 9001 cl.9.3.3 | Make Due Date a hard requirement at entry; an action without a date is a discussion note, not an action. |
| A carried-over action re-entered as a new row instead of updated in place | ISO 9001 cl.7.5.3 | Require Carried Over From A Previous Meeting to reference the prior row rather than duplicate it, so age is traceable. |
| Category left blank across most rows, so recurring themes are invisible | ISO 9001 cl.9.1.3 | Make Category mandatory and review the distribution at the meeting that owns the log, not just individual rows. |
| Status shown as In progress on an action overdue by months | ISO 9001 cl.10.2.1 | Tie Days Overdue to an automatic flag that forces a status decision — close, escalate, or reassign — past a set threshold. |
| Raised To A CAPA marked Yes with no CAPA ID entered against it | ISO 9001 cl.10.2.1 | Block sign-off while a Yes on Raised To A CAPA has an empty CAPA ID field; the link has to exist before the row is signed. |
| Chair and area manager sign the record before recounting open and overdue totals | ISO 9001 cl.7.5.2 | Sequence the Log health counts before both signature fields so signing implies the counts were actually checked. |
Case in point
Case in point: the action nobody could find
A recurring blockage in a chill store drain was raised at three consecutive tier meetings. Each time it was logged as a fresh action against a new owner, because nobody linked it back to the previous entry — the Carried Over From A Previous Meeting field was left on No each time, so the log showed three unrelated one-off issues rather than one unresolved problem escalating.
It took a customer complaint about product held too long in the chill store, and a manual search back through six months of minutes, to establish the drain had been raised and dropped repeatedly. Had the field been used as intended, Actions Carried Over Three Times would have flagged it after the second meeting, well before the complaint.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
3 sections
- Reference
- OPS-017
- Archetype
- Log
- Record ID
- MTG-2026-000
- Scoring
- Actions closed
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.9.3
- Links
- Links Tier Board Review and CAPA
- Tags
- Daily management, Actions
- Sections
- 3
- Fields
- 34
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 2
Header
8 fieldsLog ID*
Auto sequence. Format MTG-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Meeting Series*
Meeting Date*
Chair*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Discussed Monthly Because Never Written Down
An action agreed verbally has no owner and no date, so it is agreed again next month. Two lines written at the time removes an entire recurring agenda item.
Actions
Repeats12 fieldsAction*
Owner*
Due Date*
Raised By
Priority*
- High0 pts
- Medium1 pt
- Low3 pts
Category
Status*
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Closed Date
Days Overdue
Raised To A CAPA
Where the action needs verification that it worked, it belongs in the CAPA engine rather than here.
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
CAPA ID
Links to FDN-014 CAPA ID
Carried Over From A Previous Meeting*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Log health
14 fieldsOpen Actions*
Overdue Actions*
Closed Since Last Meeting*
Actions Without An Owner*
Actions Carried Over Three Times*
Feeds Tier Board Review*
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Chair*
Signature*
Area Manager*
Second Signature*
OPS-017 · record IDs look like MTG-2026-000 · Links Tier Board Review and CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping the log current, chasing owners before items go overdue, and holding the CAPA links together is the work that actually slips.
Holds the meeting and action log against every registered meeting series, flags actions approaching their due date, and keeps the CAPA and Tier Board Review links intact.
Watches for actions tagged Quality that keep recurring across meetings and surfaces them as a pattern rather than a series of unrelated one-off entries.
Checks that any action marked Raised To A CAPA carries a live CAPA ID, so the audit trail from decision to verified closure never breaks.
Rolls open, overdue and unowned counts across every meeting series into one view, and holds every write for your approval before it touches a record.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Meeting and Action Log definitions and key terms
- Meeting series
- A recurring operational meeting with a stable membership and cadence — a tier board, a safety committee — that keeps one continuous action log rather than a new sheet per session.
- Action owner
- The named individual accountable for delivering a specific action by its due date; distinct from whoever raised the action or chairs the meeting.
- Carried-over action
- An action still open at a subsequent meeting of the same series, tracked as the same row rather than re-entered, so its true age is visible.
- CAPA (Corrective and Preventive Action)
- A separate register for actions responding to a nonconformity, where the fix must be verified as effective after closure rather than simply marked done.
- Log health
- The section of the record that summarises the state of the whole log — open, overdue, closed-since-last-meeting and unowned counts — rather than any single action.
FAQ
Frequently asked questions about meeting and action log
What is the meeting and action log template based on?+
It is built against ISO 9001 cl.9.3, which requires management review to produce decisions and actions rather than just a discussion. The log is the record of those outputs.
What sections does the meeting and action log contain?+
There are 3 sections: Header, Actions and Log health. Together they hold 34 fields, 24 of which are required, with the Actions section repeating once per action raised.
How many meeting and action log records should we have?+
This is a singleton per meeting series — one continuous log set up once and maintained, rather than a fresh record for every session of the same meeting.
Which programme does the meeting and action log belong to?+
It is part of the Daily Management System programme, alongside Tier Board Review and Gemba Walk Record, which together produce actions with owners and dates that survive the board being wiped.
How is a meeting and action log scored?+
Scoring is actions closed, where high is good. Priority and status carry weighted scores so a log full of open, high-priority, long-overdue actions scores worse than one that closes items promptly.
When does an action belong in a CAPA record instead of this log?+
Once the action responds to a nonconformity and its effectiveness needs to be verified after it is done, it should be raised to CAPA and referenced back using the CAPA ID field, rather than tracked indefinitely as an ordinary log row.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Daily Management System
Audit Finding Record
Records a single audit finding with its evidence, clause reference and classification
Daily Production Report
Summarises the day across lines: output, attainment, losses, quality and the issues carried forward
Tier Board Review
Runs the daily management meeting against a fixed agenda and records what was agreed and by whom
Gemba Walk Record
Records a structured walk of the process by a manager, what was observed and what was raised
Layered Process Audit
Checks that a small number of critical process steps are being done as specified, by different levels of management on different frequencies
Daily Priority Plan
Sets the small number of things that must happen today and who owns each
More in Daily Management
Tier Board Review
Runs the daily management meeting against a fixed agenda and records what was agreed and by whom
Gemba Walk Record
Records a structured walk of the process by a manager, what was observed and what was raised
Layered Process Audit
Checks that a small number of critical process steps are being done as specified, by different levels of management on different frequencies
Daily Priority Plan
Sets the small number of things that must happen today and who owns each
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 cl.9.3 — Management review
- ISO 9001:2015 cl.10.2 — Nonconformity and corrective action
- ISO 9001:2015 cl.7.5 — Documented information
- ISO 9001:2015 cl.5.3 — Organizational roles, responsibilities and authorities
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.