A signature is only useful when everyone can identify the document that was actually reviewed. If an estimate changes after it is sent, a team should not have to guess whether the customer approved the old scope, the new price, or a file that no longer matches the workspace.
Exoserva preserves a document snapshot for the signature workflow so the signed result can be connected to the exact version presented to the customer.
Freeze the version at the right moment
An estimate is a working document while the team is preparing it. Line items, descriptions, quantities, exclusions, and prices may change during review. Once the document is sent for signature, however, the customer needs a stable version.
The snapshot creates that boundary. The version presented for review remains identifiable even if the internal estimate is edited later. A newer revision should be treated as a new document decision, not silently substituted under an existing signature request.
A synthetic example
A contractor sends an estimate for a repair with three line items. The customer asks to remove one optional item, so the office updates the proposal and sends a revised version.
The signature record should make it clear which version the customer opened and signed. The earlier proposal remains part of the history, while the completed result corresponds to the revised scope and price.
Without that separation, someone reviewing the job later may see the current estimate and assume it was the one approved. With version integrity, the team can compare the original sent document, the later revision, and the completed signature bundle without relying on memory.
Keep the document and the event connected
The signature workflow should preserve more than a visual mark. A useful record connects the document version with the relevant signing events and completed files. Depending on the configured provider and workflow, authorized users can retrieve the source document and the completed bundle for review.
That gives the office a practical audit path:
- identify the document version that was sent;
- review the scope and price in that version;
- see the relevant signature status and events;
- download the available original and completed files;
- compare a later revision without overwriting the signed record.
Changes should create a new decision
If the scope changes materially after signature, the team should not edit history to make the old approval appear current. The safer workflow is to prepare the updated document, explain the change, and obtain the appropriate new review or approval.
This matters for both the customer and the business. The customer can understand what is being accepted, and the team can avoid treating an outdated document as permission for different work.
Review remains part of completion
A completed signature status does not automatically prove that every business or legal requirement has been satisfied. Teams may still need to verify signer identity, required disclosures, authorization, contract language, retention rules, or local requirements.
The feature provides document-version integrity and a clearer record. It does not replace legal advice or a company’s own approval policy.
One version, one understandable record
The principle is simple: the file the customer signs should be the file the team can retrieve and explain later. Preserving the exact version makes estimates easier to administer, easier to audit, and less dependent on someone remembering which attachment was current.
Signature features, provider events, downloadable files, and retention behavior depend on workspace configuration and connected services. Requirements vary by jurisdiction and business process.
How does your team currently prove which estimate version a customer approved?
— The Exoserva Team