This free gemba walk checklist is for managers, team leaders and continuous improvement leads who go and see how work is done, in a factory, a warehouse, an office, a laboratory or a hospital. One run is one walk through one area or process. The walk leader sets the purpose, the theme and the route, tells the area what the walk is for and checks the safety rules. On the walk, the walkers watch the work at each stop, compare it with the standard work, follow the flow, look for waste and check safety, quality and visual management, then ask the people doing the work open questions and record what they see and hear without fixing it on the spot. The debrief picks the few things that matter, the area owner agrees the follow-up actions and owners, and the checklist follows each action through and sets the next walk.
A gemba walk is a way of learning. The Lean Enterprise Institute defines it as “a management practice for grasping the current situation through direct observation and inquiry before taking action,” and explains that gemba is the Japanese term for “actual place”: the shop floor, or anywhere value-creating work happens. This checklist runs one walk, from its purpose to the follow-up actions and the date of the next walk.
A walk sits beside processes that inspect, score or change an area without replacing them. A safety inspection checks an area against its safety standards, in the Warehouse Safety Inspection Checklist or the Safety Inspection Process for a Manufacturing Facility; a gemba walk looks at safety as part of the work and stops only for a serious hazard. The Continuous Improvement Cycle Process Checklist runs a plan, do, check, act cycle, which the actions from a walk often feed.
Asks: how is the work really done here, and what gets in the way of the people doing it?
When: regularly, led by managers, team leaders or improvement leads, in a factory, a warehouse, an office, a laboratory or a ward.
Output: observations recorded as facts, what people said, two to five actions the area owner agrees, and the date of the next walk.
Asks: how well does this area keep Sort, Set in Order, Shine, Standardise and Sustain?
When: on a schedule, in the 5S Audit Checklist.
Output: a score for each S, red tags and actions. A gemba walk with a 5S theme looks at the same things without scoring them.
Asks: how do we improve this one process against a target, over a few days?
When: when a problem is too big to fix through the actions of a walk, in the Kaizen Event Checklist.
Output: changes tried in the area, new standard work and a 30-day review. A walk can hand a problem to one.
Nine phases follow one gemba walk, from planning it to setting the next one. The first task records the area, the walk date and start time, the walk leader, the area owner and the note-taker, where the walk takes place, its theme and whether actions from the last walk are still open. The setting and the theme each show a short note on what to watch for, and open actions from the last walk add a task to check them in the area. A serious hazard seen on the walk adds three tasks to stop the work, report the hazard the same day and confirm the controls, and a problem too big for the area adds a task to hand it to a kaizen event or an improvement project. Nothing after the area owner agrees the follow-up actions can be completed until they do.
The walk leader plans the walk in the week before it. Enter the walk date and start time on the first task first: the preparation counts back from it, and the walk, the debrief and the follow-up count forward from it. The answers on the first task add the notes and tasks this walk needs.
A walk should not surprise the people who work in the area or put the walkers at risk. Tell the area what the walk is for, check the safety rules for the route and agree what happens if someone could be hurt, all before the day.
The walk starts where the work starts. Brief the walkers in a few minutes, sign in, then go to the first stop.
At each stop, watch before you ask. Look at the process, the standard work, the flow, waste, safety, quality and visual management, and write down what you see as facts. Nobody fixes anything on the spot unless someone could be hurt.
The people who do the work know it best. Ask open questions at a natural pause, listen, and write down what they say. Note ideas and problems for the debrief instead of fixing them on the spot.
Hold the debrief while the walk is fresh, ideally straight after it. Pick the few things that matter most, agree actions with owners and dates, and hand anything bigger to a kaizen event or an improvement project. The area owner agrees the actions before they are tracked.
The people in the area gave their time and their answers. Write up the walk, tell them what it found and what will happen, and put the actions where the team can see them.
Actions take days to weeks. Check progress, help remove what blocks an action, and go back to the area to see each change working before closing it.
A gemba walk works best as a habit rather than a one-off. Learn from this walk, then set the date and theme of the next one.
Watch first, then ask. Use the rows that fit the theme of the walk as prompts at each stop, and ask the person doing the work rather than their manager. The questions are this template’s suggestions: change them to fit your area.
| Look at | What to look for | Questions to ask the people doing the work |
|---|---|---|
| The process | What is done, in what order and how long it takes, and whether it runs the same way each time | Can you show me how you do this? What happens before and after your step? |
| Standard work | Whether a standard exists, is current, is posted where the work is done and is followed | Is there a standard for this? Is it the best way you know? What makes it hard to follow? |
| Flow | Queues, waiting, work in progress between steps, handoffs and batches | What are you waiting for most often? Where does work pile up? |
| Waste | Overproduction, waiting, conveyance, processing, inventory, motion and correction | What do you do that does not help the customer? What do you have to redo or check twice? |
| Safety | How people and equipment share the space, guards, housekeeping, manual handling and near misses | What could hurt someone here? What happens when you raise a safety concern? |
| Quality | Checks at the point of work, defects, rework and what happens when something is not right | How do you know this is right? What do you do when it is not? |
| Visual management | Whether boards, labels and markings show the plan, the status and what is normal | How do you know if you are ahead or behind? Who uses this board? |
| Problems and ideas | Workarounds, problems that keep coming back and how problems are raised | What gets in the way? Who do you tell when something goes wrong, and do you hear back? What would you change? |
Where the terms come from. The Lean Enterprise Institute’s lexicon lists Taiichi Ohno’s seven wastes as overproduction, waiting, conveyance, processing, inventory, motion and correction, and bases standardized work on three elements: takt time, the precise work sequence and the standard inventory. Its gemba walk entry suggests following a product family, a design or a customer-facing process from start to finish, across departments where it crosses them, which is why this checklist plans the route in the order the work flows.
Watch, ask, then act. The Lean Enterprise Institute describes Jim Womack’s practice as “go and see, ask why, and show respect.” This checklist keeps fixes for the debrief and asks the area owner to agree the actions, so the people who do the work stay part of the change.
The walk leader, the area owner and the note-taker are chosen on the first task, and each task is assigned to the person who owns it. Agreeing the follow-up actions is assigned to the area owner alone, and nothing after that approval step can be completed until they agree.
The setting and the theme each show a short note on what to watch for. Open actions from the last walk add a task to check them in the area, a serious hazard adds three tasks to stop the work, report it the same day and confirm the controls, and a problem too big for the area adds a task to hand it to a kaizen event or a project. Rules show and hide each one from the answers given.
Due dates count from the walk date and start time: the preparation in working days before it, the walk and the debrief in hours after it, and the follow-up in working days after that. Set up a recurring schedule for each area so the next walk is waiting before it is due. Overdue alerts go to the task’s assignees. The Reports Grid lists every walk with its answers, such as the area, the theme and whether a serious hazard was seen, with filters and export. Analytics shows how long walks and their actions take and where work runs late, by template, person and step.
CheckFlow does not replace your safety reporting system or your site’s action tracker. Report hazards where your site reports them and record the reference in the walk. CheckFlow runs the walk around them: what was seen, what people said, which actions the area owner agreed and whether each change works. CheckFlow’s manufacturing checklist software shows how plants run their other routines the same way.
Score an area with the 5S Audit Checklist, run a focused improvement with the Kaizen Event Checklist and write down a new way of working with the Process Standardization Checklist. To see the whole flow of a product or service before you walk it, read our guide to value stream mapping.
Describe the process in a sentence and the AI checklist generator drafts the phases and tasks for you.
The Lean Enterprise Institute defines a gemba walk as “a management practice for grasping the current situation through direct observation and inquiry before taking action.” Leaders go to where the work is done, watch it, ask the people doing it open questions and only then decide what to do. It is a way of learning how the work really happens, not an inspection of the people doing it.
Gemba is the Japanese term for “actual place.” The Lean Enterprise Institute notes that it is often used for the shop floor but covers any place where value-creating work happens: a factory floor, an operating room, a kitchen, a job site or, in software, the code itself. Japanese companies often pair it with genchi genbutsu, essentially “go and see,” to stress learning from what you see rather than from reports.
Open questions, asked of the person doing the work at a natural pause: “Can you show me how you do this?”, “How do you know it is right?”, “What gets in the way?”, “What happens when something goes wrong?” and “What would you change if you could?” Avoid questions that judge or lead, and play back what you heard. The table above has questions for each theme; they are this template’s suggestions.
The process itself, whether the work follows its standard, the flow between steps, waste, safety, quality at the point of work and visual management. The Lean Enterprise Institute lists Taiichi Ohno’s seven wastes as overproduction, waiting, conveyance, processing, inventory, motion and correction, and bases standardized work on takt time, the precise work sequence and the standard inventory. Choose one theme per walk so it stays focused.
An audit or an inspection checks an area against a standard and records findings or a score. A gemba walk is there to understand how the work is done and what gets in the way of the people doing it, so it watches and asks rather than scores. It still looks at safety, and a serious hazard is stopped and reported the same day. Use the 5S Audit Checklist to score an area.
Not on the spot, unless someone could be hurt. A fix ordered during the walk skips the people who do the work and the area owner, and often treats a symptom rather than the cause. This template notes ideas for the debrief, where the walkers pick the few that matter most and the area owner agrees the actions, owners and dates before they are tracked.
A small group: a walk leader, usually a manager or an improvement lead, a note-taker and the area owner or team leader, plus a specialist the theme needs, such as a health and safety adviser or a quality engineer. This template’s practice is three or four people, so the walk does not crowd the area. The people who do the work are not walkers: they are the people the walk learns from.
There is no fixed rule. This template plans about an hour and three quarters on the floor, a debrief straight afterwards and follow-up actions over about four weeks, counted in working days from the walk date and time. How often depends on the area. This template suggests a regular walk, set up as a recurring schedule, so each walk can check the last one’s actions. Change the due dates to fit your site.
The walkers debrief while the walk is fresh, separate facts from opinions, pick two to five priorities and draft actions with owners and dates. The area owner agrees them, the team hears what the walk found and the actions go on the area’s board. The walk leader checks progress, goes back to see each change working and sets the date and theme of the next walk.
14-day free trial, no card required. The Business plan is $10 per user per month after the trial. Full details at checkflow.io/pricing.
14-day free trial, no credit cardFull refund in your first 30 daysUS hosting, EU on request
