About Livel

Designed in the pre-admission clinic, not a product workshop.

Livel began as a spreadsheet kept by a specialist anaesthetist trying to stop the same nine problems recurring on every list. The product is that spreadsheet, made rigorous and shared with the rest of the team.

A clinician working through a case list with a colleague

An advisory group, not a focus group

Surgeons, pre-admission nurses and schedulers see each build before it reaches a patient list.

Recurring problems logged

the same nine, list after list. That list became the product backlog.

Narrow on purpose

We own the four weeks before surgery. Everything outside that window gets declined.

01 — Founder

A clinician who still runs the pathway.

Livel was started by a specialist anaesthetist and perioperative medicine physician practising in Australian public and private theatres. Every design decision has been tested against a real clinic list before it was built.

—

Specialist anaesthetist, FANZCA

—

Perioperative medicine physician, practising in Australian public and private theatres

—

Designed and ran a structured pre-admission pathway before writing a line of software

—

Building with an advisory group of surgeons, pre-admission nurses and schedulers

Founder named on request ahead of public launch.

The patient-side history, one question at a time, as it was first sketched on a clinic list

“Every anaesthetist has met the patient who should have been optimised four weeks ago. The information was almost always there.”

Founder · Specialist anaesthetist & perioperative physician

02 — How we build

Four commitments we will be held to.

Clinician-led, not clinician-consulted

The person deciding what gets built has run the clinic that week. Advisory input is real, not decorative.

Narrow on purpose

We own the weeks before surgery. Everything that tempts us outside that window gets declined.

Say which numbers are measured

Modelled figures are labelled modelled, everywhere, including in a sales conversation.

Nothing that cannot be audited

If a prompt cannot show its inputs and its reasoning, it does not ship.

03 — Where this goes

A national standard for arriving prepared.

Start with the four weeks before surgery in one service. Then make that window measurable, comparable and improvable across every service that wants it.

Now

Single-service pilot

One elective pathway, one health service, measured against its own baseline.

Multi-site readiness

Shared instruments across services so readiness can be compared, not just recorded.

Then

Pathway intelligence

Where optimisation fails, by cause — feeding back into how lists are built.

Later

Open standard

A common perioperative readiness dataset that other systems can read and write.

04 — Get involved