AI-native playbook ยท General contracting

How to make a general contractor AI-native: a playbook

A general contractor's year is decided less by how fast it builds than by whether it gave notice on time, priced the change, collected the waiver and paid the right bank account. This playbook shows how to let AI agents draft that paper from the job's own drawings, specs and contract, while named people keep every stamp, notice, price, payment and stop-work call. Every figure is sourced.

Last reviewed
October 2026
Written for
Owners, operations directors, PMs and CFOs at commercial GCs and CMs with $50M to $2B of annual volume
Reading time
About 35 minutes
On this page
01

The delay nobody gave notice on

Picture a Tuesday on a federal job. The superintendent's daily log says the owner's consultant held the level 3 slab pour over a reinforcing question, and the crews moved elsewhere. The hold lasts a week. The log is accurate and signed. Nobody turns that line into a change event. A month later the PM hears about it in the OAC meeting and writes the notice.

By then part of the cost is gone for good. Under the federal changes clause, "no adjustment ... shall be made for any costs incurred more than 20 days before the Contractor gives written notice"[11]. Private contracts have their own clocks. Nobody did anything wrong in the field. The paper did not move.

A delay logged on day 0, under FAR 52.243-4
The change event opened from the daily log

Notice on day 2. Every cost incurred since the delay began is inside the 20-day window.

Nobody opened a change event

Notice on day 30. Costs from days 0 to 10 fall outside the 20-day window and cannot be recovered under the clause.

Costs barredCosts that can still be claimedWritten notice
Illustration, not a forecast. The clause bars costs incurred more than 20 days before written notice[11]; private contracts set their own clocks.

The story above is a scenario, not a reported case. The money behind it is real. Tutor Perini, a US-listed building and civil contractor with $5.5 billion of 2025 revenue, ended the year carrying $324.7 million of claims and $402.1 million of unapproved change orders as contract assets, together about 13% of its revenue: money spent on work whose price nobody had agreed[4]. Its 10-K defines the second as work "performed before the parties have agreed on the corresponding change in the contract price". For a GC, notice, backup and pricing sit on the balance sheet.

  • $101.6M

    The charge Tutor Perini took in October 2024 after one adverse arbitration on a completed California bridge, which it is appealing[4]

  • 42%

    Firms in the AGC and NCCER survey that say shortages of their own or their subs' workers delayed projects, the most cited cause of delay[36]

  • 15.4%

    Construction businesses that used AI in any function in a two-week period in September 2026, up from 7.4% in November 2025[2]

An agent that reads every daily log on every job would have opened that change event on the Tuesday and put the deadline in front of the PM. That is worth more than a faster RFI, though the staged path still starts with documents, because a change event is only as good as the drawings and logs behind it.

Who this is for. US commercial GCs, CMs at risk and design-builders with roughly $50 million to $2 billion of annual volume, who buy most of their work from subs and run jobs in Procore, Autodesk Construction Cloud or Oracle Aconex. Specialty subs and homebuilders are not the subject.

02

The short version

03

AI-enabled vs AI-native on a job site

AI-enabled

A takeoff tool in precon, a search box in the project system, a camera that tags photos. Each sits beside the work and depends on someone remembering to open it. The RFI log, the change log and the waiver binder run the way they always did.

AI-native

Every RFI, submittal check, daily log, change event, notice, certificate check, pay app and waiver starts as an agent's draft built from the job's current drawings, specs and contract, with its source cited. A named person sends, stamps, signs or pays. Contract clocks are watched on every job, every day, and the record shows who decided what, on which document.

The field stays under the superintendent and the competent person. Agents work in the office around them and read what the field records. A useful test: on any job, can the firm show which drawing revision a draft came from, who approved it and when, and that no contract clock ran out while a log entry sat unread?

04

The missing layer

A GC will not replace Procore, its accounting system or its schedule to become AI-native. It will add agents around them: the ones its project system ships, the ones from startups, and ones it builds. Each comes with its own permissions and its own idea of what a person must approve, and nobody holds one set of rules or one record across them.

OrchKernel is that layer. Agents ask it before they act; it checks the rules, holds what needs a person, and records what happened. Procore's own agents already mirror Procore permissions and leave the final call to people[44]. OrchKernel's job is the part no single vendor covers: one set of rules, one approval queue and one log across Procore, email, accounting and any other agent the firm uses.

Asks to act
Office agents

Each works for a named project engineer, PM, estimator or project accountant, with no more access than that person has on that job.

Checks every action
OrchKernel
  • Approvals
  • Rules
  • Access by job and field
  • Human queue
  • Audit log

Allows, holds for a person, or denies, and records which.

Systems of record, unchanged
What the firm connects
  • Procore, ACC or Aconex
  • Vista, Sage 300 CRE, CMiC or Foundation
  • P6 or Microsoft Project
  • Email
  • Drawings and Bluebeam sessions
  • Certificate tracking
Stays with people on site
Field authority
  • Stop-work
  • Competent person
  • Daily log signature
  • Inspections and walks

Agents read what the superintendent records and route what they see. They do not hold the authority to stop or release work.

OrchKernel sits between the agents and the systems a GC already runs. It does not replace any of them.

What it is not. OrchKernel is not a project management, accounting, drawing-log or scheduling system; those stay the systems of record. It does not keep the drawing log current, verify a certificate with a broker or decide what is controlled information, and it has no role in physical safety. Details are in the OrchKernel blueprint.

05

Where the hours and the money go

Thin margins that a few jobs decide

Building GCs earn a thin spread on large revenue, and disputes swing the result. Operating margins of US-listed contractors for fiscal 2025[5,6,7,8,9]:

  • Tutor PeriniBuilding and civil GC. Company-wide -2.4% in 2024 and -3.0% in 2023; its Building segment ran 3.1% in 2025 against -1.5% in 20244.2%
  • Granite ConstructionHeavy civil; self-performs and owns materials6.4%
  • EMCORElectrical and mechanical specialty contractor10.1%
  • Sterling InfrastructureSite work for data centers and e-commerce16.3%
  • FluorEngineering and construction-2.4%

Self-performers and specialists earn more than the building GC model, whose spread a few bad jobs can take. Tutor Perini's 10-K ties its swings to specific projects, including a $25.9 million hit in 2024 on a Florida government building "primarily due to increased costs associated with external subcontractors and resolution of certain delay change orders"[4]. Private-GC benchmarks are member-only at CFMA, so we quote none.

Input prices for new nonresidential construction rose 8.9% in the year to August 2026[37], while ABC members held 8.5 months of backlog[38]. Work priced a year ago is being bought out now, so escalation clauses, buyout timing and change pricing carry more of the margin.

Short of people

