When a signer needs changes — a wrong name, an incorrect date, a missing clause — they don't have to decline and restart the entire process. Instead, they click anywhere on the PDF to place a comment pin, type their request, and submit.
Any signer can click anywhere on the PDF to place a comment pin during the signing review.
They type a change request: e.g., 'Please update the amount from $5,000 to $7,500'.
The request is logged with coordinates, timestamp, and the signer's identity.
The sender receives an email notification with the comment details and a link to the document.
The sender uploads a revised version of the document — it replaces the original in the envelope.
A new version is created (v2) with the updated fields. The previous version (v1) is preserved.
All signers are re-notified with the updated document. Signing resumes from where it left off.
Comment pins stored with page, x_pct, y_pct, text, signer_id, timestamp in the change_requests table.
Revised document upload triggers a new PDF version (v2, v3, ...) with SHA-256 hash diff from previous.
Previous versions are retained (last 10 stored) — accessible for audit and dispute resolution.
When a revised document is uploaded, the envelope status resets to 'pending' and all pending signers are re-notified.
Traditional e-signature platforms force you to decline and restart when ANY change is needed. That means re-uploading the document, re-placing all fields, re-sending to all recipients — losing all progress. IUSign's change request workflow preserves completed signatures, maintains audit history, and only requires re-signing from the point of change.
Every revision creates a new PDF version with an incremental number (v1, v2, v3...). Each version has its own SHA-256 hash, and the diff between versions is computed and stored.
Public link signers (anonymous signers via shareable URL) cannot submit change requests — this is by design to prevent abuse.
Create your free account and send your first document in under 3 minutes.
Get Started Free