Midway through a project a client says could we just add one more thing. A week later the deadline has moved and nobody remembers who agreed. I would rather every change arrive the same way, with the reason and the effect written down.
Who should use this?
Agencies, freelancers and IT or operations teams that run projects with a plan, a deadline and someone who approves.
What does each answer let me decide?
The area, details and reason tell you what is asked and why. "Was it in the original plan" separates a true change from a missed requirement. Urgency and the deadline question let you schedule it. The approver and the related link make the decision easy to trace later.
What would the requester's AI ask?
"What is the change, in a few words?" Then "Why is it needed?" Then "Will it move the deadline?" It shows all the answers and sends only after a yes. Read about agent-fillable forms.
Keep one form per team and sort the CSV by project. The form records requests and does not approve them.
Find more in forms for agencies and forms for IT and operations. A project intake form handles new work before it starts. A web design questionnaire helps you settle scope for a site. For broken features, use a bug report.
Questions
Does the form approve the change?
No. It records the request with its reasons and effects. Approval stays with the person named as approver, who replies in your usual channel.
How do I log changes for each project?
Download the CSV and sort by project name. Each row is one request, with its date, area and urgency, so a project owner can see how scope grew.
When is a bug report better than a change request?
Use a bug report when something built does not work as agreed. Use this form when the agreement itself changes. Mixing them hides the real cost of changes.