Of 8.364 million US construction jobs in September 2026, 5.28 million were at specialty trade contractors[1], the subs a GC buys from. 87% of firms in the AGC and NCCER survey have craft openings[36], and Deloitte puts the need at 499,000 new workers in 2026[41]. Agents in the office do not lay block. What they can take is the paper that keeps superintendents and project engineers at a desk while they coordinate subs who are short of workers.

The problem is old. Goolsbee and Syverson find US construction productivity "falling or, at best, stagnant over multiple decades"[40].

By role

Project engineer
Where the time or money goes
Turning field questions into RFIs, finding the sheet and spec section, chasing the design team, building the submittal register from the spec book, checking submittals for missing items.
Evidence
$1,080 per RFI and about one in four never answered (2013 study, read secondhand)[43]. 3.6 million pages of documents on one New York condo tower, by a vendor's account[51].
Project manager
Where the time or money goes
Changes: notice letters on contract clocks, sub quotes, backup, negotiation. Work done before the price is agreed becomes an unapproved change order or a claim.
Evidence
The 20-day bar on costs under the federal changes clause[11], and the claims balance in the opening.
Superintendent
Where the time or money goes
Daily logs, the three-week lookahead, safety paperwork, and coordinating subs who are short of people.
Evidence
No time study found. Short-handed subs, the most cited cause of delay, are in the opening.
Estimator
Where the time or money goes
Takeoff by hand, bid coverage calls, leveling sub bids with different exclusions, tracking addenda.
Evidence
Vendor claims only: takeoff "5x faster"[47]; one bidding task from a week to 20 minutes[44]. No independent time study found.
Project administrator
Where the time or money goes
Certificates of insurance for every sub and vendor: limits, endorsements, expirations, prequalification.
Evidence
"300 to 400 vendors" per project, by one certificate-tracking vendor's count (vendor claim)[49].
Project accountant
Where the time or money goes
Pay apps on each owner's form, lien waivers by tier, retainage, prevailing-wage payroll, paying subs on time, and spotting payment fraud.
Evidence
Business email compromise cost $2.77 billion across all US sectors in 2024[35]. Siteline reports 23,000+ distinct billing forms from 17,000+ GCs (vendor claim)[50].

The most quoted RFI figures are from 2013 and the time survey is from 2018, sponsored by a software vendor. The baseline you record in Stage 0 will be better evidence for your firm than anything above.

06

Bid to closeout: where AI works today

At each step of a job, some of the work is drafting and some is a decision. The diagram splits the two; the numbers point to the control points in the blueprint.

Agent draftsPerson decides
  1. 1Pursuit#1

    Lists bid opportunities, prequalification forms and due dates

    Business development and operations decide go or no-go

  2. 2Precon and estimating#1

    Takeoff drafts, bidder coverage by trade, addendum tracking, bid leveling sheets

    Chief estimator sets the number, fee, contingency and exclusions

  3. 3Prime contract#5

    Lists notice clauses and deadlines, retainage, liquidated damages and indemnity

    PM, operations director and counsel decide what to sign

  4. 4Buyout#7, 8

    Drafts subcontracts with flow-downs; checks each certificate against its subcontract

    PM awards; project administrator clears each sub to start

  5. 5Submittals and RFIs#2, 3, 4

    Builds the register from the spec book, pre-checks submittals, drafts RFIs with sheets and sections

    Project engineer stamps and sends; the engineer of record decides design

  6. 6Field#11, 15

    Drafts the daily log from voice notes, photos and manpower; routes safety observations

    Superintendent signs the log; the competent person stops work

  7. 7Changes#6, 14

    Opens a change event with its notice deadline; drafts the notice and the COR backup

    PM decides whether to give notice, what it says and the price

  8. 8Pay apps and waivers#9, 10, 13

    Builds pay-app backup, matches waivers by tier and period, flags any bank-detail change

    Project accountant and PM release payment; a named signer signs the payroll statement

  9. 9Closeout#9

    Punch lists by sub, O&M and warranty tracking, final waiver checklist

    PM releases retainage; the owner accepts the work

Numbers after # are the control points in the OrchKernel blueprint below.

What is on the market

Examples, not recommendations. Performance figures are the vendors' own.

Agents inside the project system
What it does
Search across specs, drawings, RFIs and submittals with citations; draft RFIs; check submittals against specs; draft daily logs from photos, email and voice; review contracts.
Examples and claims
Procore has agents for each, and says "Agents do the data gathering and drafting, your team makes the final call". Its customer results: submittal review "1 week โ†’ 10 minutes", spec search "1 hour โ†’ seconds" (vendor claims)[44]. Procore first announced agents in November 2024[55].
Document intelligence for GCs
What it does
Builds the submittal register from a spec book, checks submittals, catches RFIs the documents already answer.
Examples and claims
Trunk Tools: "Live on 1,000 U.S. projects" (vendor claim)[45]; $30 million raised by August 2024[51].
Contract risk review
What it does
Reads prime contracts and subcontracts and answers questions cited to the clause.
Examples and claims
Document Crunch: "500+ companies" (vendor claim). Its page does not say whether a person must review the output[46].
Takeoff and estimating
What it does
Measures areas, counts and lengths from drawings.
Examples and claims
Togal.AI: "98% accuracy on floor plans" (vendor claim)[47].
Progress capture
What it does
360-degree cameras on hard hats or walked routes, compared with the model or schedule.
Examples and claims
Buildots raised $45 million in May 2025, $166 million in total[52]. OpenSpace: "95% faster site documentation" at one customer (vendor claim)[48].
Subcontractor insurance
What it does
Reads each certificate, checks it against the firm's requirements and flags gaps.
Examples and claims
TrustLayer: "400,000+ COIs a month" (vendor claim)[49].
Construction finance
What it does
Accounts payable and receivable, billing on each owner's form, lien waivers.
Examples and claims
Briq claims up to 80% automation of AP, AR and payroll (vendor claim)[53]. Siteline: lien waivers "6x faster" (vendor claim)[50].

Nearly every category works on documents, where a mistake can be caught before anyone sends it. The governance each vendor describes stops at its own product: three tools mean three sets of permissions and three logs.

07

What the evidence says about adoption, and where the money went

Construction's AI use roughly doubled in ten months and is still low. In the Census Bureau's survey, 15.4% of construction businesses used AI in early September 2026, up from 7.4% in November 2025; 17.7% expect to within six months[2]. Manufacturing sits at 19.5% and professional services at 43.9%.

Businesses that used AI in any function in the past two weeks
  • Construction: 15.4%
  • Manufacturing: 19.5%
  • Professional, scientific and technical services: 43.9%
Nov 2025Sep 2026
Census Business Trends and Outlook Survey: share of firms answering yes in 22 two-week reference periods, the first 3 to 16 November 2025 and the last 24 August to 6 September 2026[2].

