For geotechnical firms
Geotechnical field data handoff.
A boring goes in the ground once. The logs, blow counts, and samples that come off it have to reach the office intact, and the lab results that follow have to line up with them. RoverDrop makes that geotech data transfer provable: a numbered receipt when files verify, one responsible owner per packet, and a write-once archive of everything that arrived.
No account or email needed for the demo.
One report, assembled from many hands
A geotechnical report is a reconciliation. The drill crew produces boring logs, blow counts, and groundwater readings on site. The lab returns Atterberg limits, gradation, moisture content, consolidation, and triaxial results days later. The office engineer has to bring all of it together into one document that holds up. When those pieces arrive by email, in a shared folder, and on a memory card, the question is never far away: do we have everything for this hole?
A missing field sheet or an unrecorded groundwater reading is not a small problem here. You cannot cheaply re-drill to get it back. The rig has moved on, the hole is backfilled, and recollecting a single number can mean remobilizing a crew. The record has to be complete and traceable the first time, because there is rarely a second time.
“Do we have everything for B-4?”
This is one shape of the larger job of field-to-office file transfer, with the added twist that two independent sources have to end up in the same place, matched to the same boring.
Field logs and lab results, into one packet
RoverDrop treats each submission as a packet: the files, a short cover sheet, and the job or boring number, kept together and tracked as one unit. Field data and lab data come in as packets against the same job, so the office assembles from a queue instead of hunting across an inbox and a drive.
From the field
Crew ownsDrill crew and logger, on site
- Field boring records and drilling logs
- SPT blow counts and sample intervals
- CPT and sounding data
- Groundwater readings, by date
- Photos of samples and the site
From the lab
Lab sourceGeotechnical lab
- Atterberg limits
- Sieve and gradation results
- Moisture content
- Consolidation
- Triaxial
One boring, one record
FiledOffice geotechnical engineer
Both packets sit against Job 26-2038. The engineer accepts each by name, checks the field logs against the lab results for the same boring, and files the finished record. Every step is stamped, so “do we have everything” has an answer you can point at.
What a complete geotech packet carries
The two sources rarely arrive together, which is exactly why they need one intake that knows what belongs to each job. RoverDrop does not care what the files are; it cares that they arrived whole and can be traced back later.
From the field
Recorded at the rig, often with no signal.
- Boring logs and field boring records
- Drilling logs and SPT blow counts
- CPT and other sounding data
- Groundwater level readings
- Field data sheets
- Sample and site photos
From the lab
Arrives days later, on its own schedule.
- Atterberg limits
- Sieve and gradation analysis
- Moisture content
- Consolidation test data
- Triaxial test data
- gINT data files
Traceable and intact
Because you cannot re-drill the hole
Geotech data is expensive to collect and impossible to recreate. The controls that matter are the ones that prove a file arrived whole and keep a copy that outlives the project.
Verified on arrival
Every file is checksummed before the packet counts as submitted. A truncated gINT export or a half-uploaded photo set is caught at intake, not discovered when the report is due.
A record of every hand
Who submitted, who accepted, who filed, and every view and download in between are written to an append-only log. Nothing is edited after the fact, including by an administrator.
A copy that stays
At submit, every file is copied to write-once storage that retention rules never touch. Years later, the original boring log and lab result are still there, unchanged.
The event-by-event record is the audit trail behind each submission, and the stored copy is a write-once archive that a later dispute or review can be checked against.
Geotech data transfer, answered
- What geotech files does RoverDrop handle?
- Anything the field and lab produce: gINT data files, boring and drilling logs, CPT and sounding data, SPT blow counts, groundwater readings, field data sheets, sample and site photos, and lab results such as Atterberg limits, sieve and gradation, moisture content, consolidation, and triaxial data.
- Why not just email boring logs and lab results?
- Email gives you no receipt, no single owner, and no lasting copy. When a field sheet or a lab report is missing, nobody can say for certain it was ever sent, and re-drilling to recollect a reading is far more expensive than the email ever saved.
- How does RoverDrop keep the record traceable?
- Every packet gets a numbered receipt after its files are checksum-verified, an append-only audit trail of who did what and when, and an automatic write-once archive copy of exactly what arrived.
For a step-by-step routine, read how to hand off geotech field reports and supporting data.
Related
See it in motion
Send a boring log packet in the demo
Submit field logs and lab results against one job and watch each get a receipt, an owner, and an archive copy. Nothing to install, and no account or email required.