How to Hand Off Geotech Field Reports and Supporting Data

A geotechnical report is assembled at a desk, but almost nothing in it originates there. The boring logs came off a rig in the field. The CPT traces came off a cone truck. The classifications, the moisture contents, the strength numbers came out of a lab days or weeks later. The engineer writing the report is reconciling several streams of data that arrived at different times, from different people, in different formats, and the report is only as good as the completeness of what reached the desk. A single missing field sheet or an unrecorded groundwater reading is not a small gap. It can mean a return trip to a site that has since been graded, or a boring that simply cannot be re-drilled at any reasonable cost.

That is what makes the handoff worth designing on purpose rather than leaving to email and memory. This post lays out a method for moving geotechnical field reports and their supporting data to the office so the report can be built without holes. It is a companion to our guide on getting boring logs, lab data, and field sheets to the office intact, and it borrows the same discipline civil teams use for managing field file intake without losing the record. The subsurface is unforgiving in one specific way: you usually cannot cheaply go back and collect the data again.

The streams that have to be reconciled

The first reason geotech handoffs go wrong is that there is no single thing to hand off. A complete picture of one exploration point is stitched together from several sources that rarely travel together:

• Field boring logs and drilling records.The driller's log, blow counts, recovery, drilling method, and rig notes, often on paper or a field tablet before anyone types them up.
• gINT files. The structured project database the logs eventually live in. A corrupt or half-entered gINT file is its own quiet failure, because it looks complete until someone opens it.
• CPT and SPT data. Cone penetration traces and standard penetration counts, exported from the acquisition software as their own files with their own naming.
• Field data sheets. The handwritten or tablet sheets that record what the crew actually saw and measured, the raw source the typed log is built from.
• Groundwater readings. Water levels at drilling, at completion, and on delayed readings taken days later, which means one boring can have readings that arrive on separate visits.
• Sample photos. Photos of the cores, the split spoons, the boreholes, and the site, tying a physical sample to its log entry.
• Lab test data, arriving separately. Atterberg limits, gradation, moisture content, consolidation, and triaxial results come back from the lab on their own schedule, often after the field crew has moved to the next job.

Notice the timing. Field data leaves the site on day one. Lab data trickles in over the following weeks as tests finish. If the handoff is a single email sent the day the crew got back, everything that arrives after it has no obvious home, and the report writer is left matching a triaxial result to a boring number by hand and hoping the match is right.

Why a gap is so expensive here

In most trades a lost file is a nuisance you can fix by re-sending. In geotechnical work the field data can be effectively irreplaceable. A boring is a hole drilled once, at a cost measured in mobilization, rig time, and crew hours. The site conditions that existed the day it was drilled may not exist next week. A groundwater reading taken at a specific date cannot be reconstructed later from a memory. If the field sheet for boring B-4 never made it to the office, no one can regenerate it. Someone either drives back out to re-log from photographs and hope, or the report ships with a hole in it and the engineer's stamp over the hole.

That asymmetry is the argument for treating the handoff as a tracked event with a definition of done, not a best-effort forward of whatever files happened to be on the tablet. The goal is simple to state: when the report writer sits down, every source for every exploration point is present, matched to the right job and boring, and provably the file the field or lab produced.

A handoff method that closes the gaps

The method has five parts. None of them is exotic. What makes them work is that they are done the same way every time, so nothing depends on one person remembering.

1. Package the field data into one tracked packet. When the crew comes off the site, the boring logs, drilling records, field data sheets, groundwater readings, sample photos, and any gINT and CPT/SPT exports go into a single submission tied to the job number, with a short cover note listing which borings it covers. One packet, one job, one owner responsible for it.
2. Keep lab data linked to the same job. As Atterberg, gradation, moisture, consolidation, and triaxial results come back over the following weeks, they are submitted against the same job rather than emailed to whoever asked last. The lab results attach to the exploration they belong to instead of floating in an inbox.
3. Assign one owner at each step. A packet has exactly one responsible person until someone at the office deliberately accepts it. Downloading a file to look at it does not transfer responsibility; accepting does. That keeps a packet from sitting for days while everyone assumes a colleague already pulled it in.
4. Verify completeness against the job, not the email.Before the packet is accepted, the office checks the contents against what the job requires: every planned boring has a log, every log that should have a groundwater reading has one, every sample that went to the lab has a result or a note that it is pending. The check is against a list, so a missing sheet is caught while the crew is still reachable.
5. Archive the originals write-once. The moment the field packet is submitted and verified, each file is copied to storage that cannot be renamed, overwritten, or deleted. The typed log and the processed gINT database can evolve; the original field sheet and the raw CPT trace stay sealed exactly as they arrived, so the record of what was actually measured survives every later edit.

The last step matters more in geotech than almost anywhere. When a foundation performs unexpectedly and the question turns to what the subsurface investigation actually found, the answer has to be the original field and lab data, proven to be unchanged. That is exactly the job of a sealed, write-once copy of every original, kept apart from the working files so ordinary housekeeping can never erode it.

What a complete geotech handoff includes

It helps to make the definition of done concrete. A geotechnical field handoff is complete when the office can confirm, against the job, that it has all of this:

• A log for every planned boring and sounding, with the field data sheet it was built from, not just the typed version.
• The gINT project file, opened and confirmed to load, not assumed intact because it has the right name.
• CPT and SPT exports matched to the exploration point they came from, in the raw format the acquisition software produced.
• Groundwater readings at drilling and at completion, plus a placeholder for any delayed readings still to be collected.
• Sample photos that tie each core or split-spoon sample to its boring and depth.
• Lab results linked to the job, with Atterberg, gradation, moisture, consolidation, and triaxial tests either attached or explicitly flagged as pending against a specific sample.
• A named owner and a receipt, so there is a record of what arrived, when, and who took responsibility for it.

Handling lab data that lands weeks later

The trickiest part of a geotech handoff is that it is not one event. The field packet closes quickly, but the lab data drips in for weeks, and each arrival is a chance for a result to be filed against the wrong boring or lost entirely. The fix is to keep every late-arriving result pointed at the same job the field data went to, so a consolidation curve that finishes a month after drilling still lands next to the sample it describes. The job stays open as a home for its data until the last test is in, rather than being declared done the day the crew returned.

This is where a per-job intake earns its keep over email. An inbox has no concept of “this job is still waiting on two triaxial results.” A tracked queue does. The pending items are visible, the owner is named, and the report writer can see at a glance whether the exploration is fully documented or still has holes to fill before the analysis can be trusted.

The record you are really building

Every step here produces the same thing: a defensible account of what the subsurface investigation found and where every number came from. The packet is the unit, the owner is accountable, the verification catches gaps while they are still cheap to fix, and the write-once copy makes the originals producible years later. Geotechnical firms live with a long tail of second-guessing, because the ground does not behave and the report is the document everyone returns to. Building the handoff so the data arrives complete, matched, and sealed is how the report stays defensible long after the rig has left the site. It is the same intake discipline the rest of the civil and field engineering workflow depends on, applied to the data you genuinely cannot afford to collect twice.