Two cautions. The survey counts firms, not jobs or dollars, so small contractors dominate it. And "any AI in any function" includes a chatbot opened once.

RICS's 2025 survey of 2,200+ construction professionals found 45% with no AI in their organization, 34% piloting and under 1% using it across the organization. Top barriers were skills (46%), integration with existing systems (37%) and data quality (30%), ahead of cost[39]. Its respondents are mostly in the UK, but integration and data quality are the problems of a GC whose documents live in five systems and change by revision.

Where the money went

The platform is large and still loses money. Procore had $1.32 billion of revenue in 2025 at a 79.5% gross margin and lost $124.3 million from operations[10]. It is the system of record most AI tools for US GCs sit inside or connect to.

The technology-native builder failed. Katerra took in more than $2 billion to be manufacturer, architect and contractor at once, peaked at 7,500 staff and went bankrupt in June 2021[54]. The funded AI companies in this section sell tools to GCs and subs; none builds. The realistic path is a GC that keeps its model and changes how its office works.

We found no evidence of an AI-native general contractor operating at scale.

08

The staged path

The order follows three facts. Documents and revisions are where current AI works best, and errors are reversible until a person sends. Contract clocks and payments are where a GC's money is lost. And field safety authority cannot move to software. Start on one job, then spread across jobs. Different jobs can be at different stages.

  1. 0

    Stage 0: Ground truth on one job

    About 4 to 6 weeks

    What to do

    • Pick one active job with a PM and project engineer who want to try it. Confirm that the drawing log and spec book in Procore, ACC or Aconex are at current revision, bulletins and ASIs included.
    • Pull the prime contract's notice clauses into a list: the event, the deadline, the form, who must receive it.
    • List every sub with its certificate expiry dates and the endorsements its subcontract requires.
    • List the AI already switched on in the project system, email and Bluebeam. Keep drawings, contracts and payroll out of public chatbots; mark federal and military jobs restricted.
    • Record a baseline: RFI and submittal cycle times, open RFIs, change events without notice, days to pay subs.

    Why now

    An agent drafting from a superseded sheet gives wrong answers with real-looking citations. A missed notice clock costs money from day 20 on federal work[11]. Controlled drawings on a military job are a DFARS question from the first prompt[31].

    In place first

    • A named document-control owner for the job.
    • The PM's sign-off on the notice list.

    What to measure

    Sheets in the system at current revision; notice clauses listed with deadlines; subs with a current certificate that matches their subcontract; baseline values for every Stage 1 metric.

    Common mistakes

    • Starting with the whole company.
    • Skipping the baseline.
    • Treating the project system vendor's security report as settling controlled information. DFARS 7012 asks for FedRAMP Moderate equivalence.
  2. 1

    Stage 1: Document work, people send

    Once Stage 0 shows the drawing log is current

    What to do

    • Draft RFIs from field questions with the sheet, detail and spec section attached, after checking whether the current documents already answer them.
    • Build the submittal register from the spec book.
    • Pre-check each submittal against its spec section: missing items, substitutions, a missing sub stamp.
    • List what changed in each new bulletin, and draft OAC minutes and the open-items list.

    Why now

    This is the highest-volume paper on a job, and it is reversible until the project engineer sends it. In the one large study we found, about one in four RFIs never got an answer[43].

    In place first

    • Stage 0 document control in place.
    • The project engineer's rules written down: what always needs her, which questions go to which consultant.

    What to measure

    RFI cycle time; RFIs closed by pointing to existing documents; submittals returned for missing items; engineer edits per draft; hours a week spent looking for documents, self-reported against the baseline.

    Common mistakes

    • Letting the agent send to the architect.
    • Letting an agent mark a submittal reviewed.
    • Trusting a citation without opening the sheet it points to.
  3. 2

    Stage 2: Contract and money clocks

    After a few months of Stage 1 records

    What to do

    • Every delay, directive or differing condition in the daily log opens a change event with its notice deadline and a draft notice for the PM.
    • Assemble change order request backup from sub quotes checked against their scopes, and chase certificate renewals before expiry.
    • Match lien waivers to pay apps by tier and period, on the statutory form where a state sets one.
    • Build pay-app backup against the schedule of values, track prompt-payment dates for subs, and route every bank-detail change to a person.

    Why now

    This is where a GC's margin and cash leak: work done before the price is agreed, retainage, waivers and payments that go to the wrong account. Stage 1 gives the document record that change backup is built from.

    In place first

    • The PM's notice rules in writing.
    • The project accountant's payment rules in writing.
    • A list of who may change vendor bank details and how they verify the request.

    What to measure

    Change events with notice sent before the deadline; days from change event to change order request; unapproved change orders older than 60 days; subs working with lapsed coverage (target zero); waivers missing at pay-app time; days to pay subs after the owner pays.

    Common mistakes

    • Letting an agent send notice letters. A notice can concede facts.
    • Letting an agent clear a sub to start.
    • "Improving" statutory waiver wording. In California a waiver is enforceable only in substantially the statutory form[18].
    • Paying to new bank details sent by email.
  4. 3

    Stage 3: Preconstruction

    When Stages 1 and 2 have a track record

    What to do

    • Send bid invitations by trade and track coverage.
    • Draft bid leveling sheets that line up each sub's inclusions, exclusions and qualifications.
    • Draft takeoffs, proposal letters, and a check of the prime contract against the firm's clause library.

    Why now

    Precon sets a job's margin, and a mistake here is baked into the price. By now the firm has a record of how its agents perform and a library of the clauses that have cost it money.

    In place first

    • A scope checklist per trade.
    • A written answer to who sets the number and the fee.

    What to measure

    Bid coverage per trade; scope gaps caught before bid day; bids submitted per estimator; hit rate by count and by value; buyout variance after award.

    Common mistakes

    • Letting an agent set or change a number.
    • Treating a takeoff vendor's accuracy figure, such as Togal's 98% on floor plans (vendor claim)[47], as a promise about your drawings.
    • Skipping a person's review of exclusions.
  5. 4

    Stage 4: Field records and signals

    Once the field trusts what agents write, and the camera rules are written

    What to do

    • Draft daily logs from voice notes, photos and sub manpower for the superintendent to correct and sign.
    • Check the three-week lookahead against open RFIs, unapproved submittals and subs not cleared to start.
    • Route safety observations from photos to the superintendent, and draft incident reports with the OSHA clock shown.

    Why now

    The field's record must be trusted before agents rely on it, cameras on hard hats record workers, and the authority to stop work belongs to a competent person[23].

    In place first

    • A written rule on what cameras capture and who can see it.
    • The superintendent named as the signer of the daily log.
    • A named owner for incident reporting.

    What to measure

    Daily logs complete and signed by end of day; days from a logged delay to a change event; schedule variance by activity; safety observations closed; incident reports filed inside the OSHA window (target 100%).

    Common mistakes

    • Using site footage to rank individual workers.
    • Letting an agent close a safety observation.
    • Replacing walks with camera review.
  6. 5

    Stage 5: Operating model across jobs

    When Stages 1 to 4 run with evidence on more than one job

    What to do

    • Roll the Stage 1 to 4 flows out job by job.
    • Send a Monday brief across jobs: late RFIs by who holds them, submittals at risk, change exposure, certificates about to lapse.
    • Review agent rules, permissions and scorecards every quarter, and tell owners and sureties how agents are used when they ask.

    Why now

    Freed hours only show up in fee if staffing plans change with them. And a few jobs decide a GC's year: the $101.6 million arbitration charge in the opening was more than a third of Tutor Perini's 2025 operating income[4,5].

    In place first

    • Named owners for agent operations and for document control on every job.
    • A year of records from the earlier stages.

    What to measure

    Revenue per project-management employee; fee fade or gain; unapproved change orders and claims as a share of revenue; days to pay subs.

    Common mistakes

    • Keeping staffing ratios from before, so freed time turns into slack.
    • Leaving an owner's AI restrictions in an email thread instead of in rules the agents check.
