A short, repeated routine beats a clever one. Here are five checks that many crews run in some form. They are not new, and they are not a standard.

A note before we start. This is general good practice written by a software team, not a training course and not medical or legal advice. Your training agency’s standards, your operator’s procedures and the rules where you dive come first. Where they differ from this post, follow them.

1. Count the people

Count the divers who are on the boat, and compare the number with the list. Do it out loud, with a second person if you can. A headcount done by one tired person from memory is the check most likely to be wrong.

Do the same count again when the boat leaves the last stop, and again when everyone is back on board. The number you start with is only useful if you can compare it with the number you finish with.

2. Paperwork and medicals

Before anyone gets in the water, the waiver and the medical form should be done, and someone should know the answer for each diver. Not “I think so”.

Keep it private

A medical form is private. The crew usually needs to know a status, such as complete or needs review, and not the answers. Decide who can see what, and keep the answers with the people who need them.

In DiveHive, waivers and medical forms are signed on the diver’s own phone and kept with an audit trail, and a guide sees the status rather than the answers. That is how we have set it up, and it is only one way of doing it. The principle holds on paper too.

3. Weather and sea state

Look at the sky, the sea and the forecast, and say what you see. Then ask the one question that decides the day: would we be comfortable if this got a little worse?

• Check the local forecast and any official warning for the area.
• Look at the water yourself, not only the screen.
• Agree who can call a trip off, and agree that the call is respected.

Software can flag a risk, but the decision stays with the people on the boat. DiveHive marks trips when a warning applies and leaves the decision to the shop. Where no official warning feed exists for an area, check the national service yourself, and never read the absence of a warning as a sign that the sea is fine.

A forecast tells you what the sea may do. The look of the water tells you what it is doing.

4. Equipment

Each diver’s kit should be assigned, checked and on the boat. For rental kit, that means sizes matched to the diver before the boat leaves, not discovered at the dive site. For tanks, it means the right gas and the right amount, confirmed by the person who filled them.

A few things are worth looking at every time:

1. Regulators and gauges are with the right diver’s kit.
2. Oxygen and first-aid equipment are on board and within reach.
3. Radios or phones work, and the person who carries them is named.
4. Spare equipment is stowed where it can be found.

5. The manifest

Last, know who is on the boat, where it is going and when it expects to be back, and make sure someone on shore holds the same information. If something goes wrong, the first useful question will be where the boat is and who is on it.

What a manifest has to contain, and who has to receive it, depends on where you operate. Some places require one and some do not. Find out what applies to your operation and follow it.

Making it a habit

Write the five checks down, put them where the crew will see them, and say them every time. The first week it feels slow. After that it takes two minutes, and nobody has to remember anything.

DiveHive shows a pre-departure check in the console so the same list is in front of the crew for every trip. You can read how it works under waivers and safety and on the trust and safety page. But a laminated card on the boat is a perfectly good version of the same idea. What matters is that the checks are done, in the same order, every time.

Taken together, those entries are also something else: a set of small observations from people who were actually there. Scientists have always depended on that kind of record. Divers see which animals live where, in which month, and what the water was really like, and very little of it is written down in a form anyone else can use.

What makes a sighting useful

A sighting is only a useful fact if it answers four questions: what, where, when and how sure. A log that says “big fish” answers none of them. A log that says a species, a dive site, a date and a note that the guide confirmed it answers all four.

That is why we care about verification. In DiveHive a dive can be signed by the guide who led it, so the entry is not just one person’s memory. A signed log is a stronger record for the diver, and it is a better starting point for anyone who might use it later.

Good records tend to share a few habits:

1. Log the dive the same day, while the details are fresh.
2. Name the species when you are sure, and say so when you are not.
3. Note the conditions as you found them, not as you hoped: visibility, water temperature, current.
4. Keep the site consistent, so two dives at the same place can be compared.

Conditions count too

It is easy to think only of animals. Conditions matter as much. A run of honest visibility and temperature notes at one site, month after month, tells a story that no single dive can.

Where the data goes

Here we want to be careful, because this is where trust is won or lost.

Open data systems already exist for this work. WoRMS keeps the standard list of marine species names. GBIF and OBIS collect and publish records of where species have been seen. They are real, public and used by researchers around the world. DiveHive uses WoRMS, GBIF and OBIS as sources for its own species catalogue, for names, classification and where a species is found.

What happens to a diver’s own logs is a separate question, and the answer is the diver’s.

• Sharing for research is off until you switch it on, one programme at a time.
• Public pages and research data show anonymous totals from many dives together, never a name or a single dive.
• For the most vulnerable species, public maps show only the wider area, and only after a delay.
• Every species page names where its facts and photos come from.

We are not claiming that your logs flow into any particular database today. When a research partner is signed, we will name it and say exactly what is shared. Until then, the point of the design is simple: your logbook stays yours.

What a shop can do

A dive shop sees more dives in a month than most divers do in a year. A shop that logs sightings and conditions consistently, and that lets guides confirm them, builds a record of its own reef. That is useful for the briefing today, and for the conservation work around the site tomorrow.

DiveHive also lets guides record reef observations on dives where the conservation log is switched on: coral health, threats such as crown-of-thorns starfish, protected species and debris. More about that is on the conservation page, and the diver side is described under For divers.

A small habit

You do not need a new hobby. Next time you log a dive, add the one thing you would want a stranger to know about that site this week. Then ask your guide to confirm it.

That is the whole idea. A good log is a small act of care, and it adds up.

This post is a short list of things to look at and questions to ask. It is not a ranking, and it will not tell you which shop is best. It will help you notice which ones are careful.

A note first. This is general advice from a software team, not training, medical or legal advice. Your dive agency’s standards and the rules where you dive come first, and so does your own judgement about whether a dive is right for you today.

Before you book

Write to the shop with a few plain questions. How quickly and clearly they answer says something already.

• Group size and guides. Ask how many divers go with one guide on the dive you want. Ask whether that changes for a new diver or a night dive. We will not give you a number here, because the right one depends on the site, the conditions and your agency’s standards. Ask what theirs is, and why.
• Your level. Tell them honestly how many dives you have done and how recently. A good shop will ask about it unprompted and may suggest a check dive.
• Paperwork. Ask what you need to bring and sign. A medical questionnaire and a waiver are normal. A shop that can send them to you before you arrive saves you a queue at the desk, and gives you time to read them.

At the shop

Look around before you pay.

The kit

Rental equipment tells you about the whole shop. Look at the regulators, the BCDs and the tanks. Are they clean, labelled and stored properly, or piled in the sun? Ask when the tanks were last inspected and what gas is in them, and ask to see the gauge before you dive. A shop should not mind any of this.

The briefing

Ask how the shop briefs. A good one covers the site, the plan, signals, what to do if you get separated and how divers behave around marine life. You can read what we think a good briefing includes in what a good dive briefing covers. If a shop skips it because you look experienced, that is worth noticing.

Safety gear

On the boat you should be able to see that oxygen and first-aid equipment are on board, and ask where. Ask how the boat communicates with the shop and with a nearby emergency service if something goes wrong.

How they handle weather

Ask what happens on a day with a storm warning. A careful shop has a plain answer: who decides, by what time, how divers are told, and what happens to your booking. If the answer is vague, plan for a day of waiting. If it is clear, you can plan around it. Our post on planning dive trips around storm season covers the same ground from the shop’s side.

A good shop tells you early, and tells you plainly.

How they treat the reef

Watch what the guides do, not what the brochure says. Do they brief the no-touch rule and keep to it? Do they let anyone stand on coral, chase turtles or feed fish? Do they anchor on sand or use a mooring? A shop that looks after its reef is likely to look after its divers.

Where DiveHive fits

If a shop uses DiveHive, you sign its waiver and medical form on your own phone before you arrive, once for that shop. You check in with a personal code, and after the dive the guide’s verified log lands in your logbook, with every other shop you dive with in the same place. DiveHive is free for divers, and you do not need the app to dive with a DiveHive shop: a booking link works in any browser. See for travellers for more. If the shop does not use it, the same checklist applies.

A short list to take with you

1. Ask about group size and guide ratio. Expect a clear answer.
2. Look at the kit and ask about tank inspection.
3. Get the waiver and medical form before you arrive.
4. Ask who decides on a weather day, and how you will be told.
5. Watch how the guides treat the reef.

None of this takes long, and shops that answer easily are usually the shops you want to dive with.

Shops that handle this well do not have better luck. They have a routine for it, which they use before the weather turns, and a way of telling people early.

A note first. This is general good practice written by a software team, not training, and not medical or legal advice. Your dive agency’s standards, your operator’s procedures and the rules where you dive come first.

Know your own season

Start by writing down when your weather is likely to be difficult, using what you and the other operators near you have seen over the years. Seasons differ widely by region, and a calendar from one country says nothing about another. Ask local boat captains, harbour offices and longer-established shops what months and wind directions cause trouble at which sites.

