Hidden conditions and change orders: from discovery to a signed change.

A hidden condition is anything the estimate could not see: rot behind a shower wall, a joist notched for an old drain, wiring older than the house's last renovation. The remodeling change order process exists to make sure each one is written down, described, priced and agreed before the crew builds the answer. Disputes start in the gap between finding and agreeing, when work carries on because the client said yes in the hallway.

An AI assistant can do the writing-down and the describing: a discovery-log entry for each condition and a change-order description drafted from it, with no price. The owner prices it, a person sends it, the client signs it and the crew continues. In California the signature comes before the change, by rule.

Each hidden condition moves through the same states. The value of naming them is that a condition nobody owns becomes visible while the wall is still open.

1. 01

   Found

   Owner

   The lead carpenter

   Advances when

   Photos and a written note reach the job folder the same day

2. 02

   Logged

   Owner

   The job-file Bot

   Advances when

   An entry holds all five required fields and the carpenter confirms it

   Ends when

   Marked stopped when it concerns a suspect material; nothing more is prepared until the owner decides

3. 03

   Described

   Owner

   The job-file Bot, then the carpenter

   Advances when

   The carpenter corrects and accepts the draft description

4. 04

   Priced

   Owner

   The owner

   Advances when

   The owner adds the price and any schedule effect

5. 05

   Sent

   Owner

   The owner

   Advances when

   The owner reviews the email draft and sends it

6. 06

   Signed

   Owner

   The client and the contractor

   Advances when

   Both signatures are on the change order

   Ends when

   Withdrawn if the client declines; the log records it and the original scope stands

7. 07

   Building

   Owner

   The lead carpenter

   Advances when

   The changed work proceeds and is recorded as done

A discovery log does not need to be elaborate, but every entry needs five things, and the job-file Bot is told never to mark an entry complete without them. The fields are Aevrion's pattern, not a product feature.

Two optional fields earn their place: a link to the change order once it exists, and the entry's current state from the loop above. With them, the log answers the question owners otherwise piece together from texts at the end of a job: what was found, when, and was it signed before it was built?

Grok Bot takes the paperwork of a remodel as chat attachments. Site photos, phone video, PDF drawings, spreadsheets, Word documents and forwarded emails are all accepted, six at a time from the desktop; each image or document may be as large as 25 MB and each video 200 MB, though an oversized, damaged or encrypted file may not open. Ask a Bot for a reviewable output, such as a document laid out under headings or a spreadsheet with named columns, and both the log and the draft fit that shape.

The description says what was found, where, what the carpenter or trade partner proposes, and what in the original scope changes. It does not say why the condition exists, whether it is dangerous or what it will cost. The firm's procedure for writing it can be saved as a skill, a reusable set of instructions holding the steps, decision rules and expected output, so every draft takes the same shape. The log itself stays in a file the firm keeps; the documentation tells users to hold changing facts in the source system rather than in a Bot's memory.

The Grok Bot documentation names no connector for pricing, design or e-signature tools. Getting at them means a custom integration that Aevrion builds on the vendor's API, or a Bot using the vendor's website where the terms let it; neither is trusted until tested, and sign-ins with two-factor steps go to a person.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 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 consumer page of California's Contractors State License Board on what a contract is (as checked on 15 October 2026) sets out the California position: the home improvement contract and every later change go in writing, and any move in price or scope needs a written change order carrying the signatures of both customer and contractor before that change happens, after which the order forms part of the contract. Other states set their own rules. The owner confirms them, and the wording of the firm's change-order form, with a lawyer.

The assistant's contribution is a check, not an opinion. A weekly routine owned by the job-file Bot compares the log with next week's crew schedule and lists every condition scheduled for work whose change order is not yet signed. It is defined the way the Grok Bot documentation suggests, by settling six things up front: which Bot owns it, when it runs and in which time zone, what it reads, what it should produce, where it must stop, and what to do if its input is absent. Here the stopping point is the list itself, and a schedule that has not been updated produces a note saying the check did not run, never a list built from last week. The owner reads the list and decides what moves.

Suspect asbestos stops the loop at Logged. CPSC's Asbestos in the Home guide, checked on 15 October 2026, includes among possible sources textured paint, the patching compounds used on wall and ceiling joints, some vinyl floor tiles with the backing and adhesives of sheet flooring, and coatings on hot-water and steam pipes in older houses, and its instruction is plain: do not saw, sand, scrape or drill them. When an entry concerns one of these, the Bot marks it stopped and prepares nothing further. Whether to stop the work, and whether to test, are the owner's calls; the assistant never assesses a material.

Lead paint is a boundary at Described. Under EPA's renovation rule, 40 CFR 745.84 (as checked on 15 October 2026), a firm renovating housing covered by the rule hands the owner EPA's lead pamphlet within the 60 days before work starts, and either gets the owner's written acknowledgment of receipt or holds a certificate of mailing dated at least 7 days before the renovation. A change order that carries work into painted surfaces the original scope did not touch is a moment for the firm's own lead-safe process, run by the people who hold the credential. The log flags the year built and leaves the reading of the rule to the people responsible for it. Painters' RRP paperwork has its own article in this series.

Each of these is a commitment by the firm, so each belongs to a named person.

• PRICE

  The price line stays blank until the owner fills it.

• SEND

  Change orders reach the client as drafts a person reviews and sends.

• SIGN

  Signatures are the client's and the contractor's, collected by a person or through an integration a person set up.

• RELEASE THE CREW

  The carpenter moves into changed work after confirming the signature is on file.

• JUDGE A MATERIAL OR A HAZARD

  Suspect materials, wiring and structure are judged by the people qualified to judge them.

• DECIDE WHAT IS IN SCOPE

  Whether a condition is already covered by the contract is the owner's reading, with a lawyer where it matters.

Take a finished remodel, give the job-file Bot its photos and notes, and let it build the log and the descriptions. Compare them with the change orders the firm actually issued, and fix the procedure wherever they differ. Then run it on a live job in read-and-prepare mode for a few weeks before scheduling the weekly check. Routine design in general, including what a check does when its input is missing, is the subject of the reliable home-service workflows guide.

Aevrion Ops can set this up for a remodeling firm: the log format, the description procedure, the weekly signature check, the approval boundaries and the integrations with the firm's estimating and e-signature tools, where the vendor's API or terms allow and once tested. The workflow automation readiness assessment is where that work starts.

1. Each hidden condition moves from found to logged, described, priced, sent, signed and built, and every state has one owner.
2. A discovery-log entry needs a date, a photo, a location, the PM's note and a draft description with no price.
3. In California, changing the price or scope takes a written change order that both parties sign first; elsewhere the owner confirms the state's own rule.
4. A weekly list-only routine flags scheduled work whose change order is unsigned; it changes nothing itself.
5. Suspect asbestos stops an entry, and pre-1978 paint sends the change to the firm's lead-safe process; the assistant decides neither.