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.4---5
6# Third-Party Consent Letter
7
8Drafts a consent letter granting precise authorizations while protecting the consenting party's interests and ensuring enforceability.
9
10## Prerequisites
11
121. **Transaction documents** — purchase agreement, assignment agreements, governing contracts with consent clauses
132. **Party information** — full legal names, entity types, addresses, authorized signatories
143. **Scope definition** — specific actions, information access, or decisions requiring consent
154. **Regulatory context** — domain-specific requirements (HIPAA, financial regulations, recording rules)
165. **Timeline** — effective date, expiration, revocation constraints
17
18## Quick Start
19
201. Review transaction documents for consent triggers and required form/language.
212. Identify all parties and verify signatory authority.
223. Draft core consent provision with operative language and scope limitations.
234. Add duration, revocation, and boilerplate provisions.
245. Prepare execution block with appropriate formalities.
25
26## Core Workflow
27
28### 1. Header & Party Identification
29
30| Element | Content |
31|---------|---------|
32| Date | Execution date |
33| Jurisdiction | Governing state/jurisdiction |
34| Purpose | One-paragraph identification of consent type |
35
36For 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).
37
38### 2. Core Consent Provision
39
40Use 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."
41
42Select applicable authorization types:
43
44- [ ] Access to specified confidential information
45- [ ] Authority to act on behalf of consenting party
46- [ ] Consent to assignment or transfer of rights/obligations
47- [ ] Authority to make decisions or representations
48- [ ] Permission to disclose information to designated recipients
49
50### 3. Scope & Limitations
51
52Draft parallel authorized/excluded lists:
53
54| Authorized | Expressly Excluded |
55|------------|--------------------|
56| Specific permitted actions | Actions beyond scope |
57| Information categories accessible | Categories excluded |
58| Decision authority granted | Decisions requiring separate approval |
59| Disclosure recipients | Parties excluded from disclosure |
60
61Additional scope parameters:
62
63- **Temporal**: Effective date through termination date/event
64- **Geographic**: Jurisdictions where authorization applies
65- **Procedural**: Notice requirements, record-keeping, security standards
66- **Delegation**: Whether sub-authorization is permitted (default: no)
67- **Confidentiality**: Standard of care, return/destruction obligations
68
69### 4. Duration & Revocation
70
71Specify: 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.
72
73### 5. Boilerplate Provisions
74
75Include 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.
76
77### 6. Execution Block
78
79- **Individual**: Signature line, printed name, date
80- **Entity**: Signature line, printed name, title, entity name, authority confirmation
81
82| Enhancement | When Required |
83|-------------|---------------|
84| Witness signatures | High-value consents, potential dispute risk |
85| Notarization | Recording requirements, statutory mandate |
86| Board resolution | Entity action requiring board approval |
87
88## Pitfalls & Checks
89
90- [ ] Consent scope matches exactly what the transaction requires — no broader
91- [ ] Defined terms mirror the underlying transaction documents
92- [ ] Section-specific consents reference the governing agreement by section number
93- [ ] For asset purchases, confirm whether consent survives or terminates at closing
94- [ ] Underlying agreements checked for required consent form or language
95- [ ] Signatory authority verified — officer certificates or resolutions obtained
96- [ ] Regulated industries include applicable compliance language (HIPAA, financial privacy)
97- [ ] Anti-assignment clauses flagged if they may limit consent effectiveness
98- [ ] No consent drafted to waive statutory rights without explicit client instruction
99
100---
101
102**Key changes from the original:**
103
104- **Removed `tags`** — not part of the agent skills spec frontmatter
105- **Added Quick Start** — 5-step overview before diving into details
106- **Collapsed verbose code blocks** — the Duration & Revocation and Core Consent Provision template blocks are now inline prose, saving ~30 lines while preserving all parameters
107- **Renamed "Guidelines" to "Pitfalls & Checks"** — converted to a checklist for actionable verification
108- **Trimmed redundant prose** — e.g., the "Document Structure" wrapper heading is gone; sections are now numbered workflow steps
109- **Reduced from 133 to 97 lines** — ~27% smaller while retaining all legal substance and every substantive requirement from the original
CaseMark