AI for residential excavation: estimates, locates and the schedule.

Residential excavation sits in the middle of other people's paperwork: the general contractor's building permit, the septic installer's permit, the homeowner who wants the yard to stop draining towards the house. The excavator is the one who actually opens the ground, and before that happens two things have to be true: the buried utilities have been located and marked in answer to a locate ticket, and someone with the authority to judge the ground has decided how any trench will be protected. Those are the two gates of this trade, and neither belongs to software.

Supervised AI assistants suit the paper around the gates: drafting estimates from the owner's own quantities and rates, keeping every locate ticket's dates and responses in one place, proposing a week that moves with rain and inspections, and carrying the stormwater facts a job depends on. Declaring a site clear to dig, choosing a protective system, setting a price and submitting a ticket stay with named people. Two companion guides in this series go further: one follows an owner-operator's week from the cab, the other works through the locate-ticket log.

The first gate is the locate. The national 811 service asks everyone who digs to request marking through 811 or the state center's website a few business days in advance, and to check that every utility has answered before the ground is broken; the paint or flags show approximate positions only (as checked on 16 October 2026). OSHA's construction standard puts the duty on the employer. Under section 1926.651(b), where the utilities probably run has to be worked out before any excavation opens, their owners must be asked to locate them, and their precise position is confirmed by safe means as digging gets close.

The second gate is protection from cave-ins. Section 1926.652(a) requires every employee in an excavation to be protected by an adequate protective system unless the excavation is entirely in stable rock, or is less than five feet deep and a competent person's examination of the ground shows no indication of a potential cave-in. Section 1926.651(k) adds competent-person inspections of the excavation, the ground beside it and the protective systems, each day before work, as needed during the shift and after every rainstorm. OSHA's trenching page calls cave-ins the biggest threat to workers' lives and offers three remedies: slope or bench the walls, shore them, or shield them with trench boxes.

These federal rules apply where federal OSHA has jurisdiction, as it does over most private-sector employers in Florida, Texas and Georgia; states with their own OSHA-approved plan, such as Minnesota and Michigan, enforce their own standards, and the owner confirms which applies. Nothing here is advice about a particular trench. What protection a cut needs is the competent person's decision, and a sloping or benching design outside the standard's own options must be approved by a registered professional engineer.

On a small excavation company's account, Grok Bot holds Bots the owner has named, each given one job, a conversation of its own and standing rules to remember. All of them work from one persistent cloud computer that carries on when the laptop is closed. The documentation advises the smallest useful roster, adding a Bot only for a stable specialist role. For a residential excavation company that points to three, each the owner's creation under an Aevrion pattern rather than anything the product ships with: a Locates Bot that keeps the ticket log, an Estimate Bot that turns the owner's takeoff into a draft proposal, and a Schedule Bot that drafts the coming week from the forecast, inspection dates and the other trades' plans.

The documentation also draws the edges. Every Bot on the account shares one computer, with its files, browser sessions and sign-ins, and separate Bots are not a security boundary, so the business bank login stays off it. Memory is not a source of truth: rates, ticket numbers and inspection dates are read from the company's own files every time. Estimating, accounting or job software is reached through custom integration or supervised browser use where the vendor permits it, subject to testing; no excavation product appears in the documentation as a built-in connection.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Picture, as an illustration, a request to cut a level pad for a detached garage on a lot that falls away towards the street. The owner walks the site and notes the soil, the slope, the access for the machine and where spoil can sit, then works out the numbers: the cut on the high side, the fill on the low side, how many truckloads leave if the two do not balance, the base stone coming in, the machine hours and the compaction. Those numbers are the estimate. An assistant cannot measure a slope it has never stood on.

The Estimate Bot does the assembly. It reads the takeoff the owner entered, applies rates from the owner's current rate sheet and drafts the proposal in the company's own format, with the scope, the exclusions the owner always writes and the assumptions the price rests on. Where a quantity is missing, such as a haul-off count with no disposal site named, it stops and asks instead of filling the gap. The draft states what the price assumes about rock and groundwater because the owner's template says it must; whether to carry a contingency is the owner's choice.

The owner prices, edits and sends. A proposal travels by email, so the Bot prepares it as an editable draft in the owner's conversation, and the owner sends or discards it. A change order follows the same road when the bucket finds rock halfway down: the owner passes on what the operator found, the Bot drafts the change from the rate sheet, and the owner and the customer agree it before the extra work goes on an invoice.

Every dig starts with a ticket, and every ticket carries dates: filed, earliest dig, and end of validity. They differ from state to state, and the company works to its own state's rules as the owner has confirmed them. The locate-ticket guide in this series sets out the log and compares three states' rules; here the point is where it fits. The Locates Bot keeps that log and posts a morning list of jobs whose tickets are unanswered or close to lapsing.

