Every geotechnical firm has at least one habit around its boring log software that costs more time than anyone realizes. These aren't dramatic failures. They're small, repeated frictions that compound across every project, every week, all year.

1. You're Re-Entering the Same Data in Your Boring Log Software

A field engineer logs a boring at the rig. That sample data gets typed again into a lab system. Then the lab data gets added to the boring log.

Each re-entry is a chance for a transposed number or a missed sample ID. Firms that measure this honestly usually find it's costing an hour or more per project — time that never shows up as a line item, just as staff who are perpetually behind.

2. Your Boring Log Software Isn't Connected to the Rest of Your Departments

The boring log lives in one system. The lab lives in another. Construction materials testing operations is a third. Each department can see its own data and nothing else.

Firms running this way tend to discover problems late — a classification that doesn't match the lab result, a missing sample nobody flagged — because no one had visibility into both sides at once.

3. You Haven't Re-Evaluated Your Boring Log Software Since the Last Time It Hurt

Most firms picked their current boring log software years ago, during a busy season, under deadline pressure. It solved the immediate problem and then nobody looked at it again.

The market has moved since then. Firms that haven't re-evaluated recently are often running tools that were the best available option in 2019 — not in 2026.

4. You Think You're Locked Into Your Current Boring Log Software

A common assumption: "We can't switch because our clients or the DOT require a specific format." That's rarely true anymore.

Modern platforms handle this with export formats — the firm's internal system can be whatever works best for the team, and the data still leaves in AGS, DXF, DIGGS, GPJ, or whatever format a specific client or agency requires. The tool your team uses internally and the format you deliver externally don't have to be the same thing.

5. Your Boring Logs Aren't Connected to Lab Test Results

A boring log describes what the field engineer observed. The lab result confirms — or contradicts — that observation. When those two things live in separate systems, nobody automatically checks them against each other.

Firms that catch discrepancies late are usually the ones where the boring log and the lab data never sat side by side until someone was already writing the final report.

6. You've Doubled Down on Boring Log Software You Can't Actually Customize

Every project is a little different. Boring log software that requires a support ticket, a vendor callback, or a software engineer to add a field or change a form isn't built for that reality.

Firms stuck here tend to work around the tool instead of with it — building the same three boring log templates over and over because building a fourth isn't worth the hassle.

7. You're Using Spreadsheets to Bridge the Gaps

When systems don't talk to each other, spreadsheets become the connective tissue. Someone exports from one tool, reformats in Excel, and imports into another.

This works until it doesn't. Spreadsheets have no audit trail, no version control, and no way to catch an error before it reaches a client report.

What Fixing Boring Log Software Looks Like for Geotechnical Firms

None of these seven mistakes are really about the boring log software itself. They're about the gaps between it and everything else — the lab, the report, the client deliverable.

Geotechnical firms that fix this aren't buying a better boring log app. They're moving to one system where the boring log, the lab data, and the report all live together, so there's nothing left to re-enter, reconcile, or reformat by hand.

If your team is doing any combination of the seven things above, the fix usually isn't a better process. It's fewer systems.

What This Means for Your Geotechnical Firm


Most of these mistakes don't feel urgent individually. Together, they're the difference between a geotechnical firm that runs lean and one that's perpetually catching up on data entry.

MetaField is boring log software built to close exactly these gaps — connecting field, lab, and reporting so none of the seven mistakes above have a place to happen. If you recognize your geotechnical firm in more than two or three of these, it's worth seeing what a connected system looks like.

Explore Metafield
Request a Demo

Frequently Asked Questions

Track one project from field log to final report and count how many times the same piece of information — a sample ID, a depth, a classification — gets typed into a different system. Most firms are surprised by the number.

No. Most modern platforms, including MetaField, support export to formats like AGS, DXF, DIGGS, and GPJ. The internal system your team uses and the format you deliver to a client don't need to match.

Usually the fastest win is connecting field and lab data first, since that eliminates the most re-entry and catches the most discrepancies. The rest tends to resolve naturally once field and lab share one system.

Boring log software captures field data well but stops there. A connected platform carries that data through lab testing and into the final report without anyone re-entering it — that's the difference that actually saves time for geotechnical firms.
Previous Blog Post