Change Request
Your completed fields will appear here. Load the example to see a finished document.
Control scope
Document a requested change and its effect on price, schedule, and responsibilities before proceeding.
The client or team wants to change previously approved work.
Attach the approved change to the work order and invoice.
Check names, dates, totals, and scope. Use a secure system for sensitive details that do not belong in a simple form.
Entries are processed in this browser. We do not receive them unless you save them to a Pro account.
Your completed fields will appear here. Load the example to see a finished document.
CHANGE REQUEST Document version 1.0.0 Created with FreeBusinessForms.com
Prompt for AI
Copy into ChatGPT, Claude, or another assistant for a fillable version.
You are an experienced project-operations document designer for small businesses. Create a change-request template used when a client or crew wants to alter already approved work. It should document the requested change and its effect on price, schedule, and responsibilities before anyone proceeds—so extras are not discovered on the invoice. Include these sections: - Parties and related job ([Business name], [Client], [Change request number], [Related work order or project]) - Request ([Request date], [Requested change], [Reason for the change], [Who requested it]) - Impact ([Price impact], [Schedule impact], [Scope added or removed]) - Decision ([Status: Pending / Approved / Declined], [Approver], [Decision date]) - Follow-through ([Attach to work order], [Update invoice], [Notify crew]) Do not include Social Security numbers, full bank or payment-card numbers, routing numbers, passwords, tax ID numbers, medical details, identity documents, or protected-class information. This is an operational template, not legal, tax, accounting, payroll, collections, or employment advice. Output a clean fillable template I can copy into a document and adapt. Use a professional tone, clearly labeled sections, and [bracketed] placeholders for every fill-in value. Close with a short practical review checklist.
Recommended books
Practical books that pair with this document. Links use our Amazon Associates ID.

Gives a calm way to separate the change from the original deal and negotiate the impact.

Useful when a client asks for “just a little extra” and you need a clear yes or no.

Shows how unofficial project managers keep scope changes visible and approved.
Machine access
Agents can inspect and validate the same versioned fields. View JSON Schema →
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://freebusinessforms.com/schemas/change-request.json",
"title": "Change Request",
"description": "Document a requested change and its effect on price, schedule, and responsibilities before proceeding.",
"type": "object",
"additionalProperties": false,
"properties": {
"business_name": {
"title": "Your business name",
"type": "string"
},
"business_contact": {
"title": "Business contact",
"type": "string"
},
"business_email": {
"title": "Business email",
"type": "string",
"format": "email"
},
"business_phone": {
"title": "Business phone",
"type": "string"
},
"client_name": {
"title": "Client or company",
"type": "string"
},
"client_contact": {
"title": "Client contact",
"type": "string"
},
"client_email": {
"title": "Client email",
"type": "string",
"format": "email"
},
"document_number": {
"title": "Change request number",
"type": "string"
},
"related_document": {
"title": "Related work order or project",
"type": "string"
},
"request_date": {
"title": "Request date",
"type": "string",
"format": "date"
},
"requested_change": {
"title": "Requested change",
"type": "string"
},
"reason": {
"title": "Reason for the change",
"type": "string"
},
"price_impact": {
"title": "Price impact",
"type": "string"
},
"schedule_impact": {
"title": "Schedule impact",
"type": "string"
},
"approval_status": {
"title": "Status",
"type": "string",
"enum": [
"Pending",
"Approved",
"Declined"
]
}
},
"required": [
"business_name",
"client_name",
"document_number",
"related_document",
"request_date",
"requested_change"
],
"x-form-version": "1.0.0"
}