AI for fence companies: the approvals tracker comes before the schedule.

Before a crew can dig, a fence job has to collect a short list of outside yeses: the homeowners' association where there is one, the permit office where the job trips a permit trigger, the utilities through the state 811 center, and a settled property line. None of them is the fence company's to give, and each moves at its own pace. When one is missing on install morning, the crew loses the day and the customer starts to doubt the date they were promised.

Supervised AI assistants can draft the takeoff from a customer's photos and sketch, keep one row per job showing which yeses are in, prepare the chasers the owner sends, and offer install windows only to jobs that are cleared. They grant none of the four. This page covers the whole office; the spring-backlog article follows one owner through a crowded season, and the pre-dig checklist takes the four approvals one at a time.

The City of Orlando's published guide, as checked on 16 October 2026, shows how the yeses stack up in a single city. Its fences must stand on the owner's side of the boundary or on the line itself. Plenty of residential fences need no city permit at all, yet the guide warns that where a homeowners' association exists, its approval is still required. And a permit becomes necessary the moment any item on the guide's list applies, among them: a height over six feet, concrete or masonry construction, a fence that acts as a pool or spa barrier the code requires, a vehicle or powered gate, a public easement shown on the survey, or a lot in a floodplain.

Under all of it sits the locate. The national 811 service tells anyone putting in a fence to reach their state's one-call center a few business days early and to wait until every utility has answered before breaking ground (as checked on 16 October 2026). Orlando is one city. Every jurisdiction writes its own list, and the owner checks the rules wherever a job sits; the pre-dig checklist in this series goes deeper into association approval, permit triggers and setbacks, with examples from other cities.

A fence inquiry may arrive as phone photos and a rough sketch: the back of the house, an arrow along each side, a note that the dog gets out by the shed. A Quote Bot can turn that into a draft takeoff: each run in linear feet, the line, corner, end and gate posts it implies, panels or pickets, rails, gate hardware, concrete for the footings, and removal and haul-off of an old fence. Every figure carries a label saying where it came from, the sketch, a photo or the owner's own tape, so the owner sees at a glance what was measured and what was guessed.

The owner verifies the takeoff, on site or with whatever measuring method the owner trusts, and decides how each run follows a slope, racked or stepped. Prices come from the company's own price list, read fresh every time. The documentation warns against treating what a Bot remembers as the record, so a remembered panel price never reaches a quote.

Consider an illustrative inquiry, invented for this page: a homeowner on a corner lot wants a six-foot privacy fence around the backyard and a double gate across the driveway so a trailer can be parked behind it. The draft takeoff the Quote Bot prepares might read like this.

• RUNS

  Three runs from the sketch, each in linear feet, two of them marked as estimates until the owner measures the side along the street.

• POSTS AND GATES

  Line, corner and end posts by run; one pedestrian gate by the shed; one double drive gate, with its hardware listed separately.

• APPROVAL FLAGS

  A drive gate and a corner lot. In Orlando a vehicle gate is a permit trigger, a gate across a driveway must sit at least 20 feet back from the property line, and corner sight triangles stay clear. The owner checks the same points for whichever city the job is in.

• HOA

  The homeowner mentioned an association. Approval needed before any date is offered.

• STILL TO SETTLE

  Whether a survey exists, where the street-side line runs, and what the old chain-link costs to remove.

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 owner sets these assistants up as Bots in Grok Bot; the roles are Aevrion's pattern, not product features. The documentation presents a Bot as a named teammate: it has a job, keeps its own conversation, and works from a persistent cloud computer that includes a web browser and a file system. It also advises starting with the smallest roster that covers genuinely different roles. For a fence company that means two Bots at first, Quote and Approvals, with a Schedule Bot added once the tracker matches what is really happening on the ground.

Standing rules live in each Bot's memory, given to it in chat: never state a price that is not on the price list, never give a homeowner a date for a job that is not cleared. The documentation treats a remembered rule as guidance rather than a lock, so customer-facing words still pass through the owner. Email a Bot writes waits as an editable card in that Bot's conversation until the owner chooses Send or Discard. Whether any other step waits for the owner's say-so is set by the kind of tool, how risky the step is and the owner's own rules; the product does not make every action wait.

Some things are simply not there. The documentation describes no telephony, so the Bots take no calls and send no texts, and an inquiry phoned in reaches them as the owner's note. Routines cannot be scheduled closer together than five minutes, so the office works a step ahead of the day rather than answering anything on arrival.

The tracker is a shared file in the company's own system, and a spreadsheet will do: one row per signed job. The Approvals Bot keeps it current from what arrives, such as the association letter a homeowner forwards, the permit the owner downloads or the ticket number the owner logs, and it reads the file each time it works rather than relying on what it remembers. The states below are an Aevrion pattern. The point of them is the second column: every state has a named holder, and most of those holders are outside the company or are the owner.

Not every job passes through every state. Where no permit trigger applies, the owner records that judgment on the row, so the gap is a decision rather than an omission.

1. 01

   Signed

   Owner

   The owner

   Advances when

   The Approvals Bot opens the row and lists which approvals this address needs, from the owner's notes on that city and any association

2. 02

   Waiting on outside yeses

   Owner

   The association, the permit office, the utilities and, for the line, a recorded survey or a licensed surveyor; the owner chases each

   Advances when

   Every approval the row lists is on file, as the pre-dig checklist sets out

   Ends when

   An association denial goes to the owner, who decides whether to redesign

