AI for Construction

Turn the superintendent's or foreman's raw field notes — typed bullets, a voice-memo transcript, a platform export (Procore Daily Log / PlanGrid / HammerTech / BuildPass), or a hand-written page photographed and captioned — into a properly formatted, **claims-grade** daily construction report covering weather, crew and equipment on site, work performed (by location/area), materials delivered, deliveries scheduled, visitors, safety observations, delays/disruptions, quantities installed, productivity rate, and photos — structured to be admissible as contemporaneous project documentation if a dispute arises later. The discipline this skill enforces is the same discipline that distinguishes a defensible delay claim from a rejected one: specific cause-and-effect, named owner of every disruption, time-stamped events, productivity-rate context, and weather-affected-work calls.

Read a two-week (or three-week) look-ahead schedule derived from the master CPM and critique it as a skeptical pull-plan facilitator would: surface unresolved constraints, predecessor slip risk, float consumption, missing handoffs between trades, crew overloading, material / submittal / inspection prerequisites, and weather exposure. Output a one-page briefing the superintendent can take into Monday's pull-plan or coordination meeting — not a replacement schedule.

Generate a daily, task-by-task **Pre-Task Plan** (PTP, sometimes called Pre-Task Safety Analysis or Pre-Shift Plan) that the crew leader can hand-write final corrections on, walk through with the crew at the morning huddle, post at the work area, and have signed off before work begins. The output covers the day's specific scope, the crew on it, the energy sources to be isolated, the controls in place, the PPE and rescue equipment required, the adjacent-trade and weather conditions that change the day's risk, and a stop-work trigger list calibrated to the actual hazards — not a generic template. This is the **daily** safety document, distinct from the project-level Site-Specific Safety Plan (the SSSP / safety-plan-builder output) and from the weekly toolbox-talk (which is a tactical safety briefing, not a task plan).

Answer a specific question about a construction project — "what does the spec say about slip-sheet requirements under the membrane roof?", "has this RFI already been asked?", "which approved submittal governs this fixture?", "what does the code say about the corridor rating?" — by searching across contract documents, drawings, specifications, RFIs, submittals, ASIs, meeting minutes, and referenced codes, and producing a cited, auditable answer. The answer is traceable back to a source document, paragraph, or sheet and flags uncertainty rather than guessing.

Turn raw walkthrough notes — the PM's phone voice memo, the architect's marked-up set, a stream of photo captions, or a Procore Punch / BuildPass / SpaceCapture export — into a structured punch list organized by location (floor/room) and by responsible trade, with clear item descriptions, severity, assigned party, required completion date, photo references, and a status column ready to track to close-out and substantial completion. Handles three input shapes: typed notes, raw voice-memo transcript (the most common 2026 input), and platform export (CSV / Procore / BuildPass / SpaceCapture / Bluebeam Punch markups).

Draft a clear, defensible Request for Information (RFI) response that cites specific spec sections, drawing details, and prior project decisions — structured so the receiving party (architect, engineer, GC, sub, or owner) can act on it without a follow-up round-trip. Works for both drafting an outgoing RFI from the field and drafting a response to an incoming RFI.

Generate the project-level **Site-Specific Safety Plan (SSSP)** for a construction project — the written program that the owner / GC / AHJ files at project start, posts in the trailer, and references throughout the build. Covers hazard identification, mitigation measures, emergency procedures, regulatory compliance, training requirements, and the inspection / audit cadence — formatted for jobsite posting and client/GC submittal. The SSSP is the **project framework**; the daily implementation is the Pre-Task Plan (`operations/pre-task-plan-drafter.md`), and the weekly tactical reinforcement is the Toolbox Talk (sub-mode in this skill). The SSSP sets the categories; the PTP narrows them to the day's specific task and location.

Read a submittal package (product data, shop drawings, samples, or mock-ups) and produce a one-page reviewer memo that: (a) lists every deviation from the contract specifications, (b) classifies each deviation as minor / substantive / or a substitution-request, (c) recommends a disposition (No Exceptions Taken / Make Corrections Noted / Revise & Resubmit / Rejected) consistent with the spec's allowed stamps, and (d) flags coordination impacts for related trades and the project schedule.

