Turn field notes into a change-order draft before the extra work starts

IntermediateA design, not yet run for a business

For:General contractors and builders

Post this as a projectFree to post. We call you within 2 working days to scope it with you.

The job

On a remodel the client says "while you're here, can you move that outlet?", or the crew opens a wall and finds rot. Extra work starts on a handshake. At the end, the client disputes the bill and the contractor eats the cost. The fix is a written change order, signed before the work, but writing one on site is a chore. The owner's question: "Is every change written, priced and signed before we do it?"

Trigger and outcome

Trigger: the superintendent or lead carpenter sends a note or photo tagged "change". Outcome: a change-order draft with what changed and why, the scope in plain words, labour and material lines for the estimator or owner to price, the schedule effect, and a list of open changes not yet signed.

Tools

  • Hermes drafts the change order from the note and keeps the open list.
  • JobTread or Buildertrend (or the firm's template) holds the change order and sends it for the client's signature.

Steps

Change orders: a field change is noted, the agent drafts scope and line items, the estimator or owner prices it, the owner approves the draft, the client signs, and work proceeds with the change recorded

No extra work without a signed change.

  1. Template. With the owner, the intern sets up the firm's change-order template and the unit costs the owner uses.
  2. Capture. The site lead records what was asked or found, where, and a photo. Client requests and hidden conditions are marked differently.
  3. Draft. Hermes writes the scope in plain words and lists line items with quantities. Prices are left blank for the estimator, or filled from the owner's unit costs and marked "check".
  4. Price. The estimator or owner prices it, adds the schedule effect, and approves.
  5. Sign. The change order goes to the client for signature from the project software. The site lead is told when it is signed.
  6. Track. Each week, the agent lists unsigned changes and any site notes that look like extra work with no change order.

Human checks

  • The owner or estimator sets every price and approves every change order.
  • Work does not start until the client signs, except for safety or damage prevention the owner decides.
  • The agent never tells a client a change is free or included.
  • Contract terms on changes are read by the owner, not interpreted by the agent.

Data needed

Past change orders and the owner's unit costs. For practice, invent a kitchen remodel with six site notes, two of them hidden conditions.

Variations

  • Allowance overages: a change when a client's selection costs more than the allowance.
  • Credit changes: scope removed, with a credit priced by the owner.
  • Sub changes: a subcontractor's change request turned into the client change order.

Where to find more

Further reading, not the source of this design:

Sources

Further reading

More workflow libraries elsewhere

Further reading, not part of our programme: other people's takes on the same jobs.

  • n8n workflow templates ↗

    Community-built automation flows, filterable by sales, marketing, support, document work and AI.

    Read a template for the order of its steps and the apps it touches, then design the approval points yourself.

  • Make templates ↗

    Ready-made scenarios grouped by business area, including invoicing, inventory, HR and email marketing.

    Useful for seeing which systems a small business already connects, before you pick what your agent reads.

  • Zapier templates ↗

    Short trigger-and-action recipes for lead management, support tickets, forms and campaigns.

    Most recipes are one trigger and one action; notice where an agent would add a judgement step and a human check.

  • Claude Cookbooks ↗

    Code notebooks for classification, summarising, extracting data from forms and PDFs, and tool use.

    Open it when a step needs code, such as pulling fields out of a receipt; the ideas carry over to other models.

  • Building effective agents cookbook ↗

    Minimal examples of chaining, routing, parallel calls, orchestrator and workers, and evaluator loops.

    Read it to name the shape of your workflow before you build it; the patterns matter more than the code.

  • Hermes Agent Skills Hub ↗

    Searching skills other people have written for Hermes Agent, from built-in to community sources.

    Read a community skill before you install it, and never give one access to an owner's accounts without review.

  • ClawHub ↗

    The public registry of OpenClaw skills and plugins, including email, calendar, sheets and chat connectors.

    Check who published a skill and what it can touch; treat it as a starting point you read, not a black box.

  • Agent Skills ↗

    The open format for packaging a workflow as a SKILL.md folder that many agents can load.

    Use it when you want to hand a workflow over as a skill file the owner's agent can reuse.