Skip to content

Free template

Updated

Rolling action item list (RAIL) template

A rolling action item list (RAIL) is one running list of actions that a team keeps from meeting to meeting, so that nothing agreed at a huddle or review is lost between sessions. Each row has an owner, a due date and a status, and a row stays on the list until it is done or dropped with a reason. This template has the blank list, a weekly review sheet that counts the open items by age, and a worked example. The Excel file works out age, days late and a flag for each row and summarizes the list.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the rolling action item list templateA landscape table with columns for number, opened, source, action, owner, due, status, last update and closed, and a key for Open, Blocked, Done and Dropped.
Blank list with 14 rowsOwner, due date, status, last updateWeekly review sheetAge bands for open itemsDone-on-time and days to closeWorked example with the sums
Filled-in Rolling action item list (RAIL) template: ten actions, three done, two of the open ones past due
The same sheet filled in with the worked example (page 3 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use a rolling action item list

  • For any meeting that repeats and produces actions: a daily huddle, a tier meeting, a weekly project review or a kaizen team check-in.
  • When actions are being lost in meeting minutes and the same item is discussed three weeks running.
  • To bring the actions from several places (huddle, audit, gemba walk) into one list that one person keeps.
  • As the weekly ten minutes in which a team looks at the late and stuck items before taking on new ones.
  • Not as a project schedule, a to-do list for one person or a CAPA record. A corrective or preventive action with root cause and effectiveness check belongs in the CAPA log.

How to fill it in

  1. 1

    Name the list and its keeper

    One list per meeting series, with one person who keeps it. Write the team, the keeper and the review date at the top.
  2. 2

    Add an action only when someone takes it

    Write it as a verb and an object, put one name in the owner column and a real date in Due. If nobody takes it on, it is a topic, not an action.
  3. 3

    Record where it came from

    Huddle, tier meeting, audit, gemba walk, incident or customer. The Source column shows later which meetings produce the most actions and which produce the late ones.
  4. 4

    Review it at a fixed time

    Daily for a daily huddle, weekly for most teams. Read the done items out, then the past-due ones, then the blocked ones, then add the new ones.
  5. 5

    Ask for a new date and a reason

    An owner of a past-due item gives a new date and says what got in the way. A blocked item names who can remove the block.
  6. 6

    Close with a date, drop with a reason

    Write the date closed in the Closed column. If the team decides not to do an action, mark it Dropped and write why on the row.

The columns

What each column of the list is for

Five sources we read name the same core: the action, an owner, a due date and a status. We add the rest. All of it is a choice, not a standard.

  • No.

    What goes in it
    A short number such as R-07
    Why it is there
    So a row can be named in a meeting and found again.
  • Opened

    What goes in it
    The date the action was agreed
    Why it is there
    Age is counted from it.
  • Source

    What goes in it
    Huddle, tier meeting, audit, gemba walk, incident, customer
    Why it is there
    Shows where actions come from.
  • Action

    What goes in it
    A verb and an object
    Why it is there
    A row that starts with a verb can be finished.
  • Owner

    What goes in it
    One name
    Why it is there
    Two names means no owner.
  • Due

    What goes in it
    A real date
    Why it is there
    A row with no date cannot be late.
  • Status

    What goes in it
    Open, Blocked, Done or Dropped
    Why it is there
    Blocked rows get their own question in the review.
  • Last update

    What goes in it
    One line
    Why it is there
    Shows a row nobody has touched.
  • Closed

    What goes in it
    The date it was done
    Why it is there
    Time to close and done-on-time are counted from it.

A filled-in example

Illustrative, not a benchmark

An example (illustrative): a made-up packaging line reviews its list on Thursday 5 November 2026. The list has 10 items.

  • 3 are done and 7 are open. Of the open ones, 2 are past their due date: R-03 (due 20 October, 16 days late, blocked on a supplier quote) and R-05 (due 3 November, 2 days late).
  • Age of an open item is the review date minus the date opened. The seven open items are 23, 16, 14, 9, 7, 3 and 2 days old. They add to 74 days, and 74 ÷ 7 = 10.6 days.
  • The three done items took 6, 19 and 14 days to close. They add to 39 days, and 39 ÷ 3 = 13 days. Two of the three were done by their due date: 2 ÷ 3 = 66.7%.
  • By age, the open items fall into 3 at 0 to 7 days, 2 at 8 to 14 days, 1 at 15 to 21 days and 1 over 21 days: 3 + 2 + 1 + 1 = 7.
  • The review spends its ten minutes on R-03 and R-05: who can chase the quote, and a new date for the film jam instruction.

One page shows the whole backlog, the two late items and the oldest one, and each has an owner and a next date.

Common mistakes

  • Using it as a wish list

    A row that nobody has agreed to do is a topic. Keep topics on the agenda and only agreed actions on the list.

  • No date, or the same date moved again and again

    A row without a due date never shows as late. A row whose date moves three times needs its owner, scope or blocker looked at, not a fourth date.

  • Two owners on a row

    When two people own it, each assumes the other is doing it. Give one person the row and name the helper in the update.

  • Never closing rows

    A list with 80 open rows is not read. Close done rows, drop the ones the team will not do with a reason, and clear closed rows after a month.

  • Mixing in work that needs more than a row

    A customer corrective action needs a root cause and an effectiveness check. Put it in the CAPA log and carry one row on the RAIL that points to it.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

LeanSuite runs digital daily management and tiered meetings on Lean Studio boards: each huddle enters its KPIs, assigns actions and escalates problems on one live screen, from the shift huddle to the plant review.

See it in a 45-minute demo

FAQ

Rolling action item list (RAIL) template: common questions

  1. Most pages we read say rolling action item list. One says rolling action item log. The idea is the same: a single running list of actions that carries from one meeting to the next. This template uses list.

  2. Minutes record what one meeting discussed and decided. A RAIL is cumulative: it holds every open action from every meeting in the series and shows its status. Minutes can carry a short list of what is open and point to the RAIL.

  3. At every meeting of the series. A daily huddle looks at it daily, a weekly project meeting weekly. The review should be short: done items, past-due items, blocked items, then new ones.

  4. When it is done, with the date written in, or when the team drops it, with the reason written on the row. Keeping done rows for a month lets the team see what was finished before they are cleared.

  5. No. A CAPA needs a root cause and an effectiveness check, and a kaizen list holds ideas that have not been agreed as actions. The RAIL holds agreed actions with an owner and a date, and can carry a row that points to a CAPA or a kaizen.

More free templates

All templates
Browse all 260 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.