When to use this template
Start with the questions below, then adapt them to your own process. Keep the existing scope visible and route the request to the decision maker; submitting the form is not approval.
Turn scattered requests into clear records with context and a next owner. Use this version when you need to document a proposed scope change and its likely impact before a decision.
Questions included
- Your nameShort answer · Required
- Email addressEmail · Required
Used to respond about this request.
- Project referenceShort answer · Required
- Requested changeLong answer · Required
- Reason for the changeLong answer · Optional
- Expected timing or cost impactLong answer · Optional
- What happens if it is not changed?Long answer · Optional
Make it your own
- Replace the introduction with your own context for project change request.
- Keep the existing scope visible and route the request to the decision maker; submitting the form is not approval.
- Check required questions, remove information you do not need, then test the form on a phone.
- Publish a copy and share its link or embed it on your page.
Before you publish
These forms collect requests. Define your review and escalation process before promising service levels or approvals.
Common questions
What does this project change request form collect?
It includes project reference, requested change, reason for the change, expected timing or cost impact. Every question can be edited before you publish.
What should I customize before sharing it?
Keep the existing scope visible and route the request to the decision maker; submitting the form is not approval.
What happens after someone submits it?
These forms collect requests. Define your review and escalation process before promising service levels or approvals. Published copies store responses in the form inbox. Optional owner email notifications require a connected email service.