Turquoise Dream

The public website was designed as more than a booking page.

Dive programs, dive sites, marine life and editorial content give prospective divers the context they need before choosing an experience.

That also gives Turquoise Dream a structured public presence around the subjects people are already searching for when planning a dive trip to Neil Island.

Instead of discovery ending with:

"Message us for details."

the website can carry the customer from research into an actual booking journey.

The medical questionnaire was treated as part of the safety workflow rather than administrative paperwork.

Each diver completes their own screening as part of registration. The questionnaire follows the established recreational diver medical screening structure, including conditional follow-up questions.

Where an answer requires medical evaluation, the workflow can move into physician clearance rather than allowing the issue to surface for the first time at the dive centre.

A diver can share a dedicated review link with their physician. The physician can review the relevant information, provide an approval or rejection and sign electronically, with the outcome returned to the diver.

Why it matters

For a customer travelling to an island to dive, discovering a medical clearance requirement before travelling is materially different from discovering it on dive morning.

One booking can represent several people, but medical readiness belongs to the individual.

The system therefore separates the commercial booking from each participant's preparation.

The lead customer can choose the experience and dates, while each diver completes their own details and medical screening.

That turns a group booking from one record with paperwork attached into a clearer view of who is actually ready to participate.

The checkout was designed so pricing does not depend on values supplied by the customer's browser.

The system retrieves the plan price and calculates the relevant booking amount, GST, advance and applicable fees before the payment order is created.

Payment confirmation then becomes part of the booking record rather than another transaction the team has to reconcile manually.

The same principle continues inside the operational system: pricing and completed payments determine what remains due.

The internal system was designed for the reality that staff may be working from a phone rather than sitting behind a reception desk.

Instead of manually copying every field from a customer conversation, the operator can paste the WhatsApp enquiry into the system.

The relevant customer, contact, party, plan and date information can then be turned into a structured booking.

From there, the team can share the customer's registration link back through WhatsApp.

Conversation → Booking → Diver registration → Medical readiness → Payment → Dive schedule

The workflow becomes connected without asking customers to abandon the communication channel they already use.

A booking being confirmed doesn't necessarily mean every diver is ready.

The operational view brings the important pieces together so the team can see the booking, participants, schedule, payment position and completion status without reconstructing the situation from messages and paperwork.

The weekly schedule surfaces diver readiness alongside the operational information the team needs for upcoming dives.

Instead of discovering missing information when customers arrive, staff have a way to identify it earlier.

The internal experience was built mobile-first because that's where the work actually happens.

Plans can have variants. Bookings can contain multiple divers. Payments can happen in stages. Staff need week and month views of what's coming up. Customer records need to remain searchable even as the database grows.

These weren't treated as separate admin features.

They were designed as parts of the same operational workflow — giving the team one place to move from an incoming enquiry to the information they need on dive day.