Addendum header
Reference the base agreement by date and title, and state this document is an addendum so it attaches to the original contract and inherits key terms where applicable.
The addendum prevents misidentification of parties, documents chain of title, and delays in completing transactions by documenting trust identity, trustee authority, and any limitations on action. It reduces downstream disputes by providing a concise, signed record that counterparties and financial institutions can rely on.
Common users include legal teams, trustees, corporate records staff, and financial institutions that need verified documentation of trust ownership or authority.
The document bridges the trust instrument and commercial agreement so organizations can verify authority without accepting the full trust instrument in every workflow.
Reference the base agreement by date and title, and state this document is an addendum so it attaches to the original contract and inherits key terms where applicable.
Provide the full legal name of the trust, formation date, and any trust tax identification number (EIN), so financial institutions and payors can match records accurately.
State the trustee(s) by legal name, describe their authority and any limits, and reference the trust instrument section that grants signature or disposition powers.
Describe the interest held by the trust in the business or asset, including percentage ownership or class of interests to avoid ambiguity for tax and governance purposes.
Specify the governing state law for interpretation and dispute resolution and note any forum or jurisdiction requirements tied to corporate documents.
Include signature blocks for trustees, dates, notary acknowledgement if required, and any witness lines to meet state or institutional requirements.
| Field | Configuration | Required | Format and validation |
|---|---|
| Signer authentication | Email plus SMS code recommended |
| Conditional fields | Show trustee fields only when trust indicated |
| Template naming | Use consistent naming for version control |
| Bulk send | Enable for multiple recipients when applicable |
Choose a platform that produces tamper-evident signed PDFs, supports common file types, and can attach supporting documents like trust instruments.
Ensure the provider you use supports audit trails, retains a certificate of completion, and—if you handle protected health information—provides HIPAA BAA options. Platforms vary in advanced authentication, bulk-send, and API features; choose based on your security and integration needs.
Execute before or at closing to prevent funding holds.
Allow 3–10 business days for account or title updates.
Record within 30 days of execution.
Provide certified copies within 14 calendar days if requested.
File immediately where state recordation is required.
| 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 trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |