Most dive contractors start with a spreadsheet, and for a while it works. Then the gear count grows, the crew spreads across sites, and a date gets missed. This guide covers the four ways a spreadsheet log fails, the signs you have outgrown it, and what equipment maintenance tracking software has to do to fix each failure. The cases below are typical of how it goes, not stories from a named company.

Four ways a spreadsheet fails

1. The date nobody saw

A hydro date sits in a spreadsheet nobody opened this month. The service gets missed.

How it plays out: the shop keeps a sheet of 30 cylinders with a column for the next hydro. The conditional formatting turns a cell red when the date passes. It works, as long as someone opens the file. In a busy season nobody does for six weeks, and two cylinders go out of date. In BC a scuba cylinder needs a hydro at least every five years and an internal visual inspection every year, with both dates in the maintenance log (WorkSafeBC section 24.39). An out of date cylinder is a finding at the next audit.

What fixes it: the warning has to come to you. Software should send notice before a job falls due, by email, without anyone opening anything.

2. The history in the other binder

The auditor asks for the service history on one regulator. It is in a binder at another site.

How it plays out: the spreadsheet says the regulator was serviced in March. The service centre’s invoice and test sheet are in the binder in the office, and the regulator is on the vessel. The auditor wants the record now, at the dive site. In BC, service records for breathing apparatus have to be available to an officer and to workers on the dive site (section 24.27).

What fixes it: every service recorded against the item it was done on, with the certificate attached, reachable from anywhere the crew works.

3. Gear pulled the morning of the dive

Gear gets pulled the morning of the dive because nobody can show it is in date.

How it plays out: the supervisor checks the helmets before loading. One has no record of its last overhaul in the sheet. It may well have been done, but nobody can prove it, so the helmet stays behind and the job starts short or late. The cost is not the servicing. It is a crew standing on the dock.

What fixes it: a plain status on every item, visible before the truck is loaded: in date, coming due, or overdue.

4. The one person who knew

The one person who kept it all in their head is away on another job.

How it plays out: the operations manager built the spreadsheet, knows which tab is current and which columns to ignore, and remembers that the compressor filter was changed early. When they are offshore for three weeks, nobody else can keep the log, and nobody trusts what is in it.

What fixes it: one shared record the whole team can reach, with access levels so each person sees and changes only what they should.

Signs you have outgrown the spreadsheet

  • More than one copy of the file exists, and you are not sure which is current.
  • You track more than about 30 items, or more than one servicing job per item.
  • Your crews work from more than one site or vessel.
  • You have found a missed date after the fact in the last year.
  • Certificates are kept somewhere other than the log.
  • Only one person can update the log with confidence.
  • You could not tell an auditor who changed a date, or when.

Two or more of these and the spreadsheet is costing you more than it saves.

What equipment maintenance tracking software should do

Spreadsheet failureWhat to look for in software
The date nobody sawSeveral servicing jobs per item, each with its own due date, and email warnings ahead of the date
The history in the other binderService history and certificates stored with each item, reachable from any site
Gear pulled on the morningA status for every item on one screen
The one person who knewMultiple users with access levels, and an audit log of every change

Be careful with general equipment maintenance software built for plants and fleets. It can do all of this, but it is built around work orders and takes real effort to set up. PM log or CMMS compares the two honestly.

Moving off the spreadsheet: a practical plan

  1. Clean the register first. One row per item, a Gear ID on every item, serial numbers read off the gear. Retire anything you no longer use.
  2. List the servicing jobs per item with their intervals and where each interval comes from. The preventive maintenance schedule for dive gear is a starting point.
  3. Prove the last done dates. Where there is no certificate, treat the job as due now.
  4. Pick a cut-over date. From that day, every service goes into the new system only. Two live records is how the first problem started.
  5. Keep the old file as an archive. Save it read-only and keep it with your records. Federal rules require each inspection, test and maintenance record to be kept five years (section 18.42).
  6. Give the crew access on day one, so the record is used where the gear is.

If you are not ready to switch, start with a cleaner spreadsheet. The free equipment maintenance log template has the right fields and flags jobs due within 30 days.

How GearMaster handles the four failures

GearMaster is a preventive maintenance log for dive gear, built by commercial divers and software developers around exactly these four failures:

  1. Every item carries its own servicing jobs. You get notice 30 days before one falls due.
  2. Every service is recorded against the gear it was done on. The history is one click away, with manuals, certificates and inspection reports stored next to the gear.
  3. Status is plain: Healthy, Impending or Overdue. You know before the crew loads the truck.
  4. The records sit in one place your whole team can reach, with the access levels you set. Every change is logged, and the audit log exports to CSV.

See the problem side by side on the homepage, or go straight to the features.