What does the AI Playbook for Construction AI: Prompts, Skills, Connected Work & Agents include?

Bid smarter, catch schedule slippage early, and keep crews informed in the field. This playbook covers how GCs and contractors are putting AI to work on real projects.

Inside this playbook

Prompts • Skills • Connectors • Agents • Construction workflows • Tools

AI Playbook for Construction Teams

Q: How do Construction AI: Prompts, Skills, Connected Work & Agents teams implement AI?

30-60-90 Day AI Implementation Plan. Phased rollout for construction teams. Quick wins first, then scale what works.

A practical guide to using AI for estimating, project management, field operations, cost control, and closeout.

100

AI Prompts

Claude-Ready Skills

Ways to Connect Your Work

AI Agents for Construction

100AI Prompts

12Claude-Ready Skills

20Ways to Connect Your Work

12AI Agents for Construction

Choose your next step

Need help now? Start with a prompt. Repeat the job? Save a skill. Need current project context? Connect approved work. Ready for a recurring review? Explore agents.

→

+Suggest an edit

Start With Your Role

Start with one construction task that repeats. Keep the field, contract, safety, and approval decisions with the people responsible for them.

Estimator

Start with: estimate review or bid-scope comparison
Save as a skill: required inputs, steps, and reviewer rules
Connect: bid instructions, drawings, addenda, takeoff, and cost rules
First agent: estimate review assistant
Measure: completeness, exceptions found, and reviewer changes

Project Manager

Start with: RFI draft or change-order work packet
Save as a skill: required inputs, steps, and reviewer rules
Connect: contract, schedule, RFIs, submittals, and approved templates
First agent: project correspondence coordinator
Measure: completeness, exceptions found, and reviewer changes

Superintendent

Start with: daily report or look-ahead plan
Save as a skill: required inputs, steps, and reviewer rules
Connect: daily logs, photos, schedule, safety plan, and constraints
First agent: daily field-report assistant
Measure: completeness, exceptions found, and reviewer changes

Controller

Start with: cost-to-complete review or pay-app packet
Save as a skill: required inputs, steps, and reviewer rules
Connect: job-cost report, commitments, approved changes, and billing data
First agent: cost-control reviewer
Measure: completeness, exceptions found, and reviewer changes

Start with preparation, not decisions

A useful first result is a complete work packet with the facts, gaps, owner, and next step visible.

→

+Suggest an edit

100 AI Prompts for Construction Teams

Ready-to-use prompts for estimating, scheduling, cost control, subcontractors, field operations, safety, claims, equipment, owner communication, and business planning. Copy one, add approved project context, and review the result.

12 prompts for Project Managers, Superintendents, and Schedulers — covering master schedule build, delay analysis, look-ahead scheduling, procurement, and milestone tracking.

Project Schedule Build

You are a project manager building the master schedule for a construction project. Project data: [DESCRIBE: Project type (commercial/residential/industrial/civil), scope of work, contract duration, key milestones (NTP/substantial completion/final completion), phasing requirements, known long-lead items] Build the master schedule: 1. Work breakdown structure — break the project into major phases (sitework / foundation / structure / envelope / MEP rough-in / finishes / commissioning / closeout) 2. Sequence logic — dependencies between activities; what must finish before the next can start 3. Long-lead items — materials or equipment with lead times >8 weeks; order dates required to meet schedule 4. Critical path — the sequence of activities that determines the minimum project duration; flag any activity with zero float 5. Milestone dates — calculate NTP + each phase start/finish + substantial completion + final completion Output: Master schedule framework. Critical path identified. Long-lead procurement dates. Milestone date table.

Requiring the critical path and long-lead order dates in the same output connects scheduling to procurement — the two most common sources of project delay — in a single deliverable.

Risks: AI schedule logic is based on typical construction sequences; project-specific constraints may change dependencies. Control: Project manager and superintendent review sequence logic against actual site conditions before publishing.

Schedule Delay Analysis

You are a project manager analyzing a schedule delay on an active project. Schedule data: [PASTE: Original baseline schedule (key activities and dates) | Current actual/forecast dates | Activities delayed | Delay duration per activity | Cause of delay (weather/owner/design/subcontractor/material/unforeseen)] Analyze: 1. Total delay — current forecast substantial completion vs. original; days behind 2. Critical path impact — which delays are on the critical path and actually pushing the completion date? 3. Delay cause classification: owner-caused (compensable) / excusable (weather/force majeure) / contractor-caused (non-compensable) 4. Float consumption — how much float has been consumed on near-critical activities? 5. Recovery options — acceleration measures, resequencing, or additional resources to recover days Output: Delay analysis summary. Compensable vs. non-compensable delay breakdown. Recovery plan options with cost estimate. Basis for time extension request if applicable.

Classifying delays as compensable, excusable, or contractor-caused in the analysis forces the AI to apply contract logic — not just measure days — which is what supports a time extension request.

Risks: Delay cause classification requires contract review and legal judgment that AI cannot make definitively. Control: Project manager and counsel review all compensable delay claims before submission to owner.

Look-Ahead Schedule (3-Week)

You are a superintendent preparing the 3-week look-ahead schedule. Current project status: [PASTE: Active work areas | Work completed to date | Subcontractors on site | Upcoming activities for next 3 weeks | Material deliveries expected | Inspections required | Any constraints (access/weather/owner decisions pending)] Build the look-ahead: 1. Week-by-week activities — what work is planned each day for each crew/sub 2. Crew and equipment requirements — confirm all resources are committed and available 3. Material deliveries — confirm materials are ordered and delivery dates align with installation dates 4. Inspections and approvals — schedule required inspections before work is covered 5. Constraints to clear — items that must be resolved before scheduled work can proceed; owner or owner's action Output: 3-week look-ahead table. Constraint log with owner and due date for each item. Material delivery confirmation list.

