Contracts & Billing — Overview

A full workflow for getting a project from estimate to signed contract to invoiced work — with every scope and dollar change after the signature kept honest and auditable.

What's New

Four connected features make up the Contracts & Billing flow:

• Project versioning — every project is a stack of versions. Each version is a snapshot of the rooms, line items, and pricing as of a point in time.
• Signed contracts — approving a saved estimate freezes that version as the Contract. The signed amount is now a fixed reference point.
• Change orders — once a contract exists, any scope or dollar change happens through a Change Order, not by editing the contract.
• Contract-baseline invoicing — invoices bill against the Contract and any Approved Change Orders. The numbers always tie back to something the customer signed.

Why It Matters

The whole point is to keep the signed amount honest. Before this flow, a project's price could quietly drift as line items were edited after the customer agreed to a number. With contracts and change orders, the original signed amount stays put — anything that moves the dollar total has its own paper trail.

For billing, invoices now follow the contract instead of the live project. You bill against what was agreed, and the system tracks how much of the Contract (and each approved Change Order) has already been billed.

Reading Order

If this is your first time here, read the sections in order — each one builds on the last. If you already know the flow and just need a refresher on one piece, jump straight to it:

• Versions & Approval — what a version is, how to approve an estimate
• Change Orders — drafting, submitting, approving, voiding
• Invoicing — billing against the contract baseline
• Voiding & Re-approving — what happens when an approval has to come back
• State Indicators — the badges, pills, and banners that tell you where a project stands