09

Your first 90 days

Stage 0 plus one Stage 1 or Stage 2 flow, on one job. The baseline you record in the first month tells you by the end of the quarter whether it worked. We run this with design partners.

  1. Days 1 to 30

    Pick one active job and one flow: RFIs and submittals, or change events and notice. Name the job's document-control owner. Write down the rules the PM and project engineer already follow: what always needs them, the notice deadlines in the prime contract, who may clear a sub to start. Mark the job restricted if it is federal or on a base. Record four weeks of baseline numbers.

  2. Days 31 to 60

    Connect OrchKernel to the project system, the mailbox and drawing storage for that job. Run agents in draft mode: people send everything. Track edits per draft, catches (a wrong revision, a missing spec item, a notice deadline found) and cycle times. Review the audit log with the PM every week.

  3. Days 61 to 90

    Let routine, rule-covered actions run without a click: a second reminder to the architect on an overdue RFI, a renewal request to a sub 30 days before its policy expires. Keep every notice, stamp, price, payment and clearance with a person. Decide with the numbers whether to add the second flow or a second job.

10

How roles change

Our recommendations, inferred from the work rather than from a survey.

Project engineer
Reviews and sends instead of retyping. RFI drafts arrive with the sheet, detail and spec section; submittals arrive with the gaps listed. Time goes to coordination and to walking the job.
Project manager
Manages changes on a clock. Every delay or directive in the log arrives as a change event with its deadline, a draft notice and backup. The PM decides on notice and price.
Superintendent
Dictates; the agent writes. The daily log is drafted from voice notes, photos and sub manpower, and the superintendent corrects and signs it. The hours go back to running the work. Safety authority does not move.
Estimator
Levels and decides. Takeoff and leveling drafts come from the drawings and the sub bids; the estimator judges scope gaps, risk and the number. Keep estimating some work by hand so the skill does not fade.
Project accountant and administrator
Manage exceptions. Waivers are matched to pay apps by tier; payrolls are pre-checked; certificates are chased before they lapse. A changed bank account is always verified by phone, by a person.
New owners
An owner for agent rules, permissions and scorecards, often the director of operations or the head of project controls. A document-control owner on every job. On federal work, the compliance lead decides which agents and models may touch which jobs.

What must not change: the field's safety authority, the design team's authority over design, and the PM's authority over money and notice.

11

Decisions not to automate

An agent can prepare each of these. A named person makes the call, however good the drafts get.

Sending an RFI to the design team
Why it stays with a person
It is the firm's formal question on the record, and it can start a change or a dispute.
Stamping a submittal as reviewed
Why it stays with a person
The GC's review is part of the chain that releases fabrication. Hyatt Regency shows what an unexamined connection change can cost.
Accepting a design change or a delegated-design component
Why it stays with a person
Licensed engineers seal design work[29]. The GC cannot approve a structural change.
Deciding whether something is a change, and its price
Why it stays with a person
Work done before the price is agreed sits on the balance sheet as an unapproved change order or a claim[4].
Giving or holding notice of delay, change or differing conditions
Why it stays with a person
Contract clocks run from the event[11,12], and a careless notice can concede facts. The PM owns the firm's position.
Bid number, fee, contingency and exclusions
Why it stays with a person
The firm's offer and its risk.
Clearing a sub to start
Why it stays with a person
A lapsed policy or a missing orientation puts the firm's risk on site.
Releasing payment to a sub, or signing a lien waiver
Why it stays with a person
Prompt-payment duties[14] and, in some states, a waiver that is enforceable only in statutory form[18].
Signing a prevailing-wage payroll statement or a Buy America statement
Why it stays with a person
Signed statements that can bring prosecution under 18 U.S.C. 1001 and the False Claims Act[20,30].
Changing a vendor's bank details or approving a wire
Why it stays with a person
This fraud usually arrives as an email that looks like the sub's. A call to a number already on file, made by a person, is the check.
Stopping work for a hazard, or closing a safety observation
Why it stays with a person
A competent person has "authorization to take prompt corrective measures"[23]. See the FIU bridge below.
Reporting a serious injury or fatality to OSHA
Why it stays with a person
8-hour and 24-hour clocks, and a person must confirm the facts[21].
Disciplining or ranking workers from camera or biometric data
Why it stays with a person
Biometric privacy law, labor agreements, and trust on site[62].
Sending owner reports and completion dates
Why it stays with a person
What the firm's software tells a customer binds the firm[60].
Adding an AI service to a job with controlled information
Why it stays with a person
FedRAMP Moderate equivalence for cloud services[31], and the CMMC affirmation.
12

Rules that bite

Across contracts and states, the same requirements keep coming back: give written notice on contract clocks; pay subs and protect lien rights on statutory deadlines; sign payroll statements truthfully on prevailing-wage work; report serious injuries fast and keep a competent person in charge of hazards; leave design decisions with licensed professionals; prove where materials came from on federally funded work; and protect controlled facility data. Each one ends in a person's decision or signature, which is why each one maps to a control below.

Notice clocks in the contract

Every GC; the federal clauses below apply on federal work, and private contracts set their own

Under the federal changes clause, notice of a constructive change must state "the date, circumstances, and source of the order"; costs incurred more than 20 days before written notice are not recoverable; and the contractor must assert its right to an adjustment within 30 days[11]. Differing site conditions must be reported "promptly, and before the conditions are disturbed"[12], and a suspension of work carries the same 20-day bar on costs[13].

