Real Estate & Construction

Construction Project Controls Copilot

Designed for Project manager

Give the construction project manager one grounded control surface across schedule, cost, RFIs, submittals and change orders so schedule slip and cost exposure are explained by the contract documents and the daily field record rather than reconstructed in a spreadsheet before each owner meeting.

Contract REA-02 · primary aggregate ConstructionProject · mode loading

Decision brief

Project manager approval and change order submission: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Project manager

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

On a 74 million dollar hospital expansion, the March schedule update shows the mechanical rough-in activity losing 11 days of float and pushing substantial completion from 14 November to 2 December.

Decision to make

Give the construction project manager one grounded control surface across schedule, cost, RFIs, submittals and change orders so schedule slip and cost exposure are explained by the contract documents and the daily field record rather than reconstructed in a spreadsheet before each owner meeting.

Outcome to show

submittedChangeOrder gives Project manager the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Schedule and cost update ingestion
  2. 2Slip and variance attribution
  3. 3Contract entitlement grounding
  4. 4Owner narrative drafting
  5. 5Project manager approval and change order submission

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Project manager verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved ConstructionProject evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Give the construction project manager one grounded control surface across schedule, cost, RFIs, submittals and change orders so schedule slip and cost exposure are explained by the contract documents and the daily field record rather than reconstructed in a spreadsheet before each owner meeting.
Primary aggregate
ConstructionProject
Primary container
constructionProjects
Hierarchical key
/tenantId + /projectId
Schema version
1

Sample scenario

On a 74 million dollar hospital expansion, the March schedule update shows the mechanical rough-in activity losing 11 days of float and pushing substantial completion from 14 November to 2 December. The copilot attributes 7 days to RFI 214, an unanswered ceiling-clearance conflict with the ball in the architect's court for 23 days, and 4 days to a concrete pour resequenced after a differing-site condition. It cites the prime contract clause granting a time extension for owner-caused delay and the 14-day notice requirement, and shows a 310,000 dollar pending change on the mechanical cost code. The project manager approves the narrative and submits the change order with the RFI log and float analysis attached.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
constructionProjects Primary /tenantId + /projectId Project, ScheduleActivity, CostCommitment, ContractDocChunk, ProjectIssue, ControlsNarrative

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Project constructionProjects /tenantId + /projectId project::{projectId} None
ScheduleActivity constructionProjects /tenantId + /projectId project::{projectId}::activity::{activityId}::update::{scheduleUpdateId} None
CostCommitment constructionProjects /tenantId + /projectId project::{projectId}::cost::{costCode}::{periodEndUtc} None
ContractDocChunk constructionProjects /tenantId + /projectId project::{projectId}::contract::{docId}::{chunkOrdinal} chunkVector
ProjectIssue constructionProjects /tenantId + /projectId project::{projectId}::issue::{issueKind}::{issueNumber} subjectVector
ControlsNarrative constructionProjects /tenantId + /projectId project::{projectId}::narrative::{periodEndUtc}::{narrativeId} narrativeVector

Query patterns