SiteRep WorksSiteRep Works

Change Register

Private Beta

Potential changes rarely start as clean change orders.

They start as an email, an RFI, a field conversation, a COR, an ASI, a meeting note, a pricing request, or an unexpected condition.

Change Register exists to capture that potential exposure early and maintain the evidence trail until the issue is resolved.

Request Beta AccessVisit Change Register →

The problem

The history of a change is scattered.

Potential changes and the information that supports them live across inboxes, spreadsheets, meeting minutes, RFI logs, and conversations in the field. By the time a change needs to be priced or defended, the team is reconstructing what happened weeks or months later — and some exposure never gets captured at all.

The workflow

Capture → Evidence → Exposure → Updates → Resolution

  1. 01Capture potential issue→
  2. 02Connect supporting evidence→
  3. 03Track cost exposure→
  4. 04Track updates and revisions→
  5. 05Resolve or advance into the formal change process

What the team can track

  • Potential change items
  • Estimated exposure
  • Supporting evidence
  • CORs
  • RFIs
  • ASIs
  • Emails / correspondence
  • Revisions
  • Related documentation
  • Current status
  • Resolution

Who it is for

  • Project Managers
  • Assistant Project Managers
  • Project Engineers
  • Project Executives
  • Project Controls
  • Commercial / Financial project teams

Private Beta

SiteRep Works is currently selecting construction teams to test Change Register against real project change-management workflows.

We're looking for construction teams willing to put SiteRep through real-world workflows, challenge our assumptions, and help shape what comes next.

Request Beta Access