On private work, AIA A201-2017 section 15.1.2 is commonly read as requiring a claim within 21 days of the event or of first recognizing the condition; we have not read the licensed textTo be confirmed. ConsensusDocs and owner-drafted contracts set their own clocks.

For agents: An agent reading the daily log can find a delay on day one. Whether notice goes out, what it says and which rights it reserves stay with the PM.

Payment, bonds and lien rights

Every GC paying subs; federal and state public work adds bonds and prompt-payment rules

Federal prime contracts must flow down a duty to pay subs within 7 days of receiving payment, and withholding needs written notice to the sub, copied to the contracting officer[14]. State prompt-payment laws set their own windows.

Miller Act bonds are required on federal construction contracts above $150,000[15]. A lower-tier claimant must give the prime written notice within 90 days of last furnishing and sue within one year[16].

State lien laws differ widely. In California, a preliminary notice is due within 20 days of first furnishing work, and a late one limits lien and bond rights to the 20 days before service and after[17]. A California lien waiver is enforceable only if it is "in substantially the form provided" and signed, and a conditional waiver also needs proof of payment[18]. In Texas, on commercial work, notice of unpaid labor or materials is due by the 15th day of the third month after the month the work was done[19], read in an unofficial copyTo be confirmed. Florida, New York and other states set their own notices and formsTo be confirmed.

For agents: Where a state prescribes the waiver form, an agent fills fields only. Releasing payment against an unconditional waiver is a person's decision.

Prevailing wage payroll on public work

Davis-Bacon and Related Acts jobs; many states run their own prevailing-wage laws

The contractor and each sub submit certified payrolls weekly, signed "by an original handwritten signature or a legally valid electronic signature", and keep them for 3 years after the prime contract's work is complete. "The falsification of any of the above certifications may subject the contractor or subcontractor to civil or criminal prosecution under 18 U.S.C. 1001 and 31 U.S.C. 3729". The prime is responsible for the submission of every sub's certified payrolls[20].

For agents: An agent can assemble payrolls, flag a misclassified trade or a missing fringe, and chase late subs. The Statement of Compliance is a named person's signature.

Safety: reporting, competent persons, heat

Every GC with workers or subs on site

A fatality must be reported to OSHA within eight hours; an in-patient hospitalization, amputation or loss of an eye within 24 hours[21]. Job-site inspections must be made "by competent persons designated by the employers"[22], and a competent person is one who can identify hazards "and who has authorization to take prompt corrective measures to eliminate them"[23]. Fall protection was OSHA's most cited standard in fiscal 2025[24].

Maximum penalties are $16,550 per serious violation and $165,514 per willful or repeated one[25]; the Department of Labor canceled its 2026 inflation adjustment, so the 2025 amounts stand[26].

OSHA's proposed heat rule covers construction, but "no final rule has been issued yet"[27]. States act on their own. California requires shade above 80ยฐF and high-heat procedures at 95ยฐF on construction sites[28]. Washington, Oregon and Nevada rules were not read for this pageTo be confirmed.

For agents: A camera can flag a missing guardrail. Stopping work and confirming the facts in an OSHA report belong to designated people.

Design responsibility and professional seals

Every GC; design-builders and delegated-design submittals most of all

Engineers sign and seal final documents, and in Florida, for example, "No licensee shall affix ... his or her seal ... to any plan, specification, drawing ... that depicts work which he or she is not licensed to perform"[29]. Each state's licensing law differs.

For agents: An agent can list where a shop drawing departs from the contract documents. A structural connection change goes to the engineer of record, not to the agent or the GC.

Buy America on federally funded infrastructure

GCs on projects with federal financial assistance

Federal funds for an infrastructure project may not be obligated "unless all of the iron, steel, manufactured products, and construction materials incorporated into the project are produced in the United States"; a manufactured product needs US components above 55% of total component cost[30].

For agents: An agent can check product data against origin rules and collect certifications. The firm's statement of compliance is signed by a person.

Defense and federal facility data

GCs building on military installations or for agencies with controlled information

DFARS 252.204-7012 requires cyber incidents to be reported "within 72 hours of discovery" and, where an external cloud service stores, processes or transmits covered defense information, security equivalent to the FedRAMP Moderate baseline[31]. Drawings and specifications for work on a base are often controlled.

The DFARS rule that puts CMMC into contracts took effect on 10 November 2025[33]. Phase 2, which adds third-party Level 2 assessments as a condition of award for applicable contracts, begins one calendar year after Phase 1[32]: 10 November 2026.

For agents: A model API or agent platform that reads those drawings is a cloud service under the clause. Adding one to a restricted job is the compliance lead's decision, not a PM's setting.

Worker data and cameras

GCs using biometric time clocks, site cameras or helmet capture

Illinois' Biometric Information Privacy Act requires written notice and a written release, and sets damages of $1,000 per negligent and $5,000 per intentional or reckless violation[62]. A 2024 amendment is reported to limit liability for repeated scans of the same person to a single violation; the Illinois statute site did not load for usTo be confirmed. Collective bargaining agreements may limit monitoring on union jobs.

For agents: Footage can feed progress and safety routing. Using it to discipline or rank individual workers is for HR and counsel, and agents that do not need worker identity should not see it.

For scale on safety: 1,032 people in construction and extraction occupations died at work in the US in 2024, 370 of them in falls, slips and trips[3].

13

What failure looks like

Several of the best-known collapses and fires of the past 45 years turned on document control and who had authority: a connection change approved by phone, cracks observed while work went on, product claims taken on trust. Each points to a control that agents can either support or undermine.

  1. Hyatt Regency walkway collapse, Kansas City, 1981

    114 people died. The fabricator proposed splitting the continuous hanger rods into two sets, which doubled the load on the fourth-floor beam connection. The engineer "accepted Havens Steel's proposed plan via a phone call without performing necessary calculations or viewing sketches". The engineering firm lost its licenses in three states[56].

    The control: A structural change in a submittal goes to the engineer of record with the change shown. No approval by side channel, and the record shows who approved which version (control 4).

  2. FIU pedestrian bridge collapse, Miami, 2018

    Six people died. The NTSB found "load and capacity calculation errors" by the designer, and that five organizations, the contractor among them, failed "to cease bridge work when the structure cracking reached unacceptable levels and to take appropriate action to close SW 8th Street"[34].

    The control: Stop-work and road-closure decisions sit with named people. Observations of distress go to a human queue with a deadline, never into a backlog (control 11).

  3. Grenfell Tower, London, 2017

    The inquiry's 2024 report found "systemic dishonesty" among cladding manufacturers and a "merry-go-round of buck-passing" among the architect, the principal contractor and the cladding subcontractor[57]. In September 2026 police passed files on 20 organizations and 54 people to prosecutors[58].

    The control: Product data in a submittal is a claim to check against test reports and code requirements, not a fact. Substitutions always go to a person (control 4).

  4. Hard Rock Hotel collapse, New Orleans, 2019

    Three workers died. OSHA cited the structural engineer for failing to "adequately design, review or approve steel bolt connections"; some workers said they had complained about unsafe practices before the collapse. A $106 million settlement was reached in August 2026[59].

    The control: A concern raised in the field reaches a person with authority fast, and the record shows that it did (controls 11 and 14).

  5. Business email compromise

    21,442 complaints and $2.77 billion of reported losses in the US in 2024, across all sectors[35]. GCs pay subs and suppliers large sums against invoices that arrive by email. We found no construction case with a primary source.

    The control: Bank-detail changes and wires always need a person, a call-back and a second approver (control 10).

