The morning is already full
Several departures start close together. Courses and shore dives run in parallel. A course needs its instructor and available places. One guide calls in sick, and a walk-in asks for five places.
The question is not whether software can draw a calendar. It is whether the plan shows the consequences while your team can still act.
One week, one operational view
Activities carry departure time, dive site, boat or vehicle, bookable dive types and capacity. Guests and guides are assigned to groups inside the activity. Daily notes keep maintenance, meetings and local context beside the day they affect.
Guide availability has more than two states
Regular schedules, approved absences, freelancer availability and existing assignments all contribute to the planning board. Reception can toggle a guide’s presence for one day directly on the week. Multi-day records remain deliberate manager actions.
If a guide becomes unavailable, HALIBLU warns on every affected activity. It does not silently rearrange your operation.
Courses stay connected to the dives they require
Course templates provide the structure. Reception creates a course, assigns an instructor, enrols participants and schedules its required dives. The course remains one object while its dives become part of the daily operation.
Walk-ins still get real places
Reception can block several seats on a specific activity with labels such as “Joe’s friend” before the full profiles exist. The names remain visible in the reservation book and activity board instead of turning into anonymous “Guest 1” rows.
What reaches the next step
The group knows its divers, guide and dive type. Equipment preparation and billing can use that structure without rebuilding the day.