The constraint log with named owners is the highest-value output — it converts the look-ahead from a planning document into an accountability tool for the weekly coordination meeting.

Risks: Look-ahead accuracy depends on subcontractor input that AI cannot independently verify. Control: Superintendent confirms crew commitments and material dates with each sub before distributing.

Critical Path Analysis

You are a scheduler performing a critical path analysis on a delayed project. Schedule data: [PASTE: Activities | Duration | Predecessors | Successors | Early start | Early finish | Late start | Late finish | Total float] Analyze: 1. Critical path — all activities with zero total float; sequence from start to finish 2. Near-critical activities — activities with float <5 days; these are at risk of joining the critical path 3. Float consumption rate — how quickly is float being consumed on near-critical paths? 4. Longest path analysis — if multiple near-critical paths exist, rank by risk to project completion 5. Acceleration opportunities — activities on the critical path where additional resources or overlap could recover time Output: Critical path summary. Near-critical activity watch list. Float consumption analysis. Top 3 acceleration opportunities with estimated time recovery and cost.

The float consumption rate metric changes the analysis from a static snapshot to a trend — identifying which near-critical activities are accelerating toward the critical path before they get there.

Risks: CPM analysis is only as accurate as the schedule data provided. Control: Scheduler validates activity durations and logic against field conditions before using for claims or recovery planning.

Project Phasing Plan

You are a project manager planning the phasing of a complex construction project. Project data: [DESCRIBE: Project type and scope, site constraints (occupied building/active operations/limited access), owner phasing requirements, contract completion date, key systems or areas that must remain operational during construction] Build the phasing plan: 1. Phase definition — define each phase by area, scope, and duration 2. Phase sequencing — why must phases occur in this order? (structural / MEP dependencies / owner occupancy) 3. Temporary conditions — what temporary measures are required between phases? (temp walls / HVAC / egress) 4. Transition plan — how does each phase hand off to the next without disrupting ongoing operations? 5. Phasing impact on cost — does phasing add cost vs. a single-phase approach? Quantify. Output: Phasing plan document. Phase sequence with rationale. Temporary conditions list. Cost impact of phasing.

Requiring the cost impact of phasing vs. a single-phase approach gives the owner a financial basis for their occupancy decisions — turning a logistics plan into a value engineering conversation.

Risks: Temporary conditions costs are estimates until engineered. Control: MEP and structural engineers review phasing plan for system continuity requirements before owner presentation.

Float Analysis and Recovery Plan

You are a project manager assessing schedule float and developing a recovery plan. Schedule data: [PASTE: Current project status (% complete) | Original completion date | Current forecast completion date | Days behind schedule | Activities with lowest float | Resources currently deployed] Assess float and build a recovery plan: 1. Float status — total float remaining on critical and near-critical paths 2. Root causes of float consumption — what has driven the schedule behind? 3. Recovery options: Crashing: add resources to critical path activities; estimate cost per day recovered Fast-tracking: overlap activities that were originally sequential; identify risks Resequencing: change the order of non-critical work to free up critical resources 4. Recommended recovery plan — combination of measures to recover the schedule 5. Cost of recovery — total additional cost vs. delay consequences (LDs, extended GCs) Output: Float analysis. Recovery plan options with cost. Recommended plan. Decision recommendation for project team.

Comparing the cost of recovery against the cost of delay consequences — LDs and extended GCs — frames the recovery decision as a financial trade-off, which is what the project executive needs.

Risks: Crashing and fast-tracking estimates are preliminary until subcontractors confirm resource availability. Control: Project manager validates recovery plan feasibility with key subs before committing to owner.

Procurement Schedule

You are a project manager building the procurement schedule for a construction project. Project data: [PASTE: Major materials and equipment to procure | Required on-site dates (based on installation schedule) | Typical lead times for each item | Procurement method (owner-furnished / GC-furnished / sub-furnished)] Build the procurement schedule: 1. Required order dates — work backward from on-site date minus lead time for each item 2. Long-lead items — items with lead times >8 weeks that need immediate action 3. Owner-furnished equipment — items the owner is procuring; confirm their timeline aligns with installation 4. Submittal requirements — items requiring shop drawings or product data before fabrication begins; add submittal lead time 5. Procurement risk — items with long lead times, single-source suppliers, or supply chain constraints Output: Procurement schedule table — Item | Lead time | Required on-site date | Order by date | Procurement responsibility | Status. Long-lead alert list for immediate action.

Working backward from installation dates to order-by dates is the calculation most procurement schedules skip — resulting in last-minute discoveries of items that needed to be ordered months ago.

Risks: Lead times vary by market conditions and supplier; AI estimates from typical ranges. Control: Confirm actual lead times with suppliers before finalizing order-by dates.

Subcontractor Schedule Coordination

You are a superintendent coordinating subcontractor schedules on a multi-trade project. Project data: [PASTE: Active subcontractors | Their current scope remaining | Planned start/finish for each sub | Crew sizes | Known conflicts or sequencing issues | Shared work areas] Coordinate: 1. Sequence conflicts — identify where two subs need the same area at the same time 2. Predecessor dependencies — work that one sub must complete before another can start 3. Crew stacking — too many crews in one area creating safety and efficiency problems 4. Critical sub activities — which subcontractors are on the critical path right now? 5. Short-interval commitments — get each sub to commit to specific 2-week deliverables Output: Subcontractor coordination matrix. Sequence conflicts with resolution. Short-interval commitment log. Critical path subs requiring daily check-in.

