Sample traceability
Field-to-lab
Chain-of-custody indexed from coring event to lab result.
Synthetic example · No client data · Demonstration workflow
Offshore geotechnics · Geotechnical site investigation
Offshore Geotechnical Site Investigation
CPT, piston coring, and lab testing campaign for foundation design — scoped, executed, and reported in one system.
Synthetic case study. Representative offshore workflow. No client data used. For demonstration only.
Operational pain points
Representative challenges SurveyIQ addresses — synthetic scenario, not a client claim.
Geotechnical scopes list test locations separately from marine and HSE approvals.
CPT and coring run sheets are paper-based and reconciled late in the campaign.
Lab submission tracking lacks linkage to field sample IDs and chain-of-custody.
Foundation designers receive data packages without operational context or audit trail.
Representative workflow in SurveyIQ
From scope intake to deliverables — a demonstration workflow for geotechnical site investigation.
- 01
Scope intake
Upload or paste the geotechnical investigation scope. SurveyIQ structures objectives, methods, and deliverables for review.
- 02
Missing information
Blocking and advisory gaps are surfaced early — vessel nomination, sensor configs, reporting templates, and interface points.
- 03
Procedure pack
Draft acquisition, HSE, marine, and reporting procedures are generated with source references for human approval.
- 04
Work packages
Approved procedures become executable work packages with owners, dependencies, and readiness states.
- 05
Command center
Offshore teams work from one project truth — department cards, stop-work awareness, and today's plan.
- 06
Logbook & evidence
Department logbooks capture events, downtime, QC snapshots, findings, and DPR source notes in real time.
- 07
DPR & deliverables
Daily progress reports and final deliverables are assembled from verified project facts, not end-of-shift reconstruction.
Example scope elements
- CPTu profiles at foundation footprint and anchor locations.
- Piston cores for laboratory strength and classification testing.
- Seabed video for sample location context.
- Lab testing schedule with turnaround tracking.
- Geotechnical interpretive report and data deliverable package.
How SurveyIQ supports this workflow
Procedures generated
- GEO-010 — CPTu acquisition and refusal criteria
- GEO-011 — Piston coring and sample handling
- LAB-001 — Chain-of-custody and lab submission
- VID-001 — Seabed video for sample context
- HSE-007 — Gear deployment SIMOPS
- REP-100 — Geotechnical report assembly
Work packages
- GEO-020 — CPTu campaign
- GEO-021 — Coring campaign
- LAB-010 — Lab tracking
- REP-100 — Geotechnical reporting
Department logbooks
GeotechnicalMarineHSELabReporting
Deliverables & client portal outputs
Campaign deliverables
- CPTu profiles and location plans
- Core logs and photos
- Lab test result tables
- Interpretive geotechnical report
- Digital data deliverable package
Client portal (released views)
- Sample location plan
- Lab turnaround status
- Released interpretive summary
- Data package download index
Representative outcomes
Illustrative metrics for demonstration — not measured client results.
CPT refusal handling
QC-flagged
Refusals logged with work-package context for redesign loops.
Lab turnaround
Tracked
Submission and result states visible in command center.
Designer data package
Structured
Deliverable register defines issue gates before release.
Frequently asked questions
Can lab submissions link to field sample IDs?
Yes. Geotechnical logbooks maintain chain-of-custody from coring through lab results.
Does SurveyIQ handle CPT refusal events?
Refusals are QC-flagged and logged against work packages for engineering review.
Is this real geotechnical data?
No. All locations, profiles, and lab references are fictional representative examples.
See SurveyIQ on your next offshore campaign
Book a demo, send a scope of work, or watch the product overview — all synthetic examples, no client data required.