Change-order system of record

One change.
One record.

Resolve replaces the owner log, the notification log, and the sub log — three versions of the same change, kept honest by hand — with a single record that everything else is derived from. Built by a project engineer who runs this exact workflow, by hand, on a live public hospital job.

Go to Resolve See how it works

Richmond, Virginia — taking one design-partner pilot now

The problem

One change. Three logs.
Synced by hand.

Most change-order tools track the same change in at least three separate places — and each one carries its own status that somebody has to remember to update. Nothing keeps them honest with each other. The failure is never dramatic. It's drift: a status that never got updated, a trade nobody actually notified, a deadline that silently moved for everyone.

98%of GCs have lost fee negotiating change orders — nearly half by more than 10% of fee on some jobs
93%have had project closeout delayed by change-order issues; two-thirds by over a month
72%still manage change-order requests primarily in spreadsheets or over email
20%say they can clearly see the status of unsolicited changes and T&M exposure

Industry-wide, rework and delay — largely change-driven — costs US construction roughly $177 billion a year, about 5% of all construction spending.

Source: 2026 GC change-order industry research

The idea

Keep one record.
Calculate everything else.

Resolve stores a change once. Provenance, classification, stage, trades, pricing, and the owner package all hang off that single record — and every status anyone sees is derived from it, not typed in separately. There is nothing to keep in sync, because there is nothing duplicated.

1

Intake

Drag in the bulletin or RFI, or key it in by hand. Reference, scope, and dates land already populated.

2

Notify

One notification per change, trades you pick, the pricing-due date written into the email and the record at the same time.

3

Price

Subs submit against their own line. Quotes supersede, T&M tickets accumulate. Nothing overwrites.

4

Package

Assemble the owner's authorization package from what is already in the record — no re-keying.

5

Close

Owner decision recorded, subcontract change orders issued, costs exported to your ERP.

The daily driver

The front page isn't a log.
It's a ranking.

Most tools give you a list and let you work out what matters. Resolve opens on the changes aging past where they should be, ordered by how much money is sitting in them — red and amber before they become a problem.

My Desk — ranked by urgencySample data
Red Bulletin 077 · Level 3 headwall rework18 days in CN Sent · 3 of 7 priced $214,880
Red RFI 1770 · Chilled water reroute12 days in Pricing Received $96,400
Amber Bulletin 081 · Nurse call revisions9 days in CN Sent · 2 trades not notified $41,250
On track Bulletin 074 · Roof curb additions4 days in ATP Submitted $132,000

Illustrative — fictional demo data

For your subcontractors

Free accounts, forever.

One page. Their line, their submissions, and the real stage of the change — nothing else. Subs complain loudly about a bad GC portal. Yours will be the one they don't.

What they see

  • Every change they're on, ranked by what you need from them next
  • Their own line, their own price history, their own T&M tickets
  • Scope documents you've put in the shared zone
  • The real stage — including when it's with the owner
  • A one-click "no cost impact to my scope"

What they never see

  • Your ROM — ever
  • Any other firm's price, or that any other firm exists
  • The authorization package or the owner's response
  • Internal-zone attachments and internal-only changes
  • A line they haven't actually been notified about

Who built this

Not a software company.
A project engineer.

The workflow is real, not invented. Resolve is modeled directly on the bulletin-to-SCO process our founder runs by hand on a $300M+ publicly owned hospital project in Richmond. It was built and tested end-to-end against that exact process.

Built because it was needed. Every screen exists because something went wrong without it — a status nobody updated, a trade nobody actually notified, a deadline that quietly reset for everyone but the one firm being chased.

Almost no construction software is built by someone who has to live with it on Monday morning. This one was. It just hasn't run a live project yet — that's exactly what the pilot below is for.

~19,000
lines of Java & front-end code
201
automated tests
1
real workflow it's modeled on
0
production hours — changes with one pilot

Built like it matters

Real security, not a spreadsheet with a password on it.

The kind of questions an IT or procurement reviewer actually asks — answered plainly.

Authentication

Real login security

Form login with hashed passwords and server-side sessions that are invalidated on logout. Three enforced roles gate exactly what each user can see.

Data isolation

Firm-scoped by design

Every subcontractor-facing request is checked against the requesting firm's own ID — not just "is this a sub," but "does this sub's firm own this data."

Audit trail

An honest record

Every state-changing action writes an append-only event with the actor's identity and a timestamp — the audit trail a change-order dispute actually needs.

Storage

A real database

A managed PostgreSQL database, not a local file or a shared spreadsheet. Uploaded documents are extension-validated and stored in cloud object storage.

Injection risk

No raw SQL, anywhere

All data access goes through parameterized queries. There is no string-concatenated SQL in the codebase for an injection to exploit.

Secrets

Nothing hardcoded

Credentials and keys are read from environment configuration, not committed to source — the correct pattern for keeping secrets out of a codebase.

Where it fits

Keep Procore.
Keep your ERP.

Resolve isn't a project management platform, and it isn't accounting. It owns the middle — the part where a change is priced, chased, packaged, and defended.

Documents

Procore · Autodesk Build · Newforma · Outlook

→

Resolve

Intake · notification · pricing · authorization package · audit trail

→

Cost & accounting

CMiC · Sage · Viewpoint · Vista

The offer

One project. Ninety days. Free.

We're looking for one design partner in Richmond — not a customer yet. Both sides commit to something.

What you get

  • Ninety days free — one project, unlimited people at your firm
  • Free subcontractor accounts, with no expiry
  • Hands-on setup: project, trade list, and invitations done for you
  • A weekly half hour, in person, for as long as the pilot runs
  • Your requests jump the queue — something ships every week
  • Full data export any day; deletion on request

What we ask for

  • A named champion with two hours a week
  • One real, active project — not a test job
  • A short baseline survey on day one
  • Honest answers at day 45 and day 90
  • If it works: a written case study and a reference call
Go to Resolve Ask about the pilot