Client purchase approval sheet
A concise record linking plan, country, options, period and approver before payment instructions.
Read the guide ↗CLIENT APPROVAL & HANDOVER MANUAL
Keep the operating record with the project.
Choose resources, country and period; confirm one contact email; read the selected crypto route; then keep access and recovery responsibilities usable.
- Review the service facts and the client’s project needs.
- Use a buying guide to agree the configuration and ownership.
- At checkout, confirm the contact, asset, network, amount and one-hour expiry.
- Keep payment evidence separately and complete the operating handover.
Contact and account ownership checklist
A handover-friendly record of who controls the project contact, DNS, application access and recovery path.
Read the guide ↗Crypto expense evidence
A record of the approved configuration, selected asset/network, local reference and transfer evidence a payer keeps outside this site.
Read the guide ↗DNS and launch acceptance record
A checklist for a named DNS change and client acceptance of the public website path.
Read the guide ↗Update and rollback responsibility
A decision record for an application update with an operator, evidence and approval point.
Read the guide ↗Client exit packet
A practical inventory for an agency/client transition without publishing credentials in the packet.
Read the guide ↗Payment exception handover
A record for an expired, late, partial or wrong-network transfer question that does not assume a payment result.
Read the guide ↗Backup scope agreement
A scope record distinguishing selectable backup options from application recovery responsibilities.
Read the guide ↗