The missing step
A required step that never
happened at all.
PROCEDURE & SOP ASSURANCE
Behaviour proves
the process.
Turn one critical procedure into a live tripwire — and know
the moment a required step is missed, delayed or done out of order.
Procedures are written.
Behaviour is the evidence.
Starts with the procedures that leave a trail in Google Drive.
Checklists are written before.
Audits happen after.
The procedure is clear and your people are careful.
The form gets signed, the checklist gets ticked,
the record gets filed.
Then one shift, under pressure, a required step is
skipped or done out of order. The paperwork still
looks right. Nobody finds out until the audit —
or until it matters.
TripWyre watches the behaviour the procedure
actually produces, and raises an exception while
there is still time to act.
It learns what a
completed procedure looks like.
One critical procedure, chosen with you. TripWyre learns the rhythm of the steps that leave a trail —
what happens, in what order, and how long it usually takes.
The wrong order
Steps done out of sequence, or
far faster than the work takes.
The unexpected hand
The procedure run by someone
or somewhere it never runs.
This is not
staff surveillance.
TripWyre watches a defined procedure, not people. There is no screen recording, no keystroke logging, no productivity scoring and no idle-time tracking. It cannot tell you who worked hard today — only whether the steps that keep people safe actually happened.
One procedure at a time. You choose what is watched, and everything else is left alone.
Exceptions, not reports. Silence when the process runs; a plain-English alert when it doesn't.
Evidence, before the audit. A record that the process ran, held as it happens rather than reconstructed afterwards.
Start with one procedure.
Connect the record
A normal secure Google sign-in.
No agents on machines, no rollout
to your team.
Choose the procedure
The one where a missed step
hurts most — and the observable
events it should produce.
Get told, not filed
A plain-English exception reaches
a named person in time to do
something about it.
Priced per procedure,
not per programme.
Indicative pricing while we scope our first procedures.
The first one is agreed on the call — there is no self-serve checkout here on purpose.
Single site
A$149 a month.
One site and one critical
procedure, watched continuously.
Multi-procedure
A$399 a month.
Several procedures on one site,
more alert recipients, and a
reviewable record of exceptions.
Enterprise
Custom
Multiple sites, specific reporting
and security review requirements.
Straight talk before you spend an hour with us.
TripWyre monitors procedures that leave an observable trail in files — today, in Google Drive. Procedures that live in a machine, on paper, or inside another system are not connected yet.
So the honest first question on the call is whether your procedure leaves a trail we can see. If it doesn't, we will say so rather than sell you a pilot. It is also exception monitoring, not workflow automation — it will not run the process for you.
Submit one critical procedure.
Tell us the procedure where a missed step hurts most. We will look at whether TripWyre can see it, show you the engine firing on real activity, and give you a straight answer either way.
No slide deck, no obligation, and we will tell you plainly if TripWyre is not the right fit yet.
Straight answers.
Including the ones we'd rather you heard from us first.
We already have a quality or safety management system.
Keep it. TripWyre is not a QMS and does not replace one — it sits on top and watches a few critical steps as they happen.
Your system holds the procedure. TripWyre tells you when the behaviour around it stops matching.
Our staff follow procedures.
Almost always, yes. This is about the exception — the shortcut under pressure, the step done out of order, the handover missed at the end of a long shift.
It is aimed at catching those early and holding evidence that the process ran, not at implying distrust of the people running it.
We want the system to run the workflow for us.
Then this is the wrong product and we will say so. TripWyre monitors exceptions on defined events; it does not automate work.
Can you read our documents or our clients' data?
No — and not merely as a promise. Connecting grants exactly two read-only permissions: see file names, and see the activity record. Permission to open a file is never requested, so it can never be used.
That matters if you hold client, patient or legal material: we can help you supervise it without ever seeing it.
What do we have to install?
Nothing. No agents on machines, no network changes, no rollout to your team. It connects on the Google side and keeps working with every computer in the business switched off.
How mature is this?
The detection engine is live in production today, watching real file activity and alerting a human within seconds — you can watch it fire in the demo.
This edition is in early access: we are deliberately taking a small number of organisations so each one gets a real conversation and helps shape what we connect first. Patent pending on the underlying method.
Who is behind it?
TripWyre was invented by Australian inventor Ric Richardson, who holds more than 200 patents. It is commercialised through Deadbolt Cyber Holdings.
Prefer to just ask a person? Email max@mail.ricricho.com and a human will answer.
Your SOP exists.
Can you prove it happened?
Start with the one procedure that would hurt most if it were skipped.
Submit a procedure