Change Order Management
By Phazahn Odom | Founder of Phixmo | Former bookkeeper for residential GCs | Former NFL tight end, Pittsburgh Steelers
After years of doing the books for residential GCs, I can tell you the single biggest margin killer: undocumented change orders. The homeowner asks for something extra. Your crew does it. Nobody writes it up. That's $200 to $500 gone. Multiply it by 10 to 15 small requests across a $200k project and you've lost $3,000 to $7,500 in work you did for free.
Phixmo's change order workflow solves this by making approval mandatory before invoicing. The customer reviews the scope and cost, then approves or requests changes. No approval, no invoice, no free work.
Four steps from creation to invoicing. The customer reviews via portal or email, you can't invoice until they approve, and every step is timestamped and signed.
When the scope changes (customer request, unforeseen condition, design change), you create a change order in Phixmo with a description and amount. Takes 2 minutes.
Click 'Send to Customer.' Phixmo sends a branded email with the change order details. If the portal is active, the email links to the portal. If not, the email includes approve/request changes buttons directly.
If approved, the change order status updates with a timestamp and the approver's email. If the customer requests changes, they type their feedback and the status updates so you can revise and resend.
Only approved change orders can be invoiced. Phixmo enforces this in the system. If you try to create an invoice from an unapproved change order, you'll see a warning.
Three real-world scenarios that almost every residential contractor has lived through. Each one leaks margin in a different way.
The homeowner walks the job, points at the wall, and says 'while you're at it, can we move that outlet over here?' The crew lead says 'sure, no problem.' Nobody writes it down. Three weeks later the work is done and there's no record of anyone agreeing to anything, no price quoted, no way to bill for it. That outlet just cost you $300.
You text the homeowner 'extra recessed light in the kitchen will be $250, ok?' and they reply 'yes thanks.' That's better than verbal, but six weeks later when you try to include it on the final invoice, the text is buried in a 400-message thread and the homeowner argues they don't remember agreeing to that price. You either eat it or have an uncomfortable call. Either way the documentation isn't actually built for billing.
You're a good operator, you intend to write up every change. But it's Tuesday night, you've been on site for 14 hours, and you have three other change orders to write. The kitchen drawer pull upgrade gets pushed to tomorrow. Tomorrow it gets pushed to next week. By the time you remember, the work is done and you can't credibly send a change order for completed work. Margin gone.
The same email works whether or not the customer uses the portal. Two paths to approval, one clean inbox experience.
Email layout
If the customer has a portal account, the email link drops them onto the portal change order page where they can review and approve in context. If they don't have a portal account (or just want to handle it from email), the email itself has inline Approve and Request Changes buttons that take them to a single-page signing flow. Either path produces the same signed, timestamped approval on your side.
The whole experience is built for someone reading email on their phone between meetings. They can approve a $400 change order in under 30 seconds. The faster you make the approval, the more change orders actually get approved.
Three places the change order workflow turns into real dollars on the balance sheet, not just better record-keeping.
Every change order is timestamped and signed. The homeowner can't claim they didn't approve it because the system has the email, the click, and the IP address. That documentation is what protects you when a dispute happens after the project is closed.
When a change order is approved, the project budget updates automatically. The new revenue is added to the contract value. Any added cost flows into job costing. Your margin views always reflect the current scope, not the original estimate, so you never look at outdated numbers.
This is the rule that does the most work. Phixmo blocks invoicing on work tied to an unapproved change order. You can't accidentally bill for it, you can't skip the approval step to save time. The system forces the right behavior even on the days when you're slammed.
A worked example for a typical residential remodel. The numbers add up faster than most contractors expect.
The project
Without documented change orders
With Phixmo change orders
36 minutes of documentation per project turns a 9% margin job back into a 12% margin job. Across 10 jobs a year, that's $54,000 back on the bottom line.
Change order management is included on every Phixmo plan, including Free. No add-on, no per-change-order fee.
Free
$0/mo
Free forever. Unlimited projects, field workers free.
2 office seats
+ unlimited free field workers
+ change order workflow included
Pro
$169/mo
Growing GCs with active teams.
5 office seats
+ unlimited free field workers
+ change order workflow included
Growth
$299/mo
Larger operations.
10 office seats + $25/extra
+ unlimited free field workers
+ change order workflow included
Phixmo sends an automatic reminder 48 hours after the change order goes out if there's no response, and another reminder at 5 days. You can also resend manually from the change order screen with a custom note. Most approvals come back within 24 hours because the customer wants the work to continue.
Yes. If the customer requests changes (or you just want to update the scope or cost), you can edit and resend. The customer sees the new version with the updated details and approves the revised change order from the same email or portal link.
No. The customer can approve directly from the email link without ever creating an account. If they do have a portal account (which we recommend for repeat customers), they see all pending change orders together on their dashboard. Either path produces a signed, timestamped approval.
Yes. A project can have any number of pending and approved change orders. Pending ones sit at the top of the project view and the customer portal. Approved ones are listed below with dates, amounts, and approval signatures. The project budget reflects all approved change orders combined.
Yes. Attach jobsite photos showing the condition that triggered the change, vendor quotes for added materials, or any supporting document. The customer sees attachments alongside the description when they review.
Declined and revised change orders stay in the project history with their status and any customer notes about what they wanted different. You have a complete record of the conversation even when the customer doesn't approve the first version.