Some sites are sheltered when the wind blows from one side and unusable when it comes from the other. If you know that, you can shift trips between sites before anyone has to be cancelled.

Watch the official warnings

Check the national weather service for the area where you dive, every day in season. In the Philippines, for instance, that is PAGASA, which issues the storm and typhoon bulletins. In another country it is a different agency, with different names for its warnings. Learn who it is, what the levels mean, and where a boat captain or port authority can order boats to stay in.

A few habits help:

• Look at the forecast the evening before and again in the morning.
• Read the official bulletin itself, not a screenshot someone forwarded.
• Look at the sea from the shore. A forecast tells you what may happen, and the water shows what is happening.
• Treat a missing warning as no information, not as good news.

Plan with a buffer

A plan with no slack breaks at the first delay. In storm season it helps to hold something back.

Leave room in the schedule

Keep the afternoon free or lightly booked, so a morning that is delayed can be moved. Avoid scheduling the last boat of the day so late that a short delay puts the return in the dark.

Know your fallback

Pick a second site for each main one, with a different exposure. Decide in advance what you would do with a morning that is too rough for the open sea but fine for a sheltered bay, or for a pool session or a briefing on the marine life.

Decide early and say it clearly

The hardest part of a weather call is not the decision. It is the delay in making it, because everyone hopes for improvement. Agree a time for the decision, and agree who makes it. Then tell divers in plain words, with a time for the next update.

If we cannot be sure by a set time, we decide.

A message that works says what is happening, when you will know more, and what to do now. It is short.

All boats stay in until 12:00. We’ll message you by 11:30.

Avoid long explanations and avoid hedging. Divers can plan around a clear answer. They cannot plan around “maybe”.

Where software fits

Software can watch more bulletins than a person can, and that is where it helps. DiveHive flags trips when an official storm warning applies, so the Board and the app mark affected trips with a warning and link to the official bulletin. It does not cancel anything by itself. The shop decides, and if the decision is to cancel, one action cancels the day’s trips and tells the divers and staff on them. That is a rule we hold to: software flags, people decide.

You can read more under planning and on the Board page, where conditions and storm flags show in the briefing area.

The routine matters more than any tool. Know your season, watch the official source, keep a buffer, decide at a set time, and say it in one clear sentence.

We build DiveHive in Puerto Galera, where this is ordinary, and it shapes what we make. The question we ask is not “what if the signal drops?” It is “which parts of the day cannot wait for it to come back?”

What has to keep working

A dive day has a rhythm that does not stop for an outage. The boat leaves at the same time, divers arrive at the desk, and the guide still has a group of people to brief and count. If we list what needs to work without a signal, it is short.

• Today’s trips. What is going out, when, on which boat and with whom, as last known.
• Check-in. Knowing who has arrived and who has not.
• The log. The guide writing down what happened on the dive, on the boat, before there is a signal.
• The briefing area. The screen where the day is shown, and the briefing itself.

Anything that can wait, such as a new booking request or a report, can wait. The list above cannot.

Offline by default

DiveHive is built so that check-in, group logs, the counter and the Board keep working offline and sync once the signal is back. A diver’s personal check-in code can be scanned at the desk without a connection, and it shows whether the waiver and medical for that shop are done. A guide can write the group log on the boat with no signal at all and let it send later.

Offline queues

When a phone is offline, what you enter is held on the device and synced when the connection returns. Nobody needs to remember what they entered while the signal was down, and nobody should have to type it twice.

Stale since

An offline screen that looks live is worse than a screen with an honest label. So every screen that shows data says how old it is. The Board, for instance, shows a “stale since” mark with the time of its last update when it loses its connection, so nobody reads a four-hour-old schedule as current.

A screen that is out of date should say so.

The Board after a power cut

The briefing area screen is the one most likely to lose power, since it often sits on a cheap PC or a TV that gets switched off at the wall at night. The DiveHive Board is designed to start again by itself after a power cut. It does not need someone to log in or press a key. It shows the day it last knew, marks it as stale if it is offline, and catches up when the signal returns.

It runs as a pure display. It never scrolls and takes no input, so there is nothing to click on when it restarts and nothing a visitor can break by touching it. You can read more on the Board page.

What to do on your side

Software helps, but a shop does better with a few habits. These are general practice, not a promise that nothing will ever fail.

