AI for concrete and masonry: bids, pour nights and crack questions.

A concrete contractor's week bends around one evening. The forms are set, the base is compacted, the reinforcement is up on its chairs, a ready-mix order and perhaps a pump are booked, the crew knows when to arrive, and a forecast either agrees with all of that or does not. Whether to pour is a judgment about the concrete, the site and the weather. It belongs to the contractor, with the ready-mix supplier on anything to do with the mix and a licensed engineer on anything structural.

Supervised AI assistants can shorten that evening and tidy the rest of the week. They can turn site notes into a draft bid priced from the owner's own book, watch the forecast against limits the owner wrote, draft the messages a hold would need, and keep the letter that explains cracks ready before anyone asks. They never pour, hold, cancel, choose a mix or tell a homeowner that a crack is harmless.

A flatwork pour cannot be paused halfway. Once the first truck discharges, the crew has to place, strike off, float, edge, joint and finish the slab while the concrete allows it, then protect and cure it. So the commitment is made in advance, and a lot rides on it: the plant batches against an order, a pump operator plans a day around a booking, the finishers keep the day free, and the homeowner has moved the cars.

The National Ready Mixed Concrete Association (NRMCA) gives the reason in its cold-weather sheet, checked on 16 October 2026: concrete that freezes while fresh, which happens once it drops below roughly twenty-five degrees Fahrenheit, may keep less than half of its potential strength and will lack durability. Its hot-weather sheet lists high air temperature, low humidity, wind and sun as conditions that speed up drying and setting.

What a change of date costs, if anything, is set by the supplier's own terms, which the owner knows. An assistant changes only how much of the evening goes on gathering facts rather than deciding.

This page uses Grok Bot for its examples. In its documentation a Bot is a named, durable assistant: it has a job, its own conversation and a memory that keeps the lasting rules it is told, and every Bot on an account works from the same persistent cloud computer, with a web browser, a terminal and a shared workspace folder, which carries on working while the owner's laptop is closed. Remembered rules guide a Bot rather than physically stopping it. On rosters, the documentation's advice is to begin small: give one Bot an end-to-end outcome, and add a second only when a stable specialist role exists.

Nothing in the documentation covers phone calls or text messages, so the phone stays the owner's, and a Bot starts from written material: emails, form entries, and the site notes and photos the owner attaches. No estimating program or ready-mix supplier portal appears among the documented connectors. Getting a Bot into one takes either a custom integration, built for that vendor and tested within its terms, or supervised browser use where the vendor permits it; sign-ins, two-factor codes and payments are steps the Bot hands back so the owner can take over the computer and finish them. 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. Memory, the documentation warns, cannot replace an authoritative source, so every price, yardage figure and pour date is re-read from the owner's files.

An email a Bot prepares shows up in its conversation as a draft the owner can edit, then send or discard. With an Ask first rule for consequential steps, such as submitting an order on a supplier's site, an approval card stops the Bot first, with Allow once, Always allow and Deny; approval covers that action only and cannot undo work already finished.

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 flatwork bid is a short document resting on a long list of assumptions, set out in the table below. An estimating Bot, set up by the owner as a role Aevrion suggests rather than anything the product ships with, can draft a bid from the owner's site notes and photos in the layout the company already uses. Volume is arithmetic: square feet multiplied by thickness in feet, divided by the twenty-seven cubic feet in a cubic yard, plus whatever allowance the owner adds for uneven subgrade and spillage. Prices come only from the owner's price book, opened afresh on every draft.

The useful part of the draft is what it refuses to fill in. When the notes give an area but no thickness, or describe a patio without saying where the water runs off, the draft leaves the line open and asks.

The owner prices the job, checks the scope against the site and decides what the homeowner receives. A Bot that drafts bids never sends one, and never offers a rough number to a homeowner who asks for one by email; it drafts a reply saying the owner will price the job after the visit. Bids promised but not yet sent sit on a short list the Bot keeps, so Tuesday's site visit does not quietly become a lost job.

Masonry work follows the same pattern with different lines: linear feet of joints to repoint, units to replace, matching mortar and brick, access and scaffolding. The draft lists them; any question about whether a wall is structurally sound goes to a licensed engineer, not into a bid.

The week of a pour has paperwork of its own: the order to the plant, a pump booking, the crew's start time and a note to the homeowner about cars and gates. A Bot can keep those drafts on one job record so a changed start time shows up in every message; the guide to a three-person flatwork crew's back office in this series follows that evening work in detail.

The forecast watch is a routine: a scheduled job one Bot runs, spaced at least five minutes from the next run, with up to fifty routines per Bot and the last twenty runs of each kept. The owner writes the limits for a pour, and the routine leaves a recommendation and unsent hold drafts at set points beforehand; the weather-holds guide walks through those checks and the cold-weather facts behind them.

Cracks are the conversation a flatwork contract can prepare for. NRMCA's guidance on cracking, as checked on 16 October 2026, says every slab has some tendency to crack and that entirely crack-free concrete cannot be produced; its sheet on joints describes contraction joints as weakened planes that control where shrinkage cracks form. Said after a crack appears, that sounds like an excuse; written into the paperwork before the contract, it sets the expectation.