Agent failures to design against (scenarios)

These are scenarios, not reported cases. Each is what an agent with too much access, or too much trust, could do on a job, and each maps to a numbered control point.

A. The superseded sheet
What happens
An agent drafts an RFI citing A-501 revision 3. Revision 4, in last week's bulletin, already answers it. The architect replies "see Bulletin 7" and the job loses three days.
What stops it
Agents draft only from the current drawing log, and the approval screen shows the revision check (controls 2 and 3).
B. The substitution that looked equal
What happens
A sub's product data lists a fire-rated assembly tested in a different configuration. The pre-check agent marks it as matching the spec section.
What stops it
Agents list differences; they never mark a submittal reviewed. Substitutions always go to the engineer's queue (control 4).
C. The missed 20 days
What happens
The superintendent logs a week-long hold on a slab by the owner's consultant. Nobody opens a change event. Thirty days later the PM finds out; the first ten days of cost are barred.
What stops it
A delay or directive in the log opens a change event with the contract's deadline and a reminder to the PM (control 6).
D. The notice that conceded
What happens
An agent drafts and sends a delay notice saying the delay was "due to our late steel order".
What stops it
Notices to the owner need the PM's approval, and agents have no route to send them (controls 6 and 14).
E. The lapsed sub on site
What happens
A drywall sub's general liability policy expired last Friday. The agent puts its crew on the lookahead and tells the sub it is cleared.
What stops it
Clearance to start needs the project administrator, with the certificate check attached; a rule blocks it while coverage has lapsed (control 8).
F. The new bank account
What happens
An email that appears to come from the steel sub asks to update payment details before the pay-app run. The agent updates the vendor record.
What stops it
Agents cannot change bank details. A change needs a call-back by a person and a second approver (control 10).
G. The improved waiver
What happens
An agent rewrites a California conditional waiver "for clarity". It is no longer in the statutory form.
What stops it
Statutory forms are fixed templates; agents fill the fields and nothing else (control 9).
H. The closed safety observation
What happens
A camera flags a missing guardrail on level 4. The agent marks it resolved because a later photo, from another angle, shows a rail.
What stops it
Agents open and route safety observations; only the superintendent or competent person closes them (control 11).
14

The OrchKernel blueprint for a general contractor

OrchKernel sits between AI agents and the systems a GC runs on, as drawn in the missing layer. Agents ask it before they act; it checks the rules, holds what needs a person, and records what happened.

The mechanisms

Approvals
An action waits for a named person, who sees the exact payload: the RFI with its sheets, the notice letter, the payment release.
Rules
Checked before every action, for example no clearance to start while coverage has lapsed, or payments above a threshold to the CFO. A rule allows, holds or denies, and says why.
Acting on a named person's authority
Each agent works for a named project engineer, PM, estimator or accountant, with no more access than that person has on that job. A PM's commitment limit is the agent's ceiling.
Data access by role and field
Who sees which jobs, records and fields, and which models are cleared for which data. A restricted job reaches only cleared models and hosts; worker identity stays hidden from agents that do not need it.
Tamper-evident audit log
Every request, rule result, approval and denial, hash-chained so an edited or deleted entry shows. It records which drawing revision each draft used and who approved it.
Human queue
Work only a person may do lands with an owner and a deadline: a notice due in six days, a substitution, a bank-detail change, a safety observation.
Connections to your systems
Procore, ACC or Aconex, accounting, scheduling, email, drawing storage and certificate tracking, through their APIs, MCP servers or REST adapters, each with a kill switch. Agents never hold the vendor keys. Where a system has no API, a person does that step.

Sixteen control points

Where a GC needs a control whatever tools it uses, who owns it, how OrchKernel enforces it, and what stays in another system.

Precon and the prime contract

01
Bid number, fee, contingency, exclusions and proposal letters
Owner or approver
Chief estimator; leadership for fee
How OrchKernel enforces it
Approval on any proposal or bid letter leaving the firm, with the exact payload shown.
Stays elsewhere
The number itself and the estimating system
05
Prime contract review before signing
Owner or approver
PM, operations director and counsel
How OrchKernel enforces it
The agent drafts a clause list; approval before anything goes to the owner.
Stays elsewhere
Counsel's review and the signature

Drawings, RFIs and submittals

02
Document control: which drawing and spec revisions agents may use
Owner or approver
Project engineer or document control
How OrchKernel enforces it
Agents read only the current revision set. The log shows which revision each draft used.
Stays elsewhere
The drawing log and revision control in Procore or ACC
03
RFIs sent to the design team
Owner or approver
Project engineer
How OrchKernel enforces it
Approval on every RFI. Reminders on overdue RFIs can run by rule once the project engineer allows it.
Stays elsewhere
The RFI record and the official response in the project system
04
Submittal review and stamp, substitutions, delegated design
Owner or approver
Project engineer; engineer of record for design
How OrchKernel enforces it
Agents have no tool to set a review status, and a rule denies one connected later. Substitutions go to the engineer's queue.
Stays elsewhere
The stamp and the engineer of record's review

Changes, subs and the owner

06
Change events, notice letters and change order requests
Owner or approver
Project manager
How OrchKernel enforces it
Log entries open a change event with its deadline. Approval on every notice and request; the queue shows days left.
Stays elsewhere
The PM's judgment; the change record in the project system
07
Subcontract awards and change orders to subs
Owner or approver
PM; operations above a threshold
How OrchKernel enforces it
Agents read commitments and budgets but have no tool that writes them.
Stays elsewhere
Commitments in the project system and job cost
08
Clearing a sub to start: insurance, prequalification, safety orientation
Owner or approver
Project administrator; risk manager for exceptions
How OrchKernel enforces it
Approval by the project administrator with the certificate check attached; a rule blocks clearance while coverage has lapsed.
Stays elsewhere
Verifying the certificate with the broker; the prequalification system
14
Messages to the owner: reports, completion dates, minutes
Owner or approver
Project manager
How OrchKernel enforces it
Approval on any message to the owner that contains a date, a price or a position.
Stays elsewhere
The owner relationship

