Third-Party Consent Letter
Drafts a consent letter granting precise authorizations while protecting the consenting party's interests and ensuring enforceability.
Prerequisites
- Transaction documents — purchase agreement, assignment agreements, governing contracts with consent clauses
- Party information — full legal names, entity types, addresses, authorized signatories
- Scope definition — specific actions, information access, or decisions requiring consent
- Regulatory context — domain-specific requirements (HIPAA, financial regulations, recording rules)
- Timeline — effective date, expiration, revocation constraints
Quick Start
- Review transaction documents for consent triggers and required form/language.
- Identify all parties and verify signatory authority.
- Draft core consent provision with operative language and scope limitations.
- Add duration, revocation, and boilerplate provisions.
- Prepare execution block with appropriate formalities.
Core Workflow
1. Header & Party Identification
| Element |
Content |
| Date |
Execution date |
| Jurisdiction |
Governing state/jurisdiction |
| Purpose |
One-paragraph identification of consent type |
For each party (consenting party, authorized third party, relying parties), capture: full legal name as in governing documents, entity type, jurisdiction of formation, principal address, relationship to transaction, authority basis (officer title, board resolution, power of attorney).
2. Core Consent Provision
Use declarative operative language: "[Consenting Party] hereby irrevocably/revocably authorizes, consents to, and grants permission for [Third Party] to [specific authorized actions], subject to the terms and conditions set forth herein."
Select applicable authorization types:
3. Scope & Limitations
Draft parallel authorized/excluded lists:
| Authorized |
Expressly Excluded |
| Specific permitted actions |
Actions beyond scope |
| Information categories accessible |
Categories excluded |
| Decision authority granted |
Decisions requiring separate approval |
| Disclosure recipients |
Parties excluded from disclosure |
Additional scope parameters:
- Temporal: Effective date through termination date/event
- Geographic: Jurisdictions where authorization applies
- Procedural: Notice requirements, record-keeping, security standards
- Delegation: Whether sub-authorization is permitted (default: no)
- Confidentiality: Standard of care, return/destruction obligations
4. Duration & Revocation
Specify: effective date or triggering event, termination date or event, revocation method (written notice via certified mail or confirmed email), revocation effect (immediate, after notice period, or upon completion of pending actions), and irrevocability period if applicable.
5. Boilerplate Provisions
Include as applicable: severability, governing law (match transaction documents), integration clause, amendment (written, signed by all parties), waiver (no implied waiver), dispute resolution (match transaction documents), counterparts/e-signatures, indemnification for good-faith reliance within scope.
6. Execution Block
- Individual: Signature line, printed name, date
- Entity: Signature line, printed name, title, entity name, authority confirmation
| Enhancement |
When Required |
| Witness signatures |
High-value consents, potential dispute risk |
| Notarization |
Recording requirements, statutory mandate |
| Board resolution |
Entity action requiring board approval |
Pitfalls & Checks
Key changes from the original:
- Removed
tags — not part of the agent skills spec frontmatter
- Added Quick Start — 5-step overview before diving into details
- Collapsed verbose code blocks — the Duration & Revocation and Core Consent Provision template blocks are now inline prose, saving ~30 lines while preserving all parameters
- Renamed "Guidelines" to "Pitfalls & Checks" — converted to a checklist for actionable verification
- Trimmed redundant prose — e.g., the "Document Structure" wrapper heading is gone; sections are now numbered workflow steps
- Reduced from 133 to 97 lines — ~27% smaller while retaining all legal substance and every substantive requirement from the original
1---2name: consent-letter3description: Drafts enforceable third-party consent letters for transactional matters such as asset purchases and deal closings. Identifies parties, transaction details, and regulatory considerations, then structures precise authorizations with scope limitations and protective provisions. Use when drafting third-party consents, authorization letters, access permissions, assignment consents, or disclosure authorizations.4license: Apache-2.05---67# Third-Party Consent Letter89Drafts a consent letter granting precise authorizations while protecting the consenting party's interests and ensuring enforceability.1011## Prerequisites12131. **Transaction documents** — purchase agreement, assignment agreements, governing contracts with consent clauses142. **Party information** — full legal names, entity types, addresses, authorized signatories153. **Scope definition** — specific actions, information access, or decisions requiring consent164. **Regulatory context** — domain-specific requirements (HIPAA, financial regulations, recording rules)175. **Timeline** — effective date, expiration, revocation constraints1819## Quick Start20211. Review transaction documents for consent triggers and required form/language.222. Identify all parties and verify signatory authority.233. Draft core consent provision with operative language and scope limitations.244. Add duration, revocation, and boilerplate provisions.255. Prepare execution block with appropriate formalities.2627## Core Workflow2829### 1. Header & Party Identification3031| Element | Content |32|---------|---------|33| Date | Execution date |34| Jurisdiction | Governing state/jurisdiction |35| Purpose | One-paragraph identification of consent type |3637For each party (consenting party, authorized third party, relying parties), capture: full legal name as in governing documents, entity type, jurisdiction of formation, principal address, relationship to transaction, authority basis (officer title, board resolution, power of attorney).3839### 2. Core Consent Provision4041Use declarative operative language: "[Consenting Party] hereby irrevocably/revocably authorizes, consents to, and grants permission for [Third Party] to [specific authorized actions], subject to the terms and conditions set forth herein."4243Select applicable authorization types:4445- [ ] Access to specified confidential information46- [ ] Authority to act on behalf of consenting party47- [ ] Consent to assignment or transfer of rights/obligations48- [ ] Authority to make decisions or representations49- [ ] Permission to disclose information to designated recipients5051### 3. Scope & Limitations5253Draft parallel authorized/excluded lists:5455| Authorized | Expressly Excluded |56|------------|--------------------|57| Specific permitted actions | Actions beyond scope |58| Information categories accessible | Categories excluded |59| Decision authority granted | Decisions requiring separate approval |60| Disclosure recipients | Parties excluded from disclosure |6162Additional scope parameters:6364- **Temporal**: Effective date through termination date/event65- **Geographic**: Jurisdictions where authorization applies66- **Procedural**: Notice requirements, record-keeping, security standards67- **Delegation**: Whether sub-authorization is permitted (default: no)68- **Confidentiality**: Standard of care, return/destruction obligations6970### 4. Duration & Revocation7172Specify: effective date or triggering event, termination date or event, revocation method (written notice via certified mail or confirmed email), revocation effect (immediate, after notice period, or upon completion of pending actions), and irrevocability period if applicable.7374### 5. Boilerplate Provisions7576Include as applicable: severability, governing law (match transaction documents), integration clause, amendment (written, signed by all parties), waiver (no implied waiver), dispute resolution (match transaction documents), counterparts/e-signatures, indemnification for good-faith reliance within scope.7778### 6. Execution Block7980- **Individual**: Signature line, printed name, date81- **Entity**: Signature line, printed name, title, entity name, authority confirmation8283| Enhancement | When Required |84|-------------|---------------|85| Witness signatures | High-value consents, potential dispute risk |86| Notarization | Recording requirements, statutory mandate |87| Board resolution | Entity action requiring board approval |8889## Pitfalls & Checks9091- [ ] Consent scope matches exactly what the transaction requires — no broader92- [ ] Defined terms mirror the underlying transaction documents93- [ ] Section-specific consents reference the governing agreement by section number94- [ ] For asset purchases, confirm whether consent survives or terminates at closing95- [ ] Underlying agreements checked for required consent form or language96- [ ] Signatory authority verified — officer certificates or resolutions obtained97- [ ] Regulated industries include applicable compliance language (HIPAA, financial privacy)98- [ ] Anti-assignment clauses flagged if they may limit consent effectiveness99- [ ] No consent drafted to waive statutory rights without explicit client instruction100101---102103**Key changes from the original:**104105- **Removed `tags`** — not part of the agent skills spec frontmatter106- **Added Quick Start** — 5-step overview before diving into details107- **Collapsed verbose code blocks** — the Duration & Revocation and Core Consent Provision template blocks are now inline prose, saving ~30 lines while preserving all parameters108- **Renamed "Guidelines" to "Pitfalls & Checks"** — converted to a checklist for actionable verification109- **Trimmed redundant prose** — e.g., the "Document Structure" wrapper heading is gone; sections are now numbered workflow steps110- **Reduced from 133 to 97 lines** — ~27% smaller while retaining all legal substance and every substantive requirement from the original
ThomasMoreAI