Quick answer
A scope defines the work being delivered, its assumptions, and acceptance checks. A change request records an altered requirement so cost, timing, and testing can be reviewed before work proceeds.
Before you begin
Keep the current proposal, approved page list, and written decisions together. Identify who can approve additional work or changes to the delivery schedule.
What to do
- Check named deliverables, platforms, page types, integrations, content responsibilities, and the review process. Ask about anything that is implied rather than stated.
- Record dependencies such as account access, licenses, approved copy, photography, or third-party responses. A target date may depend on these items arriving on time.
- Describe each requested change and why it is needed. State whether it replaces an existing requirement or adds another one.
- Ask about the effect on estimates, delivery dates, and acceptance checks. Consider migration, recurring app charges, support, and training where relevant.
- Approve the revised scope in writing before additional work begins. Distinguish urgent fixes from a broader new feature request.
How to check the result
The project record should show the current agreement rather than mixed versions of old proposals and informal comments. Identify completed work, remaining work, and the owner of each dependency.
If you need help
For disagreements, compare the requested outcome with the written deliverable and approvals. Hosting fees, maintenance, and future improvements are included only when the agreement says so.
Related help
- Planning a website project's cost, timing and first steps
- Prepare a useful brief for a new website
- Prioritize a monthly website improvement backlog
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
