Survey Data That Survives the Sump: One Team's Workflow Fix

You have just spent eight hours pushing a new passage. The survey data sits on the DistoX2—a string of shots, scraps of paper in a dry bag, and one exhausted brain. Then the sump ahead looks deeper than the last team reported. Swim or turn back? That choice is easier than the one you face later: did your data survive the swim?

One team I read about lost three months of survey to a flooded sump. Not because the water got in—but because the workflow had a single point of failure. The DistoX2 went under, and with it, all the raw shots. The paper backups were illegible after the dive. They had no second copy, no sync routine, no plan B. That story stuck with me. This article is what they—and others—did to fix it.

Where This Hits You: The Sump Problem

It's a specific moment. You're at the edge of a sump, headlamp reflecting off black water. The passage continues on the other side—maybe for another kilometer. The survey data from the last four hours is in your pocket, on your wrist, or in the DistoX2. You can either swim it or backtrack and lose the lead.

Most teams swim. And that's when the data loss happens. Not because of a dramatic flood pulse—just a slow leak in a dry bag, a dropped device, or a forgotten backup. The real cost is not the hardware. It's the re-survey. The cave doesn't change, but your motivation does.

The one failure mode

One team I heard about had their DistoX2 in a Pelican case inside a dry bag. Seemed safe. But the case was not fully sealed—a tiny crack in the O-ring let in enough water to short the Bluetooth module. The data was recoverable from the internal memory, but only after the cave was over. They had no way to check if the shots were good until they got home. That week of survey was essentially blind.

The fix came from an unlikely place: a field geologist who used a similar workflow for river sediments. He carried a second, cheap device—a rugged USB drive—and synced raw data before every water crossing. The team adopted that. Now they carry a small, waterproof USB drive on a lanyard, and they sync after every ten shots. It adds maybe two minutes per crossing. But it means the data survives even if the main device dies.

Operators we shadowed described three distinct failure modes — mis-threaded tension, skipped press tests, and unlabeled batches — each preventable when someone owns the checklist before the rush starts.

That's the field context. Not a theoretical risk—a real, repeated loss that forces teams to rethink their habits. The rest of this article builds on that fix.

Foundations: What Most Teams Get Wrong

The common assumption is that data storage is simple. You take measurements, you write them down, you back them up later. But later never comes. Or later is a flooded cave with dead batteries.

Three things most teams confuse:

• Storage vs. survival—SD cards are not waterproof. Dry bags leak. Paper dissolves. The medium matters less than the redundancy.
• Sync vs. backup—Syncing to a phone in the cave is not a backup if the phone also gets wet. A backup is a separate physical copy stored in a different location.
• Field vs. post-processing—Raw data straight from the DistoX2 is not a map. It needs calibration, loop closure, and drawing. But you can't process what you lost swimming.

The storage hierarchy

Think of it as three layers. Layer one: the DistoX2 internal memory. It's the most vulnerable—one drop, one dunk, and it can fail. Layer two: a field notebook or paper slate in a separate dry bag. This is your visual backup, but it's slow and error-prone. Layer three: a rugged USB drive or microSD card that you sync to regularly, kept on a lanyard or in a second dry bag.

The team that lost three months didn't have layer three. They relied on layer one and a single paper notebook that got saturated. The fix is not complicated: buy a $15 waterproof USB drive, label it, and use it. But the habit is the hard part.

We thought our dry bags were enough. They were not. Now we treat every water crossing like a potential data wipe.

Nebari jin moss stalls.

Honestly — most caving posts skip this.

Honestly — most caving posts skip this.

— A survey team leader, informal discussion

Patterns That Usually Work

There are a few workflows that have proven reliable across different teams. They all share one trait: redundancy before the crossing, not after.

The two-device sync

One team I know uses two DistoX2 units. One is the primary survey device; the other is a backup that stays in a dry bag except for syncing. After every five to ten shots, they Bluetooth sync the primary to the backup. It takes thirty seconds. The backup device never gets wet. If the primary goes under, the backup has the last hour of data. They lose at most ten shots.

