How approvals work on a Zylax project

A project moves through a series of approval points. Each one locks a decision so the next stage can be built on solid ground.

The main approval points

  • Quotation approval. Accepting the quotation fixes scope, price and payment schedule.
  • Sitemap or scope approval. Confirms the exact page list or module list before design starts.
  • Design approval. Confirms the visual direction. Development starts from an approved design, so reopening the design later means rebuilding pages that already work.
  • Content approval. Confirms the text and images that go live are the final versions.
  • Pre launch approval. Your sign off on the staging site after testing, which authorises us to push live.
  • Handover acceptance. Confirms delivery is complete and the support period begins.

What counts as an approval

A written confirmation from your named decision maker. A reply on the email thread saying "approved" is enough. A verbal yes on a call is not, because there is no record of exactly what was approved. Where an approval carries a cost, such as a scope change, we will ask you to confirm in writing before we start.

Approval windows

Each stage has a review window agreed at kickoff. If we do not hear back within that window we will follow up. Extended silence pushes the schedule and can mean losing your production slot to the next project in the queue.

Approving with conditions

You can approve a design subject to small changes, such as a colour adjustment or a swapped photo. Say clearly which changes are conditions of approval and we will apply them before moving on. What causes problems is an approval followed a week later by a fundamental change of direction.

Where approvals are recorded

Quotation acceptance and invoice status are recorded in the portal at crm.zylax.com.my. Stage approvals are recorded on the project thread so both sides can see what was agreed and when.

If you are unsure whether something has been approved, ask. Reply to your email thread or write to [email protected].

Did you find this article useful?