What this is
What is a gemba walk record?
What is a gemba walk record?
A gemba walk record captures a structured walk of the process by a manager — what was observed, who was spoken to, and what was raised. It turns a walk of the floor into a record with an owner and a next step, rather than a conversation nobody can trace afterwards.
What does 'gemba' mean?
Gemba is the place where the work actually happens — the line, the hall, the dock — as distinct from the office where it's discussed afterwards. A gemba walk means going there deliberately, on a schedule, rather than passing through.
What makes a gemba walk 'announced' or 'unannounced'?
An announced walk is scheduled or expected by the area being visited; an unannounced one is not. Both have a place, but they show different things — announced walks show the area at its best, unannounced walks show it as it normally runs.
Scope
When is a gemba walk record required?
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use this template when
- A scheduled gemba walk has just been carried out, or is about to be, in a named area of the site
- Something observed on the walk needs to be captured before it's lost — an abnormality, a barrier raised, a piece of feedback owed
- You are running the Daily Management System programme and this is its recurring leadership-visibility step
- A linked record needs this one to exist — a Hazard Report or Improvement Suggestion references it
- The workspace is being set up, or the gemba walk register needs an entry added or retired
Do not use it for
- Tier Board Review, which runs the daily management meeting against a fixed agenda at a board, not an open walk of the floor.
- Layered Process Audit, which checks a small number of critical process steps against a defined specification, rather than an open-ended observational walk.
- Standard Work Verification, which formally confirms standard work is being followed step by step, where this record captures whatever the walk happens to surface.
- Meeting and Action Log, which holds decisions and actions from any operational meeting, not a floor walk carried out alone or with one or two others.
- Anything outside KnowOps, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 45001 cl.5.1 requirements does this satisfy?
ISO 45001 cl.5.1 asks top management to demonstrate leadership by being actively involved in the safety management system, not just chairing it from an office. A gemba walk is that clause put into practice on a schedule, with cl.5.4 and cl.8.1.2 shaping what the walk is actually meant to surface.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.5.1 | Top management must demonstrate leadership and commitment by being actively involved, including through direct engagement with workers. | Header |
| ISO 45001 cl.5.4 | Workers must be consulted and enabled to participate, including having a means to raise hazards and contribute to decisions. | Conduct |
| ISO 45001 cl.8.1.2 | Hazards must be identified on an ongoing basis, including through routine and non-routine activities and conditions. | What was looked at |
| ISO 45001 cl.7.4 | The organisation must determine and implement processes for internal communication relevant to the OH&S management system. | Outcome |
| ISO 45001 cl.10.2 | Incidents and nonconformities must be investigated and corrected, with corrective action tracked to closure. | Outcome |
| ISO 45001 cl.9.1.1 | The organisation must monitor and measure OH&S performance, including proactive indicators of leading activity. | Outcome |
| ISO 45001 cl.6.1.2 | Hazard identification must consider how work is actually organised, including the routine practices of the people doing it. | What was looked at |
What it does not cover
- A walk that only ever happens on days and only ever announced, which shows the area at its best and misses whatever nights, weekends or an unannounced pass would actually reveal.
- An observation raised on the floor with no feedback ever given back to the person who raised it, which is the exact gap between a manager being seen and a manager being trusted.
- A hazard observed and left as a general note instead of a Hazard Case ID, which means it never enters the system that's actually built to track it to closure.
- Standard work marked as being followed without the manager having watched a full cycle first, which turns a genuine check into a guess dressed up as an observation.
- An abnormality marked handled with no owner or date attached anywhere on the record, which leaves 'handled' meaning nothing more than 'noticed'.
Global
Gemba Walk Record requirements by country
Gemba walks sit on top of a genuine legal expectation in several jurisdictions that leadership engages directly with how work is actually done, not just with the paperwork describing it.
ISO 45001:2018 cl.5.1 and cl.5.4
leadership must be visibly, actively involved, and workers must be consulted and able to participate
A scheduled gemba walk, properly recorded, is one of the more direct ways an auditor can see this clause actually happening rather than being asserted in a policy statement.
Model Work Health and Safety Act, s.27 (officer due diligence)
company officers must take reasonable steps to gain and keep up-to-date knowledge of work health and safety matters, including how the business's operations are actually carried out
Regulators and courts have treated a documented history of site engagement, including floor walks, as relevant evidence of whether an officer met this duty — an unrecorded walk proves nothing after the fact.
HSE HSG65, Managing for Health and Safety
sets out visible, active leadership as a core plank of an effective health and safety management system, expected of duty holders under the Health and Safety at Work etc. Act 1974
HSE inspectors assessing management arrangements look for evidence that leadership involvement is routine and recorded, not a one-off event staged for an audit.
How to complete it
How to complete a gemba walk record, step by step
The walk itself is a few minutes on the floor. The judgement calls below are what decide whether the record left behind is worth reading later.
An unannounced walk scores higher because it shows the area as it normally runs, but that doesn't make an announced walk pointless — it's the right choice when the point is coaching a specific team through a change, not auditing baseline conditions. The manager should be able to say which one this was and why, not default to whichever is easier to schedule.
Watched Before Asking and Asked Open Questions are two different disciplines — a manager can watch for thirty seconds and then ask a closed question, which technically satisfies the first field while defeating the point of the second. The record only captures that the sequence happened, not whether either step was done properly.
Feedback Given To Those Who Raised is easy to mark Yes on the day something was said in passing. Whether that counts depends on whether the person who raised the issue actually knows what happened to it — a promise to look into something is not the same as a returned answer.
An area with no equipment, or no task in progress at the moment of the walk, can legitimately leave a field N/A. A manager who didn't get to a section because the walk ran short is a different case, and the record doesn't distinguish the two unless it's noted directly.
What auditors find
Most common gemba walk record findings
Patterns worth watching for once a run of these records exists, not just the day's entry.
| Finding | Clause | What fixes it |
|---|---|---|
| Every recorded walk is Announced and every one lands on Days, across months of records. | ISO 45001 cl.5.1 / cl.9.1.1 | Force a minimum proportion of unannounced walks and off-shift coverage into the schedule directly — leaving it to the manager's discretion reliably produces the easiest option every time. |
| Observations Recorded stays consistently high while Items With An Owner stays low. | ISO 45001 cl.10.2 | Read the two fields as a ratio, not separately — a manager who notices a lot but assigns little is building a list nobody is accountable for. |
| Hazard Case ID is blank on records where Abnormality Visible And Handled or Safety Of The Task was marked No. | ISO 45001 cl.8.1.2 / cl.10.2 | Treat a No on either field as a trigger that should require a Hazard Case ID before the record can be closed, not leave the link optional. |
| Feedback Given To Those Who Raised is Yes on every record despite Next Walk Due showing gaps of several weeks between visits to the same area. | ISO 45001 cl.7.4 | Cross-check against the schedule — feedback given at the walk itself is not the same as feedback given after a finding was actually investigated, which often can't happen inside the same visit. |
| Barriers People Raised is consistently No in an area with a known, visible backlog of raised issues elsewhere in the system. | ISO 45001 cl.5.4 | Treat this as a sign the walk isn't reaching the people who'd actually raise something, not as evidence there's nothing to raise. |
| Did Not Solve It On The Spot Prematurely and Watched Before Asking are both consistently No on the same records. | ISO 45001 cl.5.4 | The two behaviours reinforce each other — a manager who doesn't watch first is also the one most likely to jump to a premature fix; coach them as one habit, not two separate scores. |
Case in point
Case in point: the walk that fixed nothing twice
An area manager walked the boning hall on the same weekday morning for six straight weeks, always announced, always the same route. Twice, line staff mentioned a recurring near-miss with a trolley on a ramp. Both times the manager said they'd look into it. Neither time did anything come back.
The third time it was mentioned, it was to a different manager on an unscheduled pass through the area, who logged it as a hazard case, assigned an owner, and fixed the ramp within the week. The observation had been available for six weeks; what changed was that someone finally wrote it down and came back with an answer.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- OPS-015
- Archetype
- Record
- Record ID
- GEM-2026-000
- Scoring
- Observations actioned
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 45001 cl.5.1
- Links
- Links Hazard Report and Improvement Suggestion
- Tags
- Daily management, Leadership
- Sections
- 4
- Fields
- 41
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
15 fieldsRecord ID*
Auto sequence. Format GEM-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Manager*
Duration Minutes*
Focus*
Safety, quality, standard work, flow, people, or open.
People Spoken To*
Announced Or Unannounced*
- Unannounced3 pts
- Announced1 pt
Shift Visited*
- Days1 pt
- Afternoons3 pts
- Nights4 pts
- Weekend4 pts
Walking Without Recording Produces Goodwill
A manager on the floor is worth something. A manager on the floor who writes down what they were told and comes back with an answer is worth a great deal more.
Conduct
6 fieldsWent To Where The Work Happens*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Watched Before Asking*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Asked Open Questions*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Listened More Than Talked*
- Yes3 pts
- Equal1 pt
- No0 pts
Did Not Solve It On The Spot Prematurely*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Thanked People For Their Time*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
What was looked at
6 fieldsStandard Work Being Followed*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Abnormality Visible And Handled*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Materials And Flow*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Equipment Condition*
- Good3 pts
- Acceptable2 pts
- Poor0 pts
Safety Of The Task*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Barriers People Raised*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Outcome
14 fieldsObservations Recorded*
Items With An Owner*
Feedback Given To Those Who Raised*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Hazard Case ID
Links to SAF-013 Case ID
Improvement ID
Links to OPS-036 Idea ID
Next Walk Due*
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Manager*
Signature*
Site Manager*
Second Signature*
OPS-015 · record IDs look like GEM-2026-000 · Links Hazard Report and Improvement Suggestion
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Coming back with an answer for everyone who raised something, making sure the walk actually reaches the shifts and areas that get skipped, and turning a hazard mentioned in passing into a tracked case is the work that actually slips.
Holds the gemba walk register against every site and area, flags when the schedule keeps landing on the same shift or area, and keeps the links to Hazard Report and Improvement Suggestion current.
Picks up anything logged under Hazard Case ID or a No on Safety Of The Task, so a hazard mentioned on a walk is tracked to closure rather than left as a line on this record.
Tracks Equipment Condition and Abnormality Visible And Handled against open maintenance work, so a fault spotted on a walk and a work order already raised for it are visibly the same thread.
Rolls observations, feedback owed and Next Walk Due across every area into one view, and holds any write back to the record for your approval before it lands.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Gemba Walk Record definitions and key terms
- Gemba
- The place where the work actually happens — the line, the hall, the dock — as distinct from the office where it's discussed afterwards.
- Gemba walk
- A deliberate, scheduled visit to where the work happens, structured around watching before asking and listening more than talking, rather than an informal walk-through.
- Abnormality
- Any condition that deviates from how the process is meant to run — outside standard work, outside a normal equipment state, or outside a safe condition — that the walk is designed to surface.
- Hazard report
- The separate record a gemba walk feeds when something unsafe is observed, carrying it through to investigation and closure rather than leaving it as a note on this record.
- Improvement suggestion
- The separate record a gemba walk feeds when the floor raises an idea worth tracking, distinct from a hazard because nothing unsafe is implied.
FAQ
Frequently asked questions about gemba walk record
What is a gemba walk record?+
A gemba walk record is used in KnowOps to capture a structured walk of the process by a manager — what was observed, who was spoken to, and what was raised. It sits against ISO 45001 cl.5.1 and forms part of the Daily Management System programme.
Why does an unannounced walk score higher than an announced one?+
Because an announced walk shows an area that's had notice to tidy up and behave, while an unannounced one shows the area as it normally runs. Both have a place, but only one gives a manager an honest baseline.
What's the difference between this and a layered process audit?+
A layered process audit checks a defined set of process steps against a written specification, run by different levels of management on different frequencies. This record is open-ended — it captures whatever the walk surfaces, not a checklist being ticked off.
Who carries out a gemba walk?+
The area manager, by design — Manager is a required field on both the walk itself and the sign-off, alongside a second signature from the site manager.
How is a gemba walk record scored?+
Scoring is observations actioned, where high is good. Coverage fields reward genuinely varied conditions — unannounced visits and off-shift timing score above the comfortable default of an announced day walk.
Can the walk's focus areas be changed?+
Yes — every field, option and conditional rule is editable, including the six focus areas of safety, quality, standard work, flow, people and open. Most sites run the template as delivered for a full cycle before adjusting what a walk is meant to cover.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Daily Management System
Audit Finding Record
Records a single audit finding with its evidence, clause reference and classification
Daily Production Report
Summarises the day across lines: output, attainment, losses, quality and the issues carried forward
Tier Board Review
Runs the daily management meeting against a fixed agenda and records what was agreed and by whom
Layered Process Audit
Checks that a small number of critical process steps are being done as specified, by different levels of management on different frequencies
Meeting and Action Log
Holds the decisions and actions from any operational meeting, with an owner and a date on each
Daily Priority Plan
Sets the small number of things that must happen today and who owns each
More in Daily Management
Tier Board Review
Runs the daily management meeting against a fixed agenda and records what was agreed and by whom
Layered Process Audit
Checks that a small number of critical process steps are being done as specified, by different levels of management on different frequencies
Meeting and Action Log
Holds the decisions and actions from any operational meeting, with an owner and a date on each
Daily Priority Plan
Sets the small number of things that must happen today and who owns each
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001:2018 cl.5.1 — Leadership and commitment
- ISO 45001:2018 cl.5.4 — Consultation and participation of workers
- ISO 45001:2018 cl.8.1.2 — Hazard identification and assessment of risk
- Model Work Health and Safety Act (Australia) s.27 — officer due diligence
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.