Website projects need room for useful feedback, but uncontrolled changes can affect time, quality, and cost. This policy explains how IQX reviews modifications clearly.
IQX separates normal in-scope feedback from modifications. If a request changes approved design, adds pages, adds features, changes structure, or needs extra technical work, IQX reviews the impact on cost, timeline, and scope before implementation.
Small in-scope refinements are handled during agreed review stages
Major changes require impact review and approval
Post-launch changes may be handled as support or new work
The modification policy keeps changes fair. It protects the client from surprise costs and protects the project from late requests that disrupt quality or delivery.
Small adjustments that fit the agreed scope and review stage can usually be handled within the approved process.
New features, new pages, major redesigns, new integrations, or structural changes after approval are reviewed separately.
After launch, updates and improvements may be handled through support, maintenance, or a new project scope.
A clear change process prevents surprise costs, uncontrolled delays, and misunderstood expectations.
The client sends a clear written request with the desired change, affected page, reason, and expected result.
Client role
Explain what should change and why it matters to the business or user.
Result
IQX can review the request without guessing.
IQX checks whether the change affects design, development, content, SEO, timeline, testing, cost, or third-party dependencies.
Client role
Answer any clarification questions and confirm whether the change is essential.
Result
Both sides understand the real impact before work starts.
If the request is outside the agreed scope, IQX may provide a revised cost, timeline, or written change note.
Client role
Approve the updated scope or decide to keep the original plan.
Result
No extra work is started without agreement.
Approved changes are scheduled and completed according to the revised agreement or support route.
Client role
Review the implemented change at the agreed point.
Result
The modification is handled cleanly and fairly.
This simple comparison helps show why some feedback is part of the normal process while other requests need a separate review.
Modifications usually include work that changes the approved direction, increases effort, adds technical complexity, or appears after the relevant approval stage.
Urgent changes may be possible, but they can affect scheduling, cost, and other planned work. Priority handling is confirmed before the change begins.
A modification is usually a request that changes approved scope, adds pages, adds new features, changes structure, introduces integrations, or requires major post-approval design changes.
Small in-scope revisions can be included during agreed review stages. The exact revision allowance depends on the selected package or project agreement.
Yes. If a request requires additional time, features, testing, design, content, or technical setup outside the approved scope, it may require an updated quote.
Yes. Post-launch changes can be handled through a support plan, maintenance agreement, or separate improvement project depending on the request.
Send the request clearly and IQX will help you understand whether it is a revision, support task, or new scope item.