Review a project scope, estimate, or specification package and produce a structured, decision-ready VE log of options that reduce first cost (or improve life-cycle cost, or compress schedule) without sacrificing function, durability, code compliance, or owner intent — each option with savings range, schedule impact, life-cycle-cost note, code/warranty risk, decision owner, and the architect/engineer review path required to implement. The output is timed to the project phase (concept / SD / DD / CD / post-bid / change-driven mid-build) because what is value-engineerable shifts dramatically with phase, and a VE log proposed at CD that should have surfaced at SD will mostly get rejected.

Generate a bid-form-aware, delivery-method-aware, project-pattern-matched construction proposal — ready to send with minimal editing — that satisfies the bidding requirements of the specific solicitation (private RFP, public ITB, design-build RFQ, CMAR proposal, GMP package, hard-bid lump sum) and reflects how the work will actually be procured and built. The output covers the cover letter, qualifications, scope-with-exclusions, cost summary in the format the solicitation requires, schedule, alternates and unit prices, terms, and required attachments — with explicit clarifications and exclusions called out as a separate section because the #1 source of post-award disputes is unstated assumptions.

Rewrite a technical construction cost estimate into a clear, client-facing summary that a non-technical reader can read in 3–5 minutes and sign with confidence. Preserves numeric accuracy while stripping jargon, collapsing line items into client-meaningful categories, surfacing the right financial-structure signals (allowance vs. fixed, alternates, contingency use, payment schedule), and — for commercial projects — respecting CSI / MasterFormat structure where the client is accustomed to seeing it.

