An issued document stops moving
The moment it reaches a client, its content and layout are captured. Editing your working copy afterwards does not rewrite what they are looking at.
CRM & SALES
CRM / MembersSales PipelinePublic Business ProfileWeb Forms & BookingSugar AssistantQUOTES & DOCUMENTS
EstimatesProposalsClient PortalINVOICING & PAYMENTS
Invoices & PaymentsPayment LinksSales ReceiptsSCHEDULING & COMMUNICATIONS
Job SchedulingCommunicationsMileage TrackerACCOUNTING & REPORTING
AccountingReports & ExportsOnline Store SyncSmall Claims & CollectionsTEAM & PEOPLE
Team & PermissionsEmployee RecordsSubcontractorsLOCATIONS & SECURITY
Multi-LocationCorporate AccountsSecure VaultSecurity & AccessBY INDUSTRY
Janitorial & CleaningIT & Low VoltageConstruction & GCAuto & MechanicTrades (HVAC, Plumbing, Electric)BY REGION
Mexico & CFDI 4.0CLIENT PORTAL
Send a document once and it gets its own private link. The client can open it, approve it, sign it and pay it — and the version they hold is preserved exactly as issued.
WHAT THE CLIENT CAN DO
WHY THE FREEZE MATTERS
The moment it reaches a client, its content and layout are captured. Editing your working copy afterwards does not rewrite what they are looking at.
An approval is recorded against the revision that was approved. Re-issue changed terms and the new version needs its own approval — an old signature never carries forward.
Content is frozen; payment state is not. A client who pays sees Paid on the same link, without a new document.
Email and text delivery are recorded per attempt with the outcome, so an unanswered document is distinguishable from one that never went out.
Sent, opened, approved, declined, signed, paid — each with a timestamp, and each attributed to the client or to you.
No portal account, no password reset, no app. The link is the portal.
COMMON QUESTIONS
No. Each document gets its own private link. There is nothing to sign up for, no password, and no app to install.
The version you sent. Content is frozen at the moment a document reaches a client, so your working copy and their copy cannot silently diverge. To change what they see, you re-issue — and that creates a new version they can be asked to approve.
Yes — against the specific revision that was approved, with a timestamp. Re-issuing changed terms requires new consent rather than carrying the old signature forward.
VERSION HISTORY YOU CAN DEFEND
When a document goes to a client it is frozen as an issued revision. Editing the working copy afterwards does not change what they were sent — the version in their hands stays exactly as issued.
This is not a planned feature. Production currently holds 1,822 issued document revisions and 11 recorded client consents across real accounts.
Delivery attempts are logged per document and per channel, with the outcome — so "they said they never got it" has an answer.
When a client approves, the approval attaches to the exact revision they saw. If the document is later re-issued, the earlier approval stays attached to the earlier version rather than silently carrying forward.