Handling Scope Changes During a Custom WordPress Project
Published:
Published by: Hedou Bibi
Use the approved baseline to assess, agree and verify a new requirement before it changes the delivery.

A request to add a filter or accept an attachment can arrive after the design has been approved. Before changing the build, write down the new behavior and compare it with the agreed scope. That gives the owner a practical choice about what to deliver now, what to postpone and what needs a revised estimate.
Start with the approved baseline
Gather the approved design version, page list, editing requirements and functional acceptance criteria. Record the approval date, decision maker and links, including questions left open at that point. A category navigation drawn in a mockup does not necessarily establish an agreement to build combined product filtering; read the functional description as well.
If the implementation falls short of that baseline, investigate it as a defect. If the documents conflict, clarify the requirement before assigning a category. Neither “all later requests are extras” nor “anything small is included” provides a reliable basis for managing the project.
Turn a short request into observable behavior
For a product filter, identify the attributes, whether visitors can combine them, how clearing a selection works and what happens when no products match. Describe the mobile interaction. Then check the data behind the interface: do the fields already exist, who will complete older products and where will translated values come from?
Assess the request across the public interface, editing tools, existing content, languages, testing and release. Mark unanswered questions with the person responsible for supplying the information. An estimate without those assumptions is difficult to use when planning a launch.
An example change request
This is an invented example for discussion. It is not a client record, a fixed quotation or a delivery promise.
Scroll horizontally or use the arrow keys to view the full table.
| Record | Example | Decision still required |
|---|---|---|
| Original scope | Browse products by category and show basic specifications | Link the approved design and functional description |
| Requested behavior | Combine material and application filters | Agree options, combinations, empty results and mobile controls |
| Affected areas | Product listing, editing fields and both language versions | Assign existing-data completion and translation |
| Cost and schedule | To be assessed and confirmed separately | Decide whether milestones move or the work is phased |
| Acceptance | Test agreed sample products, combinations and reset behavior | Confirm sample data, devices and pass conditions |
Present choices before asking for approval
Compare implementing the full request in the current phase, delivering a smaller useful version, and moving it to a later release. For each option, explain what stays in the current delivery, what is deferred and which dependencies change. Confirm the cost, schedule and responsible people before implementation. A preliminary estimate should remain visibly provisional until accepted.
Changes to stored data or existing content also need a migration and recovery plan appropriate to the work. If source data is missing, agree the information needed before fixing the implementation start date. Keeping the original launch date should not silently remove testing or editor handover.
Update the acceptance record along with the build
Give the change a stable number and link the previous baseline, revised design, implementation record and new acceptance checks. Test the new behavior and the existing journeys it may affect: category browsing, product links, enquiry access and language switching, for example. Record why those areas were selected rather than claiming an undefined whole-site retest.
WordPress post revisions can help compare saved editorial content. Keep scope approvals, code changes and release decisions in their own records; an article’s revision history is not a complete site change or recovery plan.
Make the next discussion concrete
Bring four things: the approved version, the requested user action, affected pages and the desired timing. If several stakeholders are contributing, first consolidate their feedback using the agency review and revision approach. Discuss the confirmation and handover stages with Hedou Bibi through the website development process, then record the arrangement agreed for the specific project.