Short-interval commitments — specific 2-week deliverables from each sub — convert the coordination meeting from a status report into an accountability session.

Risks: Coordination matrix is only valid as of the date prepared; conditions change daily. Control: Superintendent updates the matrix weekly at minimum; daily for critical path activities.

Weather Delay Documentation

You are a project manager documenting weather delays for time extension purposes. Weather data: [PASTE: Dates of weather events | Weather type (rain/snow/extreme heat/wind) | Measured conditions (rainfall inches/temperature/wind speed) | Work impacted | Contract weather standard (days per month or specific thresholds) | Days claimed as weather delays] Document the weather delay claim: 1. Compare actual weather to contract allowance — days of weather delay above the contractual baseline 2. Work impact — specific activities that were delayed; confirm they were critical path or on near-critical path 3. Notice compliance — confirm notice of delay was provided to the owner within the contract-required timeframe 4. Supporting documentation — weather station data, daily reports, photographs confirming work stoppage 5. Time extension calculation — compensable weather delay days based on contract methodology Output: Weather delay log. Comparison to contract allowance. Time extension calculation. Supporting documentation checklist.

Comparing actual weather to the contract allowance — not just listing bad weather days — is the calculation that determines entitlement. Many delay claims fail because they don't make this comparison.

Risks: Weather station data must be from a source acceptable to the owner per contract. Control: Use the nearest NOAA weather station or as specified; document the source in the claim.

Milestone Tracking Report

You are a project manager preparing the monthly milestone tracking report for the owner. Milestone data: [PASTE: Milestone | Baseline date | Forecast date | Actual date (if complete) | Status (complete/on track/at risk/delayed) | Variance days | Cause of any variance] Produce: 1. Milestone status dashboard — traffic light for each milestone: Green (on track) / Yellow (at risk) / Red (delayed) 2. Variance summary — milestones behind baseline; days delayed and cause 3. Recovery actions — for delayed milestones, what is the plan to recover and by when? 4. Look-ahead — next 60 days; milestones due and confidence level 5. Owner attention required — any milestone where owner action or decision is needed to maintain schedule Output: Milestone tracking report. Traffic light dashboard. Variance log with recovery plan. Owner action items.

The 'owner attention required' section is what transforms a status report into a decision tool — explicitly surfacing what the owner must do to keep the schedule on track.

Risks: Traffic light ratings require judgment calls that depend on project context. Control: Project manager reviews all Yellow and Red ratings before distributing to confirm accuracy.

Schedule Specification Compliance Review

You are a project manager reviewing schedule requirements from the contract specifications. Specification data: [PASTE: Relevant schedule specification sections — required schedule type (CPM/Gantt/P6), update frequency, baseline submission requirements, float ownership clause, recovery schedule requirements, narrative requirements] Review compliance: 1. Schedule type and software — does current schedule meet specification requirements? 2. Baseline submission — was a compliant baseline schedule submitted within the required timeframe? 3. Update frequency — are schedule updates being prepared and submitted at required intervals? 4. Float ownership — does the contract specify that float belongs to the project or the contractor? Note for claims purposes. 5. Recovery schedule triggers — what conditions trigger a required recovery schedule? Are any currently triggered? Output: Schedule specification compliance checklist. Non-compliant items requiring immediate action. Float ownership note for claims file.

The float ownership clause note for the claims file is often overlooked during execution — identifying it early is critical because it directly affects what time extension claims are available.

Risks: Specification interpretation may require legal review for ambiguous language. Control: Project manager and counsel review float ownership clause before any time extension claim is filed.

Project Completion Checklist

You are a project manager preparing for substantial completion. Project data: [DESCRIBE: Project type, contract completion requirements, remaining punch list items, outstanding submittals or closeout documents, owner training requirements, warranty requirements, commissioning status] Build the completion checklist: 1. Physical completion — outstanding construction items; estimated hours to complete each 2. Systems commissioning — mechanical, electrical, plumbing, fire protection — tested and accepted? 3. Inspections and certificates — certificate of occupancy, AHJ inspections, special inspections completed? 4. Closeout submittals — O&M manuals, as-builts, warranties, attic stock, spare parts 5. Owner training — all required system training scheduled and completed? Output: Substantial completion checklist. Outstanding items by responsible party. Estimated days to achieve substantial completion. Certificate of substantial completion readiness assessment.

The readiness assessment at the end forces an honest answer to whether substantial completion is actually achievable on the claimed date — preventing premature notifications that damage owner relationships.

Risks: Commissioning and AHJ inspection timelines are outside the contractor's control. Control: Schedule inspections and commissioning activities early; don't wait for punch list completion.

Start with a prompt

Use approved project information and review every result before it is used in the field, sent externally, or added to a project record.

→

12 Claude-Ready Construction Skills

Downloadable Claude Skill packages for repeatable construction work. Each defines inputs, output, controls, and a reviewer.

Bid scope review

# Bid scope review ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a bid scope review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a bid scope review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Estimate validation

# Estimate validation ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a estimate validation work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a estimate validation work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

RFI preparation

# RFI preparation ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a rfi preparation work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a rfi preparation work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Submittal review

# Submittal review ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a submittal review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a submittal review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Daily field report

# Daily field report ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a daily field report work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a daily field report work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Three-week look-ahead

# Three-week look-ahead ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a three-week look-ahead work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a three-week look-ahead work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Change order packet

