← Solution examplesConstruction example · Project Management ↔ ERP

Change Order Exposure Control

Field operations know what changed. Accounting knows what was booked. We connect the two so management knows what is actually at risk.

solution / change-order-exposure

Engineering blueprint

LAYER 01Existing systemsIntegrated, not replaced

Project managementERP / job costEstimatingDocument mgmtBilling

LAYER 02Governed project dataCanonical, with lineage

Change EventsCommitmentsOwner changesInvoices

LAYER 03KBSIntel change-control layerState & orchestration

Change Event engineApproval trackingException queues

LAYER 04Decisions & intelligenceBuilt on governed data

Exposure by projectMargin leakageChange aging

Problem

Changes start in the field and get committed long before owner revenue is approved. The trail runs through project management, email, subcontractor quotes, ERP, and billing, and nobody owns it end to end.

Example

An RFI is marked cost-impacting. A subcontractor prices it and starts work. The owner change is still pending, nothing is in ERP, and the job looks on budget.

Governed object · Change Event

RFI
Field condition
Drawing revision
Subcontractor quote
Potential change order
Commitment
Owner change
ERP posting
Billing
Collection

Where the systems disagree

Unrecovered exposure
Approved, not posted
Cost over approval
Work before approval
Unpriced RFI
Approved, not billed

State model

DISCOVERED
PRICING_REQUESTED
PRICED
INTERNAL_REVIEW
OWNER_PENDING
OWNER_APPROVED
COMMITMENT_ISSUED
ERP_POSTED
BILLED
COLLECTED

What we build

A change-control layer between project management and accounting. Field and office keep their tools.

Change Event model linking field, cost, and revenue
Project management, ERP, and billing integration
State tracking from discovery to collection
Duplicate change-event detection
Exposure alerts and exception queues

Controls

Flag cost exposure with no owner revenue
Flag approved changes not posted to ERP
Flag work started before approval
Route unpriced RFIs to estimating

Intelligence

Unresolved exposure by project
Margin leakage trends
Change aging and approval cycle time
Recurring sources of change

What we'd measure

Cost exposure without approved revenue
Change-event aging by state
Approved changes not yet billed
Time from discovery to owner approval

Start with one problem. Engineer the right solution.

Manual work, systems that don't talk, data nobody trusts. We trace it to the source and ship the fix into production.