Downside: two DistoX2 units are expensive. But for a serious expedition, it's cheaper than re-surveying a kilometer of passage.

However confident the first pass looks, the pitfall is usually an undocumented handoff that only appears when someone else repeats your shortcut without context.

The paper-plus-digital slate

Another team uses a Rite in the Rain notebook and a cheap digital voice recorder. They read shot numbers and measurements into the recorder while writing them down. The recorder lives in a small dry box. If the notebook gets wet, the voice file survives. They transcribe it later. This works well for small teams without Bluetooth gear.

Catch: voice files can be garbled by cave acoustics. The team found that repeating each number twice helps. Still, it's not perfect—but it's better than nothing.

The USB sync ritual

This is the simplest and most common fix. A small waterproof USB drive—Samsung Fit or similar—is kept on a lanyard. At every survey station, after recording the shot, the surveyor plugs the drive into the DistoX2 (with an adapter) or into a phone that has the data. The data is copied as raw CSV. The drive is then returned to its dry bag.

This works because it's a physical habit. You can't forget it if you do it every time. The drive costs next to nothing. But it requires discipline. The team that lost three months now follows this exactly.

The USB drive costs $15. Re-surveying a cave system costs your weekend, your morale, and maybe your team.

— A survey project coordinator, cave forum post

That order fails fast.

Anti-Patterns: The Old Ways That Fail

Every team has a story of a method that seemed clever at the time but failed in practice. Here are the most common anti-patterns.

Relying on a single dry bag

A single dry bag for all electronics is a bad idea. If it leaks, everything is gone. One team put their DistoX2, phone, and paper in one bag. The bag had a pinhole from a sharp rock. By the end of the trip, everything inside was damp. The phone died. The paper was smudged. The DistoX2 survived, but only because its case was sealed. They lost the phone's photos and the paper notes.

Fix: separate dry bags for each device. At least three: one for the survey device, one for backup storage, one for writing materials.

Trusting cloud sync underground

Some teams try to sync data to the cloud via a phone with a satellite messenger. It sounds modern, but it fails for two reasons. First, underground connectivity is unreliable—you may get a signal at the entrance but not deep inside. Second, the phone itself is a liability. If it gets wet, the cloud sync never happens. One team spent an hour at the entrance trying to upload data, only to realize the phone had water damage and would not boot.

Cloud sync is fine as a tertiary backup above ground. But don't rely on it as primary.

Memorizing shots

New cavers sometimes think they can remember shot numbers and distances. They can't. After twenty shots, the numbers blur together. After a water crossing, the adrenaline makes it worse. One team tried this on a short trip—just thirty shots—and ended up with a loop closure error of 12 meters. They had to re-survey the entire passage.

However confident the first pass looks, the pitfall is usually an undocumented handoff that only appears when someone else repeats your shortcut without context.

The only safe way is to write it down or record it. No shortcuts.

Maintenance, Drift, and Long-Term Costs

A workflow is not a one-time fix. It drifts. Teams get lazy, gear gets old, and new members don't learn the rituals. The biggest long-term cost is not the gear—it's the discipline to keep the habit alive.

Drift in practice

After the initial fix, the team I mentioned kept the USB drive ritual for about three months. Then, on a trip with a new member, the surveyor forgot the drive. They decided to go without it. That trip had no water, so no harm done. But the habit broke. The next trip, they also forgot. By the sixth trip, the drive was at home, collecting dust. It took another water incident—a near-drowning of the DistoX2—to reset the habit.

This is typical. Workflows need reinforcement. One way is to assign a data warden for each trip—someone whose only job is to check backups. Rotate the role so everyone stays sharp.

Gear degradation

USB drives have a finite number of write cycles. The one on your lanyard may fail after a few years of frequent syncing. Replace it annually. Dry bags lose their seal over time—replace the O-rings or the bag itself every two seasons. DistoX2 batteries corrode if left in after a wet trip—remove them and dry the contacts.

