When should a contractor use this pricing example?
Use this example when a contractor needs to see how pricing backup can support a change order request.
Change Order Pricing Example
Use this change order pricing example to see how a contractor can document labor, materials, subcontractor costs, markup, total price, and schedule impact.
When to use this
Use this example when a contractor needs to see how pricing backup can support a change order request.
It shows the difference between internal cost backup and the final client-facing change order price.
What to document
- Changed scope being priced and reason for the change.
- Labor hours, materials, equipment, subcontractors, delivery, disposal, and permits.
- Markup, overhead, tax if applicable, total price, and schedule impact.
- Attachments used as backup for the price.
- Client-facing price tied to the approval request.
Filled pricing example fields
Use this example as a model for documenting the basis of a change order price.
Example scope
Changed scope: Add recessed lighting in living room
Reason: Owner requested six additional fixtures after ceiling layout review
Attachments: Fixture spec, electrician note, ceiling photo
Example cost backup
Labor: 8 hours x $85 = $680
Materials: $420
Subcontractor: $0
Permit/coordination/disposal: $95
Subtotal: $1,195
Example client price
Markup/overhead: $239
Total change order price: $1,434
Schedule impact: 1 working day
Approval needed before rough-in continues
Approval boundary
Templates help you write the request. StackQuotes helps you keep the approval record tied to the job.
Pricing example summary
- Cost basis
- $1,195 direct and coordination cost.
- Client price
- $1,434 after markup and overhead.
- Approval note
- Client approval needed before the electrical rough-in schedule is changed.
CTA
Use StackQuotes when pricing examples need to become job-specific approval records.
How to use this
Use the example to build your own cost backup before sending a price.
Adjust labor rates, markup, taxes, and assumptions to match the actual job.
Keep the pricing backup tied to the final approval record.
Approval boundary
Templates help you write the request. StackQuotes helps you keep the approval record tied to the job.
StackQuotes does not guarantee payment or prevent every dispute. It helps contractors preserve the request, pricing context, client action, and job record in one place.
This is general business documentation guidance, not legal advice. For legal disputes, lien rights, or contract enforcement questions, talk with a qualified construction attorney in your state.
Common mistakes
- Copying example numbers instead of pricing the actual job.
- Showing markup without documenting direct costs.
- Forgetting schedule impact when labor or lead time changes.
- Keeping pricing backup separate from the approved request.
FAQ
What does it help document?
It helps document changed scope, price or schedule impact, supporting facts, and the client action needed before work continues.
What goes wrong if this is not documented?
The contractor may be left reconstructing scope, price, timing, or approval from memory, messages, and invoices after the job has already moved on.
Is this legal advice?
This is general business documentation guidance, not legal advice. For legal disputes, lien rights, or contract enforcement questions, talk with a qualified construction attorney in your state.
Related resources
Change Order Pricing WorksheetUse the worksheet to build your own job-specific pricing backup.Change Order Pricing ToolPrice labor, materials, subcontractors, overhead, markup, and total change impact before sending the request.Time and Materials Pricing ToolUse time and materials pricing when extra work cannot be scoped as a fixed price cleanly.Change Order ExampleCompare pricing notes against a contractor-focused change order example.Run Better resourcesKeep pricing notes tied to the request and the approval record instead of scattered across messages.Change Order Risk CheckerCheck whether scope, price, schedule, and client-action details are missing before work continues.