Workflow for Multi-Day Expeditions in Half-Mapped Systems
The Expedition Problem: Half-Mapped Systems That Burn Out Teams
A half-mapped system is the hardest kind to survey. The trunk passage is known, the first few kilometers are well-documented, and then the edges fray into side leads, sump crossings, and breakdown piles that no one has photographed. Teams arriving for a 10-day push often burn the first three days re-confirming known geometry and the last three days rushing to close loops in the frontier, with the productive middle window shorter than it needed to be.
The Woodville Karst Plain Project is the canonical example of how long this work takes. The WKPP About Us page documents 236,723 feet of staged multi-year mapping, and the Woodville Karst Plain Project article records 44.83 miles of surveyed passage across sustained expeditions. That scale only works with a repeatable workflow; improvisation does not close that much cave.
Planning failures also show up in accident data. The IUCRR Compilation of Technical Diving Incident Database identifies skipped pre-dive planning as a contributing cause in multiple repeat-visit fatalities. Survey teams in half-mapped systems often fall into a rhythm where "we already know this cave" becomes the justification for shortcutting the brief. A disciplined multi-day workflow is what prevents that drift, and it is what lets the team come back with a quilt worth publishing.
The half-mapped pattern shows up across geographies. Sistema Sac Actun's eastern leads, the deep portions of the Lot basin systems in France, and the back-of-the-cave passages at Hölloch in Switzerland all share the same shape: a well-known trunk, a mostly-known mid-zone, and a frontier where every dive produces both new geometry and new questions. Teams arriving without a workflow waste days re-confirming what is already known. Teams arriving with a workflow can land at the staging point, calibrate, and start producing patch data on day three.
A Day-By-Day Workflow for Multi-Day Survey Pushes
Picture the mapped portion of the system as the existing quilt and the unmapped frontier as the raw sound-quilt patches you plan to stitch in over the expedition window. The workflow assigns each day a specific role, so every dive adds to either the patch inventory, the stitching pass, or the QC review. No day is generic.
Day 1-2: anchor calibration. Before anyone pushes new line, the team re-runs EchoQuilt across a known trunk passage to recalibrate receivers against the existing archive. Disagreements larger than 50 cm get flagged and the sensor rig is recalibrated before any frontier dive. Use this window for stage logistics staging — drop tanks in positions that will support the deeper penetrations on day 4 onward.
Day 3: short frontier probe. A two-diver team runs a 90-minute penetration into the unmapped edge with a deliberately conservative gas plan. The goal is not to push far; the goal is to capture the first patches of sound-quilt data from the frontier and bring them back for overnight QC review. The Divesoft comprehensive guide to technical dive planning shows how SOPs formally split support teams from exploration teams, and day 3 is exactly that handoff point in an expedition workflow.
Day 4-7: production push. These are the days that fill the quilt. Plan two teams per day — one running a deep penetration with EchoQuilt primary capture, one running a shorter dive to re-map sections that came back with low-confidence patches from the day before. Rotate the roles so no diver does four consecutive deep days. The Expedition Cave Diver curriculum emphasizes that staging tanks and organizing expeditions is a trained skill, and these middle days are where that training pays back.
Day 8: consolidation dive. No new frontier pushes. Both dive teams spend the day closing loops, rebuilding any patches that came back with noise issues, and confirming that the quilt-in-progress is internally consistent. This is the day teams skip most often and regret most often. A closed loop with two clean reference dives is worth three open loops that will never get back to the same anchor.
Day 9: final push and de-stage. One team makes the deepest planned penetration with the full benefit of eight days of calibration and staged gas. The second team recovers stage bottles and does a cleanup sweep, capturing EchoQuilt patches along known passages to serve as future reference anchors. Ending the expedition with known, clean reference patches makes the next trip's day 1 dramatically easier.
Day 10: debrief and data handoff. The quilt is packaged, reconciliation against the historic archive is run, and the team drafts the next expedition's target list. Cross-generation handoffs are the difference between a system that gets mapped in a decade and one that gets mapped in a century, and the expedition handoffs piece in this niche walks through the specific documents to produce.
This cadence gives roughly five "quilt-building" days out of ten, which is a realistic fraction once calibration, consolidation, and handoff work is honestly accounted for. Teams that claim nine production days out of ten usually either sacrifice data quality or burn out diver teams.
Advanced Tactics for Long Half-Mapped Pushes
Long expeditions need surface support treated as a co-equal discipline. Borrow the command-post approach from mine rescue work — the rescue-coordination piece on long-duration command shows how to keep a live synced map at a command post during multi-shift operations, and the same pattern works at a cave expedition base camp. A laptop at the staging area shows the quilt in progress, today's dive plan overlayed on the frontier, and a running list of flagged patches the next dive should verify.
Separate the sensor operators from the surveyors. On short trips one diver does both, but on 10-day pushes the cognitive load adds up. Assign one diver per team as the primary EchoQuilt operator responsible for cable discipline, mic checks, and voice-log narration. Assign the other as the traditional surveyor running compass, slate, and tape. Rotate the assignment across days so both roles stay sharp.
Build a daily data budget the same way you build a gas budget. Each diver has a fixed number of minutes of EchoQuilt capture per day before fatigue starts degrading the quality of their voice annotations and their survey slate discipline. Teams that track this explicitly — a "clean data time" metric alongside "bottom time" — catch the drift before the patches start getting noisy.
Finally, write the post-expedition handoff document before the expedition ends, while the team is still in camp. Waiting until everyone is back home means three months of fading memory between the dive and the record. A 60-minute debrief with the quilt on screen produces a handoff note that future expeditions can actually use.
A practical note on health and recovery during multi-day pushes: deep cave-diving expeditions accumulate physical fatigue, decompression load, and sleep debt across the ten-day window. Survey teams that schedule a rest day at day 5 or day 6 — no diving, just data review and gear maintenance — produce higher-quality data over the second half of the expedition than teams that push every day. The rest day also gives the surface support and dive-team an opportunity to swap roles, which keeps everyone fresh on tasks that benefit from variety. WKPP and French Lot-basin expedition leaders both schedule explicit rest days as a default planning element, and the EchoQuilt review work fits naturally into that day's schedule.
Join the Waitlist for Cave Diving Survey Teams
If your team is planning a 10-day WKPP-style push, a Yucatán cenote-to-cenote connection attempt, or a Mexican sump extension and you want a workflow that treats every dive as a quilt patch instead of a one-off effort, EchoQuilt was built for exactly this kind of expedition. Waitlist members get access to the multi-day expedition dashboard, the production-vs-consolidation templates, and pre-expedition rig-check audio review. Sign up with your team's target system, your planned expedition window, your team size, your rig mix (sidemount, backmount, JJ-CCR, Suex DPV), and your federation affiliation; we will help you budget the first ten days against the quilt you want to end up with, scope the surveyor-versus-operator role rotation across days, set up the daily clean-data-time metric alongside your bottom-time tracker, and pre-load the rest-day data review template that French Lot-basin and WKPP teams already use.
Priority access goes to NSS-CDS, GUE, QRSS, NACD, and IUCRR-affiliated expeditions with active multi-day push windows in the next 12 months. Half-mapped systems deserve workflows that finish them.