Who owns a geotechnical report?

Who owns the report, and what does the client get?#

The geotechnical engineer usually owns the report as an instrument of service, and the client gets a license to use it for the project. That is the default under the main design forms: EJCDC E-500 excerpts keep ownership, copyright and reuse rights with the engineer, and AIA B101 treats the architect's consultants as authors and owners of their respective instruments of service.

Many geotechnical engagements are signed directly with the owner on the firm's own proposal terms, which commonly add a reliance limitation and a reuse disclaimer. Owner-drafted agreements may instead claim ownership of all reports and data on payment. The signed contract, not industry habit, decides which applies.

Paying for a report does not by itself make it the client's work. Under US copyright law, a commissioned work is a work made for hire only within listed statutory categories and with a signed written agreement; otherwise ownership moves only by written assignment.

What does a reliance letter change?#

A reliance letter changes who may rely on the report, not who owns it. Lenders, buyers, design-builders and later owners often ask for reliance, and the letter typically names the new party, limits reliance to the original site and purpose, and applies the original agreement's limitation of liability.

Reliance letters matter for licensing because they show that several parties hold expectations about a report. A report with reliance granted to a lender and a buyer is a poor candidate for reuse, even with names removed. Log every reliance letter against its project so a rights review can see it.

What makes geotechnical records useful beyond the project?#

Geotechnical records are useful beyond the project when they connect what was observed in the ground with what the engineer concluded. A boring log, the lab tests run on its samples, the design parameters the engineer selected and a senior reviewer's comments on those parameters form a chain of expert reasoning that is hard to reproduce from published references.

Construction-phase records can extend that chain. Excavation observations, foundation inspection notes and recommendations issued when conditions differed from the report show whether the original interpretation held. Those records often sit in a separate construction services file, so link them by project before deciding scope.

Narrative reports are the weakest link for reuse. They restate the data, name the client and site and carry standard limitations, while structured logs, lab tables and review notes hold the reasoning in a form that is easier to prepare.

Which geotechnical records are the firm's, and which are sensitive?#

Most geotechnical records outside the final report are the firm's own working records, but nearly all of them tie to a place. The table separates the usual holder from the identifiability risk, which is the real constraint on reuse.

Why boring logs need an identifiability check#

Boring logs need an identifiability check because subsurface conditions are facts about a specific parcel. A log showing deep fill, shallow groundwater or soft clay at a known location can reveal something an owner treats as confidential, such as development cost or suitability for a planned use.

De-identification for geotechnical data is mostly about location. Laboratory results such as moisture content, Atterberg limits and gradation keep their technical value once they no longer point to a findable site, while coordinates and site names add risk without adding much engineering meaning.

Public projects add a layer. Logs submitted to a transportation agency or bound into public bid documents may already be public, but that does not make them yours to license, and agency agreements may restrict reuse. Many firms exclude public infrastructure work by default.

• 1Remove coordinates, station and offset references, and site plans.
• 2Strip project names, client names, street names and parcel identifiers.
• 3Re-reference or generalize elevations so they cannot be matched to a survey.
• 4Scan free-text descriptions for landmarks, neighboring buildings and road names.
• 5Keep soil descriptions, classifications and lab results that no longer point to a site.

Illustrative: a geotechnical firm builds a de-identified lab dataset#

Illustrative: a fictional geotechnical and materials testing firm keeps many years of boring logs and lab results in gINT project files, with final reports in a document management system. Its CEO wants to know whether any of it can be licensed without exposing clients.

Counsel's review splits the archive. Public agency projects and every project with a reliance letter to a lender are excluded. For the remaining private projects on the firm's own terms, the team exports lab results, soil classifications and engineers' internal review notes on design parameters, with locations, project names and client names removed. Final reports stay out.

The result is a narrower but defensible dataset that pairs field observations with lab outcomes and engineering judgment, and every project in it has a documented contract basis.

How SourceX approaches geotechnical records#

SourceX approaches geotechnical records with location as the first question. In the SourceX five-step transaction, the Rights step reads engagement terms, reliance letters and any agency restrictions, and the Preparation step removes coordinates, site references and names before the firm reviews and approves the package.

The SourceX Enterprise Data Value Framework explains why lab data detached from location can still carry value: it reflects domain expertise and human-generated signal, while preparation cost and privacy burden reduce net value. Each approved package is documented in a SourceX Evidence Packet.