Catch missed scope changes before they become lost revenue.
ScopeSignal is being developed to compare the communications where work actually gets requested against your formal change-order register — bringing overlooked changes and their supporting evidence into view for human review.
Project
Documents reviewed
1,284
this project
Potential changes detected
17
across sources
Items requiring review
6
flagged
Additional electrical conduit requested
Source: RFI-042 and follow-up email
No corresponding entry found in the uploaded change-order register.
Source record
RFI-042 · May 14
“…please run additional conduit to the east riser per the revised panel schedule…”
Related CO entries
0 matches found
Reviewer status: Open · assigned to PM
A simple path from scattered records to clear findings.
Bring project records together
Upload permitted emails, RFIs, and change-order registers. ScopeSignal is designed to work with the records you already produce — no new field process to adopt.
Identify potential changes
AI-assisted analysis looks for instructions that may indicate work outside the originally documented scope — the kind of request that often starts in an email before it reaches the log.
Reconcile with existing logs
Identified events are compared against your recorded change orders so you can see where a potential change may not have a matching formal entry.
Review supporting evidence
Each potential finding is presented with the source records behind it, so a project manager can quickly judge whether it's worth pursuing.
Every finding, traceable to its source.
ScopeSignal is designed so that no potential change is a black box. Each flagged item is intended to show the records it came from and how it compares to what's already logged — so the decision stays with your team.
Additional electrical conduit requested
Finding #SS-1042
RFI-042 · May 14
“…please run additional conduit to the east riser per the revised panel schedule…”
0 matching entries
No corresponding entry found in the uploaded register.
What ScopeSignal is — and isn't.
We think clarity builds trust. Here's how we think about the boundaries of the product.
Designed to
- Surface potential scope changes that may be missing from your change-order register
- Link each finding back to the source email, RFI, or field record
- Help standardize how teams review potential omissions across projects
Not intended to
- Decide whether work is contractually billable or entitled
- Replace your project-management or accounting system
- Submit change orders or make commercial decisions on your behalf
The project team remains responsible for verifying scope, contractual entitlement, notice requirements, and submission decisions.
Curious whether this fits your projects?
We're exploring pilots with US commercial subcontractors.