Questions worth answering before the event.

Stop assembling them by hand. In Protée OS the brief is generated from the event you've already built — the vendor receives the elements with your quantities and images, the moodboard for their zone, the floor plan with their position marked, and every date and time from tenancy in to bump-out. You press one button and nothing is typed.

Most brief errors are not carelessness. They happen because someone rebuilds the brief manually from four sources, at 6pm, for the fourth vendor that day. Remove the rebuilding and you remove the errors.

The Quote Hub puts the returned quote beside the brief you sent, side by side. You asked for 200 white Ghost chairs with no arms; the quote is for 200 armed Ghost chairs. You see the difference on a screen two weeks out instead of at 6am on the day when the truck arrives.

Confirm the quote and the price flows to your scope of works and your budget automatically.

Yes — stop treating it as a document. In Protée OS the runsheet is a view of your event, not a file written about it. Assign a vendor or crew member to an element and they appear on the schedule with what they are doing, when, and who to call. Change a time once and everyone holding that record has the change.

There are three: a read-only automated runsheet for quick reference while you build, a live runsheet for what happens during the event itself, and the full schedule your site runs on.

Upload the floor plan — a CAD drawing or a sketch on paper — and drag zone pins onto the space. Each vendor’s brief goes out with the plan and their zone marked on it.

That is Zone Architecture underneath: every event space, whatever its size or shape, resolves to the same set of zones. Map it once and you control what happens where, who does it, and when. It is the part of the platform that is patent pending.

It already is. Your scope of works is generated entirely from your build — every element, who is responsible for it, and once the quote is confirmed, the price against it. It is read-only, because anything you can type into can disagree with the event.

The part you will use most: two weeks out, one screen shows you what is still unconfirmed and who to chase.

Your elements populate the risk assessment automatically, so it reflects the event you are actually building rather than the one you were building a month ago. You add the initial risks, set likelihood, choose control measures and log residual risk. Then download and share it with whoever needs it.

To be clear about what it does not do: it is a starting point, not a risk-management solution, and it is not advice. It does not remove risk and it does not make you compliant. You remain solely responsible for work health and safety at your event, under the laws that apply where the event takes place.

What it does is make sure the assessment matches the build, the controls sit against the right elements, and the person responsible is named.

Add your team once — staff, contractors, casuals — and they are available on every event on your account. Assign to a phase, finalise the shift, generate a payroll report for accounts.

Each crew member has their own portal where they add availability, upload licences, tickets and qualifications, and see their upcoming shifts. You stop chasing documents by text message; they stop asking what time they are on.

Worth saying plainly: the documents are collected and visible to you. Protée OS does not verify them or block anyone from being assigned. That judgement stays with you.

Every guest has a free Live Guest Portal. Timing changes push automatically, and you can share the live runsheet directly with them. Everyone hears it at once, from you, rather than from each other.

Guests also carry their tier and requirements — VVIP, VIP, speaker, sponsor, standard, plus wheelchair seating, baby seats and dietary needs — through from RSVP to the seating plan. Move someone from table 10 to table 2 and all of it moves with them.

No. Receiving briefs, quoting and working with you through Protée OS is free for vendors, always. They get their own portal with no seat, no subscription and nothing to learn.

Vendors can choose to pay to be promoted — appearing higher in search results with an enhanced profile — but that is paid placement they opt into, marked as promoted wherever it appears. It has nothing to do with working with you.

Venues, crew and guests are free too, each with a portal built for their part of the job. You only pay for your own team. That matters because everything they send comes back into your event record instead of sitting in an inbox.

No. The free trial is 30 days with no credit card, no call and no demo required first — you sign up and start.

Thirty days is deliberate. An event build runs over weeks, so a two-week trial only lets you click around. Thirty days is long enough to run a real event start to finish — source your venue, brief your vendors, compare the quotes, build the runsheet and scope of works, and get to bump-out — before you decide whether to pay for anything.

The trial covers one event and one user, with every feature included. Nothing is deleted when it ends; pick a plan and carry on where you left off.

They receive a complete brief they can quote from immediately, rather than four emails asking for the floor plan and the dock times. A brief that is easy to quote gets quoted faster, which is the reason vendors engage with this at all.

They do not need an account to respond. If they want to build a profile so other agencies can find them, that is their choice, not a condition of working with you.

Vendors who complete a profile get checked, and the result is shown on their profile. We run an ABN look-up, marked with a Verified pill when it passes, and a BSB look-up, marked either Bank Validated or Bank Not Validated. Their insurance documents and contact details sit on the same profile, so you can see exactly what they have provided before you assign them anything.

That Bank Not Validated result is deliberate. Most platforms hide a failed check — we show it, because you should know before you send anyone money.

Verified profiles also carry average response time and average quote value. Read those as a signal rather than a price: the average spans jobs of every size.

To be clear about what the checks are: a convenience, not a guarantee. We do not vet or endorse vendors or venues, and you should still satisfy yourself about anyone you engage.

Everyone on your account can see every event on the Team Dashboard, with its location and its owner. Only the owner edits. One live source of truth, and it stays that way.

Outside your team, access is scoped to the job. A vendor sees their brief and their zone. They do not see your budget, your client, or your other vendors.

No. We do not process, hold or make any payments between you and a vendor, venue or anyone else.

Treasury tracks what you have committed, what you have paid and what is outstanding, so your budget stays accurate without anyone maintaining it. Where vendors have provided payment details, those are stored encrypted and never displayed in full — they are there so you can generate a bank file for your own bank or create bills in your own accounting software. You make the payment, and you are responsible for checking the details before you do.

Quotes and venue contracts extract into Treasury in a click, which means the number in your budget is the number on the document.

Your event data is stored in Sydney. The platform is delivered through a global edge network and some transactional services route internationally, so cached assets and notifications may pass through servers outside Australia — your event records do not.

Nothing is deleted the moment you cancel. For 90 days after termination you can request a copy of your data.

Your events, your client list and your vendor relationships are yours — you keep ownership of everything you put in. We do not sell your data or share it with other accounts. We may use anonymised, aggregated data to improve the platform, as set out in our terms.

No — it is built for the opposite. Most event platforms are designed around registration and delegates, which suits conferences and not much else. Protée OS is built for the build: the vendors, the zones, the load-in, the scope of works and the crew.

If you are running a conference, the two are not in conflict. Your registration platform handles delegates; Protée OS handles everything that has to be constructed before they arrive.

Yes. A run sheet is a run sheet, a dock has a time on it, a vendor needs a spec. The constraints do not change between Las Vegas, Sydney and Auckland — the scale and the paperwork do.

Vendor and venue search works in any city, and nothing in the architecture assumes one country’s way of working. Protée OS launched with design partners across Melbourne, Brisbane and New Zealand for exactly that reason.

One thing that is on you rather than us: wherever you are planning from, you are responsible for the permits, licences, insurance and safety requirements that apply at the physical location of your event.

The logic is not AI. Every rule in Protée OS came from 23 years on event sites, and it is written down rather than generated.

AI does a few specific jobs where it is genuinely better than a person: extracting a palette and elements from an inspiration image, parsing documents, comparing a returned quote against the brief you sent, and finding publicly available contact details.

It does not decide how your event gets built, what belongs in which zone, or who is responsible for what. And like any AI it is not infallible — check anything critical before you act on it.