Proposals & Invoices · Article 5.7
Resending the amendment link with a fresh PIN
Client lost the email, hit the PIN-attempt lockout, or just can't find the original message? Resend with a fresh PIN. The old PIN is invalidated, the lockout is cleared, a new email goes out, and the audit log records the re-issuance.
The PIN gate's brute-force protection (5 wrong tries in 24 hours per amendment slug) is a security feature, but it's also the most common source of "client can't sign" support requests. Resend is the recovery: a single click rotates the PIN, clears the lockout cache, and re-sends the email. It's safe to use proactively — there's no penalty for re-sending, and the audit log distinguishes "initial send" from "resend" via the kind: "resend" flag on the timeline event.
Step by step
Open the proposal detail page.
/proposals/{id}. The Pending amendment panel is visible while the amendment is insentorviewedstate.Click
Resend with fresh PIN.The button is in the panel's action row, alongside
Copy sign linkandCancel amendment.Confirm in the modal (if any).
The action is reversible in effect (you can resend again) but the old PIN becomes immediately useless, so the modal asks once.
Email goes out within ~5 seconds.
Same body template as the initial send, with the new PIN. Subject line picks up an "(updated)" suffix in the locale — so the client sees it's a fresh copy, not a duplicate of the original.
(Optional) Copy the link directly.
The Pending amendment panel surfaces the public link plus the new PIN (visible only to you). Useful if the email infrastructure is the actual problem — you can hand-deliver via your usual channel.
The Pending amendment panel updates with a new "Resent at HH:MM UTC" timestamp. A Timeline event Amendment proposed at HH:MM (resend) is added (we reuse EVENT_AMENDMENT_PROPOSED with metadata kind: "resend" per the comment in AmendmentResendView).
Troubleshooting
Keep reading
Proposals & Invoices
What your client sees when an amendment lands
The client receives an email with a fresh PIN, lands on a PIN-gated page, sees a side-by-side diff of old vs new with totals and a reason, and signs (or declines) — exactly like the original proposal flow but with the diff baked in.
Troubleshooting & Reference
"My client can't enter the PIN" (lockouts and lost codes)
The 4-digit PIN gate protects every proposal and amendment link. Five wrong attempts in 24 hours triggers a per-IP lockout. Recovery is one click away — issue a fresh link.
Proposals & Invoices
When the client declines (or the amendment expires)
Two terminal states for an unsigned amendment: the client clicked Decline (with optional reason) or 14 days passed with no action. Either way, the original contract is unchanged — and you can immediately draft a new amendment to try again.