Built by First Responders, for First Responders

Dive Command started with a problem every dive team knows: file cabinets full of paper.

Our team at Charles County Dive Rescue (Company 13) had years of dive logs, diver records, and maintenance documentation stored in filing cabinets — valuable data that was either difficult to access or forgotten by time. We wanted to digitize our department's forms and eliminate the paper.

The obvious first form to digitize was our dive log. The Chief of Company 13 had developed our dive log to be incredibly detailed and functional over years of actual rescue operations. This form became the foundation that Dive Command is built from.

What started as simply replacing a paper form evolved into something more powerful. We realized we could use the data we were already collecting to provide valuable real-time information to our topside team — insight into what was happening beneath the surface during active operations.

Where we once manually calculated a diver's SAC rate based on air consumption after each dive, we now have a tool that predicts expected air remaining based on that diver's historical performance. This gives our team actionable insight during ongoing dives, not just after they're over.

This grew into including advanced tools for mapping operation scenes and providing detailed documentation in real time — work that would otherwise have to wait until we got back to the station.

Along the way, we've built in other functionality our team needed: live dive timers with breath count reminders, support for different search patterns, digital signature capture, operation type templates, and more. Each feature came from a real operational need.

Our journey to eliminate the paper isn't stopping at the dive log. The filing cabinets are still there, and we're continuing to build tools to digitize and modernize how dive teams manage their operations, their equipment, and their records.