Last Updated on June 20, 2026

Change Management

Our Policy on Scope Changes

We understand requirements evolve. Our change management process ensures every adjustment is transparent, documented, and properly estimated.

Small Tweaks (generally absorbed)

Minor text edits, small styling changes, and configuration tweaks within existing features.

New Features (require formal estimation)

New functionality, additional integrations, design changes affecting multiple pages, and third-party plugin additions.

How Change Requests Are Handled

1. Client submits change request with description and business justification
2. Project Manager evaluates scope impact — in-scope vs out-of-scope
3. If out-of-scope: Business Analyst  provides effort estimate covering hours, cost, and timeline impact
4. Client reviews and approves the estimate
5. Change request is added to the project scope
6. Work is completed and delivered with updated documentation

When Budgets or Timelines Shift

We notify you immediately if any of the following occur:

• Accumulated change requests exceed 10% of the original project scope
• External dependencies cause delays (third-party API issues, resource unavailability)
• Unforeseen technical challenges require rearchitecture

When this happens, we present your options clearly: adjust scope, extend the timeline, or revise the budget. The decision is always yours.