# Customer delivery and acceptance record Draft templates only. Professional legal review under applicable Israeli law is required before binding use. These documents are not legally approved. Draft version: 2026-11-10 / draft-4 Reusable evidence of delivered items, customer checks, agreed corrections and final acceptance for the specified project. ## 1. Package scope and equal quality Starter: One landing page, ₪700; Business: Up to 5 pages, ₪1,200; Advanced: Up to 10 pages, ₪3,000; Custom: By quotation, individually quoted. Every BTNXIO website is custom-designed for the brand, with careful user experience, responsive layouts for computers, tablets and phones, professional development and consistent testing. Packages differ in page count and agreed scope, not design quality. Colors, fonts, structure, components and content are tailored to the project. Animation, effects and interactions are available in every package where appropriate to the specification; unusually complex motion and functionality require agreed pricing. BTNXIO proposes the initial plan and design direction. Together we refine the structure, content and details before final approval, within the agreed scope and chosen working method. This does not provide unlimited development or additional deliverables. Actual pages and deliverables are listed within the selected package limit; additional pages or complex functionality require a separate quotation and prior approval. ## 2. Development-stage working method Three alternatives, available in every package at the same design and development quality. Choose one; these are not three mandatory stages. The method does not automatically change the package price. A — Flexible development: Request adjustments throughout development without a fixed number of rounds, within the agreed specification and scope. Significant changes or additions outside that scope are reviewed and separately quoted, with customer approval before any additional charge. B — Three coordinated revision rounds: Three coordinated adjustment rounds are available before launch or final handover. Further requests are assessed according to their scope; they do not automatically incur a charge. Any additional paid work requires a quotation and approval in advance. C — Design approval before development: Approve the proposed design direction and structure first. After development begins, focused adjustments remain possible within the specification. Material changes are discussed separately, including any effect on scope, cost or milestones, before approval. Record the selected method in the quotation or specification; it can be changed by mutual agreement. In-scope adjustments refine the approved pages, structure, content and components without adding new deliverables. Additional work requires a quotation and approval before charging. Defects attributable to BTNXIO do not count as a revision round. Final publication or handover always requires customer approval. These pre-handover arrangements do not use the post-handover annual minor-change round. ## 3. Identity and reference documents Acceptance is recorded by an authorized person for the identified customer, project, quotation and specification version. The date, review method and exact release or delivered archive are identified. The record does not substitute for a missing quotation or invent approval by a person whose authority has not been verified. ## 4. Delivered inventory and access The inventory lists pages, features, languages, media/content, source or build files where agreed, documents, licences and account control actually delivered. Each item can be marked received, not applicable or outstanding with an explanation specific to the project. Passwords and private keys are transferred separately through an agreed secure method, not written into this public template or a widely shared record. ## 5. Customer review and defects The customer records the agreed checks and any mismatch with the specification. Outstanding issues identify severity, affected function, responsibility and the agreed correction or further review. New feature requests are distinguished from attributable defects. Acceptance may be conditional on identified corrections; silence or the existence of this record is not proof that all work is defect-free. ## 6. Payment and publication status The record distinguishes customer review, final payment, launch authorization and actual publication or handover. The final 50% is due before the agreed publication or final delivery, after the customer review opportunity. It records confirmation of the balance and actual event without enabling an automatic charge. If publication is outside the provider’s scope, the handover destination and customer responsibilities are recorded instead. ## 7. Support, ownership and remaining obligations The record references the applicable ownership/licence schedule, start of any defined service period, minor-change allowance and maintenance scope. It identifies any remaining document, migration work, supplier charge or access removal and who is responsible. Receipt does not assign pre-existing tools or non-transferable licences, waive statutory rights or consume the defect-correction obligation as a minor-change round. ## 8. Express acceptance record The authorized customer records acceptance, conditional acceptance or a reasoned refusal against the identified deliverables. The method and evidence of approval are retained with the project documents. Any later revised acceptance is dated and linked to the correction record. This template alone is not a signature, a blanket release or an authorization to publish unapproved information. ## Individual project schedule These particulars form part of the individual approved documents. An empty schedule is not an order, signature or acceptance. No information is submitted or saved through this template. - Selected A/B/C method, development adjustments reviewed and separate post-handover annual round: ________________ - Customer, authorized reviewer and reviewed version: ________________ - Delivered inventory, accounts and documentation: ________________ - Review results, open issues, agreed remedies and responsibility: ________________ - Final payment, approval date and publication/handover evidence: ________________ ## Related drafts - [Website delivery and launch approval](en-launch-approval.md) - [Quotation and work order](en-quotation-work-order.md) - [Website ownership and transfer policy](en-ownership-transfer.md)