# Change order packet ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a change order packet work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a change order packet work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Safety observation review

# Safety observation review ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a safety observation review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a safety observation review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Schedule variance review

# Schedule variance review ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a schedule variance review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a schedule variance review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Cost-to-complete review

# Cost-to-complete review ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a cost-to-complete review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a cost-to-complete review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Pay application review

# Pay application review ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a pay application review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a pay application review work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

Closeout checklist

# Closeout checklist ## Role You are a construction workflow assistant. Prepare clear, evidence-based work for a qualified construction reviewer. Do not take consequential project actions. ## Required input - approved project records and stated rules ## Your task Prepare a closeout checklist work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. ## Working method 1. Confirm the organization, time period, owner, and source material. List missing inputs before you begin. 2. Use only the supplied or approved connected sources. Never invent facts, policy, or context. 3. Prepare a closeout checklist work packet from the approved information. Flag missing evidence and do not change project records, commitments, schedule, payments, or safety decisions. 4. Separate confirmed facts from assumptions or hypotheses. Cite source names, report lines, or record IDs when available. 5. Flag exceptions by urgency, risk, and accountable owner. ## Return this format 1. Executive summary (3-5 bullets) 2. Detailed evidence and analysis 3. Exceptions, open questions, and required evidence 4. Owner, priority, and next step for each unresolved item 5. Review checkpoint: a review-ready packet with gaps and next steps ## Human review boundary the responsible construction lead approves actions ## Non-negotiable guardrails - Do not change source records, send external communications, make commitments, or make a legal, financial, or policy decision. Ask for human review whenever the evidence is incomplete or the policy is unclear.

+Suggest an edit

Connect Your Work

Start with one approved source for one job. Some connections are easy to try; construction-system integrations usually need an administrator or implementation work.

Easy start

Start with a limited, low-risk connection your team can test quickly.

Start With Project Documents

Access: approved drawings, specifications, addenda, meeting notes, and templates
Useful for: bid review, RFI preparation, and closeout checklists
Setup & limit: use a scoped folder and treat uploads as copies, not a live system connection

Google Workspace: Email, Files & Contacts

Access: approved Gmail, Drive, Calendar, Contacts, and shared Docs, Sheets, or Slides through the available Google Workspace app
Useful for: finding project correspondence, meeting context, drawing transmittals, customer contacts, and approved templates
Setup & limit: begin with one project folder or mailbox; confirm who can access each source before expanding

Microsoft 365 Project Files

Access: ChatGPT can search SharePoint files a user is permitted to access
Useful for: finding project records, templates, and owner or internal materials
Setup & limit: start with a selected site or folder; administrator approval may be required

Slack Job Communications

Access: ChatGPT can search Slack messages, threads, and channels the signed-in user can access
Useful for: finding job discussions, decisions, shared links, and follow-up context
Setup & limit: use it only if your team already runs work in Slack; start with search and keep messages or channel changes disabled until reviewed

QuickBooks Finance Data

Access: an authenticated QuickBooks connection in Claude or ChatGPT, subject to product and regional availability
Useful for: job-cost questions, invoices, cash, receivables, and finance-report preparation
Setup & limit: begin with read-only questions and report preparation; an authorized finance person owns book changes, payments, and payroll

Xero Finance Data

Access: a direct, read-only Xero connector in Claude
Useful for: cash, invoices, receivables, profit, and construction-finance questions with links back to Xero
Setup & limit: it cannot edit invoices, post transactions, or change the books; finance reviews every result

Needs an administrator

These can be useful, but someone needs to set access and permissions first.

Microsoft Teams Job Communications

Access: Teams chats, channels, Planner tasks, and meeting artifacts available to the signed-in user
Useful for: finding project discussions, action items, shared links, and meeting follow-up
Setup & limit: Microsoft Entra approval may be required; begin with read/search and keep sending messages or creating tasks disabled until reviewed

CRM, Owner & Customer Records

Access: permitted lead, customer, company, opportunity, contact, and activity records through a CRM’s approved API or hosted MCP connection
Useful for: bid handoff briefs, owner-contact history, follow-up worklists, and project-to-customer context
Setup & limit: begin read-only with the minimum fields; protect personal contact information and keep customer outreach, record edits, and deal decisions with the assigned person

Procore: Controlled Project Integration

Access: Procore project data through its OAuth-protected developer platform
Useful for: a narrowly defined RFI, submittal, daily-log, or project-reporting workflow
Setup & limit: set approved scopes and read/write boundaries with a Procore administrator before connecting

Autodesk Construction Cloud: Controlled Integration

Access: Autodesk Construction Cloud and BIM 360 data through Autodesk Platform Services
Useful for: governed document, model, checklist, or project-data workflows
Setup & limit: requires an app, permission review, and a project-specific implementation

Primavera Cloud Schedules

Access: Primavera Cloud schedule and project data through its REST API
Useful for: look-ahead summaries, schedule narratives, and variance-review packets
Setup & limit: use a read-only service account first; Oracle documents OAuth or Basic Authentication depending on the environment

Integration project

Plan the use case, source data, permissions, and owner before connecting.

Payroll & Time: Integration Project

Access: payroll and people data through a vendor-approved integration or a controlled export
Useful for: payroll-information review and cost-code or time-report preparation
Setup & limit: start with a narrow report; payroll submissions, employee changes, and compensation decisions stay with authorized staff

Trimble Viewpoint Vista Job Cost

Access: Vista ERP and project-management data through the Vista API
Useful for: controlled job-cost, commitment, and cost-to-complete reporting
Setup & limit: this is an ERP integration project; finance and IT define permitted records and actions

