Modification Policy

A fair way to handle revisions, extra requests, and changed scope.

Website projects need room for useful feedback, but uncontrolled changes can affect time, quality, and cost. This policy explains how IQX reviews modifications clearly.

  • Revision
  • Impact review
  • Approval
  • Implementation
Illustrative photo of a designer reviewing a website interface
Illustrative modification policy scene.
Review the change before work begins
Review
before extra work
Agree
timeline and cost
Build
approved changes
Short answer

How does IQX handle website modifications?

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

Change Control

Good feedback improves the project. Uncontrolled scope changes slow it down.

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.

Layered concept render of revised page layouts, a design pen, change arrows, and an approval checklist

Included Revisions

Small adjustments that fit the agreed scope and review stage can usually be handled within the approved process.

Modifications

New features, new pages, major redesigns, new integrations, or structural changes after approval are reviewed separately.

Post-Launch Changes

After launch, updates and improvements may be handled through support, maintenance, or a new project scope.

Step by step

Modification Request Process

A clear change process prevents surprise costs, uncontrolled delays, and misunderstood expectations.

  1. 01

    Request the change

    The client sends a clear written request with the desired change, affected page, reason, and expected result.

    Client role & result
    Client role
    Explain what should change and why it matters to the business or user.
    Result
    IQX can review the request without guessing.
  2. 02

    Impact review

    IQX checks whether the change affects design, development, content, SEO, timeline, testing, cost, or third-party dependencies.

    Client role & result
    Client role
    Answer any clarification questions and confirm whether the change is essential.
    Result
    Both sides understand the real impact before work starts.
  3. 03

    Updated scope or quote

    If the request is outside the agreed scope, IQX may provide a revised cost, timeline, or written change note.

    Client role & result
    Client role
    Approve the updated scope or decide to keep the original plan.
    Result
    No extra work is started without agreement.
  4. 04

    Implementation

    Approved changes are scheduled and completed according to the revised agreement or support route.

    Client role & result
    Client role
    Review the implemented change at the agreed point.
    Result
    The modification is handled cleanly and fairly.
Compare the request

Revision Or Modification?

This simple comparison helps show why some feedback is part of the normal process while other requests need a separate review.

Text correction

Usually Included
Minor wording or spelling fix
Needs Review
Large rewrite across many pages

Design change

Usually Included
Small spacing, image, or style refinement
Needs Review
New layout direction after approval

Website structure

Usually Included
Adjusting an existing section
Needs Review
Adding new pages or a new navigation model

Features

Usually Included
Fixing agreed functionality
Needs Review
Adding forms, integrations, store logic, or automation

Post-launch work

Usually Included
Agreed support fix
Needs Review
New improvement project or ongoing maintenance
Practical detail

Examples of modifications

Modifications usually include work that changes the approved direction, increases effort, adds technical complexity, or appears after the relevant approval stage.

  • New pages or landing pages
  • New payment gateways, booking tools, CRMs, or APIs
  • Major redesign after approval
Practical detail

Urgent changes

Urgent changes may be possible, but they can affect scheduling, cost, and other planned work. Priority handling is confirmed before the change begins.

  • Confirm urgency
  • Review impact
  • Approve revised timing or cost
FAQs

Frequently Asked Questions

Direct answers about scope, responsibilities, and the next step for your project.

01ModificationsWhat counts as a modification?

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.

02RevisionsAre small changes included?

Small in-scope revisions can be included during agreed review stages. The exact revision allowance depends on the selected package or project agreement.

03PricingCan modifications increase the price?

Yes. If a request requires additional time, features, testing, design, content, or technical setup outside the approved scope, it may require an updated quote.

04SupportCan I request changes after launch?

Yes. Post-launch changes can be handled through a support plan, maintenance agreement, or separate improvement project depending on the request.

Next step

Need to change an existing project?

Send the request clearly and IQX will help you understand whether it is a revision, support task, or new scope item.

Privacy and analytics

Optional Google Analytics helps us understand site visits. It only loads if you allow analytics. You can change your choice at any time. Read the privacy notice