Worldwide Standards AlignmentSafety Never Sleeps

Safety Never Sleeps

Predictive safety and operational excellence

The gap is always there before the incident is.

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.

SOP-OPS-014 · step 3 Example record
action
Confirm every restraint is locked and pull-tested before dispatch.
criticality
C1 Safety Critical
source
Manufacturer operations manual, section 4.2 · ASTM F770
why
A restraint can look closed and still be unlatched. This check is the last point where that can be found.
confirmed by
Ride operations lead, March 12, 2026
generates, from this one step
Checklist itemTraining lessonAudit criteria item

Change the step and all three change with it. There is no second copy to forget.

Our purpose

To reduce risk and increase safety at companies of every size, through solutions that drive lasting operational excellence.

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.

The Learning Ladder

Where an organization's lessons come from. Each rung up finds the gap earlier, and at a lower cost.

Rung 1The floor

Our own incidents

Every organization learns here. The question is whether it learns anywhere else.

Rung 2The gift

Our own near misses

The same rigor as an incident, without the cost. A near miss with no response is itself a finding.

Rung 3Borrowed lessons

Others' incidents

An incident anywhere in your industry becomes a question here within days: do we have this equipment, this process, this gap?

Rung 4Listening

What our people tell us

Reports, proposals, job task findings and procedures flagged as not matching the work, because people have seen reporting produce action.

Rung 5Predictive

What has not happened yet

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

It worked. It genuinely worked, for about three years.

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.

  1. The call comes in. There has been a serious incident.
  2. Within 48 hours there is a war room, a root cause team and an open budget.
  3. You retrain. You rewrite the procedure. You update the audit criteria.
  4. The regulator visits. You show everything you changed. The finding closes.
  5. Everyone moves on, and the same conditions slowly come back.

What we see in every operation

Six gaps, in almost every company we walk into

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.

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.

The silent conflict

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.

The forgotten why

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 document nobody trusts

The procedure describes a task nobody can actually perform as written. The binder is for the auditor, not for the person doing the work.

The seam between departments

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.

The department that satisfies the audit

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

You already own the lens. You only use it once.

After an incident

An investigation traces every contributing gap: documentation, training, audit history, near misses and manufacturer requirements, all pulled together and suddenly obvious.

Every other day

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.

1

Find

A gap assessment across documentation, training, audit history and incident data, ranked by worst credible consequence.

2

Close

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.

3

Verify

Field audits measure whether the change is performed, not whether it was communicated, with the most critical steps first.

4

Hold

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

Twelve modules, built on one foundation

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

External requirementsStandards, regulations, customer and insurer requirements
Internal requirementsManufacturer manuals, company policies, hazard, risk and job task analyses

Build

Turn requirements into daily practice

  • 3Documentation
  • 4Checklists
  • 5Training

Verify

Check that practice matches the requirement

  • 6Audit setup
  • 7Field auditing
  • 8Audit reporting

Learn

Find out why things go wrong, and fix the system

  • 9Investigations
  • 10Safety reporting

Invest

Spend where it removes the most risk

  • 11Capital planning
  • 12Hazards and change

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

One step, followed from the manual to the boardroom

A single procedure step for a boom lift, traced through four screens. Every name, site and number below is example data.

SOP-PRD-014  Boom lift pre-use and operationRiverside Plant · Example data
Manufacturer manual rev. D arrived Sep 30. Steps 3 and 5 come from it, so they and their checklist items, training and audit criteria are flagged for review. Nothing changes until a qualified person reviews them.
Steps
1Walk around the lift. Look for damage, leaks or missing parts. C3 Operationally Significant
2Test the ground controls, including the emergency stop. C2 Safety Significant
3Inspect the load-bearing pin. Confirm the retaining clip is fully seated. C1 Safety Critical
4Check the guardrails and confirm the gate latches closed. C2 Safety Significant
5Check the harness anchor point for damage or cracks. C1 Safety Critical
Why step 3 matters
A clip that is not fully seated lets the pin work loose under load. Nothing else on the lift would catch it, so this check is the barrier.
Written with the operations lead · confirmed by M. Reyes, Safety Lead
Where step 3 comes from, and what it feeds
External requirement ANSI/SAIA A92.22, inspect before each use
Internal requirement BL-02 operator manual rev. C, p. 42
This procedure step Step 3 · C1 Safety Critical
Checklist item BL-02 daily pre-use, item 3
Training Boom lift operator, lesson 2
Audit criteria AC-PRD-014-03, used by every audit type

