Engineering and architecture
Can geotechnical engineering firms license boring logs and reports?
By SourceX Editorial · Updated
Short answer
Geotechnical engineering firms can often license boring logs and laboratory results once site locations and client details are removed, because those records pair field observations with tested properties. Signed reports and their recommendations are harder: they are tied to a named site, a client and reliance terms. Screen each record family for ownership, location and client sensitivity first.
Key takeaways
- Laboratory results and soil classifications are usually the least sensitive geotechnical records once they are detached from a boring location.
- Foundation and earthwork recommendations carry the most client and reliance baggage and are often carved out of a license.
- A boring location with coordinates, elevation and a drilling date can identify a property, so locations are coarsened or removed.
- Archives that link a boring to its lab tests, analysis, recommendation and construction observations are the most distinctive.
- Environmental findings, critical facility sites and disputed projects are commonly excluded before any other screening.
What records does a geotechnical firm actually hold?#
A geotechnical firm holds a layered archive: boring and test pit logs, in situ test data such as CPT soundings and standard penetration test blow counts, laboratory results, engineering analyses, signed reports, and often construction materials testing records from the build. Each layer depends on the one beneath it, and that chain is what gives the archive its character.
Most firms keep logs in a dedicated logging database such as gINT or a similar tool, laboratory results in a lab information system or spreadsheets, and reports as PDFs in a document management system. Construction-phase records, such as field density tests, concrete cylinder results and daily field reports, often live in yet another app. Knowing which system holds which layer is the first step of any assessment.
A first inventory needs only descriptive answers: which systems hold each layer, roughly how many years of borings remain searchable, whether lab results link back to boring and sample IDs, and which clients or project types carry restrictive terms. Those answers show whether the firm holds one linked archive or several disconnected ones, which matters more than raw volume.
Logs, lab results and recommendations compared on sensitivity#
The table compares the main geotechnical record families on client sensitivity and location sensitivity. The ratings are general; the actual position for any project depends on its contract and its site.
| Record | Client sensitivity | Location sensitivity | Usual handling |
|---|---|---|---|
| Boring and test pit logs: strata, groundwater, blow counts | Low to medium | High: tied to coordinates and elevation | Keep descriptions and test values; remove or coarsen coordinates, project names and dates |
| Laboratory results: moisture, Atterberg limits, gradation, consolidation, strength | Low | Low once detached from the boring | Usually the strongest candidate; keep sample depth and classification |
| CPT soundings and other in situ test files | Low | High | Keep the soundings, strip site identifiers |
| Engineering analyses and calculations | Medium | Medium | Keep method and inputs; remove client and site references |
| Signed reports with foundation and earthwork recommendations | High: named client and reliance terms | High | Often excluded, or reduced to de-identified decision records |
| Construction materials testing and observation records | Medium to high: tied to contractor and owner | High | Check contract terms; remove contractor, inspector and site names |
| Environmental and contamination observations | Very high | Very high | Commonly excluded |
Why are lab results easier to license than recommendations?#
Laboratory results are easier to license because they describe material, not a decision about a client's property. A gradation curve or a set of Atterberg limits, separated from where the sample came from, reveals little about anyone, and the firm generally produced the result itself.
Recommendations are the opposite. A foundation recommendation names the structure, depends on site-specific conditions, and is written for a client under terms that often limit who may rely on it. Even with names removed, the judgment in a recommendation stays closely tied to one project, and some clients treat their geotechnical reports as confidential.
Standard owner-engineer forms often reserve the engineer's rights. A published excerpt of the 2014 EJCDC E-500 agreement states that the documents are instruments of service and that the engineer retains an ownership and property interest, including the copyright and the right of reuse. Wording differs between editions and negotiated versions, and many projects run on client-drafted agreements instead, so the signed contract on each project controls, and counsel should read it.
Location and client sensitivity checks#
Location and client sensitivity checks come before any test value is reviewed, because they decide which projects enter scope at all. A boring log with coordinates, ground elevation and a drilling date can often be matched to a property using public records and aerial imagery.
- Remove project names, addresses, client names and parcel references from log headers and footers.
- Replace coordinates with a coarse region or drop them, and decide whether elevations stay.
- Strip driller, logger, technician and engineer names, plus license and seal details.
- Exclude projects with environmental findings, contamination notes or regulatory involvement.
- Exclude critical facilities, such as utilities, transportation structures and secure sites, unless the contract clearly allows reuse.
- Flag projects with claims or litigation history and leave them out.
What makes a geotechnical archive valuable to AI developers?#
A geotechnical archive is valuable when it links observations to engineering decisions and then to what happened in the field. A boring log, the lab tests on its samples, the settlement analysis, the recommendation and the construction observation that confirmed or contradicted it form a complete reasoning record.
In the SourceX Enterprise Data Value Framework, that linkage raises domain expertise, human-generated signal and AI utility, and long runs of consistently formatted logs add scale and recency. Reproducibility lowers value where public agencies already release comparable subsurface data, and preparation cost rises when logs exist only as scanned PDFs. Coarsening locations also trims some value, since a model developer may want regional geology context; that trade-off is set per package and recorded in the privacy record.
| Archive trait | Raises value | Lowers value |
|---|---|---|
| Format | Structured log database with consistent fields | Scanned PDFs with handwritten field notes |
| Linkage | Logs tied to lab tests, analyses and field observations | Reports with no underlying data |
| Coverage | Many years of work in consistent regional geology | Scattered projects logged to mixed standards |
| Rights | Firm-retained work files under clear agreements | Client-owned deliverables or restrictive public contracts |
| Sensitivity | Private commercial sites with simple contracts | Environmental, critical facility or disputed work |
Illustrative: a geotechnical firm narrows its scope#
Illustrative: a fictional geotechnical and materials testing firm keeps borings in a logging database, lab results in a laboratory system, reports in a document management system and construction testing in a separate field app. The CEO asks whether the archive could support a data license without straining client relationships.
The rights review removes projects for a state transportation agency whose contracts restrict reuse, every project with environmental findings, and all projects in dispute. The remaining scope pairs boring logs and lab results with de-identified analyses, with coordinates reduced to a broad region and every name stripped from the logs. Signed reports stay out. The CEO approves a small sample for buyer review before any wider export.
How SourceX approaches geotechnical records#
SourceX runs geotechnical archives through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The firm first describes systems, record families and years of work, and nothing is shared during that assessment. Rights are checked project group by project group, and preparation applies the location and client rules the firm approves.
Each released package carries a SourceX Evidence Packet with provenance, licensing rights, permitted use, the privacy record and release authorization. The data is licensed, not sold, so the firm keeps ownership of its logs and reports.
Frequently asked questions
Does a reliance letter affect licensing?
A reliance letter extends the right to rely on a report to named parties for a stated purpose. It is generally not a transfer of ownership, but it shows that others have an interest in how the report is used. Projects with reliance letters deserve a closer rights review, and many firms leave those reports out while keeping de-identified test data.
Can we license data from projects that were never built?
Often those projects are simpler on the client side but thinner on value. Unbuilt projects lack the construction observations that confirm or contradict a recommendation, so the reasoning chain is shorter. Their logs and lab results can still be useful, subject to the same contract and location checks as any other project.
What about records from geotechnical firms we acquired?
Acquired archives carry the terms of the agreements they were created under and the terms of the acquisition itself. Confirm that the purchase agreement transferred the records and the right to use them, and check whether the acquired firm used different contract forms. Treat each acquired archive as its own rights group.
Do scanned logs need to become structured data first?
Not to start. The first assessment only records what exists and where. If scanned logs move forward, extracting them into structured fields is a preparation task with its own cost, and checking the extracted values against the originals is part of quality control before release.
Could licensing logs create professional liability exposure?
Raise that with counsel and your professional liability insurer before signing. A license can state permitted uses and exclude reliance on the records for design, and de-identification separates records from specific sites. The final terms, including warranties and indemnities, should be reviewed with counsel for each deal.
Sources
- EJCDC E-500 Owner-Engineer agreement language (2014 edition excerpt) states that all Documents are instruments of service and the Engineer retains an ownership and property interest therein, including the copyright and the right of reuse at the Engineer's discretion, whether or not the Project is completed. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.