Delivery Policy

This Policy explains the general delivery approach. The approved SOW and project agreement govern the deliverables, schedule, review criteria, and obligations for each engagement.

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.

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. A preview is a review artifact and not, without express agreement, a production-ready release or proof that backend and live third-party integrations are complete.

Commencement occurs as stated in the approved SOW and may depend on written scope approval, required materials, access, and the applicable payment arrangement. Preview, build, and payment order may differ where the parties expressly agree in writing.

Delivery dates are estimates unless the approved agreement expressly makes a date binding. Timing depends on complexity, scope, Client feedback and approvals, payment milestones, third-party dependencies, and infrastructure readiness. No universal delivery period is guaranteed.

The Client should provide requested content, lawful assets, decisions, authorized access and feedback within agreed review periods, and identify a representative able to approve the work. Missing inputs or delayed decisions can affect schedule and may require a written adjustment.

Milestones and their acceptance criteria apply only where included in the SOW. TECH360 may provide milestone work for review using the agreed channel. A milestone review does not alter payment terms unless the SOW says so.

Testing is limited to the checks and environments identified in the SOW. Where agreed, the project may include functional, responsive, compatibility, security, performance, or integration checks. No particular test suite or certification is implied unless expressly included.

The SOW states any included revision rounds and how they are counted. A correction to conforming work is handled under the agreed correction terms; a request that changes approved requirements may be a separately quoted change. TECH360 will document material scope, fee, or timing impacts for written approval before starting additional work.

Delivery may be through an agreed client portal, repository, secure file transfer, approved hosting environment, or another method specified in the SOW. Method and access depend on project configuration and security needs. Delivery evidence may record the items, recipient, method, and date without exposing secrets.

Deployment, domain configuration, hosting setup, migrations, monitoring, and ongoing hosting are included only when stated in the SOW. Third-party service accounts, fees, limits, and outages remain subject to those providers' terms and availability.

The Client should compare delivered items against the agreed criteria and report a specific mismatch through the agreed channel. Any review or deemed-acceptance mechanism must be expressly stated in the contract and legally valid. Silence alone is not unconditional approval. Acceptance does not waive non-waivable rights.

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. After final payment has been verified and cleared, TECH360 delivers the agreed source-code package, project documentation, and Client-owned credentials specifically identified in the approved Scope of Work. TECH360's internal secrets, shared infrastructure credentials, and other clients' information are excluded.

Support, training, maintenance, response targets, and correction periods are included only if stated in the agreement. Material non-conformity is reviewed against the SOW and addressed as required by the contract and applicable law. Work outside included support may be separately quoted.

A schedule may be affected by Client inputs, scope changes, provider approvals or outages, third-party services, payment status, security review, or unavailable infrastructure. The parties should document material changes to dates and dependencies. TECH360 does not promise control over third-party timelines.

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.