Meeting action log template

Capture the action before the meeting closes

Write the action while the decision is still fresh. Begin with a verb and describe the result another reader should be able to recognise: “Issue the approved access list to the venue” is clearer than “Access list”. Confirm the owner and due date aloud. If the group has not agreed either one, record “owner to confirm” or “date to confirm” and make resolving that gap an action in its own right; do not invent certainty after the meeting.

Give every row a stable action ID so people can refer to it without copying the whole sentence. Use a small, agreed set of statuses such as Open, In progress, Blocked and Complete. A blocked action should name the dependency or decision needed. Completion should mean that the promised outcome exists and can be checked, rather than that somebody has sent a chasing message.

Review one live list

Keep the log where the project team already expects controlled working information to sit. The meeting record can link to it, but avoid keeping separate copies in minutes, email and personal notes. Before the next meeting, ask owners for concise updates and update the same row. During the meeting, review overdue and blocked items first, confirm any changed dates, then close completed actions with a short evidence note. Retain old rows according to the organisation’s own information and retention rules rather than deleting history casually.

Fictional worked example

Imagine the fictional North Quay mobilisation team agrees that Mina will confirm workshop access requirements by 11 September. The action is recorded as ACT-001 with the meeting date, Mina as owner, the due date and an evidence reference to section 3 of the workshop brief. The next morning Mina learns that the venue’s security contact is unavailable. She changes the status to Blocked and records the dependency. At review, the team assigns a route to resolve it; once the confirmed requirements are filed, Mina marks the action Complete and adds the file reference.

The log means a colleague can see what was agreed, who owns the outcome, what changed and what evidence supports closure without reconstructing the story from messages.

Keep the fields proportionate

Start with the supplied columns and remove any that nobody will maintain. A small internal meeting may need only ID, action, owner, date and status. A regulated or contract-heavy project may need a workstream, decision reference or formal approval field defined by its own controls. The log supports follow-through; it does not replace the meeting record, risk register, decision log or document repository.

Source note

The government project-delivery standard GovS 002 covers reporting on progress, risks, issues and decisions. It applies to government bodies; this template is our practical starting point for other teams. APM also describes reporting and document control as PMO services.