Plan Identifier
Exact plan or plat number, revision date, and file name so the document unambiguously references the correct drawing or exhibit.
A written acknowledgement creates an auditable record of who accepted a plan and when, reducing later disputes over scope, approvals, or notice. Electronic acknowledgements are generally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes where adopted.
Several parties commonly complete or sign this acknowledgement depending on the transaction type and local process.
Use depends on role: developers and owners usually produce the plan; agents, title officers, and government reviewers sign to confirm acceptance and readiness to proceed.
Exact plan or plat number, revision date, and file name so the document unambiguously references the correct drawing or exhibit.
Legal description or parcel identifier (lot, block, subdivision, or county parcel number) to tie the plan to the recorded property.
Full legal names and roles of all signers (owner, developer, reviewer, title agent) with organization names where applicable.
Clear statement that the signer has reviewed the plan and accepts any listed conditions, exceptions, or required corrections noted in the acknowledgement.
Date when the acknowledgement takes effect and when any obligations or review periods begin, entered consistently across the document.
Reference to supporting exhibits such as marked-up plans, conditions of approval, or permit numbers appended to the acknowledgement.
| Workflow Field Name Header Row | Recommended Setting |
|---|---|
| Signer Authentication Method | Email link or SMS code for routine; KBA or MFA for high-assurance |
| Field Validation Rules | Require MM/DD/YYYY for dates; enforce parcel number format |
| Signing Order | Set owner, title, then municipal reviewer for sequential approval |
| Bulk Send Setup | Enable bulk sends for identical acknowledgements across multiple parcels |
Choose a platform that supports secure signatures, audit trails, and the file formats used by your stakeholders.
Ensure the chosen setup preserves an audit trail (timestamps, IP, signer identity) and stores completed acknowledgements in a secure repository with access controls and retention policies.
Complete upon final plan delivery or within contract-specified review period
Record as required by county or contract; local deadlines may apply
Title companies often require executed acknowledgement before closing
Some permits require signed acknowledgement before permit issuance
Retention begins on signature date for recordkeeping purposes
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Tim Martin, Founder, Martin Properties, streamlined plan approvals with online acknowledgements.
Dan Rotelli, CEO, BIS, selected a compliant eSignature workflow focused on ESIGN and UETA compliance.