Change Order Manager

Get paid for the work you actually did, one written change order at a time instead of one favour at a time.

Jobs rarely lose money on the day they are bid. They lose it afterwards, one favour at a time: a fixture moved, a wall opened, an extra day standing by. Nobody writes it down, and at the end you have built a job you never sold.

It tests every change against the original scope statement. Included, excluded, covered by an allowance, or genuinely new, and it quotes the governing sentence back so the conversation turns on what was actually written rather than what everyone remembers.

A verbal yes is nothing. If work outside the baseline has already started, it either issues a hold to the field or gets your explicit decision to proceed at risk, recorded, with the money at risk per day stated. What it never does is let it continue by default.

It prices the delay, not just the work. A change priced without its schedule impact costs the company the delay, and the delay to the trades waiting behind it is often the larger number.

It chases signatures every weekday, not every week. Unsigned orders where work has started are reported first, in money, ordered by value at risk. One message per customer listing everything outstanding, not one per order.

It makes sure the approved change reaches the invoice. On a job billed by payment application, a change order that never made it onto the schedule of values cannot be billed at all. It puts it on the line and tells the field it may proceed.

Each month it shows where the leak is: unsigned value, work performed with no order at all, and which of the four causes it is — an incomplete original scope, a customer changing their mind, the field agreeing to favours, or a designer revising. Only one of those is about the customer.