Scope is the list of inclusions on your accepted quotation. Anything outside that list is a scope change, and it is handled through a written variation so the cost and schedule effect is visible before work starts.
Typical scope changes
- Adding pages or modules that were not quoted.
- Adding an integration, such as a payment gateway, courier system or accounting tool.
- Adding a second language.
- Changing the design direction after design approval.
- Restructuring the site navigation once development has begun.
The process
- You raise the request in writing on your project thread or by email.
- We assess it against the approved scope and confirm whether it falls in or out.
- If out, we send a written variation with the additional cost in MYR and the effect on the launch date.
- You approve or decline in writing.
- Approved work is scheduled. Declined requests can be parked for a later phase.
Why the schedule moves too
Extra work takes extra time, and it also has to be designed, built, tested and reviewed alongside everything else. A change that looks small in isolation can affect templates, responsive behaviour and testing across the site. The variation states both the money and the days.
Trading scope instead of adding
If your budget is fixed, ask whether something can be swapped out to make room. Removing a feature that has not been built yet is straightforward. Removing one already built is not, since the effort is already spent.
Phasing
When a launch date is fixed, the usual answer is to launch phase one as quoted and add the new items as a phase two immediately after. This protects the date without dropping the idea.
Keep the record
Approved variations become part of your project scope and are recorded against the project in the portal at crm.zylax.com.my, alongside the original quotation.
To discuss an idea before formally requesting it, reply on your project thread or write to [email protected].
