AI Playbook
for Construction

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.