Amending signed coverage
Signed coverage is a matter of record: a reader put their name and a date on it. So CoverQueue never lets you edit a signed document in place. When something needs to change, you create a new version, and the original stays exactly as it was.
Signed means immutable
The moment you sign, the coverage locks: no field is editable, and the document keeps the template snapshot it was written on. This is what makes coverage trustworthy: an exec reading it months later sees precisely what the reader signed.
If you catch a mistake before signing, just fix it; immutability only kicks in at signing. The confirmation modal is your last chance to review verdicts.
Amending creates a new version
To correct or update signed coverage, create an amendment. That produces a new version of the document; the earlier one is marked superseded but remains on record and readable. The version chain shows both, so nothing is lost and the history is auditable.
Coverage
v1 signed Nov 3 2025 (superseded)
v2 signed Nov 7 2025 ← current
The Coverage Read view links between versions when a chain exists, and every sign event is written to the audit log.
Amendment vs. a new draft of the script
These are different things:
- Amending coverage: same script, corrected or updated evaluation → new coverage version.
- A new draft of the script: a revised PDF → a new submission linked in a version chain, which gets its own coverage. See Handling duplicates and new drafts.
Common questions
Can I delete the old version? No. Signed coverage isn't deletable; superseding is the mechanism. This keeps the record intact.
Who can amend? Like signing, the assigned reader or an exec/owner, and the new signer is recorded.
Do exported PDFs show the version? Yes. Each version exports as its own branded PDF with its signer and date.