The step and its why

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

External and internal requirements

It starts with knowing exactly what applies to you

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

What the outside world requires

Standards and regulations for your jurisdiction and industry, and the requirements your customers and insurers place on you.

Internal requirements

What your own knowledge requires

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.

How a requirement is found

  1. ExtractedThe platform reads your sources for the language of obligation: shall, must, never, intervals, limits and tolerances. You can add the words your own documents use.
  2. ProposedEach requirement is proposed with its source, a criticality from factual questions, and where it appears to be met. Where two sources disagree, both are shown and the more protective is proposed.
  3. ConfirmedA qualified person at your company confirms, corrects or rejects it, and reviews the cross-referenced documents. Nothing is built on a requirement until it is confirmed.

Coverage, stated honestly

CoveredMet, and the place it is met can be named: a procedure step, a training module, an engineered control or a record.
Partly coveredMet in some places and not others. The most common state, and the least visible.
Not yet coveredNothing in the company meets it. It becomes a proposed requirement for a person to confirm.

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.

Kept current, without anyone having to remember

A new edition is publishedEvery requirement from the old edition is flagged. Whether the old edition still governs is asked, never assumed.
A manual is revisedEvery requirement, step, checklist item, training module and audit criteria item built on it is flagged for review.
A regulation changesThe affected requirements are flagged for the sites in that jurisdiction.
An incident happens anywhereThe barrier that was missing there becomes a question at every comparable site here.

Documentation and checklists

Procedures written to be performed, not filed

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.

The performercan do the task from it, in the words they actually use.
The trainercan teach it from it, from the same source.
The auditorknows exactly what they should expect to see performed.

One step, one observable action

Typical

“Ensure the assembly is secure.”

Nobody watching could say whether it happened.
WSA

“Confirm the retaining clip is fully seated.”

One action, observable, with its criticality, its source and its why attached.
  • Written at the reading level of the people who perform it, in their language.
  • Generated as a first draft from confirmed requirements, then edited by your experts. Every edit records who, when and why.
  • An edit that changes meaning is a change to the step, so every checklist item, training module and audit criteria item built on it is flagged.

Checklists that behave like the work

  • One item at a time, in sequence, so a checklist cannot be completed from memory.
  • Critical items cannot be skipped. They are completed or flagged as an exception, and a C1 or C2 item can never be marked not applicable.
  • Completion time is data. A checklist finished faster than the task can be performed is a finding about the checklist.
  • Linked to the equipment. Scan the code on an asset to open its current checklist. Works with no signal.
  • Proving tests for engineered controls. Each control carries a test that shows it would actually act, not just that it powers on. A control never proven is recorded as unproven.
Emergency documents always reachableOffline, on a low battery, during an outage, without signing in. A site keeps a printable continuity copy of its current checklists and emergency documents.
Change history in plain viewEvery version, what changed, who changed it and why, visible to the people who use the document.
Read and acknowledgedWhen a document changes, the people it affects acknowledge the version they read, and the record shows it.

Training

Training that proves competence, not attendance

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.

The verification ladder

5Can performDone correctly, observed against defined criteria, under real conditions.Required for every C1 Safety Critical step
4Understands whyCan explain the hazard the step controls, and what happens if it is skipped.
3KnowsCan state the steps correctly, assessed against defined criteria.
2AcknowledgedSigned. Evidence of a signature.Where most training records stop
1AttendedWas present. A roster.

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.

Three clocks, not one

CurrencyWhen were they last trained?
RecencyWhen did they last actually do it?
DriftDoes the training still match the work?

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.

Built from the procedure

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.

The why at the center

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 right method for the task

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.

Consistent across trainers

Instructors assess the same demonstration independently on a set cycle. When they disagree, the group is retrained, and the content itself is reviewed.

Measured in the field

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.

For everyone who needs it

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

An audit program built on what matters most

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.

