Describe your project and how changes get approved. Makeform turns it into a change order request form — scope of work description, itemized cost breakdown, schedule impact, and signature fields — so every change to the contract is priced and approved in writing before the work happens.
Send change order requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Pick a prompt, edit it above, or send it into the real Makeform builder. The structure here is an example, not a live AI result.
Audience
General contractors submitting changes to the project owner
Format
Full change order request with cost and schedule impact
Prompt size
607 chars
Example form structure
Full change order request with cost and schedule impact
Project name and contract number
Describe the change to the scope of work
Reason for the change
Cost breakdown: labor, materials, equipment, markup
Schedule impact in days
Supporting drawings and specifications
Contractor and owner sign-off
Suggested routing tags
Pending review
Approved
Revise and resubmit
Make the cost breakdown and schedule impact required fields — a change order request without a price is just a conversation.
Step 1
Request
scope change described, priced, and dated
Step 2
Review
owner or GC checks cost and schedule impact
Step 3
Approve
signatures recorded before work proceeds
Step 4
Update
contract sum and completion date adjusted, log current
Why a request form
On most projects the scope change is real, the extra cost is real — and the paper trail is a text message. A change order request form makes every change priced, documented, and signed before the crew touches it.
"Go ahead, we'll sort it out" is how contractors eat the cost of extra work. A signed change order request is how they get paid for it.
A single "$8,400 extra" invites pushback. An itemized breakdown — labor, materials, equipment, markup — gets reviewed and approved.
Ten undocumented changes later, nobody can explain the gap between the original contract sum and the final invoice. A change order log can.
Built for how changes flow
Start from the version closest to who submits changes on your projects, then edit the fields in the builder.
The formal change order request — scope description, cost breakdown, schedule impact, and both signatures on one record.
Trades submit itemized pricing for out-of-scope work, with photos of field conditions attached to the request.
Plain-language change descriptions with the new project total, approved or declined with a signature from the client's phone.
Same-day time-and-materials records with photos — the evidence that backs the formal change order request later.
Change order workflow
Makeform turns your change process into a live form with notifications, so requests stop living in email threads and job-site texts.
Tell Makeform who submits changes, what has to be priced, and who approves — it drafts the change order request form with the right fields.
Adjust cost fields for lump-sum or unit-price contracts, add conditional logic — time-extension questions only when the schedule is affected — and mark the breakdown required.
Each request emails the owner, PM, or architect and can post to Slack, so pricing gets reviewed before anyone commits to the work.
Submissions flow to your inbox and Google Sheets — one running log of every change, its cost, its status, and the cumulative contract value.
Form vs template vs email thread
A change order template gives you a document to re-fill by hand on every project. A generated form is already yours — subs and clients submit online, and every request files itself.
Field guide
Looking for a change order request template? These are the sections that make one work on a real project — generate them as a form, then adapt the wording to your contract.
Contract & identification
A change order only means something relative to the contract it changes. Reference the original agreement precisely, and number every request so the log stays auditable.
Scope & justification
Vague descriptions are where disputes start. Describe the addition, deletion, or modification to the scope of work in specific terms, and record the cause — it drives who pays.
Cost breakdown
Reviewers approve itemized numbers and dispute round ones. Break the price into labor, materials, equipment, and markup, and show what the contract is worth after the change.
Schedule & approvals
Cost is only half the impact — extra work moves the completion date. State the time extension explicitly and close with signature lines for everyone whose approval the contract requires.
Related tools
The change order is one document in the chain. Build the work orders, progress reports, and prequalification forms for the same projects from one AI builder.
Dispatch and document the work itself — the order the change order amends.
Open toolThe generic change request pattern for IT, operations, and service teams.
Open toolLet clients and staff request new work before it becomes an order.
Open toolWeekly site progress, photos, and blockers — the context behind every change.
Open toolQualify the trades before they're the ones submitting change orders.
Open toolCollect bids to join your projects — scope, pricing, and documents in one place.
Open toolFAQ
Short answers for contractors, PMs, and remodelers replacing email-thread change management.
It is the document used to propose and approve a modification to an agreed scope of work — most commonly on construction projects. It records what is changing and why, the cost adjustment to the original contract sum, the schedule impact, and the signatures of the owner, contractor, and other approving parties. Once approved, it becomes part of the contract.
Reference the original contract (project name, contract number, date), give the request a sequential change order number, and describe the change to the scope of work in specific terms. Itemize the cost impact — labor, materials, equipment, markup — state the schedule impact in days, attach supporting drawings or photos, and end with signature lines for every party who must approve. The generator builds all of these fields into your form automatically.
To formalize changes before the work happens. A written request documents exactly what will change, what it costs, and how it affects the completion date — so the owner keeps budget control, the contractor gets paid for extra work, and neither side ends up disputing verbal instructions. The approved log also explains the gap between the original contract sum and the final cost.
A change request is the generic pattern — any proposal to alter agreed work, common in IT and service projects. A change order is the construction-contract version: it carries pricing and schedule impact and, once signed, formally amends the contract. If you need the generic version, use our change request form generator instead.
A work order authorizes and dispatches the work itself. A change order modifies work that is already under contract — different scope, different price, or different schedule than originally agreed. On many projects an approved change order results in a new work order for the crew.
The core set: project and contract identification, a sequential change order number, description of the change to the scope of work, reason for the change, itemized cost breakdown with labor, materials, equipment, and markup, schedule impact and revised completion date, attachments for drawings or photos, and signature fields for each approver. Add a running total — original contract sum, approved changes, new total — if you track the log in the same place.
AIA G701 is the American Institute of Architects' standard change order document, licensed by AIA. This generator does not produce AIA-licensed paperwork — it builds your own request form that collects the same information: description of the change, adjustments to the contract sum and completion date, and the approval signatures. Many teams use a form like this for the request stage and issue the formal G701 once approved.
Yes. Add separate fields for labor hours and rates, materials with quantities and unit prices, equipment, subcontractor costs, and a markup percentage. Structured number fields mean the pricing arrives itemized and reviewable instead of buried in an email.
Yes. Add signature fields and approvers sign on screen from any device, alongside an approve-or-decline choice. The signature and timestamp are stored with the submission, so every change has a recorded approval. For which documents require particular signature formalities, follow your contract and local requirements.
Send submissions to Google Sheets and keep a running change order log: each row carries the change order number, description, cost, schedule impact, and status. Totals against the original contract sum update as requests are approved — the same log the Excel templates promise, without re-typing each request.
Yes. Publish the form as a public link, embed it on your site, or send it by email or text — subs and clients submit from their phones, no login required, with photos attached from the job site.
Yes. You can generate the form, edit it, and publish it for free. Paid plans add higher submission volumes and advanced workflow features.
Stop doing extra work on a handshake.