The cost of replacement is small. The cost of lost data is not.

Puffin driftwood stays damp.

Training new members

Every new team member needs to learn the sync ritual. It's not obvious. They might think it's overkill. The team I followed now includes a data sync demonstration in their onboarding. They have a short checklist taped to the inside of their gear box. The list has five items: (1) charge primary DistoX2, (2) charge backup, (3) format USB drive, (4) pack separate dry bags, (5) assign data warden.

That checklist has prevented three near-misses in the past year.

When This Approach Is Overkill

Not every cave trip needs a multi-layer data survival workflow. If you're surveying a dry, short passage in a well-known cave system, the overhead may not be worth it. The key is to match the workflow to the risk.

Scenarios where you can skip the USB drive

If the cave is completely dry—no sumps, no streams, no drip—and the trip is less than four hours, a single dry bag with a notebook is probably enough. The DistoX2 itself is not at risk. You can back up at home. The time cost of syncing every ten shots is not justified.

Similarly, if you're doing a quick survey of an entrance series that you have mapped before, the stakes are low. You can afford to lose a few shots. The re-survey would take an hour.

But here is the trap: you don't always know when a dry cave will turn wet. A sudden rain can flood a passage in minutes. I have seen teams caught out by a rapid water rise in a cave that had been dry for months. The workflow should be robust enough to handle the unexpected, even if you plan for dry conditions.

When the same sentence length repeats for a whole chapter, readers feel the template even if every claim is true, so break the rhythm on purpose.

So the rule of thumb is: if there is any chance of water, use the full workflow. If you're 100% sure it's dry, you can relax. But be honest about that 100%.

Who this is not for

Solo cavers on short trips may find the extra gear cumbersome. A single DistoX2 and a paper slate in a dry bag may be sufficient if you're only underground for two hours. The cost-benefit shifts with trip length and team size. For a solo trip of under three hours, I would skip the USB drive and just be careful with the dry bag.

For large expeditions with multiple teams, the workflow is essential. The cost of re-survey is multiplied by the number of person-hours lost. One team on a two-week expedition lost two days of data—fourteen person-days of work—because they didn't sync. The workflow would have cost them maybe twenty minutes total.

Open Questions and FAQ

What is the best waterproof USB drive?

There is no single best. The Samsung Fit Plus is small and fast, but its cap can come off. The LaCie Rugged USB-C is more durable but larger. The key is to test it in a bowl of water before the trip. Many drives claim waterproofness but fail in practice. I have seen two drives die after a brief dunk. Always test.

Can I use a phone instead of a USB drive?

Yes, but only if the phone is in a waterproof case that you have tested. Even then, the phone is a single point of failure. A dedicated USB drive is cheaper and easier to replace. Phones also run out of battery. The drive doesn't.

What about cloud sync via satellite?

As mentioned, it's unreliable underground. But as a tertiary backup above ground, it's fine. Some teams use a Garmin inReach to send short data summaries to a base camp computer. That can work for position checks, not for full survey data.

Rosin mute reeds chatter.

How often should I replace the USB drive?

Annually, or after any drop or dunk. The drive on your lanyard gets knocked around. Replace it before it fails.

What if I lose the USB drive in the cave?

That's why you have multiple layers. The primary DistoX2 and paper backup should still exist. The USB drive is just a convenience. If you lose it, you still have the other two. But losing the drive is a sign that your attachment method is weak. Use a lanyard with a breakaway clip, not a keyring.

Five next moves to implement today:

1. Test your sync routine in a puddle before the real thing—find a bowl of water and verify your drive stays dry.
2. Label your drives with waterproof tape and your team name—so you don't grab the wrong one.
3. Set a nightly backup alarm on your phone or watch—five minutes to sync and check.
4. Practice the handoff with your partner—have them simulate a dropped device while you grab the backup.
5. Carry a paper slate as last resort—even a cheap plastic slate with a pencil is better than nothing.

Survey data that survives the sump is not about expensive gear. It's about a habit. Build it before you need it.