# Reactive Site Scheduling

*/Problems/Reactive_Site_Scheduling*

## Problem Overview

Construction project managers and site superintendents build master schedules using idealized timelines that rarely survive contact with the field. When reality diverges due to delayed material drops, weather events, or absent subcontractors, the site operates blindly until the next manual update. Superintendents react to delays by pushing dependent trades backward, creating compounding bottlenecks that disrupt the entire project flow.

Traditional scheduling software relies on static Critical Path Method models that require constant manual data entry from field personnel to track progress. Because site supervisors lack the administrative bandwidth to input daily completion metrics, the master schedule quickly drifts from actual site conditions. This data disconnect forces teams to reconcile schedules retroactively during weekly coordination meetings, reducing planning tools to historical ledgers of lost time.

## Problem Severity Frequency

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Severity**: 4
**Frequency**: daily
**Budget Reality**:
- **Price Ceiling**: ~$15k–30k/yr per company — anchored to standard project management software subscriptions, far below the actual cost of project delays
- **Who Controls Spend**: VP of Construction or Project Executive approves; Project Manager recommends
- **Existing Budget Line**: true
- **Switching Cost From Status Quo**: high: rip-and-replace of the scheduling system of record (e.g., Primavera P6), requiring field staff retraining and disruption to existing contractor coordination workflows
**Regulatory Risk**: moderate
**Time Cost Per Event**: ~2–4 hours
**Money Cost Per Event**: ~$2k–10k
**Annual Cost Per Affected Entity**: ~$150k–500k all-in

## Problem Why Now

The construction industry faces a severe shortage of skilled trades (per AGC ~2023), driving up the financial penalty for idle labor. Subcontractors now routinely charge general contractors for stand-by time when job sites are not ready for their scheduled arrival. This shifts the cost of reactive scheduling directly onto the builder, turning daily schedule drift into a critical margin liability rather than a theoretical planning issue.

Prior software attempted to solve this by digitizing the Critical Path Method, but still required constant manual input from site superintendents. Field supervisors lack the bandwidth to log daily installed quantities on tablets, causing master schedules to immediately diverge from actual site conditions. Consequently, project teams only discover cascading delays during weekly coordination meetings, making adjustments retroactive and forcing trades into compounding bottlenecks.

This problem is addressable today because multimodal AI and computer vision have crossed a critical cost and accuracy threshold. Rather than relying on human reporting, modern vision models can ingest unstructured, ambient site data from standard smartphone photos or hardhat cameras to automatically verify trade progress. This structural shift eliminates the data entry bottleneck that doomed previous scheduling tools, allowing master timelines to sync with field reality continuously.

## Problem Current Solutions

**Status Quo**: Site superintendents maintain master schedules using static models, typically waiting until weekly coordination meetings to manually reconcile field delays and push dependent subcontractor timelines backward.
**Workarounds**:
- whiteboard updates in trailer
- subcontractor group text threads
- spreadsheet exports for look-aheads
- retroactive schedule patching
**Named Tools In Use**:
- [Oracle Primavera P6](/Products/Oracle_Primavera_P6)
- [Microsoft Project](/Products/Microsoft_Project)
- [Procore](/Products/Procore)
- [Smartsheet](/Products/Smartsheet)
**Why Insufficient**: Current scheduling software relies on manual data entry from field personnel lacking administrative bandwidth, ensuring the master schedule always lags behind site reality. These static tools act as historical ledgers rather than dynamic models capable of instantly recalculating critical paths based on real-time field conditions.

## Problem Market Profile