Money and signed statements

09
Pay applications, lien waivers, retainage, payments to subs
Owner or approver
Project accountant; PM; CFO above a threshold
How OrchKernel enforces it
Approval thresholds on payments. Waiver templates are fixed; agents fill fields only.
Stays elsewhere
The accounting system, the statutory forms and the payment itself
10
Vendor bank details and wires
Owner or approver
Accounting, with a call-back and a second approver
How OrchKernel enforces it
Agents cannot change bank details. Any request goes to the human queue for a call-back and a second approver.
Stays elsewhere
Bank controls and positive pay
13
Prevailing-wage payroll statements and Buy America statements
Owner or approver
Payroll or project accountant; a named signer
How OrchKernel enforces it
The agent assembles; the signer approves. The log records what was signed and when.
Stays elsewhere
The legal signature, the payroll system and the submission

The field, people and access

11
Safety observations, stop-work, incident reports
Owner or approver
Superintendent or competent person; safety director
How OrchKernel enforces it
Agents open and route observations and draft incident reports. Only the named superintendent or safety lead closes or files.
Stays elsewhere
The stop-work decision and the OSHA report itself
15
Worker data: cameras, biometrics, monitoring
Owner or approver
HR, safety and legal
How OrchKernel enforces it
Field-level access so agents that do not need identity or biometric fields never see them.
Stays elsewhere
Consent, notices and labor agreements
12
Access to drawings, contracts, payroll and controlled information, by job and field
Owner or approver
IT or security; compliance lead for federal jobs
How OrchKernel enforces it
Access by job and field. Restricted jobs reach only cleared models; allowed hosts; self-hosted inside the firm's boundary.
Stays elsewhere
What counts as controlled, the provider's FedRAMP equivalence, the security plan
16
Changes to agents, rules and models
Owner or approver
Agent operations owner; the CMMC affirming official where relevant
How OrchKernel enforces it
Rules and kill switches kept as code with review; a bad change is rolled back; a kill switch per agent, per job or for everything.
Stays elsewhere
The affirming official's signature and the firm's change procedure

Honest limits

OrchKernel governs what agents do in the systems a GC connects. It does not make a model provider FedRAMP-equivalent or decide what is controlled information, and whether a self-hosted OrchKernel with a cleared model fits a firm's CMMC boundary needs a CMMC practitioner's view. Some of these controls, such as approval on RFIs and permissions that mirror the project system, also exist inside Procore's own agents[44]; OrchKernel holds them in one place across the other systems and agents too.

OrchKernel is source-available under the Business Source License and can run on your own servers, so you can read the code that enforces these controls.

15

Scorecard by stage

Record your baseline in Stage 0, then track the same numbers at each stage. Public benchmarks for GC operations barely exist, and we say so row by row rather than quote rules of thumb.

Sheets at current revisionStage 0
How to count it
Sheets in the project system matching the latest issued revision, divided by all active sheets
Public benchmark
No public benchmark
RFI cycle timeStage 1
How to count it
Working days from RFI sent to answer received, plus the share never answered
Public benchmark
Only a 2013 Navigant study, read secondhand: 6.4 to 10 days on average, about one in four unanswered[43]. No current independent benchmark
Submittals returned for missing itemsStage 1
How to count it
Submittals sent back by the design team for missing or wrong content, divided by submittals sent
Public benchmark
No public benchmark
Hours spent looking for project dataStage 1
How to count it
Self-reported hours a week, against your own baseline
Public benchmark
A 2018 vendor-sponsored survey: 5.5 hours a week[42]. Use it for context, not as a target
Notices sent before the deadlineStage 2
How to count it
Change events with written notice sent inside the contract's clock, divided by change events
Public benchmark
No public benchmark
Unapproved change orders and claimsStage 2
How to count it
Their total as a share of revenue, and the amount older than 60 days
Public benchmark
Only from public filings: about 13% of revenue at Tutor Perini at the end of 2025[4]
Sub-days on site with lapsed coverageStage 2
How to count it
Days any sub worked while a required policy had lapsed
Public benchmark
No public benchmark; the target is zero
Days to pay subsStage 2
How to count it
Days from the owner's payment to payment of each sub
Public benchmark
No public benchmark; federal work sets a 7-day duty, so measure against it there
Hit rate and bid coverageStage 3
How to count it
Bids won by count and value; bidders per trade on bid day
Public benchmark
No public benchmark; vendor claims only
Incident reports inside the OSHA windowStage 4
How to count it
Reports filed within 8 or 24 hours, divided by reportable events
Public benchmark
A legal requirement, not a benchmark: the target is 100%
Fee fade or gainStage 5
How to count it
Final margin against margin at award, by job
Public benchmark
No public benchmark; CFMA holds member-only data
AI useContext
How to count it
Whether the business used AI in any function in the past two weeks
Public benchmark
Yes, for adoption only: 15.4% of construction businesses in early September 2026[2]
16

What we don't know yet

  • How much of a GC's office time goes to RFIs, submittals, changes and billing today. No current independent time study exists; design partners' baselines will be the first good data.
  • Private GC margins. CFMA's benchmarker is member-only, so we quote only public contractors.
  • Whether AI drafting changes change-order recovery or dispute outcomes. Nobody has published it.
  • The exact wording of AIA A201-2017 sections 1.5 and 15.1.2, which we have not read, and whether firm-wide AI search over past drawings fits the license.
  • Lien and prompt-payment timelines beyond California and Texas, the Washington, Oregon and Nevada heat rules, and the 2024 change to Illinois' biometric law.
  • How Autodesk, Oracle and Trimble's AI features compare. Their pages were blocked when we checked, so vendor claims here come mostly from Procore and startups.
  • Whether a self-hosted control layer with a cleared model fits a given firm's CMMC assessment boundary.
17

Sources

Last reviewed October 2026. Sources were read in October 2026 unless the entry says otherwise; dates are publication or data dates. Vendor figures are directional, not an industry benchmark.

Primary sources