BIM, Drawings & Model Data

Access: selected model or document data via Autodesk Platform Services
Useful for: model-data lookup and a controlled coordination or review workflow
Setup & limit: do not treat model data as field-verified; an administrator must set project access and data scope

Your Internal Systems

Access: approved reports or APIs exposed through a controlled integration
Useful for: one narrow, view-only recurring job
Setup & limit: document permitted data and actions before building

Good to know

Useful limits and honest gaps to keep in mind before you connect anything.

Bank, Card & Expense Exports

Access: approved bank, card, and expense exports, not banking credentials
Useful for: cash review, coding-review preparation, and expense-exception worklists
Setup & limit: use a controlled export or vendor-approved integration; finance verifies every recommendation

Estimating, Bid & Takeoff Exports

Access: approved takeoffs, bid tabs, invitations, addenda, and estimate exports
Useful for: scope comparison, bid leveling, addendum tracking, and estimator review packets
Setup & limit: treat this as a controlled export first; the estimator verifies scope, quantities, and pricing

Field Photos, Daily Logs & Forms

Access: approved photo sets, daily logs, inspection forms, and issue lists
Useful for: daily-report drafts, missing-information lists, and closeout follow-up
Setup & limit: do not use AI to direct crews or make safety determinations; the superintendent verifies content before sharing

Schedule, Cost & Field Exports

Access: approved exports from scheduling, job-cost, time, quality, or field-photo systems
Useful for: a reviewable schedule narrative, cost variance packet, or daily-report draft
Setup & limit: confirm the export date, source, and owner; do not write back to the source system

What to Avoid at First

Access: do not begin with unrestricted project records, payroll, bank details, or safety investigations
Useful for: choosing a small, reversible first connection instead
Setup & limit: do not let AI submit an RFI, alter a schedule, approve a change, release payment, or direct field work

Start with one project question

Connect one approved source to one reviewable job. Expand access only after the project team sees useful, safe results.

→

+Suggest an edit

70+ AI Tools for Construction

Comprehensive landscape. Organized by category. Click to filter.

Document & Communication AI 6 Tools

EgnyteHardlineProcore DocumentsStack CTe-BuilderAutoSpecs

No single tool = complete solution

Layer tools across the construction lifecycle. Start with LLMs and your existing PM platform, add purpose-built tools as you scale.

12 AI Agents for Construction Teams

An agent prepares one recurring job from approved information for a named construction reviewer.

What makes an AI agent useful

A good first agent handles one task your team already does. Give it the information it needs, tell it when to stop, and have a person check the work.

Bid Intake Coordinator

# Bid Intake Coordinator

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Estimate Review Assistant

# Estimate Review Assistant

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

RFI Coordinator

# RFI Coordinator

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Submittal Status Watcher

# Submittal Status Watcher

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Daily Field Report Assistant

# Daily Field Report Assistant

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Look-Ahead Planner

# Look-Ahead Planner

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Change Order Packet Assistant

# Change Order Packet Assistant

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Safety Follow-Up Assistant

# Safety Follow-Up Assistant

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Schedule Variance Monitor

# Schedule Variance Monitor

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Cost-to-Complete Reviewer

# Cost-to-Complete Reviewer

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Pay Application Packet Assistant

# Pay Application Packet Assistant

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

Closeout Coordinator

# Closeout Coordinator

## Job to be done
Prepare recurring accounting work for qualified human review.

## When it runs
On an approved schedule or trigger.

## Approved context
Only the approved systems, files, and records named by the workflow owner.

## Operating loop
Gather context, apply the approved skill, prepare a work packet, and route exceptions.

## What it delivers
A review-ready work packet with evidence, questions, and next steps.

## Human owner
A named accounting owner reviews and approves the output.

## What it must never do
Never take a consequential action without explicit human approval.

## How to measure it
Measure accuracy, cycle time, exception resolution, and human override rate.

## Operating rules
1. Use only approved sources and follow the linked accounting skill.
2. Cite source records and separate facts from hypotheses.
3. Route missing evidence, threshold breaches, and material exceptions to the human owner.
4. Keep an auditable record of trigger, inputs, output, reviewer, decision, and override.
5. Stop and ask for human review when the policy, evidence, or approval authority is unclear.

+Suggest an edit

AI for Preconstruction & Estimating

Win more bids, faster. AI automates takeoffs, sharpens estimates, and spots risks before ground breaks.

AI-Powered Quantity Takeoff

What AI does: Reads blueprints and PDFs, auto-measures quantities for concrete, steel, and drywall
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Bid Analysis & Pricing

What AI does: Analyzes historical bid data across projects, regions, and trades
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Risk Assessment & Flagging

What AI does: Scans specs and plans for scope gaps, ambiguities, and conflicts
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Subcontractor Prequalification

What AI does: Scores subs on financials, safety record, past performance, and capacity
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Plan Comparison & Revision Tracking

What AI does: Compares drawing revisions automatically, highlights structural, MEP, and architectural deltas
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Cost Database Intelligence

What AI does: Maintains real-time material and labor cost databases with supplier pricing
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Preconstruction Implementation Checklist

Workflow

Pre-Implementation

Map current estimating process and tools in use
Identify highest-volume bid types for AI pilot
Establish baseline metrics for takeoff time, estimate accuracy, and win rate
Define data standards for historical bid import
Train estimators on AI takeoff tools

Post-Implementation