1. Print the day’s schedule in the morning, or keep it somewhere your phone can read without signal.
2. Keep a paper copy of the manifest for each boat, so the people ashore and aboard hold the same list.
3. Agree who calls whom if the network is down, and write the numbers on a card, not only in a phone.
4. Test your setup once. Switch off the router for ten minutes on a quiet day and see what you can still do.

Not everything can work offline. A booking request from a diver, for instance, needs a connection to reach you. The aim is for the dive day itself, the part that happens on the boat and at the desk, to carry on.

Why we start there

Most software assumes a connection and adds offline mode later, if at all. On an island that order is backwards. If the day itself keeps working, the rest can catch up. If you want to see how the schedule, check-in and the Board fit together, the FAQ has a short answer on offline use, and the Board page shows the screens.

All of these work, until they do not. The book is left in a hotel room. The shop you dived with last year changes its software, or closes. A guide’s signature is a scribble you can no longer read. The record of your diving ends up scattered across the places you have dived, and none of them is yours.

What goes wrong with scattered logs

Three things tend to happen.

• The record lives with the shop. The shop keeps a note of your dive, which is useful to them, but you may never see it again, and it does not follow you to the next shop.
• Numbers drift. Dive 150 on paper is dive 147 in a spreadsheet and dive 152 in your head. Nobody can say which is right.
• Trust is hard to check. A stamp shows you were somewhere. It does not show what was done, or that someone who was there agrees.

None of this is anyone’s fault. It is what happens when a logbook is treated as a by-product of a booking instead of something a diver keeps for life.

What a verified log adds

A log is more useful when someone who was on the dive has confirmed it. In DiveHive, the guide who led the dive writes one group log, with the site, the entry and exit times, the depths, the conditions and the sightings. Each diver who was checked in receives a personal copy, prefilled, with the guide’s version marked as verified.

Your own notes stay yours

You can add your own notes, and you can ask for a change, for instance when the depth on your own computer differs. The guide confirms or declines. If you change something yourself, the log shows it as edited by the diver and not verified, so a log never looks verified when it is not. After seven days, the verified log locks.

The point is not to catch anyone out. It is that when you show a log to a new shop, they can see which parts a guide stood behind.

One logbook across every shop

Divers rarely stay with one shop. You dive on holiday, in a different country, with a friend’s club, on a liveaboard once. A logbook that stays with a single shop breaks at the first change.

DiveHive keeps your verified dives from every shop in one logbook that belongs to your own account. You can also log dives that did not happen through DiveHive, and keep the numbering you already have from your paper book. If you move on or change shop, your logbook comes with you. You can export it as a PDF or JSON file at any time, so the record never depends on us being around.

A logbook should outlast any shop, any app and any phone.

You decide what is shared

Owning a logbook also means deciding who reads it. The shop you dive with sees what it needs for the trip: your name, certification, dive count, gear sizes and the notes you choose to share. Medical answers go only to the shop you sign for, and they do not appear on the Board, in notifications or in analytics. Guides see the signing status, not the answers. What other divers can see of you is your choice.

You can read more on the trust page, and on the features for logs and sites page if you want the detail of how a guide writes a group log. The divers page shows what is open today, and divers pay nothing for any of it.

A habit worth keeping

Whatever you use, a few habits make a logbook worth having.

1. Log the dive the same day, while you remember the conditions.
2. Keep your numbering consistent, and write the starting number down.
3. Ask the guide to confirm the log when you can.
4. Keep a copy somewhere other than the phone you take on the boat.

A logbook is a record of your diving life. It is worth the small effort of keeping it in a place you control.

The trouble is not that guides forget how to brief. It is that a briefing given on the thirtieth day in a row drifts. A part gets shortened, then skipped. The fix is an order that never changes, so that nothing has to be remembered.

A note first. This is general good practice written by a software team. It is not training, and it is not medical or legal advice. Your dive agency’s standards, your operator’s procedures and the local rules come first. Where they differ from this post, follow them.

The site and the plan

Start with where you are and what you are about to do. Divers listen better when they can picture the dive.

The site

Name the site and say what is special about it: a wall, a sloping reef, a wreck, a sandy patch before the reef begins. Draw it on a board or show it on a screen if you can. A simple sketch of the shape of the dive is worth more than a minute of description.

Entry and exit

Say how divers get in and where they come back. Giant stride from the boat, back roll from a small banca, a shore entry over rocks. Then say how you get out: the ladder, the line, a pick-up by the boat after a drift. Divers should never have to guess how the dive ends.

Depth and time

Give the maximum depth, the planned bottom time and the turn pressure, in the units your divers use. Say what happens when someone reaches the limit first. The dive ends for the group when the first diver reaches it, not when the guide does.

