30-min call with RobBook a proof-of-concept call
Job 01 · Proposal desk

// Geotechnical engineering firms · Investigation proposal scopes

Geotechnical investigation scopes, drafted from the request and site plan for the engineer who sets them.

A county posts a bid, an architect forwards a site plan, a developer sends three lines and a map. Before anyone prices the drilling, a project engineer has to work out what the request really says. In a free AI proof of concept, AI reads copies of 20 to 30 requests your office already scoped and drafts the scope sheet: project type and loads as stated, borings and depths asked for, access and utility items, lab tests named, standards cited, and what the request never mentions. Your reviewer, the engineer who knows your proposals best, sets each draft beside the scope you sent.

Book a proof-of-concept call30 minutes with Rob
Scoped requests
20 to 30
Scopes set
None
Proposals sent
None

// The one job

From a request and a site plan to one scope sheet

A request for geotechnical work scatters what matters. The structure and its loads sit in a project summary, boring locations on a plan sheet, depths in a note from the structural engineer, lab tests in a specification, utilities and permits in the general conditions, and an addendum may move any of them. Your project engineer pulls it together, decides what the site needs and writes the scope your firm will price.

For the test, AI reads copies of each request and drafts a scope sheet: the project type, stories, below-grade work and loads in the request's own figures and units; each boring or test pit with its label, depth and the person who asked for it; access, utility and permit items; the lab tests and sampling intervals named; every code or standard cited; and a list of what the request leaves unsaid. Each line points to its page. The sheet sets no boring count, no depth and no fee, and your reviewer compares it with the scope your firm actually sent.

Client requestRequest and site plan
Owner
Project
Site plan
Addenda
ItemPageAs stated
Illustration, not a real request
Read into
a scope sheet
Scope sheetDraft for your engineer
Loads as stated
Borings and depths
Access and utilities
Lab tests
ItemSource pageNot stated
Made-up scope sheet, for illustration

// What makes it hard

What a geotechnical request says, and where it hides it

Loads arrive in someone else's shorthand. Portage County, Wisconsin's 2025 request for soil boring services on a new law enforcement center named the 2015 International Building Code with Wisconsin amendments, up to two stories, elevator pits, and a basement under the jail that the geotechnical report's groundwater findings might settle. It gave maximum column loads written as 375k, 225k and 75k for three building cases, asked for recommendations on all three, listed a wall load of 6.5 klf, and gave typical settlement limits while deferring to the geotechnical engineer's recommendation. The sheet copies each figure with its unit and its case exactly as written, and notes the basement question as one the request hands to the report.

Depths come from different people. In that same request the structural engineer wanted building borings to 35 feet inside the footprint, the civil engineer wanted road borings to 5 or 10 feet, and the retention ponds got 5-foot test pits classified according to USDA and Wisconsin DNR technical standard 1002, signed by a soil scientist. The bid form priced lines by plan label, TP 1-12, BB 1-15, R5 1-18 and R10 1-2, listed extra borings and rock coring by the linear foot as alternates, and awarded on the lowest total. Samples were to follow ASTM D1586 every 2.5 feet to a depth of 10 feet and every 5 feet below. The sheet gives every label, depth, interval and requester its own line.

Access, utilities and permits sit in the back pages. Dane County, Wisconsin's 2015 request for on-call geotechnical services wanted a work plan before anyone drilled: a sketch of test pit and borehole locations, the depth of each hole, sampling intervals, sample custody and the ASTM methods to be used, reviewed with the county first so right-of-way and environmental clearance could happen. Its special instructions gave the Diggers Hotline call, and any private locating, to the general contractor. North Carolina DOT's on-site checklist for its field staff, updated December 3, 2025, lists property owners, drill site access, utilities and traffic control, wants every utility cleared through 811, expects a Nationwide 6 permit on site for every project, and adds a right of entry permit in railroad right of way. The sheet lists each item and whether the request assigns it to anyone.

Codes and contracts already hold some of the numbers. Where a request cites New York City's Building Code, section 1803.4.1 sets minimum boring counts by built-over area and one boring for every 50 linear feet of retaining wall taller than 10 feet, and 1803.4.2 gives borings from an earlier engineer only partial credit, with at least one new boring required. Cone penetration tests may stand in for borings one for one, but never below half the required standard borings, and never fewer than two. Loudoun County's 2025 on-call request asks the consultant to review and develop the number, location and depth of borings before the investigation starts, calls out karst evaluation, and lists lab work from moisture content, Atterberg limits and gradation to California Bearing Ratio and Standard and Modified Proctors under ASTM D698 and D1557 or AASHTO T 99. The sheet quotes whatever section or list a request cites. Whether the site needs more is your engineer's call.