Compare AI vs. manual takeoff accuracy weekly
Track bid win rate improvement vs. baseline
Monitor cost database currency and update frequency
Review all AI-flagged risks before bid submission
Collect estimator feedback on tool effectiveness and usability

Controls for AI Estimating

Estimate accuracy: All AI takeoffs must be spot-checked by senior estimator before bid submission
Scope verification: AI-flagged risks reviewed by project manager before pricing
Historical data quality: Bid data must be cleaned and standardized before AI training
Confidentiality: Never upload proprietary pricing or client data to public AI tools
Version control: Track which plan revision the AI analyzed; re-run for all updates
Override logging: Document all manual overrides to AI estimates with reasoning
Margin guardrails: Set min/max margin thresholds; AI cannot auto-submit bids

Top Preconstruction vendors

Togal.AIProEstDESTINI EstimatorPlanSwiftBuildxactConEstStack CTBluebeam

+Suggest an edit

AI for Project Management & Scheduling

Predict delays before they happen. AI optimizes schedules, tracks progress, and keeps projects on time.

Predictive Scheduling

What AI does: Builds and optimizes schedules using historical project data, weather, and supply chain signals
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Progress Tracking & Monitoring

What AI does: Uses drone imagery, photos, and sensor data to track actual vs. planned progress
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

RFI & Submittal Management

What AI does: Drafts RFI responses from specs, drawings, and historical data
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Resource Leveling

What AI does: Optimizes crew assignments and equipment allocation across multiple projects
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Meeting Intelligence

What AI does: Transcribes OAC meetings, generates minutes, and extracts action items automatically
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Document Control AI

What AI does: Auto-classifies, routes, and tracks construction documents
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Project Management Implementation Checklist

Workflow

Pre-Implementation

Audit current scheduling tools and data quality
Define schedule data standards with WBS and activity codes
Establish baseline metrics for schedule variance and RFI turnaround
Identify pilot project with good historical data
Train PMs on AI scheduling features and outputs

Post-Implementation

Compare AI schedule predictions vs. actual weekly
Monitor RFI response time improvement
Review AI progress tracking against manual counts
Track resource utilization metrics across projects
Measure PM time saved on admin tasks and reporting

Controls for AI Project Management

Schedule authority: AI-generated schedules reviewed by PM before client distribution
RFI accuracy: All AI-drafted RFI responses reviewed by subject matter expert
Progress verification: Spot-check AI progress tracking against physical inspection monthly
Data security: Project data classified per owner requirements before AI tool access
Change management: AI schedule impacts reviewed before change order pricing
Audit trail: All AI-suggested schedule changes logged with reasoning
Client communication: AI-generated reports reviewed before external distribution

Top Project Management vendors

ProcoreAutodesk BuildOracle PrimaveraBuildertrendFieldwireCoConstructNewformae-Builder

+Suggest an edit

AI for Field Operations & Safety

Safer sites, smarter operations. AI monitors hazards, tracks compliance, and optimizes field workflows.

Computer Vision Safety Monitoring

What AI does: Analyzes camera and drone feeds for PPE violations, fall hazards, and exclusion zone breaches
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Predictive Safety Analytics

What AI does: Identifies incident patterns from near-miss data, weather, crew fatigue, and task type
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Digital Daily Logs & Reporting

What AI does: Auto-generates daily reports from photos, check-ins, and sensor data
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Quality Control Inspections

What AI does: Photo-based QC with AI comparison to specs and standards
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Toolbox Talk Generation

What AI does: Generates job-specific safety talks from activity type, weather, and incident history
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Site Logistics Optimization

What AI does: Optimizes material staging, crane placement, and traffic flow patterns
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Field Operations Implementation Checklist

Workflow

Pre-Implementation

Assess current safety incident tracking and reporting systems
Identify highest-risk activities for AI monitoring pilot
Install cameras and sensors at pilot site
Establish baseline safety metrics for TRIR, near-misses, and EMR
Train field supervisors on AI safety tools and alert response

Post-Implementation

Monitor AI hazard detection accuracy daily with supervisors
Review false positive rate and adjust sensitivity thresholds
Track TRIR improvement vs. baseline metrics
Audit daily log completeness and accuracy
Collect superintendent feedback on tool usability and effectiveness

Controls for AI Field Operations

Safety authority: AI hazard alerts supplement but do not replace competent person requirements
Privacy: Camera placement must comply with labor agreements and privacy laws
False positives: Calibrate detection thresholds to minimize alert fatigue
Incident reporting: AI-detected incidents still require formal investigation and documentation
OSHA compliance: AI-generated safety docs reviewed by safety director before use
Data retention: Safety camera footage retained per project requirements, typically 3-5 years
Worker notification: All workers informed of AI monitoring per company policy and regulations

Top Field Operations vendors

OpenSpaceSafesiteNewmetrixSmartvid.ioHoloBuilderSiteDocsVersatileSpot-r

+Suggest an edit

AI for Financial Management & Cost Control

Control costs before they control you. AI tracks budgets, predicts overruns, and automates pay applications.

Real-Time Cost Tracking

What AI does: Monitors actual costs vs. budget across all cost codes in real time
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Change Order Impact Modeling

What AI does: Models ripple effects of change orders on schedule, cost, and downstream trades
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Cash Flow Forecasting

What AI does: Predicts project and portfolio cash flow from schedule, commitments, and payment history
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Pay Application Automation

What AI does: Generates progress-based pay apps from schedule and cost data
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Lien Waiver & Compliance Tracking

What AI does: Tracks lien waiver status across all tiers of subcontractors
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Productivity Analysis