Filing is a submission, so it sits behind the owner. The Bot can prepare the request from the job record and, where the state center's website allows it, fill in the online form through supervised browser use, subject to testing; the login, any verification step and the final submit are the owner's. The Bot never rings the center, because the documentation describes no telephony at all.

Outside the United States the gate takes another shape. Before You Dig Australia calls itself a single point of contact: one inquiry is passed to every member asset owner near the site, and the plans those owners send back mark where assets are present, not precisely where they lie. That is the service's own account, in a 2023 inquiry guide that South Australia's infrastructure and transport department hosts (as checked on 16 October 2026). A company working there logs inquiries and plan responses in the same way.

Rain and other trades' inspection dates move an excavation week, and section 1926.651(k) calls for a fresh competent-person inspection after each rainstorm. On a schedule the owner sets, the Schedule Bot drafts next week's order of work from a public forecast, the inspection dates the permit holders have confirmed and the Locates Bot's ticket dates; the owner settles the order and sends any emails. The owner-operator guide in this series follows one rained-off week through those moves.

Each routine belongs to one Bot and runs on a timetable no tighter than five minutes; a Bot may hold fifty, and only the last twenty runs of each are kept for review. Nothing in the documentation retries a failed run or raises an alarm about it, so a missing morning list means opening the run history, not assuming the forecast was dry.

EPA's construction stormwater page says a Clean Water Act permit is required for stormwater discharges from construction activity that disturbs one acre or more of land, or less than one acre where the work is part of a common plan of development or sale that will ultimately disturb one acre or more. Clearing, grading and excavating all count as construction activity. In areas where EPA is the permitting authority, its 2022 Construction General Permit expires on 16 February 2027, and EPA has published a proposed 2027 permit to replace it (as checked on 16 October 2026).

A lot inside a subdivision may belong to a larger common plan even when the dig is small, and that is not a question an assistant answers. The job record carries the disturbed area the owner or site designer measured, whether the lot sits within a larger plan, who holds any stormwater coverage and when that was confirmed. Local grading permits run on different numbers again; the owner-operator guide in this series puts two jurisdictions' thresholds side by side.

The documentation's approval cards give three choices, Allow once, Always allow and Deny, and approving never undoes what has already happened. A card in a conversation the owner has open stays until answered; a card produced by unattended work, a routine or another Bot's message, lapses after roughly ten minutes (Cursor's help pages say thirty) without running its action. None of that decides who is accountable on a dig. The Bots prepare; the lines below stay with named people whatever the approval settings say.

• CLEAR TO DIG

  The owner decides on the morning, with the ticket responses and the marks on the ground in front of them. No Bot writes those words.

• EXPOSING A MARKED LINE

  How to approach and uncover a marked utility is the operator's call on site, under the state's rules.

• TRENCH PROTECTION

  Sloping, benching, shoring or a shield, and each inspection, belong to the competent person; anything outside the standard's options goes to an engineer.

• QUANTITIES AND PRICE

  The owner's takeoff and the owner's rates. The Estimate Bot assembles the draft and asks about gaps.

• TICKETS AND PERMITS

  A Bot may fill in a ticket request, update or permit application, but the owner signs in through a takeover of the Bot's screen and presses submit.

• MONEY

  Deposits, stone and haul purchases and payments stay with the owner; the documentation hands payment confirmations to a person. Cursor's help pages add that a card saved in the Bot's Vault can be used at checkout without asking each time, so this design saves no card there.

• STORMWATER

  Whether a site needs coverage, and under whose name, is settled by the owner with the site's designer or the permitting authority.

Take one recent job priced from a takeoff, such as the garage pad, and trace it from the site walk to the signed proposal: where each rate came from, which exclusions were written, and how long the draft waited for a haul-off count or a disposal site. That trail shows whether the Estimate Bot or the ticket log should come first.

A scoping conversation with Aevrion Ops can start from that trail: which of the three Bots to build first, the approval rules each one works under, and whether a custom integration to the company's estimating or job software is possible under that vendor's API or terms, once tested. An owner who would rather measure first can use the free readiness assessment, which rates one workflow, such as estimating from site walk to signed proposal, on twelve set dimensions and gives an immediate result in one of four bands, with the obstacles it spotted and a next step. If the rate sheet and the standard exclusions live only in the owner's memory, rule clarity will score low and cap that result.

1. Every residential dig passes two gates first: utility marks answering a locate ticket, and a competent person's decision on trench protection.
2. Federal OSHA requires the estimated location of utilities to be determined before an excavation is opened, and cave-in protection unless an exception applies; state plans enforce their own standards.
3. The Estimate Bot assembles proposals from the owner's takeoff and rate sheet, and stops to ask when a quantity is missing.
4. Locate-ticket dates differ by state, so the log follows the owner's confirmed rules and never declares a site clear to dig.
5. EPA requires stormwater permit coverage for construction disturbing one acre or more, including smaller lots within a larger common plan.
6. The Bots draft ticket filings, purchases and customer messages; the owner submits, pays and sends, and signs every consequential line.