Documents rarely move from sent to signed without friction. A signer spots a wrong date, legal wants a clause adjusted, a deal falls through. GingerDocs handles the messy middle without forcing you to rebuild from scratch — and without breaking the audit trail.
Amendment proposals
If a change is needed after sending, propose an amendment in place. The proposed change is presented to the affected parties rather than silently applied, and the document supports up to three amendment proposals before you would need a fresh document.
This keeps one continuous record: the original content, the proposed change, and the responses all live in the same document history instead of being scattered across "v2_final_FINAL" email attachments.
Voiding a document
Senders can void a document at any time before completion — when a deal is cancelled, terms are renegotiated, or the wrong file went out. Voiding immediately ends the workflow, recipient links stop working, and the void event is recorded immutably in the audit log.
When a recipient declines
Recipients can reject a document rather than ignore the request. They must provide a reason, the sender is notified immediately and can make changes and resend, and the decline is written to the audit log with a timestamp — so "they never signed" has an answer to when, how, and why.
Expiry
Documents that are never completed do not linger as open requests forever — an expired document moves to a terminal Expired state, distinct from voided or declined, so your dashboard reflects what actually happened.
Why terminal states matter
Voided, Declined, and Expired are recorded states, not deletions. The document and its full audit history remain intact, which is exactly what you want when someone asks six months later why an agreement was never executed.