Turn a project plan set, spec outline, or scope narrative into a full set of trade-specific Invitations to Bid (ITBs) — one per trade — each with a targeted scope summary, submission requirements, key dates, site access notes, an explicit scope-handoff matrix that prevents the most common bid-day overlap errors, and a coverage / responsiveness self-check before release. Built for GCs who want to send 8–15 trade ITBs in under two hours instead of spending a full bid day rewriting the same template for every sub, with the discipline that prevents post-award scope disputes (the #1 cause: "I thought that was the other trade's").

Read a quantity takeoff — whether it was generated by AI (Togal, Kreo, STACK, Buildxact, Beam AI, TaksoAI, CountBricks, Bluebeam VisualSearch) or prepared manually in a spreadsheet — and produce a second-pair-of-eyes reviewer memo that flags the specific error classes AI takeoff tools (and estimators in a hurry) are known to miss: legend-symbol misreads, missed openings, wall-type confusion, scale / enlarged-detail errors, schedule-vs-plan count mismatches, plan-only items missed from elevations, and scope gaps between trades. The output is a correction list and a confidence-tier summary the estimator uses before the number goes in front of a client.

Draft clear, plain-language project updates for homeowners and residential clients during a remodel, custom build, or occupied renovation — tuned for the situation (weekly progress, delay notification, change order preview, site access request, punch list close-out) and in the company's voice.

Turn a documented sub-tier failure — defective work, missed cleanup, damage to other trades, missed milestone, equipment misuse, no-show on a fix — into the disciplined paper chain that survives a sub's later mechanic's-lien claim, an attorney's review, and an owner's pass-through audit. Output a four-document package: (1) a written **Notice of Deficient Work** identifying the specific defect and demanding cure, (2) a **Notice of Intent to Cure & Backcharge** issued after the cure window expires, inviting the sub to observe the corrective work, (3) the itemized **Backcharge Notice** itself with cost detail and supporting attachments, and (4) the **Deduction Authorization Letter** instructing AP to net the backcharge against the next pay application. Each document is scoped to a single contract clause and a single timeline so the chain can be reconstructed in any later dispute.

Turn a scope change — whether owner-directed, architect-directed, hidden condition, or a constructive change via field direction — into a properly documented Change Order Request (COR) or executed Change Order (CO) that: (a) is cost-reconciled with labor, material, equipment, subcontractor, bond, insurance, overhead & fee markups consistent with the contract, (b) states the schedule impact (time extension, no impact, or reservation of rights), (c) traces the origin of the change to a drawing, RFI, ASI, PCO, CCD, or field directive, and (d) matches the contract's change-order clauses (AIA G701/G701-CMa, ConsensusDocs 802, EJCDC C-940, or owner custom form).

Audit a construction project's closeout package — as-built drawings, operation & maintenance (O&M) manuals, warranties, final lien waivers, attic stock, training records, and the certificate of occupancy — against the contract-specified deliverables, and produce a gap list so final payment and retainage release aren't held up by missing documents.

Analyze a construction contract (prime contract, subcontract, or purchase order) and produce a plain-language risk summary that flags problematic clauses, missing protections, and compliance gaps — so the user can negotiate or escalate before signing.

Draft a contractually compliant notice of delay, request for extension of time (EOT), or formal delay claim narrative that: (a) satisfies the contract's notice-timing and notice-form requirements, (b) identifies the causation and the delay event with contemporaneous evidence references, (c) quantifies schedule impact using an industry-accepted delay-analysis method (Time Impact Analysis, Windows, As-Planned vs. As-Built, Impacted As-Planned, or Collapsed As-Built), (d) addresses concurrent delay and contractor-caused delay honestly, and (e) produces both a notice-level and a claim-level document appropriate to the stage.

Generate a clean, state-correct lien waiver — conditional or unconditional, progress or final — that an owner, lender, or upstream contractor will accept without rework, and that does not silently surrender lien rights for unpaid work or for sums in dispute. Output a fully populated waiver in the form prescribed by the project state (where the state mandates a statutory form), or a clean four-corner waiver that mirrors the canonical structure (where the state does not), plus a one-page transmittal cover and a defensibility self-check that confirms the waiver is right for the moment in the payment cycle.

Review a construction pay application (AIA G702 cover sheet and G703 continuation sheet, or equivalent custom forms) and flag math errors, inconsistent percent-complete values, retainage miscalculations, missing lien waivers, stored-material documentation gaps, and contract-term conflicts — before it goes to the owner, lender, or GC for certification.

Review a subcontractor's prequalification submission — certificate of insurance (COI), safety metrics (EMR, TRIR, OSHA 300 logs), financial snapshot, bonding capacity, licensing, and references — and produce a go / no-go recommendation with specific gaps, risk flags, and coverage deltas vs. the GC's minimum requirements.

Read a contractor's monthly Work-in-Progress (WIP) schedule — the cost-to-cost percentage-of-completion roll-up that ties earned revenue to billings on every active job — and produce a CFO/PM-ready review memo that flags stale ETCs, profit fade, overbilling concentration, underbilling neglect, ASC 606 treatment errors (uninstalled materials, variable consideration, loss-job recognition), schedule-of-values front-loading, and cash-flow inversion risk. The output is a job-level flags table, an overall portfolio risk readout, and the questions the CFO should bring to the next PM-by-PM job review meeting.

Turn rough notes, bullet points, or verbal context into a professional, ready-to-send construction email that preserves the contractual posture appropriate to the situation (notice, transmittal, coordination, follow-up), uses the right register for the recipient (client, GC, architect, sub, supplier, AHJ, owner's rep), and lines up with the company's voice. Output is copy-paste ready: subject line, body, signature block, and — where it matters — a CC list and a next-step action.

Turn construction meeting notes — typed, voice-transcribed, or bullet — into structured, distributable minutes that (a) match the meeting type's conventions, (b) separate decisions from action items from open issues, (c) make every commitment traceable (who, what, by when), and (d) flag risks the meeting surfaced but did not resolve. Output is pattern-specific: OAC minutes look different from a foreman huddle, which looks different from a punch walk.

Draft a professional public response to an online review (Google, Yelp, Houzz, BBB, Procore referrals, Angi, NextDoor) — tailored to the construction industry's specific review patterns: disputes over change orders, punch list and warranty callbacks, jobsite dust/noise/parking complaints from neighbors, schedule slippage, and praise from satisfied homeowners or commercial clients. Output is ready to post, with the right balance of accountability, brand voice, and legal caution.