Template Library
Gemba Walk Checklist Template
An Excel workbook for pre-walk prep, on-floor observation, follow-up action tracking, and a live dashboard, so a Gemba walk turns into a repeatable, measurable habit instead of an occasional stroll.
The Pre-Walk Prep tab sets a focus, a comparison standard, and now the shift, walk type, and who else was present before you head to the floor. The Observation Checklist and Follow-Up Actions tabs are real Excel Tables spanning every walk, with automatic item numbering and a Days Overdue formula so nothing observed gets lost once the walk ends. The Dashboard rolls all of it up into live counts and charts — concern-level distribution, open versus closed follow-ups, and how many items are overdue — with zero manual tallying.
What Is Included in the Workbook
| Sheet | Purpose | What Teams Capture |
|---|---|---|
| How-To | Method guidance and orientation | How to prep, observe, follow up, and read the dashboard |
| Pre-Walk Prep | Pre-walk planning fields | Walker name, date, shift/time, area, walk type, team members present, focus question, and the standard to compare against |
| Observation Checklist | On-floor observation log (Excel Table) | Time, area or station, what was observed, whether it matched the standard, concern level, and any immediate action taken |
| Follow-Up Actions | Running action tracker across all walks (Excel Table) | Numbered items, priority, owner, due date, status, and an automatically calculated Days Overdue |
| Dashboard | Live rollup and charts | Total observations, high/critical concerns, open and overdue follow-ups, concern-level distribution, and follow-up status breakdown |
Key Features Inside the Template
Focus Question Before the Walk
Forces a single, specific question to observe for, rather than a vague intent to "check on the floor."
Live Dashboard With Charts
Concern-level distribution and follow-up status update automatically as you log walks — no separate reporting spreadsheet needed.
Automatic Days-Overdue Tracking
Every open follow-up item calculates how many days overdue it is on its own, so nothing slips through by simply not being looked at.
One Running Action Log
A single Follow-Up Actions table spans every walk, so recurring issues become visible over time instead of scattered across separate sheets.
Best Use Cases
- A shift supervisor's daily floor walk
- A plant manager's weekly cross-area walk
- Leadership training on structured go-and-see practice
- Auditing whether documented standards match actual practice
How to Use the Template Effectively
- Set one focus area or question before each walk, not a general intent to "look around."
- Observe a full work cycle before asking questions or filling in the checklist.
- Compare what's observed to the documented standard, and question the standard too if it's outdated.
- Log follow-up items rather than fixing everything during the walk itself.
- Review the Follow-Up Actions tab regularly and close the loop with the team.
Who Should Use This Template
- Shift supervisors and plant managers building a regular walk habit
- Quality and CI leaders auditing standard-versus-practice gaps
- Trainers coaching new leaders on structured observation
Common Mistakes to Avoid
- Turning the walk into a compliance inspection instead of an observation practice
- Fixing every issue on the spot instead of logging it for proper follow-up
- Letting the Follow-Up Actions tab go unreviewed, so walks stop producing visible change
Related Guides and Tools
Read the Gemba Walk Guide
The go-and-see principle and full six-step walk structure this template is built around.
Read the Leadership Principles Guide
Gemba walks are one concrete practice within a broader set of Lean leadership behaviors.
Read the Standard Work Guide
A Gemba walk is most useful when there's a documented standard to compare actual practice against.
Gemba Walk Checklist Template Frequently Asked Questions
Should I fill out a new sheet for every walk?
Duplicate the Pre-Walk Prep and Observation Checklist tabs for each new walk, and keep a single running Follow-Up Actions tab across all walks so nothing gets lost between them.
What if I don't find anything to note on a walk?
Record that too. A walk with no observations is still worth logging with a date and confirmation that things matched the standard, rather than leaving a gap that looks like the walk was skipped.