The group

Next, how the divers move together.

• Buddies. Confirm every diver has one, by name. Pair up the diver who arrived alone before the boat leaves, not in the water.
• Group size. Say who leads, who follows at the back, and where each buddy team swims in relation to them.
• Signals. Check the signals you will use: up, down, okay, low on air, stay close. Do not assume a diver from another country uses the same ones.

Conditions and hazards

This is the part divers remember when it matters, so keep it concrete.

• Current: direction, strength, and where it changes.
• Surge, visibility and temperature at depth.
• Boat traffic and the surfacing plan, including how to signal the boat.
• Anything specific to the site, such as a fishing line or a ledge.

Say the same thing in the same words each time. Short phrases are easier to follow than clever ones.

If you get separated

Every briefing should include this, and none should skip it. The usual practice is simple: look around for about a minute, and if you cannot find your buddy, surface slowly, safely and wait. Your agency or operator may teach a different version. Say yours out loud, and ask the group to repeat it back.

A good briefing is one a diver can repeat to a stranger in thirty seconds.

Marine life rules

Finish with how divers behave around the reef. Do not touch, chase, feed or stand on anything. Keep fins up and off the bottom, stay a respectful distance from turtles and sharks, and take nothing with you. Say it kindly and once. People follow rules more readily when they hear the reason: the reef is slow to recover, and animals that are crowded move away or change their behaviour.

Making it stick

A fixed order helps the guide as much as the diver. Write the eight parts on a card, a whiteboard or a screen, and run through them in the same sequence each time. Ask a question at the end, such as “what is our turn pressure?”, to see whether the message arrived.

In DiveHive, the briefing steps for each site sit on the Board in the briefing area, and the guide moves through them from their phone while facing the group. The Board never needs touching. That is one way to keep the order fixed, and a laminated card does the same job. More on how we handle safety features is on the trust and safety page.

The habit matters more than the tool. Use the same order, say the same words, and ask one question at the end.

We are building DiveHive for that hour. It is a small idea with a lot of detail behind it: the dive day should live in one place that the whole crew can see.

What the dive day needs

A dive day is a chain of small facts. Who is on which boat. Which guide has which group. Whether the waiver is signed, whether the medical form is in, whether the tank fills are done. None of these is hard on its own. The trouble starts when each one lives in a different place.

So DiveHive keeps them together. Trips, boats, guides, waivers, check-in and logs sit in one console, and the same day can be shown on a screen in the briefing area. We call that screen the Board. It is meant to be glanced at, not studied. If the schedule changes, the screen changes, and nobody has to rewrite a whiteboard.

Two things matter to us more than any feature list.

• It has to keep working when the island internet does not. Dive shops are often where the signal is thin. DiveHive is built to run offline and catch up when the connection returns.
• It has to be calm. A tool that adds noise to a morning briefing has failed, however clever it is.

Free for divers, paid by the shop

Every diver gets a logbook that is free. That is not a trial and it is not a teaser. A diver’s logbook is theirs, and the shops that take them out pay for the software that runs the day. Shop pricing is per location, so a shop with one base pays for one base.

We think a logbook behind a fee pushes people back to a notebook. A free, verified logbook that a guide has signed off is more useful to everyone, including the shop that dived with them.

We also built it for more than one language from the start. DiveHive speaks ten languages, because the people standing on a dive boat rarely share one.

One percent for the reef

DiveHive gives 1% of its net revenue to conservation partners every year. We are not naming organisations yet, because we will name partners only once an agreement is signed. When we do, we will say so here.

We think the 1% is the smaller part of the story. The larger part is what divers see underwater every day, and how rarely any of it is written down in a way that anyone can use. We wrote about that in Your dive log can help the reef.

A tool for the dive day should make the morning quieter, not busier.

It is the test we try to hold every screen to.

Where we are

DiveHive is made in Puerto Galera, Philippines, a short walk from the boats it is built for, and that is where it launches first. It is not open yet. The first shops will get a founding offer and help moving over from what they use today. If you run a shop, a crew or a club, the waitlist is the place to start. If you would rather just follow along, the newsletter and the blog’s RSS feed will do.

What we will write about

Expect short, practical posts. How a calm briefing is run. What makes a dive log worth keeping. How a shop can tell when a day is going wrong before it does. Where the software is involved, we will say exactly what it does and what it does not.

We would rather write fewer posts and have each one be useful. If a post is not, tell us at hello@divehive.app and we will fix it.