What AI does: Analyzes labor productivity by trade, crew, and activity
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Cost Control Implementation Checklist

Workflow

Pre-Implementation

Map current cost reporting workflow and reporting cadence
Define cost code structure and data standards
Establish baseline metrics for cost variance and change order frequency
Identify pilot project with good cost data history
Train project accountants on AI cost management tools

Post-Implementation

Monitor AI cost alerts accuracy and timeliness
Track change order pricing accuracy vs. actuals
Review cash flow forecast accuracy monthly
Measure pay app processing time improvement
Audit lien waiver compliance rates and exceptions

Controls for AI Cost Management

Financial authority: AI cost projections reviewed by project controller before reporting
Change order pricing: AI-modeled impacts verified by estimating before negotiation
Payment approval: AI-generated pay apps require PM sign-off before submission
Audit trail: All AI cost adjustments logged with timestamps and reasoning
Confidentiality: Cost data classified; restrict AI tool access to authorized personnel
Threshold alerts: Configure alert thresholds per project risk profile
Reconciliation: AI cost tracking reconciled with accounting system monthly

Top Cost Control vendors

Sage 300 CREFoundation SoftwareCMiCViewpoint VistaProcore FinancialsGCPayTexturaInEight

+Suggest an edit

AI for Equipment, Materials & Supply Chain

Right materials, right time, right place. AI optimizes procurement, tracks assets, and prevents delays.

Predictive Procurement

What AI does: Forecasts material needs from schedule, BOMs, and lead time data
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Equipment Telematics & Utilization

What AI does: Tracks equipment location, usage, idle time, and maintenance needs via IoT
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Supply Chain Risk Monitoring

What AI does: Monitors supplier health, shipping delays, and material price volatility
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Automated Material Tracking

What AI does: Tracks material deliveries, storage locations, and installation status
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Tool & Small Equipment Management

What AI does: RFID and GPS tracking for tools and small equipment across projects
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Vendor Performance Scoring

What AI does: Rates suppliers on delivery timeliness, quality, pricing, and responsiveness
What to review: Confirm the source information, assumptions, gaps, and exceptions
Control: The assigned construction lead verifies the result before any project action

Equipment & Materials Implementation Checklist

Workflow

Pre-Implementation

Inventory current equipment fleet and utilization rates
Map procurement workflow from requisition to delivery
Establish baseline metrics for material waste and equipment idle time
Identify pilot project for material tracking and RFID rollout
Define data standards for supplier performance tracking

Post-Implementation

Monitor equipment utilization rates weekly across fleet
Track material delivery on-time performance
Review AI procurement recommendations vs. actual needs
Measure waste reduction against baseline metrics
Audit tool tracking accuracy and loss rates quarterly

Controls for AI Supply Chain

Procurement authority: AI purchase recommendations require approval per delegation matrix
Vendor data: Supplier performance data verified before AI scoring calculations
Equipment safety: AI maintenance alerts supplement but do not replace required inspections
Inventory accuracy: Physical counts reconciled with AI tracking quarterly
Price verification: AI-suggested pricing validated against current market quotes
Data privacy: Supplier financial data restricted to authorized procurement staff
Contract compliance: AI procurement aligned with project-specific contract requirements

Top Equipment & Materials vendors

HCSSTennaToolWatchHilti ON!TrackBuildingConnectedPlanHubProcore BIMInEight

+Suggest an edit

30-60-90 Day AI Implementation Plan

Phased rollout for construction teams. Quick wins first, then scale what works.

Implementation Timeline

Days 1-30 Foundation

Assign AI champion (project manager or ops lead)
Pick 1 pilot use case (daily reports OR RFI drafting OR estimating)
Deploy ChatGPT/Claude to 5-10 PMs and supers with prompt templates
Establish baseline KPIs (RFI turnaround, report time, estimate accuracy)
Create AI usage guidelines (approved tools, data rules, safety provisions)
Run 2-week pilot on one active project; collect feedback daily
Train team on 3-5 starter prompts from this playbook

Days 31-60 Expand

Roll out to all PMs and superintendents
Add 2nd tool (project management AI OR safety monitoring)
Integrate with existing systems (Procore, scheduling software)
Measure KPI improvement vs. baseline
Build team prompt library (10-15 proven construction prompts)
Publish prompt library; run weekly prompt sharing sessions
Brief leadership on ROI metrics and field feedback

Days 61-90 Standardize

Add 3rd workflow (cost tracking OR equipment management)
Formalize AI usage policy; get leadership sign-off
Cross-train team; knowledge not concentrated in 1 person
Create SOPs for each AI-assisted workflow
Measure total impact (time saved, accuracy improvement, cost reduction)
Present results to leadership; plan next wave
Launch "Share Your Prompt" program for continuous improvement

GOALS Implementation Success Metrics

30-Day Targets

5-10 team members trained and actively using AI tools
Baseline KPIs established (RFI time, report time, estimate accuracy)
AI usage guidelines documented and communicated
Daily feedback collected from pilot group

60-Day Targets

Full PM and superintendent team deployed with AI tools
10-15 proven prompts in shared library
2nd tool integrated and live
KPI improvement measured vs. baseline (e.g., 40% faster RFI response)

90-Day Targets

3 workflows operationalized with SOPs
AI usage policy formalized and approved
Team cross-trained (no single points of knowledge failure)
Total ROI calculated: hours saved, accuracy improved, costs reduced
Next wave planned (e.g., safety AI, equipment tracking, BIM integration)

90 days for 3 workflows plus governance. Start with one project, prove value with your team, then scale across all projects.

+Suggest an edit

