Agreements and payments
Keep the signed document and the working template separate
Editorial team · Reviewed
Templates evolve as a business learns. A document someone already accepted should remain an identifiable record of the terms they saw, even when the reusable template changes the following week.
A practical sequence
- Keep a dated, immutable copy of the accepted content and its signature record.
- Use new revisions for proposed changes instead of silently editing the old record.
- Distinguish draft, sent, accepted, declined and replaced states.
- Test how the record is exported and retrieved after a system change.
Work through an example
A photographer updates a package template to include a different album. That change should affect new proposals, not replace the album described in a couple's accepted agreement. The original remains available while any agreed amendment is linked separately.
Where judgement matters
A visible name and timestamp alone do not explain the whole signing process. Ask a provider what evidence it retains and obtain appropriate advice about your requirements. Do not make blanket claims of legal enforceability based on a software badge.
Make it usable
Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
A client signs a particular contract version. Later, a staff member spots a typo and wants to edit the document in place. Even a small change can make the displayed record differ from what was accepted. Preserve the accepted version and use the business’s reviewed correction or reissue process.
| Decision | Why it matters |
|---|---|
| Freeze the accepted content with its evidence. | Names, timestamps, version and signature records should remain attached to that exact document. |
| Separate a draft correction from a signed record. | The editor should make it clear which copy can still change. |
| Use explicit voiding or reissue where required. | Do not silently transfer old signatures onto different wording. |
Make one usable artifact
Rehearse a fictional signature workflow and export the accepted record with its verification details. Confirm that a later draft edit does not alter the signed artifact.
Then test the difficult case
One signer has completed their part and another requests a scope change. Pause the decision and inspect the supported reissue process instead of replacing content underneath the first signature.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.