The dangerous copy is often the one called “final.” Someone corrects the case, someone else prints an older PDF, and both believe they are using the current document. A clear change process gives every version a status and every correction a traceable reason. This guide is an office workflow; the right legal form of an amendment or replacement depends on the document and your requirements.
Check the document status before editing
| Stage | Office action | Evidence to keep |
|---|---|---|
| Draft | Correct the source information and review the regenerated content | Reviewer and current draft reference |
| Awaiting signatures | Decide how to stop the earlier request before issuing a replacement | Earlier request status and replacement reference |
| Completed | Preserve the signed copy; use an approved amendment or new document | Signed original, reason and approval |
| Voided or replaced | Make the status clear to staff and identify the document to use | Reason, date and link between records |
Changing the case record does not establish that a previously sent or signed PDF changed too. Open the actual document you intend to use. That check matters more than a filename or the time shown in a downloads folder.
Use a short change record
Record the case reference, earlier document, reason, approving person and replacement. Add whether another signature is required and who has been notified. Our document change-control log gives the office one place to record those checks.
Download the document change log (CSV)
- Find the exact document and check its current status.
- Confirm the corrected information with the person responsible for that part of the case.
- Decide the approved amendment or replacement process and whether signatures are required again.
- Handle the earlier outstanding invitation using the supported document action before sending another.
- Review and issue the corrected document, preserving the original record.
- Tell the relevant staff which copy to use and check the completed replacement when it returns.
Worked example: a selection changes after signing
In this fictional example, a family changes a merchandise selection after signing the statement. The director records the requested change and reviews the resulting price difference. Staff preserve the signed statement, prepare the required replacement or amendment under the firm’s process, and collect any required new signatures. A payment correction is reviewed separately if money needs to move.
The office should be able to answer three questions without asking the director from memory: what was signed originally, what changed, and which record now governs the next task. Use the refund workflow if the revised arrangement also means returning money.
How FuneralHQ supports document changes
FuneralHQ keeps documents and e-signatures with the case that supplies their details. Document statuses distinguish drafts, pending signatures, completed, declined, error and voided records. Supported document actions include voiding with a reason; already-issued completed PDFs are not overwritten by PDF regeneration.
This gives the office a practical reason to choose a connected platform: the correction can be reviewed beside the case details, related tasks and payment history. It reduces the need to reconstruct what happened from separate signing accounts and inboxes. Staff still choose the permitted correction process; software does not decide whether a change is legally effective.
Test the correction on your next software demo
Ask the vendor to generate a fictional document, send it to a test signer, complete it, then demonstrate a correction. Watch whether the original remains retrievable and whether a second member of staff can identify the replacement. Ask how an earlier outstanding signing request is handled. Do not accept a slide saying “audit trail” in place of the actual records.
FuneralHQ can walk through its available document actions with your team. Use the software acceptance worksheet to record what was demonstrated, what required staff assistance and any gap to resolve before rollout.
Common document-version questions
Should we delete an earlier signed copy after replacing it?
Follow your retention requirements and approved policy. Preserve the signed history needed to explain the change rather than deleting a record simply to avoid confusion. Make its earlier status clear.
Does correcting a case field update a signed PDF?
Do not assume that it does. In FuneralHQ, an already-issued completed PDF is preserved. Review the correction and use the appropriate document process instead of expecting a case edit to rewrite signed content.
The FuneralHQ advantage
Documents belong inside the case workflow
FuneralHQ generates, sends, signs, and stores documents on the case, so a completed packet returns to the work it authorizes instead of living in a separate signature account.
The walkthrough separates what ships today from what is in development, then tests FuneralHQ against one of your real workflows.
Challenge us with your workflowAbout the FuneralHQ Editorial Team
This guide was written by the FuneralHQ Editorial Team, the in-house team behind funeral home software used by independent firms to run cases, documents, payments, and QuickBooks sync in one record. Our editorial standards explain how we review product claims, outside sources, automation, updates, and corrections.