~4,000Every documented step in the operationThe inventory
~900Steps with a credible path to a serious outcomeScreened for consequence
~220Severe outcome, thin protectionScreened for barrier depth
~60Audited often, by nameThe critical few

The numbers are illustrative. The proportions hold in every operation we have examined.

How the WSA audit program differs from a typical program
A typical audit programThe 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.
Who

Five audit types

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.

How

23 audit methods

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.

When

Four occasions

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

Held by your people, and earned in the field

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.

Level 1Checks at the point of work against fixed audit criteria, with evidence recorded correctly.
Level 2Plans and conducts audits, grades findings and runs the diagnosis.
Level 3Owns an audit program, confirms criticality and calibrates other auditors.
Level 4Audits the audit programs themselves, across sites.
  • Assessed by performance. Candidates conduct a supervised audit, grade real findings and defend their grading to an assessor. A written exam alone shows familiarity, not competence.
  • Kept current. Renewed each year through audits performed, calibration sessions and contributions to the library of failure modes. A credential that never expires shows only that someone once completed a course.
  • Taken seriously. It can be withdrawn for falsified evidence or a finding closed without the required check.

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

A method that improves from the field

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.

  • Reviews findings across the organizations that use the method.
  • Examines the audit criteria on which qualified auditors disagree, and settles them.
  • Evaluates new failure modes and better methods brought from the field.
  • Decides what the methodology adopts next.

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.

Calibrated auditorsAuditors assess the same work independently on a set cycle. When they diverge, the group is retrained, not the individual.
Judgment protectedWhat was observed is recorded before who was observed, so reputation and familiarity cannot quietly change a finding.
Observed properlyEvery criteria item states where to stand and how long to watch, so a finding cannot be logged from a distance or in passing.

The safety management system

A safety management system that runs in the gaps

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.

Sized to each department

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 front door for every report

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.

Where a person is the only barrier

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.

Temporary stays temporary

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.

Understood, not just sent

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.

Leading indicators, not only lagging ones

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

Learn from what happened elsewhere, before it happens here

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.

Hazard analysisFilter by industry, equipment and process to start a hazard register from demonstrated failure modes. Identifying hazards becomes retrieval instead of recall.
Audit scopeAn incident that matches your equipment or process becomes a question at your sites within days: do we have this exposure?
InvestigationsComparable incidents appear during an investigation, with their causes and fixes. A team that knows the same mechanism has occurred eleven times elsewhere investigates differently.
TrainingThe lesson is attached to the step it explains, so the reason for a procedure is a real event, which people remember in a way they never remember a policy.

Bulletin effectiveness

A bulletin is closed, then kept closed

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.

  1. Matched on arrivalThe bulletin is matched against the equipment you hold. Where it applies, it becomes a requirement with an owner and a due date.
  2. Closed with evidenceThe work order, the revised procedure or the part fitted is recorded as proof it was done.
  3. Checked in the fieldA bulletin closure audit confirms the change is still in place and working, rather than accepting the paperwork.
  4. Kept as the whyThe bulletin becomes the recorded reason for every step it changed. Anyone who later proposes to change that step meets the bulletin first, so nothing is changed back without knowing why.

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 method, not a document repository

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.

Every step carries its why

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.

One source, no drift

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.

Five checks before anyone looks at the person

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.

Audits built on criticality

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.

Investigations that reach the system

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.

The Safety Outlook for leadership

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

One connected record, and what each person gets from it

For the person doing the work

Know why, not just what

  • Every step says what it protects you from, in plain words.
  • A real lesson from your industry attached to the step it relates to.
  • Procedures meant to be right, and a quick way to say when one is not.
  • A free, permanent way to report a hazard or a near miss, and to see what happened with it.
  • Audits about the work, not about you.

For the supervisor and trainer

Teach from one source

  • Training that matches the procedure because it is built from it.
  • Who is current, who is due, and who last actually did the task.
  • Checklists that reflect the work as it is really performed.
  • Findings that point at the cause instead of at a person.
  • Calibration against other trainers, on the same demonstration.

For the safety and quality lead