What your reviewer will check. Did the sheet catch every load with its unit, every boring and test pit with its label, depth and requester, each sampling interval, each access, utility and permit item, every lab test and standard named, and every gap, each tied to its page? Did it add anything the request never said? The scope your engineer wrote is the answer key. The program, the count and the depth stay with your engineer. None of this is legal or engineering advice.

// What you send

Requests your office has already scoped

Copies only
Fee pages optional
01

20 to 30 requests

Investigation requests from the last year or two, won and lost: public bids, on-call task orders, an architect's email with a site plan attached. Include a few that an addendum changed.

02

The scope that went out

Each proposal or task order scope as sent, with its boring layout and exclusions. Black out the fee pages if you like; the test reads the scope, never the price.

03

Your engineer's notes

Whatever your engineer marked up while scoping: a checklist, questions sent to the client, a sketch of boring locations. They show what a good sheet should have caught.

04

Only after the NDA

Copies move once the NDA is signed. We never sign in to a bid portal, a client's document site or any system of yours. If a request has to stay in-house, we build a look-alike of it with your reviewer.

// Before it starts

Agreed before any request is copied

Each item is approved by the owner or a principal before work begins.

Terms for the scope testOwner signs off
Your reviewer
Named by the owner, usually a senior project engineer who writes scopes
Success criteria
In writing: which items must be caught, and how a missed or invented item counts
Sample
Your reviewer's pick of public and private requests
Engineer only
Boring count, depth, lab program, fee and every recommendation
Price
A range for running it live, quoted before the first copy
NDA
Signed before the first request

// How the test is judged

The scope you sent beside each draft sheet

Request by request
item by item
Across the same 20 to 30 requestsThe scope you sentDraft scope sheet
Project type, stories, below-grade work and loads as statedFilled in on your requestsFilled in on your requests
Each boring and test pit: label, depth and who askedFilled in on your requestsFilled in on your requests
Sampling intervals and in-situ tests namedFilled in on your requestsFilled in on your requests
Access, utility, permit and clearance itemsFilled in on your requestsFilled in on your requests
Lab tests and the standards citedFilled in on your requestsFilled in on your requests
What the request leaves out, written as questionsFilled in on your requestsFilled in on your requests
Nothing added that the request never saidFilled in on your requestsFilled in on your requests
No scores yet. Every cell stays empty until your own requests have been through the test.Your reviewer scores each one and makes the call.

// After a yes

A month of live requests

Once your reviewer approves, new requests get the same scope sheet for about 30 days.

Your engineer reads every sheet before a scope is written, and each proposal still leaves your office exactly as it does today.

Live requests keep being compared with the scopes your team writes. A second job would be its own decision, with its own price.

// Possible next jobs

After proposal scopes, if you want more

Ranked, not promised
Priced one at a time
  1. 01

    Boring log data tables

    Once drilling is done, field logs and lab sheets reconciled into report tables for the engineer of record.

    Next
  2. 02

    Lab test request sheets

    The samples your engineer picks for testing listed for the lab by boring, sample number and method.

    Then
  3. 03

    Addendum change logs

    Each addendum to an open request compared with the version you scoped, so a changed boring, depth or test is seen before pricing.

    After that

// One hard limit

The scope is your engineer's, never the AI's.

The sheet repeats what a request says and lists what it leaves out. It never sets a boring count, a depth, a lab program or a fee, never classifies a soil or recommends a foundation, and never sends a proposal, a question or anything else. It never touches your project system, a client portal or a live proposal, and it works only on copies. A licensed engineer on your staff makes each technical decision and seals each document.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob sets the range on the call from two counts: requests your office scopes in a month, and how many come from public agencies with their own forms.

// Questions

Proposal scope questions

Will the AI decide how many borings we drill?
No. It lists the borings, depths and intervals a request asks for, with the page and the person who asked. The program your firm proposes stays your engineer's decision.
Our requests range from a full county bid to a three-line email. Does that matter?
No. A thin request mostly produces a longer list of what it leaves out, which is often the part your engineer finds most useful. Put both kinds in the sample.
What if a request contradicts its own site plan?
The sheet shows both versions with their pages and turns the conflict into a question for your engineer. Whether to ask the client, and how, is up to your team.
Does it read addenda and answers to pre-bid questions?
Yes, when you include them. Each item on the sheet notes whether an addendum changed it, so nobody scopes from a page that was replaced.
Can it check a request against the building code?
It quotes any code section or standard the request cites, and what that section asks for when its text is in the file. It never decides whether a code applies or whether a scope complies. That judgment is your engineer's.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Start with last year's investigation requests.

A half-hour call with Rob about your firm and your role, the clients who send you requests, and roughly how many you scope in a month. Requests and proposals are not copied until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.