AI for drain and sewer companies: from camera footage to an approved repair.

A drain and sewer specialist is paid twice on the same job. The first time is for the cable or the jetter that gets water moving again. The second is for the repair the camera inspection points to: a spot repair, a lined pipe, a replacement, or a maintenance plan that buys time. Between the recording and that decision sits work nobody on the truck has time for: the report, the options, the permit question and the follow-up.

That work is what supervised AI assistants can prepare. They start from what the technician has already produced, meaning the coded observations, the stills and the notes, and they produce drafts. They do not code the footage, choose the repair method, set the price, decide who owns a damaged section or present the options to the customer. Those stay with the trained technician and the owner. This page is the drain and sewer guide in Aevrion's home-service industries series.

A camera inspection produces a recording, a distance counter and a set of observations at points along the pipe. To the technician that is a clear picture. To the person paying for the work it is several minutes of dark video and a list of codes. A homeowner who cannot follow the evidence may hear a repair recommendation as a sales pitch.

That makes the back office of a sewer company unusually concrete. Four documents decide whether a camera finding becomes approved work, and each is built from evidence that already exists by the time the truck leaves. The test for an assistant is whether it can assemble them faithfully without adding anything the technician did not see.

Structured coding is what turns a recording into something that can be compared from one inspection to the next. NASSCO runs three assessment programs for it: PACP for mainline pipes, LACP for laterals and MACP for manholes. Its pages describe them as the reference for consistent condition coding, intended to help system owners plan, prioritize and renew their assets from condition evaluations. Its separate BSDI program covers building sewers and drains, and differs from LACP in that its inspections usually start inside or close to the building and run down the lateral towards the main (all as checked on 15 October 2026).

The assistant's rule follows directly: it never assigns, changes or second-guesses a code. A code is a judgment by a person trained in the standard, and NASSCO requires those people to recertify every three years to keep their PACP, LACP and MACP certification. An assistant can hold the date each technician's certification lapses, entered by the owner from NASSCO's record, and flag any booked inspection where the coder's certification would lapse first. Whether a customer, a municipality or a lateral program requires coded inspections at all is a question the owner settles from that body's own rules.

Each assistant here is a Bot in Grok Bot: it carries a name and a single job, keeps its own conversation and working context, and operates on a persistent cloud computer that has a web browser, a file system and a terminal. A Bot prepares and drafts; a person reviews. The Grok Bot documentation describes no telephony at all, so the Saturday backup call stays with whoever answers the company phone today, and the assistants start from what that person and the technician write down afterwards.

Evidence reaches a Bot as files. The documentation lists images, audio, video, PDFs and documents among the attachment types, with images up to 25 MB each, video up to 200 MB and up to six attachments at a time on desktop. A technician's stills reach the Documentation Bot through the owner, or through a shared folder the owner gives that Bot access to (a custom integration, tested first); a Bot belongs to one person's account, so a crew member's phone does not send to it directly.

Inspection software, the job system and the price book are where that evidence is kept, and none of them has a documented Grok Bot connector. Reading from them is a custom integration or supervised browser use where the vendor permits it, subject to testing. Whatever login the inspection software or a city permit portal needs, once saved on the Bots' shared computer, can be used by every Bot on the account, because Bots share that computer and are not a security boundary from one another; a desk whose login must stay apart needs its own user account, and with it its own computer.

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.

The Documentation Bot's draft follows the pipe. For each observation the technician coded, it gives the distance from the access point, a still where one was supplied, the code exactly as recorded, and a plain sentence on what that kind of observation means for the homeowner, taken from wording the owner has approved once and reuses. It ends with the technician's own summary, quoted, and a list of anything it could not match, such as a still with no observation.

The rules are given to the Bot in chat for it to remember, which is how the documentation says durable rules are set. They are guidance to the Bot rather than a technical control, so the owner still reads every draft. In this trade the rules are short. Never describe a defect as more or less severe than it was coded. Never add a finding. Never recommend a method in the report, because that is the option sheet's job and the owner's. Never state who owns a section of pipe.

Consider a house from the 1950s where the technician finds the pipe material changing at the foundation wall, an offset joint near the sidewalk, and a deformed section beyond it. In this illustration the draft sets out the three observations in order with their stills and codes, explains each one in the owner's approved wording, and flags that the technician's note mentions the sidewalk while nothing in the job record marks the property line. The flag goes to the owner. The draft does not guess where the line is.

The option sheet exists so that the homeowner's choice rests on the evidence rather than on who is standing at the door. The layout used here has three columns: keep the line serviceable with cleaning and a maintenance schedule; repair the defective section, by open cut or another method the owner names; or renew the whole run by lining or replacement. The Estimate Bot fills that layout from the findings and the owner's method notes, reading every price from the owner's price book on every draft. The documentation tells users not to treat a Bot's memory as the authoritative record, and a remembered figure on a sewer quote is that mistake exactly.

The sheet describes; it does not rank. For each option it lists what the work involves, which coded observations it addresses according to the owner's method notes, what it leaves in place, whether excavation, a permit or a locate request is involved, and how long the owner expects the work to take. Whether a deformed section can be lined, or repaired at all, is the owner's decision. When the findings fit nothing in the method notes, the draft says so and stops.

