Release remains owner-controlled
Proofmark records approval and payment state, but it does not turn payment confirmation into automatic file release. The owner decides when final files unlock.
How it works
One handover flow from finished work to final release.
Proofmark is designed to prepare a standard project handover in under 3 minutes. That is a product design target, not empirical certification.
Send a HandoverProofmark
Client Handover
AgreementReview the current scope
PreviewApprove this version
PaymentConfirm when paid
DownloadFinal files wait for release
Approval, payment state, release, and version evidence stay separate.
Owner side
- 1
Add client
Enter the client and project closeout details in the handover composer.
- 2
Drop final files
Upload deliverables once; previews and final release rules stay explicit.
- 3
Confirm terms
Record scope, approval requirement, payment instructions, and release note.
- 4
Send handover
Create the authoritative handover link through the existing server share flow.
Client side
- 1
Review agreement
The client sees the handover scope without creating an account.
- 2
Preview current version
Approval applies to the exact version presented for review.
- 3
Approve or request changes
A clear choice is recorded on the handover trail.
- 4
Confirm payment
Payment state is recorded separately from Proofmark subscription billing.
- 5
Wait for release
Payment confirmation does not automatically release files.
- 6
Download final files
Released files are served through access-checked, short-lived download links.
Evidence stays separate from analytics
Handover evidence records real approval, release, download, and certificate facts. Marketing analytics are separate, coarse, and never become evidence events.