Core AI Stack for Construction

Start with LLMs for research and documentation. Layer in construction-specific tools as workflows mature.

LLMs — Your AI Foundation

ChatGPT, Claude, Gemini for RFI responses, submittals review, specification analysis, meeting summaries, contract clause interpretation

Estimating & Takeoff Tools

AI-powered quantity takeoffs from plans
Automated cost databases with regional pricing
Historical bid analysis for competitive positioning

Project Management AI

Predictive scheduling with weather/supply chain integration
Resource leveling across multiple projects
Automated progress tracking from drone/photo data

Safety & Compliance AI

Computer vision for PPE detection and hazard identification
Predictive incident analytics from near-miss data
Automated OSHA documentation and toolbox talks

Document & BIM AI

Plan comparison and revision tracking
Clash detection in BIM models
Automated submittal review and RFI drafting

Financial & Cost AI

Real-time cost tracking against estimates
Change order impact modeling
Predictive cash flow and payment forecasting

Architecture tip

Start with LLMs for immediate documentation wins. Layer in estimating and scheduling AI as your data matures.

+Suggest an edit

Where AI Can Help Construction Teams

Use AI to prepare, organize, and review approved project information. The responsible people still make contract, financial, schedule, and field decisions.

Estimating & Bid Review

Compare scope, addenda, exclusions, and bid inputs
Prepare a missing-information and clarification list
Estimator verifies quantities, scope, pricing, and bid terms

Project Administration

Draft RFIs, meeting notes, submittal follow-up, and owner updates
Summarize approved records into a work packet
Project manager verifies contract language, commitments, and external messages

Field Documentation

Organize daily-log inputs, photos, constraints, and next steps
Prepare inspection and closeout follow-up lists
Superintendent and safety lead verify conditions and decide field actions

Cost & Cash Review

Prepare job-cost, commitment, receivable, and pay-application review packets
Flag missing information and items that need a finance review
Controller verifies coding, forecasts, approvals, payroll, and payments

AI prepares work; people stay accountable

Use it to make the facts, gaps, owner, and next step easy to review. It does not make or send consequential construction decisions.

→

+Suggest an edit

Governance, Ethics & Compliance

How to use AI in construction responsibly. Safety, liability, data protection.

Safety & Liability

AI safety tools supplement human safety officers. AI flagging a hazard does not replace competent person duties. Document AI vs. human decisions for liability protection. OSHA compliance remains with the contractor.

Data Security & Confidentiality

Project data (bids, costs, drawings) is highly sensitive. Never upload proprietary data to public AI tools. Use enterprise-grade AI with data isolation. Classify data per owner and contract requirements.

Professional Licensing

AI does not replace licensed professionals (PE, RA). Engineering calculations require PE stamp regardless of AI involvement. AI assists but does not make design decisions. Document AI's role in any professional work product.

Contract & Specification Compliance

AI-generated documents must comply with contract terms. Verify AI output against project-specific requirements. Standard specs may differ from AI training data. Always reference current edition of applicable standards.

Worker Privacy & Consent

AI monitoring (cameras, wearables) requires worker notification. Comply with labor agreements regarding surveillance. Biometric data (face recognition) has strict state regulations. Data retention policies must be documented and communicated.

What NOT to Automate

Structural engineering decisions (humans own). Safety stand-down calls and emergency response. Owner and architect communications on sensitive matters. Final quality acceptance and occupancy decisions.

Bias in AI Tools

AI trained on historical data may reflect past biases. Monitor subcontractor scoring for discriminatory patterns. Equipment maintenance predictions may not account for unique conditions. Regularly audit AI recommendations for systematic bias.

Red Flag Scenarios

AI safety system misses obvious hazard → investigate calibration immediately. Cost predictions consistently wrong → check data quality. Scheduling AI creates impossible timelines → verify constraints. AI vendor access to competitor bid data → review security.

If an owner or inspector would question how a decision was made, document the AI's role clearly.

Sections

Start Here Prompts Skills Connect Your Work Tools Agents

Set Up & Get Running

Start With Your Role

100 AI Prompts for Construction Teams

12 Claude-Ready Construction Skills

Connect Your Work

Easy start

Needs an administrator

Integration project

Good to know

70+ AI Tools for Construction

Estimating & Takeoff 10 Tools

Project Management & Scheduling 10 Tools

BIM & Design AI 7 Tools

Safety & Compliance 8 Tools

Reality Capture & Progress Monitoring 7 Tools

Financial & Accounting 8 Tools

Equipment & Fleet Management 7 Tools

Preconstruction & Bidding 7 Tools

Document & Communication AI 6 Tools

12 AI Agents for Construction Teams

AI for Preconstruction & Estimating

Preconstruction Implementation Checklist

Pre-Implementation

Post-Implementation

AI for Project Management & Scheduling

Project Management Implementation Checklist

Pre-Implementation

Post-Implementation

AI for Field Operations & Safety

Field Operations Implementation Checklist

Pre-Implementation

Post-Implementation

AI for Financial Management & Cost Control

Cost Control Implementation Checklist

Pre-Implementation

Post-Implementation

AI for Equipment, Materials & Supply Chain

Equipment & Materials Implementation Checklist

Pre-Implementation

Post-Implementation

30-60-90 Day AI Implementation Plan

Days 1-30 Foundation

Days 31-60 Expand

Days 61-90 Standardize

GOALS Implementation Success Metrics

30-Day Targets

60-Day Targets

90-Day Targets

Core AI Stack for Construction

Where AI Can Help Construction Teams

Governance, Ethics & Compliance