An aftercare Bot can keep the company's expectation letter and assemble a version for each job from the owner's wording: why the slab has joints and where they are, that hairline cracks can still appear, what the owner's own warranty covers and excludes, and the owner's care instructions. Every figure comes from the owner's sheet; the Bot never invents a curing time.

When a homeowner later emails a photo of a crack and the owner attaches it to the aftercare Bot's conversation, the Bot can file it with the job, draft an acknowledgment and list what the owner will want to know: the pour date, the joint layout and the date of the photo. It never says whether a crack is normal, structural or covered. The owner decides what to say, and a question about a structural slab, a footing or a retaining wall goes to a licensed engineer, with the building official's permit rules alongside.

For a contractor working in Queensland, Australia, a page from the Queensland Building and Construction Commission (QBCC), as checked on 16 October 2026, says the placement of concrete paths and driveways is one of the ten most common complaints the regulator receives. It gives examples of defective work, which it says are not the only ones:

• SHRINKAGE

  Plastic shrinkage cracking.

• CORNERS AND PENETRATIONS

  Cracking at internal corners and cracking at penetrations.

• APPEARANCE

  Inconsistent color and inconsistent surface finish.

• FALLS

  Surface levels not graded to disperse ponding water.

The same QBCC page says contractors are responsible for substrate preparation, the reinforcing mesh, placing the concrete, curing the surface and cleaning. It says reinforcement should generally sit in the top half of the slab with at least thirty millimetres of cover, that isolation, control and expansion joints should be provided to minimize cracking, and its weather point appears in the weather-holds guide. It points contractors to industry publications and to Australian Standard AS 3727, the guide to residential pavements.

For a Queensland company, those categories can become a handover list: a Bot prepares it from the job record and the owner's photos, one line per category, and the owner completes it on site with the homeowner. Whether the work meets the standard is never the Bot's judgment, and the company confirms its obligations with the QBCC, not with this summary.

Sawing control joints, cutting out a damaged panel, breaking out an old drive and grinding mortar from brickwork all make dust that contains respirable crystalline silica. OSHA's construction page on silica, as checked on 16 October 2026, says that applying water to a saw blade when cutting materials such as concrete, brick and block substantially reduces the dust. Whatever control method an employer uses, every covered construction employer must have a written exposure control plan and a competent person to implement it, among other duties. These duties fall on employers under federal OSHA; where a state operates its own OSHA-approved plan, the employer checks that plan's version. The standard's table of specified controls lists respiratory protection for handheld grinders used to remove mortar even when the grinder has a shroud and dust collection, with a higher level of protection when the task runs beyond four hours in a shift. A records Bot can keep the plan, tool list and task logs current and flag gaps for the competent person; deciding what a task requires is never its call. The flatwork crew guide shows a pour week's task log, and the siding guide on fiber-cement silica records covers the wider records.

A concrete company whose bids sit unwritten for a week begins with the estimating Bot. One that has poured into weather it should have held for, or spent a dark evening ringing a plant and a pump, begins with the forecast watch. One with a run of crack complaints begins with the aftercare letters. Each Bot only prepares: the estimating Bot never sends a price, the watch never cancels a truck, and the aftercare Bot never tells a homeowner what a crack means. A second Bot is worth adding once its job has its own sources, schedule or approval boundary.

One cloud computer serves every Bot on the account, with the same files and sign-ins, and the documentation is explicit that dividing work between Bots creates no security boundary: a supplier login used by one is usable by all. Work that needs its own computer and credentials belongs under a separate user account.

To begin, put every signed job that has not yet poured on one page: its planned date, whether the order and any pump are booked, and where that information lives today. If the only complete copy is in the owner's head and the owner's phone, that is the first gap an assistant cannot fill on its own.

Free and ungated, the workflow automation readiness assessment has you rate a single workflow on twelve set dimensions and see the outcome at once, with the blockers it found and a suggested next step. Score pour-week preparation, meaning the paperwork from signed bid to poured slab; ownership clarity shows whether anyone but the owner could say which jobs pour this week, and a low score there caps the result. If the result points to a build, the contact page is where to have Aevrion Ops scope the estimating Bot, the forecast watch and the aftercare letters, including which supplier or estimating systems would need a custom integration and how each would be tested.

1. In flatwork the costliest decision of the week is made the evening before the pour; the owner makes it, with the supplier on the mix and an engineer on anything structural.
2. An estimating Bot drafts bids from site notes and the owner's price book and leaves open any line the notes do not settle.
3. A forecast watch compares the forecast with limits the owner wrote and leaves a recommendation and unsent drafts; it never holds or cancels a pour.
4. NRMCA says no concrete is completely crack-free, so a crack-expectation letter before the contract does more than an explanation afterwards.
5. Queensland's regulator counts concrete paths and driveways among its top ten complaints; OSHA says water at the blade substantially reduces silica dust.