When a patio becomes a permit: walls, drainage and paving at estimate.

How tall can a retaining wall be before it needs a permit? That depends on the jurisdiction and on where it starts measuring. Portland, Oregon requires a building permit for a wall more than four feet high measured from the bottom of the footing to the top of the wall, or for any wall supporting a surcharge, which the city describes as load beyond the weight of level earth backfill (as checked on 16 October 2026). Other places set other heights and add their own rules on paving and runoff.

So the moment to ask is the estimate, not the dig. An AI assistant can flag possible triggers on every draft quote against rules the owner has written down. It only flags: the building or planning department decides what its rules require, and only a licensed engineer or the building official can say whether a wall must be engineered. Nothing here is legal or engineering advice.

Because Portland measures from the bottom of the footing, a wall with a visible face a little over three feet, standing on a footing set below finished grade, can be over the four-foot line on the drawing while looking under it on site. A tape held against the face measures the wrong thing for that city.

The same page says walls over four feet need stamped drawings and calculations from an engineer registered in Oregon; that a zoning permit may apply where a building permit does not, and a Site Development permit on complex sites or for slope stabilization; and that no part of the wall's foundation, the toe included, may end up off the property. Its site plan shows property lines, easements, distances to property lines, the wall's placement and the area of any proposed paving.

Paving area is easy to miss because it is spread across line items: patio, path, steps, a widened drive. In Portland, the retaining-wall permit page says a project adding more than five hundred square feet of impervious area needs a mitigation form, a stormwater plan or both. Mt. Lebanon, a Pennsylvania municipality, requires a permit for any new, replaced, modified or relocated residential patio, and a patio adding more than five hundred square feet of impervious surface needs stormwater management under Mt. Lebanon's stormwater management ordinance (patio procedure dated May 2023, as checked on 16 October 2026).

That two pages land on the same figure tells an estimator nothing about the next town, so the sheet keeps a row per jurisdiction.

Under Class F of the Town and Country Planning (General Permitted Development) (England) Order 2015, a hard surface between the wall forming the principal elevation of a house and a highway that covers more than five square meters must be porous, or drain its run-off to a permeable or porous area within the property, to count as permitted development (legislation.gov.uk, as checked on 16 October 2026). The government's 2009 guidance on permeable front gardens, still on GOV.UK, says a traditional impermeable drive over that size with nowhere for water to soak away needs planning permission.

The guidance adds that rights are tighter in designated areas such as conservation areas and national parks, advises speaking to the local planning authority first, and warns against directing water towards a neighbor's property. The questions for an estimate are where the paving sits, how large it is, what it is made of and where its water goes; the planning authority answers them.

Drainage resists a single number. Portland lists slope and retaining-wall drainage and erosion control among the matters its site development review addresses, requires erosion control to be installed and inspected before further ground disturbance once a permit is issued, and issues a separate permit for work in the public right-of-way. The trigger sheet does not judge any of that. It records where the water from the scope goes, and any answer pointing at a neighbor, a right-of-way or a slope goes to the owner, who decides with whichever engineer or official the job needs.

This is Aevrion's pattern, not a Grok Bot feature. Grok Bot's Bots are durable and named, and they all work on one persistent cloud computer shared across the account. The owner creates an Estimate-Check Bot and gives it a trigger sheet: each jurisdiction's rules copied from the department's own pages, with the address and the date read. The documentation is explicit that recalled facts are not authoritative, so the Bot opens the sheet and the quote afresh every time.

For each draft quote it returns a document with headings and source links, a kind of reviewable output the documentation suggests asking for: one heading per possible trigger, the line items behind it, the rule and its link, and what the quote could not tell it, such as the depth of a footing nobody has designed. Its lasting rules say it flags and never concludes; a remembered rule guides rather than enforces, so the owner reads every sheet before a quote goes out.

What the sheet asks of every quote, in an illustrative form:

• WALL HEIGHT, AS MEASURED LOCALLY

  Measured from the point the local rule names, such as the bottom of the footing in Portland, or marked unknown.

• LOAD ABOVE THE WALL

  A drive, patio, steps or slope above the wall, flagged as a possible surcharge for the department or an engineer to judge.

• NEW HARD SURFACE

  New paved area summed across all line items and set against each threshold.

• FRONT OF THE HOUSE

  In England, paving between the house front and a road: its size, material and drainage.

• SETBACKS AND LINES

  Distances to property lines and easements, and any part of the work, footing included, that could fall outside the property.

• WATER LEAVING THE SITE

  Where the scope sends water, and whether that is towards a neighbor or a right-of-way.

• ASSOCIATION

  Whether the client says the property has a homeowners' association or design covenants. Their rules are not public, so the client or owner obtains them, and the association's approval is a separate step from any permit.

• DIGGING AREAS

  Planting and excavation areas, ready for the 811 locate request a person submits a few business days before digging.

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.

A flag is a question for a person. The owner decides whether to ask the building department, bring in an engineer, order a survey or record why the rule does not apply. The assistant never suggests lowering, splitting or moving a wall to stay under a threshold; those are design and engineering choices.

What changes is candor about dependency. A wall that may need engineering appears as a line that depends on that decision, and the client hears it before signing, in an email the assistant drafted and the owner sent. Applications and signatures go to the department from a person, and if a portal asks for a login, the Bot hands that step to the owner through a takeover instead of bypassing it. A weekly routine can list quotes with open flags; the documentation describes no alert if a run fails, so the owner checks the run history when the list does not arrive. The reliable-workflows pillar covers routine design.

Open the building and planning pages for the town where the company quotes most. Copy its retaining-wall, impervious-area and patio rules into a sheet with links and dates, then run last season's quotes against it by hand. A job that crossed a line nobody priced is the argument for the check.

Then score the estimate-to-proposal check in the workflow automation readiness assessment. There is no sign-up and no charge; it scores that one workflow across twelve dimensions and straight away shows one of four results, the obstacles it detected and a suggested next step. If the rules live only in the estimator's head, expect rule clarity to score low, which caps the result until the sheet exists. From there, Aevrion Ops can turn the sheet into an Estimate-Check Bot with its stop points, and connect it to estimating software, subject to that vendor's API or terms and to testing first.

1. Retaining-wall permit height is local: Portland's line is more than four feet from the bottom of the footing, or any wall with a surcharge.
2. New paving can bring its own rules: Portland's retaining-wall page and Mt. Lebanon's patio procedure both name five hundred square feet of new impervious area.
3. In England, more than five square meters of hard surface in front of a house must be porous or drain to a permeable area, or it needs planning permission.
4. An Estimate-Check Bot reads each quote against the owner's written rules and flags possible triggers; it never decides one.
5. Engineering is for a licensed engineer or the building official, and every application is made by a person.