The owner presents the options, by phone or at the door, and the customer chooses. The backup-to-proposal article in this series follows a single job from a Friday backup to a Monday proposal, including how the owner uses the sheet on that call.

Any option that involves digging needs a locate request through the state 811 center, made a few business days ahead, with no digging until every utility has answered the ticket (the national 811 service's guidance, as checked on 15 October 2026). Waiting periods vary by state. The ticket is the crew's legal step, taken by a person. A Permits Bot can keep the ticket's status beside the job and flag digging booked too early; the backup-to-proposal article shows it tracking both clocks.

Sewer permits and lateral programs are local, so the Permits Bot researches them where they are published: the city's permit pages and any program the sewer agency runs. That is supervised browser use: the documentation says Bots can use many browser-based tools, but a site can block automation, and logins, two-factor codes and payments go back to a person. Cursor's help pages add a Vault, where saved logins and cards let a Bot sign in and check out without seeing them, and no setting asks for approval each time a saved card is used, so this design saves no card there. In parts of the East Bay of California, the East Bay Municipal Utility District requires a lateral compliance certificate, or for a sale a time extension certificate in its place, before the title transfers, before final sign-off on permitted work above one hundred thousand dollars, or for a change in water meter size (as checked on 15 October 2026). The sewer lateral certificates article in this series covers that program in detail.

A homeowner may ask who is responsible for a damaged section, and the honest answer depends on the jurisdiction and on where the defect sits. In England and Wales, responsibility moved on 1 October 2011: shared private sewers, and lateral drains beyond the curtilage of the single property they serve, that drained to a public sewer passed to the water and sewerage companies; a drain serving one property inside its curtilage stayed private, and so did pipes draining to a septic tank or private treatment works. The lateral certificates article sets out where the boundary is uncertain. In California, EBMUD's regional ordinance draws its own line, dividing the private lateral into an upper and a lower section at the cleanout near the curb (all as checked on 15 October 2026).

So the rule for every assistant is absolute: a Bot never tells a customer who owns or pays for any section of pipe. It can gather the evidence, meaning the stills with their distances, the cleanout location, the property boundary where a survey is on file and the relevant agency's published definitions, and put it in front of the owner, who makes the statement or refers the customer to the agency.

Plumbing companies also clear drains, and the plumbing guide in this series covers that general service business. A sewer specialist's back office is shaped differently. Its unit of work is the inspection and what follows it, its paperwork is coded findings and option sheets, and its regulatory contact is with sewer agencies, lateral programs and locate centers. The assistants described here are designed around that camera-to-repair business.

Starting small is what the documentation recommends: a single Bot responsible for a whole outcome, with specialist Bots added only once a role has settled. In a sewer business the first Bot is Documentation, because every later step depends on the report. Estimates follows once the reports are dependable, then Permits, then Follow-up, which drafts reminders on open proposals for the owner to send. Follow-up's morning routine never asks for approval, because a card it raised with nobody watching would lapse after about ten minutes (Cursor's help pages say thirty) and the step would not run. That is four Bots at most.

Each of these rests on a trade credential, a duty on site or the customer relationship.

• CODING

  Every PACP, LACP or BSDI code is assigned by the person trained to assign it.

• DIAGNOSIS

  What the defect is, and what caused it, is the technician's finding.

• METHOD

  Cleaning, spot repair, lining or replacement is the owner's recommendation and the customer's choice.

• PRICE

  Every figure comes from the owner's book and is approved by the owner.

• OWNERSHIP

  Who owns or pays for a section of pipe is stated by the owner or the agency, never by a Bot.

• DIGGING

  Locate requests, excavation and site safety belong to the crew; a Bot only tracks status.

• THE CONVERSATION

  The owner presents the options, and drafts reach the customer only when the owner sends them.

Pick five recent camera jobs and follow the paper on each: did the homeowner receive a report they could follow, an option sheet in writing, a permit and locate status, and a follow-up? Settle the report's format first, since the option sheet, the permit research and the follow-up are all built from it; a document the company has never produced by hand is not yet one to hand to a Bot.

Aevrion Ops can help a sewer owner set those pieces down before any Bot is created: the report wording, the option-sheet layout, the boundaries each Bot works within, and custom integrations to your inspection software and job system, as far as each vendor's API or terms permit and once they have been tested. The place to start is a scoping conversation through the contact page.

1. In sewer work the repair decision comes after the camera, and four documents carry it: the report, the option sheet, permit and locate status, and follow-up.
2. PACP, LACP and BSDI coding stays with the trained technician; an assistant explains coded observations and never assigns or changes a code.
3. Option sheets set cleaning, repair and renewal side by side, priced from the owner's book on every draft, and the owner presents them.
4. The locate ticket is the crew's legal step; a Bot can track it and flag digging booked before every utility has responded.
5. Who owns a section of pipe depends on the jurisdiction, as the 2011 transfer in England and Wales shows, and only a person says so to a customer.
6. Start with a documentation Bot; estimates, permits and follow-up come only once each desk before them is dependable.