The expert nobody wrote down
There is one person everyone asks. They have refined a process over fifteen years and it works. It exists only in their head, so when they leave, it leaves.
Safety Never Sleeps
Predictive safety and operational excellence
WSA connects what your company is required to do, from standards and regulations to manufacturer manuals and your own hazard analysis, with the procedures, training and audits your people use every day. The gaps show up on an ordinary Tuesday, while they are still cheap to close.
For amusement and water parks, hospitality and resorts, and manufacturing.
Change the step and all three change with it. There is no second copy to forget.
Our purpose
We believe compliance and risk reduction are not competing priorities. Together, they are what drives results across an organization.
WSA was built so that any company, regardless of size, can operate with the safety insight of a large international corporation. We do it by aligning what a company already has, its standards, regulations, technical documentation and hazard analysis, with the tools that turn that knowledge into daily practice: documentation, training and auditing.
Success is measured in expertise retained, not headcount reduced.
Where an organization's lessons come from. Each rung up finds the gap earlier, and at a lower cost.
Every organization learns here. The question is whether it learns anywhere else.
The same rigor as an incident, without the cost. A near miss with no response is itself a finding.
An incident anywhere in your industry becomes a question here within days: do we have this equipment, this process, this gap?
Reports, proposals, job task findings and procedures flagged as not matching the work, because people have seen reporting produce action.
Exposure found with no incident, no near miss and no complaint to trigger it.
Most organizations work on rungs one and two. Established maturity models stop at rung four. WSA is built for rung five, and makes rungs three and four routine on the way there.
You already know this story
Every one of the gaps behind a serious incident existed the week before, the month before, the year before. The information was in the building. What was missing was a way to see it before an incident made someone look.
What we see in every operation
None of them are caused by careless people. They are caused by systems that keep documents, training and audits in separate places, maintained by separate people, on separate schedules.
There is one person everyone asks. They have refined a process over fifteen years and it works. It exists only in their head, so when they leave, it leaves.
Someone edits a document in good faith with no idea it now contradicts a manufacturer's manual or a regulation. Nobody finds out until something forces a close look.
A procedure was changed for a hard-won reason. Three years later nobody can explain it, so the change looks arbitrary and quietly reverts to the old way.
The procedure describes a task nobody can actually perform as written. The binder is for the auditor, not for the person doing the work.
A procedure relies on another department's step without confirming that department has one. Each document is right on its own. The gap between them belongs to nobody.
Records in order, answers correct, every audit clean. But the procedures and training were written elsewhere, and nobody there believes they are theirs.
The core idea
An investigation traces every contributing gap: documentation, training, audit history, near misses and manufacturer requirements, all pulled together and suddenly obvious.
WSA makes that same lens continuous and affordable, running across documentation, training, audits and incident data at once. Not a report you commission every few years. A condition you operate in.
A gap assessment across documentation, training, audit history and incident data, ranked by worst credible consequence.
Procedures, training and audit criteria built together from the same source, so all three agree. Your experts own them and their names are on them.
Field audits measure whether the change is performed, not whether it was communicated, with the most critical steps first.
The platform helps you spot the day a regulation, manual, procedure or training module falls out of step, so the fix does not erode.
The platform proposes and your qualified people decide. Nothing safety-relevant becomes live on the system's authority, and every confirmation records who made it and when.
The platform
Every module works from the same record of what applies to your company and why. A procedure step traces up to the requirement behind it and down to the checklist item, training and audit criteria generated from it.
Foundation
Build
Turn requirements into daily practice
Verify
Check that practice matches the requirement
Learn
Find out why things go wrong, and fix the system
Invest
Spend where it removes the most risk
Alongside them: Industry Lessons, a library of incidents from across your industry matched to your own equipment and procedures, and an offline-first field tool that works with no signal.
See the platform
A single procedure step for a boom lift, traced through four screens. Every name, site and number below is example data.
Every step shows its criticality, where it came from and the reason it exists. When the manufacturer issues a new manual, the steps it touches are flagged by name, along with their checklist items, training and audit criteria.
Example data
The auditor sees what to look for and why it matters, at the point of work, with or without signal. Conforming results are recorded as well as gaps, and every grade stays a proposal until a qualified person confirms it.
Example data
Before anyone looks at the person, the platform walks the finding through five systemic checks in a fixed order. Here the cause is the design of the task, so the fix is to the lift, not a reminder to the operator.
Example data
Six questions leaders actually need answered, in place of a wall of charts. Every number opens to the finding, the audit criteria, the source requirement and the photograph underneath it.
Example data
External and internal requirements
If the requirements are wrong, the procedures are wrong, the training teaches the wrong thing, and the audits confirm the wrong thing. Every document agrees with every other, every audit comes back clean, and nobody finds out until an incident. This is the one point in the chain where an error is still cheap to fix.
External requirements
Standards and regulations for your jurisdiction and industry, and the requirements your customers and insurers place on you.
Internal requirements
Manufacturer manuals and service bulletins, company policies, and your hazard, risk and job task analyses.
Neither is enough alone. A company meeting every regulation can still be unprotected against a hazard no standard names, and a company following every manual can still miss a regulation nobody read. The gap between the two is where the findings are.
Coverage is a claim about the company, not the document. A requirement counts as covered only when the step that meets it exists, is current and is audited.
Documentation and checklists
Most procedures are written to be defensible rather than performable, and the binder ends up serving the auditor instead of the person doing the work. WSA documents are held to three words, clear, concise and complete, and to one test.
The three-reader test
Every document has to work for all three. One that only one of them can use is the most common defect in industrial documentation.
“Ensure the assembly is secure.”
Nobody watching could say whether it happened.“Confirm the retaining clip is fully seated.”
One action, observable, with its criticality, its source and its why attached.Training
The problems with safety training are structural, and they appear in organizations with excellent training teams. Training is written separately from the procedure and drifts away from it. The why is missing. A signature is treated as proof of ability. WSA is built to fix each of these at the source.
Level four is the one no learning management system can generate, because it requires knowing the hazard behind the step. A C1 step is demonstrated where it can be, and simulated where it cannot.
Every system in the market reports this person as qualified
Training current. Certificate valid. Record complete.
They last performed the task fourteen months ago, on equipment modified since, against a procedure revised twice since they were trained.
A critical task is not assigned when any clock has run out, and the people at risk are listed by the criticality of the task, not by days overdue.
Training is generated from the same step as the procedure and the checklist, so it cannot teach work the procedure no longer describes. When the step changes, every affected module and every qualified person is identified.
Each lesson carries the reason the step exists and, where there is one, the real event behind it. A person told why a check exists is far less likely to be the one who drops it three years later. Leaders are told the why too.
The method is chosen from criticality, difficulty and frequency, not habit. A critical, rare task gets more structure, not less, and every departure from the default is recorded with its reason.
Instructors assess the same demonstration independently on a set cycle. When they disagree, the group is retrained, and the content itself is reviewed.
Whether training worked is checked where the work happens, through the audit program, and recorded as held, did not hold, or inconclusive. Inconclusive is never recorded as held.
Audio narration and closed captions on every lesson, translated content for critical steps, and a ready safety briefing for contractors, workers from other employers and visitors.
The audit program
Most audit programs spread attention evenly, check what is easiest to reach, and end in a pass or a fail. The WSA audit program starts from a different premise, and every part of it follows from that.
The founding constraint
Nobody can watch everything. A program that tries protects nothing.
An operation holds thousands of procedural steps, and an auditor has hours. So the program decides what matters most, says so openly, and puts its depth there. The critical few are audited often, by name, by qualified auditors, with fixed samples. Everything else is covered by lighter methods: self-verification, document review, data monitoring and rotating samples.
The numbers are illustrative. The proportions hold in every operation we have examined.
| A typical audit program | The WSA audit program |
|---|---|
| Attention spread evenly, weighted toward what is easy to reach. | Attention set by criticality. The C1 Safety Critical steps are audited first, most often and by name. |
| A checklist written once and reused for years. | Audit criteria generated from the current procedure step. Each carries its source and its why, and the report it will produce is previewed before the audit is used. |
| One kind of audit for everything. | Five audit types, 23 methods, four occasions. Each step is audited by the method that answers the question it raises. |
| The sample shrinks when early observations look fine. | Sample, vantage point and observation time fixed in advance. A sample can be expanded in the field, never reduced. |
| Results reported as a pass or a fail. | Findings graded by severity. Critical, Major, Minor, observation or opportunity for improvement, so people report what they see. |
| The finding lands on the person who did the work. | Five systemic checks before individual conduct. Workarounds, auditor calibration, training, documentation and the requirement itself are examined first. |
| Closed when the paperwork is complete. | Closed when the fix is shown to hold. A repeat finding reopens one grade higher, as evidence that the first diagnosis was wrong. |
| What works well stays invisible. | Effective practices recorded and shared. A practice that works at one site is offered to every site with the same conditions. |
Local checks at the point of work, Cross-functional peers from another department, Site, Enterprise and independent Third-Party audits. Each type has its own purpose, and all draw on one shared library of audit criteria.
From performance observation and condition audits to why verification, data fusion and the worst case scenario audit. Each answers one of four questions: is the work done as designed, is the system sound, what has not been tested, and is there a better way.
Scheduled, called by a condition, triggered by an event such as an industry incident, or taken as an opportunity when a rare critical procedure is about to be performed for real.
The WSA auditor credential
The credential belongs to the individual, not the employer, and travels with them. It is meant to make the person who holds it more valuable in their industry than they were before.
The WSA credential complements accredited auditor certifications, such as ISO 45001 lead auditor, and does not replace them or claim to be equivalent.
The auditor council
Senior credential holders meet on a fixed schedule as a standing council of practitioners. It is how the method keeps improving from the people who use it, rather than from the vendor who sells it.
Holding the credential means joining a body of practitioners who shape the standard, not just receiving a certificate. The council is being formed with our first credential holders.
The safety management system
Most organizations already have most of a safety management system: policies, training, inspections, incident forms, a committee and a set of spreadsheets. What they lack is the connection between them, which is how the same hazard can be known to four departments and addressed by none.
Safety Never Sleeps
Hazards do not keep to the audit calendar, the training cycle, the day shift or the fiscal year. A system that works only when someone is looking is a set of events, not a management system. This one is designed to run in the gaps, which is where almost all of the time is.
Every department meets the same floor: a way to report, a named accountable person and a hazard register. Above that, each department is profiled as Operating, Enabling, Administrative or Distributed, so a maintenance shop and an accounts office are not handed the same system.
One channel for a hazard, near miss, incident, concern or suggestion, anonymous if the person chooses. Nobody has to classify their own report first. Every report receives an answer, including when nothing will change, and why.
The hazard register shows which hazards are held by a procedure alone, with no engineered control behind it. That list exists before anything happens, and it is read in two places: by the site lead deciding where to look, and by the executive deciding where to invest.
When a control is down or bypassed and work continues, the stand-in is declared, approved, visible to the shift it affects, and given an end date. A workaround renewed past its limit is reported as the design change it has become.
A message was sent, received or understood: three different claims. Most systems measure the first and report it as the third. Here, understanding is checked on anything that matters, in the language and reading level of the people it is for.
Recordable rates and days since the last incident are required and useful, but they only look backward. The system adds measures that look forward: reporting and response rates, open exposure, live workarounds and whether fixes held.
It maps onto the framework you already use, including ISO 45001, ANSI/ASSP Z10 and OSHA's Recommended Practices, and can run alongside a safety management system you already have.
Industry Lessons
An organization that has never had a serious incident has no record of its own to learn from. That is the normal condition, and the absence of incidents is not the absence of exposure. Industry Lessons gives every company the lessons of its whole industry.
Each entry is an incident from another organization, structured so it can be used here: what happened, which barrier did not hold, what should have stopped it, what changed afterward, and who else carries the same exposure.
Entries are classified by mechanism rather than by industry, so a lesson from a chemical plant can inform a ride inspection, and a lesson from a hospital can inform a production line.
Industry Lessons is a curated selection, not a complete record of every incident. An absence of a match does not mean no relevant precedent exists.
Bulletin effectiveness
A manufacturer service bulletin, recall or regulator alert is the clearest statement anyone outside the company will make about a hazard in its equipment. In most companies it arrives, someone reads it, and unless the connection is obvious, nothing happens. WSA tracks each one as an obligation until it is closed, and then until the closure is shown to hold.
The platform also tracks how long a change takes, from request to implemented procedure, especially for safety-critical steps. A change process that grows slower is an early sign that the whole system is losing credibility.
What makes it different
A repository stores files. WSA holds the obligation, the step that satisfies it, and the reason the step exists, and treats every document as a view of those.
The reason a step exists, in plain words confirmed by a person, travels with it into the checklist, the training and the audit. It survives turnover, reorganization and system changes. Leaders get the why too: a notification says why the procedure exists and why they are being told.
Checklist items, training and audit criteria are generated from the same validated step. When a standard or manual changes, every dependent item is flagged by name for a person to review.
When a step is not performed as written, the platform walks through five systemic checks first: is the task practical, would other auditors agree, is the training current, is it documented, does it match the requirement. Individual conduct comes last.
Five audit types, 23 audit methods and attention allocated to the most critical steps first. Findings are graded by severity and never described as a pass or a fail, so people report what they see.
A fact base assembled before the team meets, and six closure gates that keep an investigation from stopping at a single cause or at the person doing the work.
Six questions executives actually need answered, such as where protection is thinnest and what is bypassed right now, each one traceable to the evidence underneath it.
What changes for you
For the person doing the work
For the supervisor and trainer
For the safety and quality lead
For the executive and the board
Where this applies
ASTM F24 · state ride authorities · manufacturer manuals
Fire · food safety · aquatics · general industry
OSHA 1910 · ISO 45001 · IATF 16949 · PFMEA
If your operation runs on procedures, manuals and people who know the work, the same method applies. Ask us about yours.
Pilot sites
We are selecting a small number of pilot sites. A pilot is a bounded, 90-day assessment of a single location, with a defined deliverable and a decision point at the end.
Every engagement is led personally by a founder, on your site, with your people.
Pricing follows the size of the site, with everyone at the site included. No per-user licenses.
The work is designed to transfer ownership to your team, not to make you dependent on ours.
Who you would be working with
Founder · Amusement, hospitality and recreation
Co-Founder · Manufacturing and automotive
Your people are already the experts.The software does what people are poorly suited to do: exhaustive search, perfect recall, and cross-referencing thousands of documents. Your people observe, judge and own the outcome. Success is measured in expertise retained, never in headcount reduced.
Questions we hear
WSA connects what your company is required to do, from standards and regulations to manufacturer manuals and your own hazard analysis, with the procedures, training and audits your people use every day, so gaps are found and closed before an incident finds them.
Any operation that runs on procedures, equipment manuals and people who know the work, from a single site to many sites across regions. Our first focus is amusement and water parks, hospitality and resorts, and manufacturing and automotive.
Small companies are a deliberate part of that. Our purpose is to give a company of any size the safety insight of a large international corporation.
Most EHS software records events and tracks actions after something has been reported. WSA starts earlier in the chain. It links each requirement to the procedure step that meets it, and builds the checklist, the training and the audit criteria from that same step, so all of them agree and stay current.
It also comes with a method: how to decide what is critical, how to audit it, and how to find the systemic cause when a step is not performed as written. WSA can work alongside a safety management system you already have.
No. A document system stores files. WSA holds what you are required to do, the steps that satisfy each requirement, and the reason each step exists. Procedures, checklists, training and audit criteria are views of that record, so they cannot drift apart.
No, and it is designed not to. The platform takes on what people are poorly suited to do: exhaustive searching, perfect recall, and cross-referencing thousands of documents. Your people observe, judge and decide. We measure success in expertise retained, never in headcount reduced.
No. The platform proposes and a qualified person at your company decides. Nothing safety-relevant becomes live on the system's authority, and every confirmation carries the name of the person who made it and the date.
It starts from two sources. External requirements are the standards, regulations and customer or insurer requirements for your jurisdiction and industry. Internal requirements are your manufacturer manuals, company policies, and your hazard, risk and job task analyses.
The platform proposes what applies and where each requirement is already met. Your qualified people confirm it, and they review the cross-referenced documents themselves. You can also add the words your own documents use for a requirement, so nothing is missed because it was phrased differently.
Yes, for the work AI does well: reading large volumes of documents, finding requirements and conflicts, cross-referencing, and preparing first drafts. Anything safety-relevant is reviewed and confirmed by a qualified person before it is used, and the platform never invents the reason for a step to fill a gap.
Every procedure step that came from it is flagged by name, along with the checklist items, training and audit criteria built from those steps. Nothing is changed silently. A qualified person reviews each flag and decides what changes.
Yes. The platform guides your people through a job task analysis, a hazard analysis or a risk analysis where one does not exist yet, so the company gets better rather than only recording what it already has.
Audits are planned from criticality, so the most critical steps get attention first. Five audit types define who performs an audit, from local checks at the point of work to independent third-party audits. A catalog of audit methods defines how, from performance observation to knowledge assessments, and every type draws on one shared library of audit criteria.
Findings are graded by severity and never described as a pass or a fail, so people report what they see.
Yes. The field audit tool is built to work offline first. Checklists, findings and photo evidence are captured on the device and sync when a connection returns.
Yes. Anyone at a covered site can report a hazard, a near miss or an incident, anonymously if they choose, and see what happened with their report. Reporting is never limited or held back by plan.
No. The platform can work alongside the systems you already use, starting with a file import and adding a direct connection where your system offers one. We will be clear about what works best with your system and what works best with ours, so you can choose.
The method is available now through a founder-led pilot. The platform is being built in step with our first pilot sites, which see each part as it becomes ready and help shape it.
A pilot is a bounded, 90-day assessment of one site. You receive a scored gap assessment across documentation, training, audit history and incident data; the diagnostic sequence run on your highest-consequence processes; and one critical process rebuilt end to end, with its procedure, training and audit checklist aligned to source and checked in the field.
We ask for access to your existing documents and records, two subject-matter experts part time, and an honest decision at day 90.
A pilot is priced as a fixed engagement for one site, agreed before it starts. Tell us about your operation and we will give you a figure.
Per site, set by the size of the site, with everyone at the site included. There are no per-user licenses, so you never have to choose who gets access, and contractors are not charged.
You decide whether to expand or to stop. Either way, your procedures, training and records remain your company's, and the people who did the work with us keep the skills.
Each company's data is kept separate from every other company's. Records carry a sensitivity level, and access follows role, site and named permission, so people see what their work requires.
Yes. An investigation prepared with counsel can be held in a privileged workspace with named access controlled by counsel, separate retention, and a label your counsel words, printed on every page. Whether privilege applies is always decided by your counsel under your jurisdiction's law.
You are offered an export of your records before anything is removed, on a period announced in advance. Your procedures, training and records remain your company's.
No. The platform helps you see what applies to your operation and where it is met. Decisions about compliance, and any legal question, stay with your qualified people and your counsel.
A founder leads every engagement personally, on your site and with your people. You will work with operators who have run safety, operations and engineering programs themselves.
Yes. The WSA auditor credential has four levels, from checks at the point of work to auditing the audit programs themselves. It is earned by performance, renewed each year, and held by the individual. Senior holders join the auditor council, which shapes how the method develops.
The credential complements accredited auditor certifications, such as ISO 45001 lead auditor, and does not replace them.
The platform is designed to handle requirements by jurisdiction and content in more than one language. Tell us where you operate and we will tell you what that means for a pilot.
Email us with your company, your industry, how many sites you have and what prompted you to reach out. We reply personally and set up a first conversation.
Talk to us
Whether you are considering a pilot site or have a question, we reply personally.
A founder reads every message and replies personally.