Whereas, The Parties Agree That This Revocation Is To Be Effective Upon Execution In Form
Use a WHEREAS, The Parties Agree That This Revocation Is To Be Effective Upon Execution In template to make your document workflow more streamlined.
What this revocation form does
This document records the parties’ agreement that a stated revocation becomes effective upon execution. In practice, the parties identify the earlier agreement or obligation, state the revocation language, and sign the same final record. Under ESIGN, 15 U.S.C. chapter 96, and applicable UETA provisions, an electronic signature may satisfy a signature requirement when intent, consent, attribution, and record retention are established. The exact effect still depends on the document’s wording, governing law, and any required notarization, filing, or court procedure.
Who uses this revocation form
Contracting parties
Contracting parties use this revocation form to cancel, withdraw, or replace an earlier agreement when the document’s operative clause makes effectiveness conditional on execution by the parties.
Legal operations
Legal and operations teams use the completed record to verify signer identity, execution sequence, effective wording, and the relationship between the revocation and the original agreement.
Legal standing of this revocation
For a U.S. business transaction, this revocation can be admissible when the parties show intent, consent, signer attribution, and a retained reproducible record under ESIGN, 15 U.S.C. chapter 96, and applicable UETA law. It does not replace wills, codicils, testamentary trusts, court orders, official court filings, or family law decrees.
Recommended setup for this revocation form
Configure signer identity, signature evidence, access controls, and retention before sending this revocation form for execution.
| Setting | Recommendation |
|---|---|
| Authentication method | Email link with SMS OTP |
| Signature type | Typed or drawn e-signature |
| Audit trail | Export certificate of completion |
| Document retention | Retain under applicable agreement |
| Encryption | TLS 1.2/1.3 and AES-256 |
Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.
Complete this revocation form in signNow
Use this sequence to prepare the revocation, collect execution evidence, and preserve the completed record.
Upload form:
Upload the revocation document to signNow. Check fields:
Review detected fields and add missing signer fields. Add signers:
Enter the parties’ email addresses and signing order. Send document:
Send the revocation for electronic signature. Store record:
Download the executed copy and audit trail.
Platform requirements for signing
Complete this revocation form in Chrome or Edge on Windows, Safari on macOS or iOS, or the signNow mobile apps for iOS and Android. Use an internet connection supporting TLS 1.2 or TLS 1.3.
Desktop browsers Chrome and Edge on Windows Apple devices Safari on macOS and iOS Mobile apps signNow apps for iOS and Android
Organizations can route the revocation through managed Windows, macOS, iOS, or Android devices. Enterprise deployments may connect signNow with SSO, APIs, and named systems such as Microsoft 365 or Google Workspace, while retaining the executed PDF and audit trail according to the governing agreement and applicable law.
Privacy pitfalls in revocation workflows
A revocation may expose contract dates, party names, addresses, or account details to unintended recipients if signer assignments are not checked. A signer may execute without reviewing the electronic-record disclosure or understanding that the revocation changes the parties’ prior agreement. Shared templates can preserve an outdated Whereas clause, execution condition, or party role after the underlying agreement has changed. Broad administrator permissions may allow a user to alter recipients or fields without a documented approval step.
State rules and document exclusions
Excluded documents
Court filing rules
State procedure
Notary requirement
Record-keeping practices for this form
Preserve the exact revocation text, signer evidence, audit trail, and retention rule that governs the underlying agreement.
Export the executed record
Set the applicable retention period
Secure the document archive
Verify party intent before sending
How the audit trail supports this form
The audit trail connects the parties, actions, timestamps, final revocation text, and completion record without replacing the agreement’s governing legal requirements.
Authenticate signer:
Record timestamp:
Track document history:
Preserve integrity:
Export certificate:
Control access:
Processing stages for this revocation
The document moves from exact wording review through signer delivery, execution, and preservation of the completed record.
Prepare document
Deliver to signers
Collect signatures
Archive completion
Troubleshooting this revocation workflow
Resolve field, signer, evidence, plan, and legal-scope issues before relying on an executed revocation form.
Upload the original PDF again, then inspect signNow’s detected fields before sending. Auto-detection may not recognize every blank or signature line in a clause-based revocation. Add signer, date, and acknowledgment fields manually where the document requires them, and confirm each field is assigned to the correct party.
Use signNow’s Business Premium plan when this revocation must be sent to many separate parties through bulk send. Business includes templates and audit trails, while the product ground truth identifies bulk send as a Business Premium feature. Confirm the intended recipient data before generating invitations.
A signNow audit trail records the signing event, timestamps, actions, and document history. Export the certificate of completion with the executed revocation. Under ESIGN and UETA, retain a record that accurately reflects the transaction and remains accessible for later reproduction.
For a consumer-facing revocation, review the electronic-record disclosure requirements in ESIGN, 15 U.S.C. §7001(c). The signer must receive required consent information and be able to access the electronic record. signNow can capture the signing workflow, but legal sufficiency depends on the transaction and disclosure process.
If the revocation concerns a will, codicil, testamentary trust, court order, official court filing, or family law decree, do not rely on ordinary electronic execution. ESIGN excludes these categories. Check the applicable state law, court rules, or Secretary of State requirements before sending it through signNow.
Business is priced at $8 per user per month with annual billing and includes legally binding eSignatures, audit trails, templates, mobile apps, ISO 27001, SOC 2, and GDPR coverage. The product ground truth states that paid plans include 100 signature invites per user annually, with overage fees.
Key performance indicators that demonstrate SignNow's proven track record.
BE READY TO GET MORE
Get this form now!
If you believe that this page should be taken down, please follow our DMCA take-down process.