Client Approval Policy

This Policy explains how TECH360 records Client decisions. The SOW and project agreement identify which decisions require approval and their consequences.

The approved SOW establishes requirements, deliverables, exclusions, milestones, fees, timing, review criteria, revisions, and ownership or licence arrangements. A project-specific written agreement and approved Scope of Work (SOW) define the deliverables, price, schedule, revision allowance, payment milestones, support, and ownership or licence terms. A website description, proposal draft, or preliminary discussion does not replace that approval. The parties should approve the version that will govern the project before authorized work proceeds.

An HTML Preview is supplied before the applicable project payment only where it is included in the agreed process. Approval confirms the visual design and elements actually shown; it does not, by itself, establish that backend functions, production integrations, security testing, or deployment are complete. The Client should identify specific requested changes and distinguish visual refinements from new or changed functionality.

Where the agreed process requires approval before a payment request, TECH360 will seek the Client's written approval of the relevant SOW and preview before issuing that request. The agreed quotation, invoice, and SOW still control when payment is due. Approval is not a substitute for a payment provider's authorization or verification.

Revision requests should identify the page, feature, or criterion and desired result. Included revision rounds and response windows are only those in the SOW. A request outside those limits or changing approved requirements may be treated as a change request.

A material addition, removal, or alteration to approved requirements should be documented with impacts on fees, dates, and acceptance criteria. TECH360 will obtain the Client's approval of the change before performing chargeable additional work.

If milestone reviews are included, the SOW identifies the deliverable, review criteria, review period, payment trigger, and next step. Approval of a milestone records the review outcome; it does not itself waive defects or mandatory legal rights.

The Client should identify representatives authorized to approve scopes, changes, milestones, and delivery. TECH360 may reasonably rely on approvals from a representative identified by the Client, subject to verification where appropriate. The Client should promptly notify TECH360 of changes in authority.

Approvals may be recorded by email, electronic signature, client portal, or another agreed written method. Where available, TECH360 records the project, document or preview version, approval date, and authorized representative. Records are retained as reasonably necessary for project, legal, security, accounting, and dispute purposes.

If a Client misses a review date, TECH360 may send a reminder and discuss a reasonable schedule adjustment or pause. Silence is not unconditional approval unless the project agreement expressly provides a legally valid mechanism. Any such mechanism is subject to applicable law.

Final acceptance is determined by the agreed criteria and procedure in the SOW. The Client should report identified non-conformity with enough detail to investigate. Any acceptance record does not waive rights that cannot legally be waived.

Approval records are relevant evidence but do not automatically establish completion, eliminate all refund rights, or prove payment authorization. Refund decisions follow the Refund Policy and applicable law. Unless otherwise agreed in writing, final source-code handover takes place after all required project payments have been received and cleared. Any suspension or withholding of work or delivery must follow the approved agreement and applicable law.

Contact TECH360 LLC at info@bdtech360.com. Please include the relevant project or invoice reference, but do not email passwords, full payment-card details, or card security codes.