3. 03

   Cleared to dig

   Owner

   The owner

   Advances when

   The owner gives the ground-break go and the job joins the crew calendar

4. 04

   Installed

   Owner

   The crew lead

   Advances when

   Posts set, panels hung, gates adjusted; the crew lead's photos reach the Bot through the owner

5. 05

   Inspected

   Owner

   The building inspector, where the permit calls for a final inspection

   Advances when

   The result is recorded on the row

   Ends when

   A failed item goes back to the owner and the crew lead

6. 06

   Invoiced

   Owner

   The owner

   Advances when

   The invoice and the written warranty go out, sent by the owner

7. 07

   Under warranty

   Owner

   The owner

   Advances when

   A warranty call is logged with the install photos, and the owner decides whether it is covered

   Ends when

   The warranty period ends and the row is archived with its approvals attached

Scheduling at a fence company is mostly a question of which jobs are allowed onto the calendar at all. A Schedule Bot that offers dates to every signed job fills the crew's week with holes that may not be dug. So it is given a narrow lasting rule: propose windows only for rows marked cleared to dig, check that the materials for that job have a confirmed delivery, and draft the customer's confirmation for the owner to send.

Reading the crew calendar or a supplier's order page needs a custom integration, which exists only if that vendor's API or terms permit one and is tested before the crew depends on it, or else supervised browser use where the site permits. Bots can work many browser-based tools, the documentation notes, though sites can block automation, and any password, two-factor code or payment is handled by the owner taking over the Bot's screen. 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.

The obvious first routine is a weekly check that lists next week's installs still missing a yes. The spring-backlog article shows that check at work in a crowded season, so only its limits belong here. When work starts without the owner, as a routine does, any approval request it raises expires after roughly ten minutes (Cursor's help pages say thirty) and the action it asked about does not run; a request raised in a chat the owner is in simply waits. Nor do the docs promise a second attempt or a warning after a failed run, so the owner opens the run records. The routine produces a list; the owner moves the crew.

Where a fence company also builds decks, the office pattern carries over but the substance does not. A deck is a structure. Its footings, framing, attachment to the house, guards and stairs are matters for the jurisdiction's building code, the building department and whoever designs the deck. This page states nothing about any of them, and an assistant built on this pattern never does either.

What a Bot can do for a deck job is keep its paperwork moving: the drawings the designer produces, the permit application the owner submits, and the inspection dates the building department sets, each logged against the job as the owner enters it. Orlando's fence guide lists decks among the features a site-plan survey should already show, a useful reminder that a deck and a fence on one property often rest on the same survey. Whether a given deck needs a permit, drawings or inspections is the building department's answer, read by the owner.

The Bots prepare paper for every item below and hold none of them. Each is either a judgment about land and safety or a commitment made in the company's name.

• PROPERTY LINE

  Where the line runs: a recorded survey or a licensed surveyor's stake-out, and any doubt about a marker goes to a licensed surveyor. No Bot reads a boundary off aerial imagery or a parcel map.

• GROUND-BREAK GO

  Whether the crew digs: the owner, once every utility on the ticket has responded and the line is settled.

• PRICE

  The owner, from a verified takeoff and the company's own price list.

• POOL BARRIERS

  Whether a pool fence and its gates meet the local rule: the building inspector decides; the owner builds to the rule the jurisdiction has adopted. The CPSC's barrier guidelines are not mandatory unless a state or locality has adopted them.

• ASSOCIATION APPLICATIONS

  Submitted in the homeowner's name and signed by the homeowner. A Bot assembles the drawing and drafts the covering letter.

• NEIGHBORS

  Anything said to a neighbor about a shared boundary: the homeowner, whose boundary it is, with the owner there to explain the work if asked.

Before any Bot exists, take last season's jobs and mark, for each one, the outside yes it waited on longest and who was supposed to be chasing it. If the honest answer to the second question is nobody, the tracker is the first thing to build and the Approvals Bot is the first Bot.

Then score that approval-chasing workflow in Aevrion's readiness assessment for workflow automation. It is free and ungated, and it rates a single workflow on twelve set dimensions, among them repeatability, rule clarity, manual re-entry and ownership clarity. The result arrives at once: a score, one of four verdicts running from not ready yet to high-leverage candidate, the blockers behind it and a suggested next step. Ownership clarity is the dimension to watch if association follow-up belongs to no one, because a low mark there caps the whole result. If the result points towards building, a scoping conversation with Aevrion Ops would cover the tracker, the three Bots, where each stops for approval, and any custom integration to the calendar and supplier systems already in use.

1. A fence job stalls before the first post hole, on the association, the permit office, the utility locate or the property line, so the office is an approvals tracker first.
2. In Orlando, as checked on 16 October 2026, a city permit can be unnecessary while HOA approval is still required, and every fence stays on or inside the property line.
3. A Quote Bot drafts linear-foot takeoffs from photos and a sketch with every guessed figure labeled, and the owner verifies them and prices from the company's own list.
4. Install windows go only to jobs marked cleared to dig with a confirmed materials delivery.
5. Decks get the same paperwork tracking and no structural statements from anyone except the code, the building department and the designer.
6. The property line, the ground-break go, price, pool-barrier compliance and neighbor conversations stay with people.