**Incumbents**:
- [Oracle Primavera P6](/Problems/Reactive_Site_Scheduling/Competitors/Oracle_Primavera_P6)
- [Microsoft Project](/Problems/Reactive_Site_Scheduling/Competitors/Microsoft_Project)
- [Procore](/Problems/Reactive_Site_Scheduling/Competitors/Procore)
- [Smartsheet](/Problems/Reactive_Site_Scheduling/Competitors/Smartsheet)
- [Autodesk Build](/Problems/Reactive_Site_Scheduling/Competitors/Autodesk_Build)
**Substitutes**:
- Whiteboard updates in site trailers
- Subcontractor group text threads
- Spreadsheet exports for look-ahead planning
- Retroactive schedule patching during weekly meetings
**Position Axes**:
- Update Automation (Manual Entry vs. Automated Telemetry)
- User Focus (Back-Office Planners vs. Field Superintendents)
**Market Dynamics**: The scheduling market is consolidating into broader construction management platforms, moving away from standalone critical path software. Simultaneously, the space is seeing attempts to use computer vision and natural language processing to extract progress data from site photos and daily logs to feed legacy scheduling engines.
**Competition Concentration**: Incumbents like Oracle Primavera P6 and Microsoft Project cluster heavily in the manual, back-office quadrant, demanding dedicated administrative personnel to maintain complex static models. Substitutes such as trailer whiteboards and group texts dominate the manual, field-centric quadrant due to their immediate accessibility for superintendents. The quadrant representing automated telemetry combined with field-centric usability remains distinctly sparse, as most existing software still relies on retroactive human data entry to advance the timeline.

## Mint Vocabulary Bag

**Action Verbs**:
- sequence
- allocate
- dispatch
- synchronize
- preload
**Gerund Stems**:
- sequenc
- allocat
- dispatch
- level
**Abstract Nouns**:
- latency
- bottleneck
- slack
- throughput
- backlog
**Concrete Nouns**:
- rebar
- girder
- scaffold
- foreman
- transit
- conduit
**Metaphor Nouns**:
- fulcrum
- cadence
- relay
- pylon
- beacon
**Structure Nouns**:
- docket
- roster
- matrix
- grid
- queue

## Problem Candidate Solutions

- [Clarent](/Problems/Reactive_Site_Scheduling/Startups/Clarent) — Agent
- [Matrixgirder](/Problems/Reactive_Site_Scheduling/Startups/Matrixgirder) — Service-as-Software
- [Docketfire](/Problems/Reactive_Site_Scheduling/Startups/Docketfire) — Software
- [Phyvis](/Problems/Reactive_Site_Scheduling/Startups/Phyvis) — Agent
- [Gridansit](/Problems/Reactive_Site_Scheduling/Startups/Gridansit) — Service-as-Software
- [Relaydome](/Problems/Reactive_Site_Scheduling/Startups/Relaydome) — Software

## Problem Solution Space2x2

```mermaid
quadrantChart
title Reactive Site Scheduling Solutions
x-axis Static Allocation --> Dynamic Auto-routing
y-axis Macro (Project Level) --> Micro (Task/Worker Level)
Clarent: [0.3, 0.7]
Matrixgirder: [0.2, 0.3]
Docketfire: [0.8, 0.4]
Phyvis: [0.6, 0.8]
Gridansit: [0.9, 0.9]
Relaydome: [0.5, 0.2]
```

## Problem Affected Roles

- Construction Project Manager — Project Planning
- Site Superintendent — Field Operations
- Lead Project Scheduler — Project Controls
- Subcontractor Foreman — Trade Execution
- Materials Coordinator — Supply Chain
- Site Supervisor — Site Management
- Director Of Operations — Executive Leadership

## Problem Affected Processes

- Subcontractor Coordination — Trade Sequencing
- Material Logistics Planning — Supply Chain
- Equipment Fleet Allocation — Resource Management
- Progress Billing Verification — Finance
- Critical Path Analysis — Risk Management
- Daily Field Reporting — Site Operations
- Change Order Valuation — Contract Administration

## Problem Matching Opportunities

- Predictive Schedule Routing for Contractors — AI Agent
- Autonomous Dispatch for Field Crews — Workflow Automation
- Dynamic Capacity Planning for Builders — Predictive SaaS
- Automated Delay Mitigation for Subcontractors — Optimization Engine
- Algorithmic Material Sequencing for Sites — Supply Chain AI

## Problem Token Hero

**Genre**: problem-hero
**Rendered**: Construction project managers and site superintendents build master schedules using idealized timelines that rarely survive contact with the field.
**Mechanism**: overview-derived-v1
**Template Id**: problem-overview-derived
**Vocab Fingerprint**: 6dd4b77151511830

## Neighborhood

### Who addresses this

- [Clarent](/Startups/Clarent) — addresses · Startups

### Who exposes this

