Hereinafter Referred To As Grantor, Does Hereby Release, Remise, And Forever Form
Use a , Hereinafter Referred To As Grantor, Does Hereby Release, Remise, And Forever template to make your document workflow more streamlined.
What this release form does
This release form records a grantor’s decision to give up, transfer, or permanently release specified rights or claims to another party. Its legal effect depends on the exact property, claim, consideration, parties, governing law, and execution requirements written in the document. A signer should identify the released interests precisely, review any indemnity or reservation language, and confirm whether state law requires witnesses, notarization, recording, or separate disclosures. signNow can route an eligible release form for electronic signing, preserve the completed document, and attach an audit trail showing signer activity.
Who uses this release form
Property transactions
Property owners and grantors use the form to release claims, transfer defined interests, or document consent connected with a specific transaction.
Business agreements
Businesses and counsel use it for negotiated releases, settlement documentation, waivers, and other agreements requiring clear parties and signature evidence.
Features for this release workflow
signNow connects field preparation, signer routing, electronic execution, and audit-ready storage for eligible grantor release documents.
Field placement
Upload the release document and place grantor, grantee, date, initials, and signature fields without rebuilding the form from scratch.
Signing order
Route the release to multiple parties in a defined order when grantor approval must precede witness, representative, or counterparty signing.
Audit trail
Capture signer activity, timestamps, and document history in an audit trail connected to the completed release form.
Mobile signing
Allow signers to review and execute the release from a desktop browser or signNow mobile app when the transaction requires remote completion.
Record storage
Store the executed release with its completion certificate and supporting evidence for later contract, property, or dispute review.
Reusable templates
Use templates for recurring release language while requiring reviewers to confirm transaction-specific parties, property descriptions, and reserved rights before sending.
Complete and send the release form
Use this sequence to prepare the release language, collect signatures, and preserve evidence of execution.
Prepare document:
Upload the completed release form. Review fields:
Check grantor, grantee, property, and release language. Assign signers:
Add each signer and required signing order. Track signing:
Send the form and monitor completion.
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.
How the release workflow works
The signNow workflow keeps the document wording intact while organizing fields, signer routing, completion, and evidence.
Upload: Upload the grantor release document. Detect fields: Auto-detect fillable fields, then correct field assignments. Route: Send the release to grantor and counterparty signers. Archive: Store the executed form with its audit trail.
Platform requirements for signing
Use signNow in Chrome, Firefox, Safari, or Edge on Windows and macOS, or complete the release through the signNow apps for iOS and Android. A current browser and internet connection help ensure fields, signer routing, and the completed document display correctly.
Browsers Chrome, Firefox, Safari, Edge Desktop Windows and macOS desktops Mobile iOS and Android signNow apps
Organizations handling sensitive grantor or property information should manage access through approved devices and role-based permissions. Enterprise deployments can evaluate API access, SSO provisioning, and certificate or long-term validation requirements against the transaction, industry, and applicable state-law controls before enabling broad release workflows.
Recommended release form setup
Configure the release workflow around signer identity, execution evidence, secure transfer, and the retention rule for the underlying transaction.
| Setting | Recommendation |
|---|---|
| Authentication method | Email verification with SMS authentication |
| Signature type | Typed or drawn electronic signature |
| Audit trail | Export with completed release |
| Document retention | Three years from filing under IRC §6501(a) |
| Encryption | TLS 1.2/1.3 and AES-256 encryption |
Security controls for signed release forms
Data in transit:
Stored document protection:
Security assurance:
Information security:
Electronic signature law:
Healthcare data protection:
Retain the executed release properly
Accurate execution records matter because the form’s effect depends on its wording, signing evidence, and applicable state law.
Export the signed release and audit trail
Preserve every executed document version
Set retention by transaction type
Archive records with controlled access
Check state rules before signing
Notarization
Wills
Family law
Real-estate deeds
Avoid release form privacy pitfalls
Personal addresses, property details, and claim descriptions can be exposed when completed releases are shared beyond the intended parties. A grantor may sign without clearly demonstrating consent to electronic records, creating an evidence issue under ESIGN consumer-disclosure requirements. Broad release language can unintentionally waive claims or rights that the grantor intended to reserve for a separate transaction. Uncontrolled access to templates can cause outdated parties, property descriptions, or signature fields to appear in a newly issued release.
Key performance indicators that demonstrate SignNow's proven track record.
Release form questions and fixes
These answers address execution, authentication, plan selection, privacy, and recordkeeping issues specific to grantor release documents.
Upload the release as a PDF or supported document, then inspect every auto-detected field. signNow’s field tools allow the sender to correct missing or misplaced grantor, grantee, date, initials, and signature fields before sending.
A signed release can generally use electronic signatures for eligible transactions under ESIGN and applicable state law, including UETA jurisdictions. Confirm that the transaction is not a will, court filing, family law decree, or another statutory exception.
Use signNow’s signer authentication options when identity evidence matters, and preserve the audit trail with the completed document. Authentication supports attribution, but it does not replace a state-required notarial acknowledgment or witness requirement.
The Business plan includes legally binding eSignatures, audit trails, templates, mobile apps, ISO 27001, SOC 2, and GDPR support at $8/user/month when billed annually. Business Premium adds bulk send and kiosk mode at $15/user/month annually.
For healthcare-related releases containing protected health information, signNow is HIPAA compliant when a BAA is required. The release itself must still satisfy applicable authorization, privacy, and state-law requirements for the disclosed information.
Export the completed release and audit trail after signing, then apply the retention period for the underlying transaction. Federal tax records generally use three years from filing under IRC §6501(a), but state law or contract terms may require longer.
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.