Skip to content

Practical guide · 5S and visual management

Rolling action item list (RAIL): the columns, the weekly review and a worked example

Short answer

A rolling action item list (RAIL) is one running list of actions that a team keeps from meeting to meeting, so that nothing agreed in a huddle or review is lost between sessions. Each row has one owner, a due date and a status, and it stays on the list until it is done or dropped with a reason.

RAIL stands for rolling action item list. One source we read spells it rolling action item log, and the idea is the same. The list rolls because open items carry forward to the next meeting instead of being rewritten in each set of minutes. The minimum is who does what by when. Most teams add a status, a last update and the date closed. Reviewed on a fixed schedule, with the late and the stuck items first, it is the simplest way to see whether a team finishes what it agrees to do.

Last reviewed:

What is a rolling action item list?

A rolling action item list is a single list for a series of meetings. The daily huddle, the weekly project review and the tier meeting each add rows. Rows stay until they are finished. A team that reads one list every week can see at a glance what is open, who has it and what is late.

The sources agree on the core and differ on the edges. The Lean Six Sigma Definition glossary describes a shared, continuously updated tracker with the action, an owner, a due date, a status and comments. A project management blog from 2018 calls it a rolling action item log and uses it for items that turn up after a project has started, including a parking lot for items that are not urgent. A Quality Digest article describes it as a list of tasks the team has decided should be done, and says it is not a project schedule, a list of personal goals or a project pipeline. We could not read where the term first came from, so this page does not say.

The wording differs, so decide your own. In this guide a RAIL holds only agreed actions. A topic nobody has taken on stays on the agenda.

The columns of a RAIL

Every source we read has the action, the owner, the due date and a status. The rest is our choice, and each extra column is one more thing to keep up. Start with these nine.

Columns of a rolling action item list
ColumnWhat goes in itWhy it is there
No.A short number such as R-07A row can be named in a meeting and found again.
OpenedThe date it was agreedAge is counted from it.
SourceHuddle, tier meeting, audit, gemba walk, incident, customerShows which meetings produce actions and which produce late ones.
ActionA verb and an object: replace the guard latchA row that starts with a verb can be finished.
OwnerOne nameTwo names is no owner.
DueA real dateA row with no date cannot be late.
StatusOpen, Blocked, Done or DroppedBlocked rows get their own question in the review.
Last updateOne lineShows a row nobody has touched.
ClosedThe date it was doneDays to close and done on time are counted from it.

The columns beyond action, owner, due date and status are our defaults, not a standard. The [free RAIL template](/templates/rolling-action-item-list-template) has all nine.

The weekly review: ten minutes, in this order

A RAIL that nobody reviews is a list of old intentions. A weekly review works for most teams. A daily huddle that owns its own list looks at it daily. One person keeps the list and leads the review.

  1. 1

    Read out what is done

    Say what was finished since last time. It takes a minute and it is the reason people keep the list honest.

  2. 2

    Take the past-due items

    The owner gives a new date and says what got in the way. If the date has moved before, ask what is different this time.

  3. 3

    Take the blocked items

    Name who can remove the block and by when. A blocked row with no named person stays blocked.

  4. 4

    Check the quiet ones

    An item with no update for two reviews is re-confirmed with its owner or re-scoped.

  5. 5

    Add the new items

    One owner, a verb, a date. If nobody takes it on, it is not an action.

  6. 6

    Clear the old rows

    Drop what the team will not do and write why. Remove done rows after about a month.

Ageing and closing rules

Age is the number of days since an item was opened. For an open item, count to the review date. For a done item, count to the date it was closed. Days late is the days past the due date. Both are simple to work out and they show where a list is stuck, which a count of open rows does not.

Rules are a choice the team makes, not a standard. The GoTranscript blog publishes one set: an item overdue by 7 days gets a new date and a named blocker, an item blocked for two meetings goes to the meeting leader, and an item with no update for two meetings has its owner reconfirmed. They are a reasonable start. Pick your own numbers, write them at the top of the sheet and use them for a few months before changing them.

  • Done means the action was carried out. If it needs proof that the fix worked, that belongs in a CAPA, not on the RAIL.
  • Dropped needs a reason on the row. A list with silent deletions cannot be trusted.
  • A date that has moved three times is a signal about the scope or the owner, not a reason for a fourth date.

A worked example (illustrative)

Illustrative: a made-up packaging line reviews its RAIL on Thursday 5 November 2026. The list has 10 items. Three are done and seven are open.

The open items on 5 November 2026 (illustrative)
No.ActionDueAge in daysDays late
R-03Get a quote for a second label printer (blocked)20 Oct2316
R-05Write the stop-and-clear step for the film jam3 Nov162
R-06Trial a second kanban card for tape5 Nov140
R-07Retrain two operators on the changeover check sheet12 Nov90
R-08Send the customer the corrective action reply19 Nov70
R-09Fix the leaking air line at station 49 Nov30
R-10Confirm the overtime plan for the week of 16 Nov10 Nov20