See the whole chain

  • One set of requirements, with coverage shown honestly, gaps included.
  • A flag the moment a source changes, so nothing goes quietly out of date.
  • Five audit types sharing one library of audit criteria.
  • Every temporary workaround declared, visible and time-limited.
  • An incident elsewhere in your industry becomes a question at your sites within days.

For the executive and the board

Defend every dollar

  • A ranked view of where a person is the only barrier to a serious outcome.
  • Options shown with your own costs, ranked by the protection they add.
  • Evidence behind every line, ready for a board, an insurer or a regulator.
  • What is bypassed right now, across every site.
  • Expertise kept in the system when people move on.

Where this applies

The same gaps in every industry. Only the vocabulary changes.

Amusement and water parks

ASTM F24 · state ride authorities · manufacturer manuals

  • A pre-opening checklist printed two rehabs ago, missing the restraint step added since.
  • A new ride control system, with a training video that still shows the old screens.
  • An evacuation procedure practiced twice a year and never audited at night.

Hospitality and resorts

Fire · food safety · aquatics · general industry

  • A pool chemical sheet in the pump room that the current SDS has superseded.
  • A new dishwasher with a different dosing system, and training that describes the old one.
  • A fire pump test done annually by a contractor and never witnessed by the property.

Manufacturing and automotive

OSHA 1910 · ISO 45001 · IATF 16949 · PFMEA

  • A work instruction older than the last PFMEA revision, with a torque value that has since changed.
  • New end-of-arm tooling that moved a lockout point, and training that teaches the old sequence.
  • An annual die change on the large press that nobody has observed.

If your operation runs on procedures, manuals and people who know the work, the same method applies. Ask us about yours.

Pilot sites

Start with one site

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.

What you get in 90 days

  • A scored gap assessment across documentation, training, audit history and incident data.
  • The diagnostic sequence run on your highest-consequence processes.
  • One critical process rebuilt end to end: procedure, training and audit checklist, aligned to source and checked in the field.

What we ask of you

  • Access to your existing documentation and records.
  • Two of your subject-matter experts, part time, as the owners of the work.
  • An honest decision at day 90: expand, or walk away.
Led by a founder

Every engagement is led personally by a founder, on your site, with your people.

Priced per site

Pricing follows the size of the site, with everyone at the site included. No per-user licenses.

Yours to keep

The work is designed to transfer ownership to your team, not to make you dependent on ours.

Who you would be working with

Two operators, not two salespeople

Founder · Amusement, hospitality and recreation

President and Chief Executive Officer

  • Three decades running safety and operations programs at global scale
  • Direct relationships in the ASTM F24, IAAPA and NAARSO communities
  • Author of the Predictive Improvement Process
  • Leads every engagement personally

Co-Founder · Manufacturing and automotive

Chief Operating Officer

  • Degreed engineer with an MBA
  • Lean, cost reduction and continuous improvement
  • Anchors the manufacturing and automotive practice
  • Brings the operational excellence half of the model

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

Questions companies ask us

About WSA

What does WSA do, in one sentence?

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.

Who is WSA for?

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.

How is this different from EHS or safety management software?

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.

Is this a document management system?

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.

Will this replace our safety team or our consultants?

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.

How the platform works

Does the system make safety decisions for us?

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.

How does the platform know which requirements apply to us?

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.

Does it use AI?

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.

What happens when a standard or a manufacturer manual changes?

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.

We don't have a hazard analysis or job task analysis. Can we still use it?

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.

How do audits work?

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.

Does it work where there is no signal?

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.

Can our employees report hazards and near misses?

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.

Do we have to replace our current safety, training or document systems?

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.

Pilots and pricing

Is the software available today?

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.

What does a pilot involve?

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.

What does a pilot cost?

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.

How is the platform priced?

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.

What happens at the end of a pilot?

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.

Data, security and legal

How is our data protected?

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.

Can an investigation be kept privileged?

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.

What happens to our data if we stop?

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.

Does WSA give legal or regulatory advice?

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.

Working with us

Who will we work with?

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.

Can our people become certified auditors?

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.

Do you work outside the United States?

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.

How do we start?

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

Tell us about your operation

Whether you are considering a pilot site or have a question, we reply personally.

Send us a note

Fill in what you can and select Send. Your note comes straight to us.