Change orders & events

The job pressure

Changes float as email threads until someone manually patches the budget.

Commercial and Homebuilder change paths

On the job

Changes should not float in email until someone patches the budget by hand. EstiLumina logs a change event with ROM and scope, closes it into a seeded change order, and on approval updates contract value and budget lines together.

Pay applications can seed the next period from that approved CO. Job Run hints the next step so the PM is not hunting which tab owns the money.

That is how change stays on the same spine as the locked estimate — not a side spreadsheet.

How it works

1. 1

   Log a change event with ROM and scope notes.

2. 2

   Close the event into a seeded change order.

3. 3

   Approve the CO to update contract and budget lines.

4. 4

   Pay applications pick up the CO seed on the next draw.

What you get

• Change events → CO one-path close
• ROM seed totals on the CO
• Approve updates contract value + budget
• Clear next step after approval
• Feeds pay application CO seed

Why teams subscribe

• Change events close into a seeded CO in one path
• Approval updates contract value and budget together
• Next pay application can seed from the approved CO

Honest boundaries

• Not automatic owner approval without a human sign-off.
• Not a claim of specific owner form numbers you may not use.