Age is 5 November minus the date opened. R-03 was opened on 13 October: 18 days left in October plus 5 is 23.

The seven ages add up to 23 + 16 + 14 + 9 + 7 + 3 + 2 = 74 days, so the average age of an open item is 74 / 7 = 10.6 days. Two of the seven are past due, which is 2 of 7. By age band the open items split as 0 to 7 days: 3, 8 to 14 days: 2, 15 to 21 days: 1, over 21 days: 1, and 3 + 2 + 1 + 1 = 7.

The three done items took 6, 19 and 14 days to close. They add up to 6 + 19 + 14 = 39 days, so the average is 39 / 3 = 13 days. Two of the three were done by their due date, which is 2 / 3 = 66.7 percent. R-02 closed on 27 October against a due date of 22 October, 5 days late.

The review does not need to read all ten rows. It spends its time on R-03, the oldest and the most overdue, where the question is who can chase the supplier and by when, and on R-05, where the draft is written but not yet tried. Both leave with a new date and one name.

RAIL vs meeting minutes, a tier board, a CAPA log and a kaizen list

A RAIL overlaps with four things teams already have. Each one has an owner page, and the RAIL should point to it rather than copy it.

Which list holds what
RecordWhat it holdsHow the RAIL relatesOwner page
Meeting minutesWhat one meeting discussed and decidedMinutes are one meeting. The RAIL is cumulative across the series. Minutes carry a short list of what is open and point to it.Safety committee minutes template
Tier boardMetrics against target and the escalations between tiersThe board shows what is off target. The RAIL holds the actions that follow, and an item the team cannot close is escalated to the next tier.Tiered meetings and the tier 2 meeting agenda
CAPA logCorrective and preventive actions with a root cause and an effectiveness checkA CAPA is bigger than a row. Put it in the CAPA log and carry one RAIL row that points to it.CAPA guide and CAPA log template
Kaizen listImprovement ideas, most of which have not been agreedAn idea becomes a RAIL row when someone agrees to do it and picks a date.Kaizen ideas and kaizen guide

Common RAIL mistakes

  • A wish list. Rows nobody has agreed to do. Keep topics on the agenda and only agreed actions on the list.
  • No date. A row without a due date never shows as late.
  • Two owners on a row. Each assumes the other has it. Give it to one person and name the helper in the update.
  • Never closing. A list with 80 open rows is not read. Drop or close, and clear done rows after a month.
  • Too many columns. Every extra column is one more thing to keep up. Start with the nine above or fewer.
  • No keeper. If everyone can edit and nobody owns it, it decays. One person keeps it and leads the review.
  • Skipping the review. The list only works if it is read out loud on a fixed schedule.

RAIL template

The rolling action item list template has a blank list, a weekly review sheet that counts the open items by age, and the worked example above, as a PDF and as an Excel file. In Excel, age, days late and a flag are worked out from the review date for every row.

Tiered Meetings

Run your daily actions in LeanSuite

each huddle enters its KPIs, assigns actions and escalates problems on one live screen, from the shift huddle to the plant review.

See Tiered Meetings

Go deeper

This page is the short version. These guides cover each part in full.

All our articles on this subject are in the 5s and visual management topic.

Free templates and tools

Key terms

Lean glossary

Doing this in LeanSuite

See it on your own lines

Bring the problem you are working on to a 45-minute demo. Or look around with sample data first, or pilot LeanSuite on your own lines for 90 days, with the setup done by our team.

Book a 45-minute demoClick through the interactive demoStart a 90-day pilot

FAQ

Questions about rolling action item list (RAIL)

  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.

  2. It tracks agreed actions across a series of meetings, so a team can see what is open, who owns it and what is late. It is used in huddles, tier meetings, project reviews and improvement teams.

  3. Minutes record what one meeting discussed and decided. A RAIL is cumulative and holds every open action from the whole series. Minutes can carry a short list of open items and point to the RAIL.

  4. At least the action, one owner, a due date and a status. Most teams add the date opened, the source, a last update and the date closed, so that age and done-on-time can be worked out.

  5. At every meeting in the series: daily for a daily huddle, weekly for most teams. Take the done items first, then the past-due and blocked ones, then add the new ones.

  6. No. A CAPA has a root cause, corrective and preventive actions and an effectiveness check. The RAIL holds smaller agreed actions and can carry one row that points to a CAPA.

Related guides and tools

More method guides

Or browse the topics, the full library and the lean glossary.

Rather see it on your own problem?

Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

Schedule Demo

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.