Design change and site impact coordination

The business situation

Illustrative reference architecture. Validate requirements for your organization.

Illustrative architecture: A commercial building project receives a revised mechanical layout after installation has begun. The contractor needs to identify affected work packages, material orders, and coordination questions. Agents prepare change evidence and scenarios; licensed designers and authorized project managers retain technical and commercial decisions.

Problem

Drawings, building models, requests for information, and purchase orders use different identifiers and revision conventions. A generated summary can overlook installed work or treat an unapproved sketch as the governing design, creating rework and contractual confusion.

Why a multi-agent system?

Revision, quantity, schedule, and procurement specialists examine distinct dependencies. Model comparison and quantity calculation services provide deterministic evidence while agents draft questions and explain bounded schedule scenarios.

Intended outcome

The intended result is a reviewable operational decision with source evidence and explicit ownership. Evaluate review preparation and missed dependencies before claiming reduced project delay. Construction outcomes depend on design resolution, site execution, and commercial agreement; the agent system should expose those dependencies rather than obscure them.

Specialist agent team

Revision investigator

Compare approved drawing and model revisions and identify changed elements.

Tools

• Common data environment
• model diff service

Authority boundary

Cannot approve design changes or treat draft drawings as issued instructions.

Quantity impact agent

Map changed elements to measured quantities and installed-work records.

Tools

• Quantity takeoff service
• site progress reader

Authority boundary

Cannot certify payment quantities or structural adequacy.

Sequence planner

Evaluate work-package dependencies and access conflicts around the change.

Tools

• Schedule simulator
• work breakdown query

Authority boundary

Cannot authorize unsafe sequencing or alter the contractual baseline.

Commercial evidence agent

Retrieve affected orders and draft requests for clarification or change review.

Tools

• Procurement read API
• change-event draft tool

Authority boundary

Cannot accept claims, agree prices, or issue subcontract instructions.

Enterprise systems

Common data environment

Controls model and drawing revisions, issue status, and project permissions.

Project controls platform

Owns schedules, work packages, progress evidence, and authorized change records.

Procurement and site systems

Provide committed orders, installation observations, and accountable field confirmations.

Architecture diagrams

flowchart LR
    N0["Design change and site impact coordination"]
    N1["Revision investigator"]
    N2["Quantity impact agent"]
    N3["Sequence planner"]
    N4["Commercial evidence agent"]
    N5["Evidence ledger"]
    N6["Human decision"]
    N7["Authorized adapter"]
N0 --> N1
    N1 --> N2
    N2 --> N3
    N1 --> N4
    N3 --> N4
    N4 --> N5
    N5 --> N6
    N6 --> N7

sequenceDiagram
    participant O as "Case orchestrator"
    participant S as "Common data environment"
    participant H as "Accountable reviewer"
O->>S: Verify drawing issue status
    S-->>O: Revision remains draft
    O->>H: Block instruction and request design clarification
    H-->>O: Supply approved issued revision
    O->>S: Register governed change evidence

Runtime flow

1. 1

   Register issued revision

   Verify the document's issue status, project scope, and superseded revision before opening a change investigation.

2. 2

   Compare design elements

   Run governed model or drawing comparisons and retain element identifiers and view references for human inspection.

3. 3

   Map physical progress

   Join changed elements to installed quantities and active work packages, flagging unverified site reports.

4. 4

   Evaluate consequences

   Calculate quantity deltas and bounded schedule scenarios, separating confirmed procurement commitments from estimates.

5. 5

   Prepare coordinated review

   Present design questions, site conflicts, affected orders, and scenario assumptions to design and project-control owners.

6. 6

   Publish authorized actions

   Record approved instructions through established project channels and track acknowledgement by each affected subcontractor or supplier.

Failure recovery

Security & decision boundaries

• Require issued-document status and revision lineage before treating design information as authoritative.
• Preserve licensed designer approval for technical design and safety decisions.
• Keep contract notices and commercial commitments behind project-manager authorization.
• Record quantity units and model element identifiers for every calculated delta.
• Enforce project and subcontract access boundaries in drawings and cost records.

Operational metrics

Measurement definitions, not promised improvements.

Impact packet latency

Time from accepted revision to a coordinated review packet with affected work references.

Element traceability

Reported impacts linked to governed model or drawing elements divided by reported impacts.

Field verification coverage

Affected installed-work items supported by current verified site evidence divided by affected installed items.

Acknowledgement completeness

Approved instructions acknowledged by every required recipient divided by issued instruction sets.

Architecture tradeoffs

Rollout plan

Completed revision replay

Project teams verify issued status, element mapping, quantity units, and installed-work contradictions.

Shadow project pilot

One work package receives draft impact packets without contractual instructions or baseline changes.

Controlled change integration

Approved actions enter existing registers after superseded-document and missing-acknowledgement tests pass.

Connected concepts

• 2 — Directed Acyclic Graphs (DAGs)
• 28 — Deterministic Data Grounding
• 30 — Non-Repudiation Logs
• 38 — Data Lineage Tracking
• 44 — Human-in-the-Loop (HITL)
• 58 — Partial Success Management
• 67 — Graph RAG / Knowledge Graphs

Primary references

• CloudEvents specification project
• Temporal: Workflow execution
• NIST SP 800-207: Zero Trust Architecture