Government statistics, regulations, statutes, investigation reports and SEC filings. Where we read a statute in an unofficial copy, the entry says so.

  1. 1
    Employment Situation, Table B-1 (construction). US Bureau of Labor Statistics, September 2026, preliminary.
  2. 2
    Business Trends and Outlook Survey, sector data (sectors 23, 31 to 33 and 54; AI use questions 7 and 24). US Census Bureau, published 24 September 2026; latest reference period 24 August to 6 September 2026.
  3. 3
    Census of Fatal Occupational Injuries, 2024. US Bureau of Labor Statistics, released 19 February 2026.
  4. 4
    Tutor Perini Corporation, Form 10-K for fiscal 2025. US Securities and Exchange Commission (EDGAR), filed 26 February 2026.
  5. 5
    Tutor Perini Corporation, company facts (XBRL), fiscal 2023 to 2025. US Securities and Exchange Commission, 10-K filed 26 February 2026.
  6. 6
    Granite Construction, company facts (XBRL), fiscal 2025. US Securities and Exchange Commission, 10-K filed 13 February 2026.
  7. 7
    Sterling Infrastructure, company facts (XBRL), fiscal 2025. US Securities and Exchange Commission, 10-K filed 26 February 2026.
  8. 8
    EMCOR Group, company facts (XBRL), fiscal 2025. US Securities and Exchange Commission, 10-K filed 26 February 2026.
  9. 9
    Fluor Corporation, company facts (XBRL), fiscal 2025. US Securities and Exchange Commission, 10-K filed 17 February 2026.
  10. 10
    Procore Technologies, company facts (XBRL), fiscal 2025. US Securities and Exchange Commission, 10-K filed 24 February 2026.
  11. 11
    FAR 52.243-4, Changes (JUN 2007). Federal Acquisition Regulation, acquisition.gov.
  12. 12
    FAR 52.236-2, Differing Site Conditions (APR 1984). Federal Acquisition Regulation, acquisition.gov.
  13. 13
    FAR 52.242-14, Suspension of Work (APR 1984). Federal Acquisition Regulation, acquisition.gov.
  14. 14
    FAR 52.232-27, Prompt Payment for Construction Contracts (JAN 2017). Federal Acquisition Regulation, acquisition.gov.
  15. 15
    FAR 28.102-1, General (performance and payment bonds for construction contracts). Federal Acquisition Regulation, acquisition.gov, read October 2026.
  16. 16
    40 U.S.C. 3133, Rights of persons furnishing labor or material. Legal Information Institute, Cornell Law School.
  17. 17
    California Civil Code section 8204 (preliminary notice). California Legislative Information.
  18. 18
    California Civil Code section 8124 (lien waivers). California Legislative Information.
  19. 19
    Texas Property Code section 53.056 (notice of claim for unpaid work). Public.Law (unofficial copy of the statute), read October 2026.
    The official Texas statutes site did not load; check the official text
  20. 20
  21. 21
  22. 22
    29 CFR 1926.20, General safety and health provisions. Legal Information Institute, Cornell Law School.
  23. 23
    29 CFR 1926.32, Definitions (competent person). Legal Information Institute, Cornell Law School.
  24. 24
    Top 10 most frequently cited standards, fiscal 2025. Occupational Safety and Health Administration.
  25. 25
    OSHA penalties. Occupational Safety and Health Administration, read October 2026.
  26. 26
    Department of Labor Federal Civil Penalties Inflation Adjustment Act Annual Adjustments for 2026. Federal Register, 27 May 2026.
    Cancels the 2026 adjustment, so the January 2025 amounts stand
  27. 27
    Heat injury and illness prevention: rulemaking. Occupational Safety and Health Administration, read October 2026.
  28. 28
  29. 29
  30. 30
    2 CFR 184.3, Build America, Buy America requirements. Legal Information Institute, Cornell Law School, amended effective 1 October 2024.
  31. 31
  32. 32
    32 CFR 170.3, Applicability (CMMC phase-in). Electronic Code of Federal Regulations, read October 2026.
  33. 33
    DFARS: Assessing Contractor Implementation of Cybersecurity Requirements (DFARS Case 2019-D041), 90 FR 43560. Federal Register, published 10 September 2025; effective 10 November 2025.
  34. 34
  35. 35
    Internet Crime Report 2024. FBI Internet Crime Complaint Center.

Industry bodies and independent research

Contractor associations, RICS, NBER and consultancies. Two of them were sponsored by or reached through a software vendor, and are marked.

  1. 36
    Construction workforce shortages remain acute despite soft market conditions. Associated General Contractors of America and NCCER, 3 September 2026.
    Survey of 1,830 firms
  2. 37
    Construction input costs climb 8.9% between August 2025 and August 2026. Associated General Contractors of America, 10 September 2026.
    Based on the BLS producer price index
  3. 38
    ABC survey: 1 in 6 members perform data center work; backlog rebounds in August. Associated Builders and Contractors, 15 September 2026.
  4. 39
    Artificial intelligence in construction report 2025. Royal Institution of Chartered Surveyors, 12 September 2025.
    2,200+ respondents; 48% in the UK, 10% in the Americas
  5. 40
    The strange and awful path of productivity in the US construction sector (w30845). Austan Goolsbee and Chad Syverson, National Bureau of Economic Research, January 2023.
  6. 41
  7. 42
    Construction Disconnected. FMI and PlanGrid, 2018.
    Survey of 599 professionals, sponsored by PlanGrid (now part of Autodesk)
  8. 43
    RFI in construction (quoting a 2013 Navigant Consulting study of 1,362 projects). Procore.
    Secondhand: we read the vendor's summary, not the Navigant original

Vendor sources

Published by companies that sell AI or software to contractors. Directional, not an industry benchmark.

  1. 44
    Procore AI: agents, Deep Search and customer results. Procore, read October 2026.
    Vendor source
  2. 45
    Trunk Tools. Trunk Tools, read October 2026.
    Vendor source
  3. 46
    Document Crunch. Document Crunch, read October 2026.
    Vendor source
  4. 47
    Togal.AI. Togal.AI, read October 2026.
    Vendor source
  5. 48
    OpenSpace. OpenSpace, read October 2026.
    Vendor source
  6. 49
    TrustLayer. TrustLayer, read October 2026.
    Vendor source
  7. 50
    Siteline. Siteline, read October 2026.
    Vendor source

Company and press

News coverage and encyclopedia summaries, used for funding rounds, company histories and cases where no primary text was reachable.

  1. 51
  2. 52
  3. 53
  4. 54
    Katerra. Wikipedia.
  5. 55
    Procore. Wikipedia.
  6. 56
  7. 57
    Grenfell Tower Inquiry. Wikipedia.
    Summary of the Phase 2 report of 4 September 2024
  8. 58
  9. 59
  10. 60
    Moffatt v. Air Canada. Wikipedia.
    Encyclopedia summary of the 2024 tribunal decision
  11. 61
  12. 62
    Biometric Information Privacy Act. Wikipedia.
    Statute text on ilga.gov did not load

Become a design partner

Run Stage 0 and one Stage 1 or Stage 2 flow on one of your jobs with us. You get early access, help connecting your project system, and a say in what we build next.

Or email support@prefero.ai