- [Construction Managers](/CompanyTypes/Construction_Managers) — exposes problem · CompanyTypes

### Competitors

- [Autodesk Build](/Competitors/Autodesk_Build) — competes with · Competitors
- [Smartsheet](/Competitors/Smartsheet) — competes with · Competitors
- [Procore](/Competitors/Procore) — competes with · Competitors
- [Oracle Primavera P6](/Competitors/Oracle_Primavera_P6) — competes with · Competitors
- [Microsoft Project](/Competitors/Microsoft_Project) — competes with · Competitors

### What it's used for

- [Smartsheet](/Software/Smartsheet) — used for · Software
- [Microsoft Project](/Products/Microsoft_Project) — used for · Products
- [Oracle Primavera P6](/Products/Oracle_Primavera_P6) — used for · Products
- [Procore](/Software/Procore) — used for · Software

### Solves problem

- [Gridansit](/Startups/Gridansit) — candidate solution for · Startups
- [Docketfire](/Startups/Docketfire) — candidate solution for · Startups
- [Relaydome](/Startups/Relaydome) — candidate solution for · Startups
- [Phyvis](/Startups/Phyvis) — candidate solution for · Startups
- [Matrixgirder](/Startups/Matrixgirder) — candidate solution for · Startups

### Entails child problem

- [Critical Path Recalculation](/Problems/Critical_Path_Recalculation) — entails child problem · Problems
- [Daily Log Ingestion](/Problems/Daily_Log_Ingestion) — entails child problem · Problems
- [Field Progress Verification](/Problems/Field_Progress_Verification) — entails child problem · Problems
- [Look-Ahead Planning](/Problems/Look-Ahead_Planning) — entails child problem · Problems
- [Material Delivery Tracking](/Problems/Material_Delivery_Tracking) — entails child problem · Problems
- [Subcontractor Coordination](/Problems/Subcontractor_Coordination) — entails child problem · Problems

### Similar Problems

- [Sequence Subcontractor Schedules](/Problems/Sequence_Subcontractor_Schedules) — similar · Problems
- [Jobsite Subcontractor Coordination](/Problems/Jobsite_Subcontractor_Coordination) — similar · Problems
- [Coordinate Subcontractor Schedules](/Industries/Construction/Problems/Coordinate_Subcontractor_Schedules) — similar · Problems
- [Coordinating Subcontractor Schedules](/CompanyTypes/General_Contractor/Problems/Coordinating_Subcontractor_Schedules) — similar · Problems
- [Subcontractor Schedule Sequencing](/Problems/Subcontractor_Schedule_Sequencing) — similar · Problems
- [Subcontractor Schedule Clashes](/Problems/Subcontractor_Schedule_Clashes) — similar · Problems
- [Material Delivery Schedule Drifts](/Occupations/Construction_and_Extraction_Occupations/Problems/Material_Delivery_Schedule_Drifts) — similar · Problems
- [Site Material Delivery Delays](/Industries/Construction/Problems/Site_Material_Delivery_Delays) — similar · Problems
- [Weather-Induced Schedule Delays](/Problems/Weather-Induced_Schedule_Delays) — similar · Problems
- [Subcontractor Performance Tracking](/Industries/Construction/Problems/Subcontractor_Performance_Tracking) — similar · Problems
- [Jobsite Material Delivery Coordination](/Problems/Jobsite_Material_Delivery_Coordination) — similar · Problems
- [Material Delivery Synchronization](/Skills/Coordination/Problems/Material_Delivery_Synchronization) — similar · Problems
- [Prevent Costly Project Rework](/Problems/Prevent_Costly_Project_Rework) — similar · Problems
- [Production Schedule Overruns](/Problems/Production_Schedule_Overruns) — similar · Problems
- [Crew Scheduling Conflicts](/CompanyTypes/Commercial_Roofing_Contractor/Problems/Crew_Scheduling_Conflicts) — similar · Problems
- [Site Readiness Verification](/Problems/Site_Readiness_Verification) — similar · Problems
- [Site Commissioning Overruns](/Problems/Site_Commissioning_Overruns) — similar · Problems

### Similar Metrics

- [Construction Cycle Time](/Metrics/Construction_Cycle_Time) — similar · Metrics