Risk, compliance and safety, configured your way

Plans, registers and documents, generated for every project and site.

We built Obliwise after years of rewriting the same safety plans, registers and documents by hand for every new project, site and client. Now the work is recorded once, in one place, and the paperwork writes itself from it. Start with the one job you need done, or run all of it.

Book a demoFind your solution
The Obliwise home screen for a builder with three projects: 24 plans generated, 142 people on site, 6 live permits and 9 actions due; a list of what needs attention today, led by a project safety plan ready to approve; how many plans are current on each project; what is due this week; and what happened most recently.

Set up once, produced for every project and site

You set a plan, register or document up once as a template. From then on the platform fills it in for each project, site or client from the records your people already keep, and produces it when it is due.

  • Filled in from the record

    Each field on the template reads from the record, your organisation's details or a saved register view. Sections appear only when the record needs them, and tables grow with it.

  • Produced when it's due

    From the record, at a stage in a workflow, on a schedule, or for many records at once, then published into your document library under version control.

  • Standard wording written once

    Policy statements and legal clauses are held as approved, controlled wording. When a new version is published, the templates still using the old one tell you.

See how plans and documents write themselves.

Start with the job you need done

Each of these works on its own. If visitor sign-in or contractor management is all you need, that is all you buy. Add anything else later, only if you want it.

Also sold on its own:

Set up for the way your industry works

Each industry page shows the parts people in that industry use most, with a worked example.

The workflow chases the follow-up

When a record changes, the workflow raises the actions, tells the owners, books the reviews and escalates anything that runs late. Each step is recorded on the record, so you can show what happened and when.

  1. Someone reports it

    From a phone, a tablet or a desk. With no signal, the report waits on the device and sends when there is.

  2. The action goes to the right person

    Your workflow names who gets it. It lands in their own work list with a due date.

  3. Late work is escalated

    If an action runs overdue, the person accountable for it is told. Nobody has to notice.

  4. Sign-off comes with proof

    A record closes when your workflow's conditions are met and someone approves it. The evidence stays attached.

Follow an incident from report to close.

Report it whichever way suits the moment

Nobody should have to find the right form. An incident, a hazard or an observation can come in from wherever the person is, and the platform does the sorting.

  • From a phone, a code, an email or a link

    A form on a phone or tablet, with or without signal. A QR code on the wall that opens the form with no login. An email sent to an address you publish. A link sent to a contractor. An anonymous report with a tracking code for a two-way conversation. Each one lands in the same register.

  • Or just tell the assistant what happened

    Describe it in your own words. The assistant drafts the report, suggests the incident type and severity from how you describe it, and asks only for what's missing. Every suggested value is marked as suggested until you confirm it, and you stay the author of record.

  • It brings the context with it

    When an investigation opens, the platform pulls in what it already knows: the permits active at that time and place, who was signed in, the risk assessments in force, the equipment's maintenance history, earlier events at the same location, and the weather at the time. It can check the account against your own procedures and point to where the work departed from them. The investigator decides what that means.

Requirements written as rules, each with its source

The obligation engine watches your records and raises a duty when a rule says it's time. We've written packs of these rules for the places we cover, and you can write your own for anything else you have to meet. Here's a licence rule, as your team would see it.

The rule

Anyone operating a forklift holds a current high risk work licence for that class.

Applies to
Every worker or contractor assigned to a task or permit that involves forklift operation in Queensland
Source
Work Health and Safety Regulation 2011 (Qld), section 81 and Schedule 3, licences for high risk work
What it watches
The licence class and expiry on each person's record, and the tasks and permits they are named on
What it raises
A duty to renew, owned by the person you name, at the point you set before the licence expires, and a flag on any task or permit that names someone without a current licence

Installed switched off. Someone in your organisation reads it and turns it on.

The packs are a starting point, not legal advice. Your organisation stays responsible for its own obligations, and every duty the platform raises says so. See what's ready-made for where you work.

Ready to use, yours to change, and never on your own

  • A library to install from

    Inspection checklists, pre-start checks, permit types, toolbox talks, training courses, risk assessments and contractor requirement profiles. Install what suits you in one click, then change it however you like.

  • Builders your own team can use

    Forms, modules and workflows are built in one visual workspace. Add fields, set the rules, arrange the screen and preview it before anyone depends on it. Every published version is kept, so you can roll back. See how changes are made.

  • And us, whenever you want a hand

    Buying the software isn't where we stop. We set up your workspace with you, load your forms and registers, configure the workflows and rules for how you work, train your people and stay on hand afterwards. Do as much or as little of it yourselves as you like. Either way, the platform is yours to change.

Your data

  • Hosted where you need it

    We host in any AWS region. Sydney, Ireland and Northern Virginia are standard, and other regions are available on request.

  • AI you control

    AI features are optional. You choose which ones are on, a person approves each draft, and AI can run inside your hosting region.

  • We say what we hold

    We publish every provider that may handle your data, and we'll go through your security questionnaire with you, answers on screen.

Read about trust and security.

Who's behind it

We spent our careers putting management systems in place and running them inside organisations. Obliwise is the platform we wanted then: set up on day one, changeable by our own team, and honest about what it does.

Read our story.

Questions people ask us

Can we change the forms and workflows ourselves?

Yes. Forms, modules and workflows are built in a visual workspace. You can preview a change before it goes live, publish when you're ready, and roll back to any earlier version. And you're not on your own: we'll build it with you, or for you, whenever you ask.

Do you help with setup and configuration?

Yes, as much as you want. We run the setup with you, bring your existing forms, registers and requirements across, configure the workflows and rules, and train your team. After that we stay available for changes, new modules and questions. Plenty of customers end up doing most of it themselves because the builders make it easy, and that's fine too.

How long does it take to get going?

You can be recording on the first day. Every module is ready when your workspace is created, and a guided setup walks you through each one you switch on. The template library gives you checklists, permit types, courses and contractor requirements to install in a click. Your existing registers come across through imports that give you the template, a filled sample and a preview of every row before anything is saved, and paper forms can be read into digital records with a person checking each field. Your people can sign in with the accounts they already have. A first module is usually up and running the same day, with us alongside you for as much of it as you want.

Where is our data stored?

On Amazon Web Services, in the region you choose. We can host in any AWS region, and your data is kept separate from every other customer. See the trust and security page.

Does it work on a phone, and without signal?

Yes. People use it on a phone or tablet, in the browser or in the iOS and Android apps, and it keeps working without signal. Anything entered is queued and sent when the connection comes back.

What does it cost?

Team is AUD 39 a user a month (billed annually) from 5 users, Business is AUD 29 from 25 users, and Enterprise is by quote. Every module is in every tier, and visitors and kiosk sign-ins are free. If you only need one module, you can buy that one on its own. See the pricing page.

Want to see it on your own paperwork?

Bring a form or checklist you already use. We'll rebuild it in Obliwise with you, connect the workflow and show you the follow-up as it happens. That's how we work with every customer, from setup onwards.

Book a demoSign in