Change of Scope Policy

This Change of Scope Policy explains how we handle requests that go beyond the deliverables agreed in your Statement of Work ("SOW"). It protects both parties by making timelines, costs and expectations clear.

1. What Counts as a Change of Scope?

• New pages, features, integrations, automations or additional deliverables not listed in the SOW
• Significant revisions beyond the agreed revision rounds
• New stakeholder requirements introduced after sign‑off
• Changes that require rework due to delayed or incorrect client information

2. How to Request Changes

Email info@code-flux.co.uk with:

• The requested change and the reason
• Any deadlines or constraints
• Any relevant access, assets or references

3. Our Assessment

• We will assess impact on cost, timeline, and technical feasibility.
• We may respond with: (a) approval as in‑scope; (b) a change quote; or (c) a revised SOW.
• We are not obliged to start change work until it is agreed in writing and any required payment is made.

4. Emergency Work

Where urgent work is required (e.g., a site outage), we may proceed to protect your business. Any emergency work outside scope will be chargeable and confirmed as soon as possible.

5. Version Control & Sign‑off

Once a deliverable is approved, later changes may be treated as a new scope item. We recommend consolidating feedback to avoid avoidable rework and delays.

Last updated: 11 January 2026.