Risk you can proveyou managed.
Your elements populate your risk assessment automatically. You set the controls. Everything is documented, owned, and shareable with whoever asks for it.
THE PROBLEM
The risk assessment gets written last, by whoever's left.
Everyone knows it has to exist. It usually gets built the week of the event, from a template, by someone reconstructing what's on site from an email chain — which means it describes an event that's already changed.
A risk assessment written from a stale list isn't managing anything. It's paperwork.
HOW IT WORKS
Built from what's actually in your event.
Your elements populate the assessment
Every element you’ve allocated to a zone appears in your risk assessment automatically. No transcribing from a spreadsheet, no missed items, no version that predates last week’s change.
You set the controls
Add the initial risks from the list, assign a likelihood, choose a control measure, log the residual risk. It takes minutes because the hard part — knowing what’s on site and who’s responsible for it — is already done.
Download and share
Send it to the venue, the client, your crew, or whoever’s asking. One document, current as of your build.
DOCUMENTS
Upload once. Available everywhere.
Insurance certificates
Public liability and workers compensation certificates are uploaded once and available to every user on your account, for every event. Send them to the venue with one button instead of digging through email.
Venue contracts
Venue contracts live here too — stored, extractable to Treasury, and findable at 5am when someone asks what was agreed.
Vendor Checks
Know who's coming to your site.
Vendors who complete a profile in Protée OS become verified: ABN checked, BSB verified, insurance documents and contact details on file. You can see what they've provided before you assign them anything.
WHAT THIS IS, AND WHAT IT ISN'T
Protée OS doesn't remove risk and it doesn't make you compliant. No software can do either.
What it does is make sure the assessment reflects the event you're actually building, that the controls are recorded against the right elements, that the person responsible is named, and that you can produce all of it when someone asks.
That's the difference between managing risk and filing a document about it.
Written by someone who's been the person responsible.
23 years in event production, including years in event security and venue operations. This was built by someone who has stood on a site knowing the paperwork didn't match what was in front of him.