Your Inspection Began Before the Inspector Arrived
The evidence trail starts with the first signal and grows with every decision that follows.
Imagine it is 7:10 in the morning. A compliance officer walks through the front door and asks to speak with management.
When did the inspection begin?
The obvious answer is 7:10. The more useful answer is much earlier.
It may have begun when an employee first reported a concern, when a supervisor observed a recurring workaround, when maintenance opened a work order, or when an audit identified a weakness. It continued when someone assigned an owner, extended a deadline, accepted an interim solution, or decided the issue did not require escalation.
By the time the inspector arrives, the organization has already created much of the record it may later need to explain.
I am not using “began” as a legal definition. I am describing the evidence trail. The formal inspection may begin at the front door, but the organizational story begins with the first signal and every decision that follows.
THE INSPECTOR ARRIVES LAST
Inspection readiness is often treated as an event. Someone receives the inspector, notifies leadership, locates the written programs, and begins gathering records.
That is necessary, but it is late in the process.
The more important work happens through ordinary operating decisions long before regulatory contact. Those decisions generally create three types of evidence:
Signals: What surfaced?
Employee reports, near misses, work orders, audit findings, recurring defects, training confusion, and supervisor observations all indicate that something may require attention.
Decisions: What happened next?
Who evaluated the concern? Who owned the response? What deadline was established? Was an interim control necessary? When would the issue be escalated if the owner could not resolve it?
Proof: What changed?
Was the condition corrected? Was the control verified? Were affected employees informed? Did the correction hold after the work resumed?
A signal does not automatically mean an organization failed. It means the system received information that required a decision. The strength of the system is revealed by what happened next.
YOUR ORGANIZATION IS ALREADY WRITING THE CASE FILE
Many leaders picture inspection evidence as a collection of safety records maintained by the safety department. In reality, the evidence is distributed across the organization.
It can be found in at least four areas:
• Worker voice: Concerns, complaints, near misses, exit themes, accommodation requests, supervisor conversations, and escalation attempts.
• Capability: Onboarding, qualifications, training, language access, coaching, staffing decisions, and supervisor preparation.
• Operating evidence: Work orders, inspections, maintenance history, observations, temporary labor decisions, audit findings, and recurring deviations.
• Closure evidence: Corrective actions, due date extensions, interim controls, proof of completion, effectiveness checks, and communication back to affected employees.
HR may hold essential pieces of the story even when HR does not own the physical control. Operations and maintenance may hold other pieces. Safety may see patterns across several systems. Leadership may control the resources or priorities needed to resolve the issue.
Each department can hold a reasonable fragment while the organization still fails to reconcile the complete story.
Most organizations do not lack signals. They lack a dependable process for connecting those signals to ownership, action, and verified closure.
That is not only a compliance gap. It is an execution gap.
INTENT IS NOT EVIDENCE
Most organizations have policies that express the right intent. They commit to protecting employees, correcting hazards, providing training, and encouraging people to report concerns.
Those commitments matter, but intent alone does not demonstrate how the system performs.
A stronger test examines three levels:
Policy: What should happen?
This includes written requirements, assigned responsibilities, planned training, expected controls, and escalation procedures.
Practice: What actually happens?
This is the work as it is performed, supervised, staffed, changed, and stopped when real operating pressure enters the picture.
Proof: What can the organization demonstrate?
This includes records, observations, employee understanding, completed controls, and verification that the correction was effective.
A training record may demonstrate completion without proving practical capability. A work order marked closed may document an administrative status without showing that the condition was actually controlled. A policy may encourage employees to report concerns while individual supervisor behavior makes reporting feel ineffective.
Documentation should support action. It cannot substitute for action.
Inspection readiness exists when policy, practice, and proof tell the same story.
KNOWN IS NOT THE SAME AS CLOSED
Organizations also create risk when they confuse assignment with resolution.
A reliable closure process moves through four distinct states:
1. Reported: The signal entered the system.
2. Assigned: A person accepted ownership and a deadline.
3. Corrected: The work or control changed.
4. Verified: Someone confirmed the control worked and continued to hold.
Reported and assigned are administrative states. Corrected and verified are control states.
An action tracker can create the appearance of progress while the underlying condition remains. “Assigned,” “in progress,” and “awaiting resources” may accurately describe the administrative status, but they do not demonstrate that people are protected.
Due date extensions are not automatically unreasonable. Permanent corrections may require engineering, equipment, capital, scheduling, or outside expertise. However, an extension should also identify the reason, the interim control, the new commitment, and the escalation point.
Repeated extensions without those elements can document that the organization knew an issue remained unresolved without demonstrating that it was controlled.
The question is not simply, “Did we know?”
The question is, “What did we do once we knew, and can we show that the response worked?”
CLEAR LANES PREVENT OWNERLESS RISK
Shared accountability does not mean anonymous ownership.
Each function needs a defined role:
• Operations owns the work and closes the control. The people directing the work are responsible for the operating response.
• Safety advises and verifies. Safety helps interpret requirements, evaluate options, and confirm that controls are effective.
• HR protects worker voice and governs capability. HR supports credible reporting, connects onboarding and competency expectations, prepares supervisors, and escalates concerns when the normal system is not responding.
• Leadership removes barriers and resources action. Senior leaders resolve conflicts involving priorities, authority, staffing, capital, and competing deadlines.
HR should enable the system without absorbing operational ownership. Safety should not become the default owner of every condition. Operations cannot transfer control of the work to a support function. Leadership cannot demand closure without providing the authority and resources required to achieve it.
Clear lanes prevent a familiar failure: everyone participated, but no one owned the result.
TRACE ONE EVIDENCE TRAIL
Choose one significant concern that is currently open or was recently marked closed. Begin with the operating record, not the policy.
Ask:
• What was the earliest signal?
• Where was it recorded?
• Who owned the next decision?
• What interim and permanent controls were implemented?
• Who verified that the correction worked?
• How was the outcome communicated?
• Do policy, practice, and proof tell the same story?
If different functions tell different versions, the problem is not merely incomplete documentation. It is system misalignment.
The goal is not to make the records look cleaner. The goal is to identify where the organization loses information, accountability, or follow-through before an outside audience exposes the gap.
The inspector may arrive last, but the organization does not have to wait for an inspection to understand the story it is already writing.
What signal is your organization creating but not routinely reconciling?
This is Segment 1 of a four-part series leading into my October 14 session at the Southern Indiana SHRM Conference: “Safety Update: Same Hazards. New Spotlight. Workplace Safety, Public Trust, and the 2027 Enforcement Outlook.”
Next: Your Workplace Has an Audience Now.
Originally published August 17, 2026 in The All-In on Safety Brief — https://www.linkedin.com/pulse/your-inspection-began-before-inspector-arrived-nick-combs-ma-csp-n5edc.
Explore the SoIN Safety approach — https://www.soinsafety.com/our-approach · Request a Diagnostic Conversation — https://www.soinsafety.com/contact?SQF_SOURCE=insights-newsletter&SQF_OFFER=diagnostic
