Before an ISO audit
Hundreds of work instructions are digitised. The “who read this instruction” report the auditor asks for is produced from one screen.
Instructions and policies live in one library, versions are tracked, and who read and acknowledged what goes on record. The evidence an auditor asks for comes out ready.
What this runs on today

Procedures
It all comes together in one module.
Entered from the same screen, tracked from the same place.
The three situations we run into most often. If one of them sounds familiar, we have something to talk about.
Three copies of the same instruction are circulating; on site, nobody knows which one is up to date.
The procedure was announced but who read it is not recorded. When an incident happens, responsibility stays arguable.
Documents and signature sheets are gathered for days before an audit; some are never found at all.
Every item is a real screen or flow in the product; we walk through them one by one in the demo.
Every procedure, instruction and policy is collected in one searchable library; existing documents are uploaded in bulk.
Every update is versioned; old and new versions are compared, and you can roll back when needed.
A new or updated document is not published until it has passed the defined approval flow.
The employee confirms they have read the document; it is stored with the date, time and user record.
Documents are tagged; which department or position can see each one is defined separately.
Who read which document, at which version, and when — produced as a report ready for audit.
Once it is set up, every period runs in the same order, and most of the steps happen on their own.
Existing files are transferred in bulk; the content is converted to searchable text.
The relevant managers review and approve it, and a version number is assigned.
Employees in scope get a notification and can read it on mobile.
Whoever confirms goes on record; reminders go to those who have not read it.
The same data is entered once. What this module takes in and produces is below — you do no extra work to move data between modules.
Takes the data in once and shares the same record with the other modules.
Not promises with numbers, but real setups. Let us go into the one closest to yours in the demo.
Hundreds of work instructions are digitised. The “who read this instruction” report the auditor asks for is produced from one screen.
The same service standard applies at every hotel. Updates are published centrally, and read acknowledgements are tracked separately at each location.
When the protocol changes, the new version is re-sent to everyone who read the old one; the risk of working to an outdated instruction closes.
A demo is not a presentation: we build your scenario and run it on screen. You leave with a written proposal covering scope and timeline.