Action Log Template: Free UK Excel & Word + Example

An action log is a single shared list of the actions a team has agreed to do — usually arising from meetings — each with one owner and one due date, tracked through to completion. It is the difference between a promise made in a meeting and a promise that actually gets done. You can download a free, editable UK template in Excel and Word below, with a worked example filled in. No email address required.

Key takeaways

  • An action log records every agreed action in one place, with an owner, a due date, and a status — so nothing agreed in a meeting quietly disappears.
  • The discipline that makes it work: one owner and one due date per action, and a review at the top of every meeting.
  • It differs from a personal to-do list by being shared, owned and tracked. A shared action log beats a dozen forgotten verbal promises.
  • The standard columns are: action ID, description, raised date and source, owner, due date, status, and notes.
  • Download the free Excel and Word template below — blank, plus a filled UK small-business example. The Excel version has a status dropdown that colours itself and highlights overdue actions.

What is an action log?

An action log — sometimes called an action tracker or action item list — is a shared record of the tasks a team has committed to. Each row is one action: a short description of what needs doing, who owns it, when it is due, and where it stands. Most actions arrive out of meetings, but they also come from phone calls, emails, and corridor conversations. The log gathers them in one place so you are not hunting through six sets of minutes to remember who promised what.

Its real job is closure. Anyone can write a task down; the point of a log is that someone is named against it, a date is set, and the action is chased until it is done. For an established owner-manager juggling a build, a supplier, and a small team, that single shared list is often the difference between a project that drifts and one that lands.

A note on jargon: the owner is the one person accountable for an action — not necessarily the person who does every part of it, but the one who answers for it. The status is where the action stands: Open, In progress, or Done. We define the rest as we go.

What goes in an action log? The columns explained

A good action log is deliberately short. Seven columns carry everything you need; adding more usually means more to keep up to date and less that anyone actually fills in. Here is each column and what it holds.

The columns of an action logAction IDA unique reference, e.g. A01, A02Action descriptionStart with a verb: “Book the photographer”Raised date & sourceWhen, and which meeting it came fromOwnerOne named person — never a teamDue dateOne date — when it must be closedStatusOpen / In progress / DoneNotes / updateThe running history: what has happened, what is still outstanding, when you last chased

  1. Action ID. A short unique reference (A01, A02, and so on) so you can point to “A04” in a meeting instead of reading out the whole description.
  2. Action description. What needs doing, started with a verb — “Approve the homepage copy” rather than “homepage”. A verb keeps it a task, not a topic.
  3. Raised date and source. When the action was agreed, and where it came from — which meeting, email, or call. This lets you filter a meeting’s actions before the next one.
  4. Owner. One named person. Not “marketing”, not “the team” — a name. Shared ownership is the most common reason actions stall.
  5. Due date. One date by which the action must be closed. One owner, one date, per action: that is the whole discipline.
  6. Status. Where it stands — Open, In progress, or Done. Three values are usually enough; more states mean more debate about which one applies.
  7. Notes / update. A running history of progress and chases. Useful for a long-running action so you can see how many times you have followed up, and why it still is not closed.

How does an action move from open to done?

Every action follows the same short life. It is raised and recorded as Open, moves to In progress once someone starts work, and is marked Done when it is finished. The one state that is not a column but matters most is overdue: an action past its due date that is not yet Done. Those are the rows to chase.

The life of an actionOpenRaised & recordedIn progressOwner is working on itDoneClosedOverdue: past its due date and not yet DoneNot a status of its own — a flag that says “chase this now”

In the Excel template below, the status dropdown colours itself — grey for Open, amber for In progress, green for Done — and any due date that has passed without the action being Done turns red on its own. You see the state of the whole log at a glance, without reading a single date.

Action log vs to-do list vs RAID log: which do you need?

Three tools get confused here, and choosing the wrong one is why some teams drown in spreadsheets while others lose track of everything. The short version: a to-do list is personal, an action log is shared, and a RAID log is for the bigger things that threaten the project. Here is how they compare.

ToolWhat it tracksShared?When it fits
To-do listYour own tasksNo — personalOnly you, nobody waiting on you
Action logAgreed actions, with an owner and due dateYesA team or project where people owe each other tasks
RAID logRisks, Assumptions, Issues, DependenciesYesA project big enough to need formal risk tracking

The decision is a quick one. If no one else is waiting on the work, a to-do list is enough — do not build a shared log for yourself alone. The moment other people owe you tasks, or you owe them, you need an action log so the promises are written down and visible. And once a project is large enough that you are tracking risks (things that might go wrong), assumptions (things you are taking on trust), issues (things already going wrong), and dependencies (things waiting on other things), those belong in a RAID log — a single register named for those four words. The action log and the RAID log sit side by side: an issue in the RAID log often generates an action in the action log. We cover the RAID log in its own RAID log template, and because most actions come out of meetings, our meeting minutes and agenda template feeds straight into the log. The difference is one of scope: your minutes record what happened in a single meeting, while the action log is the standing list that carries every open action across all of them until it is closed.

A filled example: a UK small business

