Skip to content

Legal & policies

Client Approval Policy

Written approval gates, what approval commits, and how scope changes are handled without silent drift.

Updated January 2026Applies as written; a signed engagement agreement prevails where it differs.

Client Approval Policy

Written approval gates, what approval commits, and how scope changes are handled without silent drift.

1. Why approvals are written

Every consequential step in an engagement is approved in writing: the Final Scope of Work, the HTML preview, each milestone acceptance, delivery, and the handover confirmation. Written approvals protect both parties — the record answers any later question about what was agreed and when.

Written means: an explicit reply (email, WhatsApp message, portal action) that states approval. Silence is not approval; where a review period closes without response, the Delivery Policy's acceptance rules apply instead.

2. The approval gates

Gate one — Scope approval: the Final Scope of Work (deliverables, timeline, milestones, payment terms) is approved in writing. Work, previews and payment requests all begin after this gate.

Gate two — Preview approval: the HTML preview is approved or revised in writing. Payment begins only after approval.

Gate three — Milestone acceptance: each milestone is accepted in writing before the next proceeds. Acceptance confirms the milestone conforms to the approved scope.

Gate four — Delivery confirmation: you confirm in writing that the delivered solution passes the agreed checklist.

Gate five — Handover confirmation: after full payment and handover, you confirm that passwords have been changed and access is complete.

3. What approval commits

Approving a scope, preview or milestone confirms that the item conforms to the agreed requirements and authorises the next phase — including the payment milestone attached to it, per the Payment Policy.

Approval is not a waiver of defects. Non-conformity with the approved scope discovered later is remedied under the Delivery Policy warranty even after acceptance.

4. Scope changes

A scope change is any addition, removal or material alteration to the agreed deliverables or requirements. Scope changes are normal — mishandled scope changes are not.

Every scope change follows the same path: request documented — impact assessment (cost, timeline, technical) — written quotation — your written approval — scope document amended and re-versioned. Work on a change never begins before its approval.

We do not absorb changes silently into "goodwill", and we do not let clients' changes proceed informally. The amendment quote states exactly what changes and what it costs, so your budget never drifts without your signature.

5. Disagreements

If a disagreement arises about whether delivered work conforms to the scope, the comparison is objective: the approved scope document, the approved preview, and the delivery checklist. We provide the full record to you on request.

Where genuine ambiguity exists in the written scope, we resolve it toward the interpretation that a reasonable client would have understood at approval time — and we amend the scope text so it never recurs.

Questions about this policy?

Write to info@bdtech360.com or start a chat with our AI assistant (on any page) quoting your Client ID. Policy questions are answered by the team that wrote the policy.