5 Site Investigation Workflow Bottlenecks (And How to Fix Them)
From field data collection to final report delivery, here are the five most common bottlenecks slowing down geotechnical site investigation workflows — and practical ways to address each one.
Why Geotechnical Workflows Get Stuck
Geotechnical engineering is inherently multi-stage: fieldwork, laboratory testing, data interpretation, and report writing all happen sequentially, and a delay in any one stage ripples through the rest. The result is projects that run over time budgets, clients asking for status updates, and engineers working late to hit submission deadlines.
Most of these delays aren't caused by technical complexity — they're caused by process inefficiencies that have become so normalised they're invisible. Here are five of the most common, and what you can do about each.
1. AGS Data That Doesn't Match Your Template
The AGS (Association of Geotechnical and Geoenvironmental Specialists) data format is the industry standard for digital transfer of ground investigation data in Australia and the UK. In theory, this should make data handover seamless. In practice, almost every AGS file needs some level of manual cleanup before it's usable.
Field codes differ between drillers. Column headers aren't always consistent. Some groups are populated, others aren't.
Fix: Build a standard AGS validation checklist that your field team works through before submitting data, and use software that can handle common AGS variations without manual intervention.
2. No Clear Handover Point Between Field and Office
The transition from fieldwork to office reporting is where projects frequently lose momentum. Questions pile up: Has all the data been submitted? Are lab results pending? Which borehole logs have been reviewed?
Without a clear handover protocol, engineers spend time chasing answers instead of doing technical work.
Fix: Create a simple project handover checklist that field supervisors complete before a project moves to the interpretation phase. It should confirm: data submitted, logs reviewed, outstanding tests flagged.
3. Report Templates That Aren't Actually Templates
Many firms have a "standard report template" that, in practice, gets manually edited for every project. Sections get rearranged. Boilerplate text gets rewritten. Formatting drifts across documents.
This isn't just inefficient — it's a quality risk. Inconsistent formatting makes reports harder to review and increases the chance that something gets missed.
Fix: Invest time in building a genuinely locked-down template. Protect the formatting, lock the styles, and create a library of standardised boilerplate paragraphs for common soil types and site conditions that engineers can insert and edit rather than write from scratch.
4. Interpretation Bottlenecked on One Senior Engineer
In many practices, the interpretative sections of a geotechnical report can only be written — or meaningfully reviewed — by a senior engineer. This creates a queue. When that senior engineer is busy, reports wait.
Fix: Use AI-assisted drafting tools to generate a structured first draft of interpretative sections based on the data. This gives the senior engineer a document to review and correct rather than a blank page to fill — fundamentally different cognitive tasks, with the review being much faster.
5. Revision Cycles That Start from Scratch
Client and peer review comments often trigger a full re-edit of a report section, even when the changes needed are relatively minor. This happens because the original document wasn't structured to make revision easy — sections are long, logic isn't clearly separated, and finding the relevant passage takes time.
Fix: Structure reports so that each major interpretative section is self-contained and clearly delineated. When a reviewer comments on the groundwater section, that section should be easy to locate, understand in isolation, and revise without disturbing adjacent content.
The Common Thread
Most of these bottlenecks share a root cause: processes that were designed for one project volume and have never been updated as the practice has grown.
As you take on more projects, the manual overhead of each step compounds. The firms that scale successfully are the ones that invest in systematising their workflows before the inefficiencies become critical.
AI tools are one part of that picture. But process design comes first.
If you're looking at your report preparation workflow specifically, GeotechReport can help you cut drafting time significantly. Start a free trial to see how it handles your next site investigation.