Most action-log examples online are either empty or years out of date. Here is a current one for a realistic UK situation: a small homeware shop, Wren & Willow (an illustrative example, not a real firm), relaunching its tired website as a proper online shop. These are the kind of actions that come out of a kick-off meeting, with two deliberately left to run overdue so you can see how the log flags them.

IDActionOwnerDueStatus
A01Book the product photographer for the new rangeAnna20 Jun 2026Open
A02Test card and Apple Pay on the staging siteRavi5 Jul 2026In progress
A03Approve the homepage copyAnna28 Jun 2026Done
A04Send the agency the product spreadsheetRavi10 Jun 2026Open
A05Confirm delivery lead times for stock syncRavi9 Jun 2026In progress
A06Draft the staff training plan for launchAnna18 Jul 2026Open

Read it the way Ravi’s manager would. A03 is closed and can be ignored. A02 is moving. But A04 and A05 are both past their due date and not Done — the red dates — so they are the two to raise first at the next meeting. That is an action log doing its job: not merely holding the list, but pointing straight at what has slipped. The full version, with the raised date, source and notes columns, is in the download.

Do you even need an action log? A two-minute decision

Not every job needs one. For a cost-conscious founder, the honest question is whether anyone other than you is relying on these tasks. If the answer is no, a personal list is enough and a shared log is only overhead. The moment the answer is yes, the maths flips: a shared action log beats a dozen forgotten verbal promises, and it costs nothing but the few minutes it takes to keep current.

Use a log when actions come out of recurring meetings, when more than one person owes tasks, or when you find yourself chasing the same thing twice because nobody wrote it down. Skip it when the work is yours alone and short-lived. The template below scales down comfortably — even six rows in a shared spreadsheet, reviewed at the top of each meeting, will catch most of what would otherwise slip.

How do you keep an action log working?

  1. One owner, one due date, per action. If two people own it, neither does. If there is no date, it is a wish, not an action.
  2. Review it at the top of every meeting. Not the end, when people are leaving — the top, when they are paying attention. Run down the open actions first.
  3. Capture actions as they are agreed. Write the action into the log during the meeting, not from memory afterwards. Read it back so the owner hears what they have taken on.
  4. Chase the overdue ones. Most people need reminding of what they said they would do. The notes column is where you record each chase, so a stuck action’s history is visible.
  5. Close actions cleanly, and spin off new ones. Mark Done when it is genuinely finished. If completing one action reveals another — “approve copy” leads to “publish copy” — log the new one as its own row.
  6. Keep it short. Resist adding columns you will not maintain. A log people actually update beats a richer one they abandon.

The action log is not your project schedule. Big, deliverable-sized work belongs in the schedule; the log is for the everyday tasks that come out of conversations — the follow-ups, the chases, the small things that, left unwritten, are exactly what slips.

Download the free UK action log template

Free, editable, no email required. Each file includes a blank action log and the filled Wren & Willow example above, so you can see exactly how it is used.

  • Excel template (.xlsx) — with a status dropdown (Open / In progress / Done) that colours itself, and overdue due dates that turn red on their own. Download Excel version
  • Word template (.docx) — the same columns as a clean table, for those who prefer to keep it in a document. Download Word version

UK English, designed for small businesses. Made by a practitioner, not a software vendor — there is nothing to sign up for.

Once the project is running, you will want to report on it too. Our project status report template rolls the open actions, risks and progress into a one-page update for whoever is paying for the work.

Frequently asked questions

What is an action log?

An action log is a single shared list of the actions a team has agreed to do, usually arising from meetings, each with one owner and one due date, tracked through to completion. It keeps every agreed action in one place so nothing slips between sets of minutes.

What is in an action log?

The standard columns are: an action ID, the action description, the raised date and source (which meeting it came from), the owner, the due date, the status (Open, In progress or Done), and a notes or update column for progress. Keep it to those; extra columns usually go unmaintained.

What is the difference between an action log and a to-do list?

A to-do list is personal and private — your own tasks, in any order. An action log is shared, and every action has a named owner and a due date that others can see. The action log exists precisely so that promises between people are written down and tracked, which a private list cannot do.

What is the difference between an action log and a RAID log?

An action log tracks agreed tasks to closure. A RAID log tracks Risks, Assumptions, Issues and Dependencies — the bigger things that threaten a project. They work together: an issue logged in the RAID log often produces an action, which goes in the action log. Small teams may only need the action log; larger projects use both.

Who owns the actions in an action log?

Each action has one named owner — a single person accountable for it, even if others help. The project manager or whoever runs the log owns the log itself: keeping it current, chasing overdue actions, and reviewing it at each meeting. Avoid assigning an action to a team or a department; ambiguous ownership is the main reason actions stall.

How do you track overdue actions?

Compare each action’s due date with today’s date: any action past its due date that is not yet Done is overdue. In the Excel template, those due dates turn red automatically, so the overdue actions stand out without checking each one. Review them at the top of every meeting and record each chase in the notes column.

This article is general guidance on project documentation, not formal project-management certification material. The Wren & Willow example is illustrative — the business, people and figures are fictional. Adapt the template to your own organisation’s needs. Updated 14 June 2026.



Leave a Comment