Amicus Coalition Management
Coordinates multi-organization amicus briefs from intake through filing. Prevents the most common coalition failures: unauthorized org listings, missed sign-off deadlines, incomplete disclosures, version proliferation, and unresolved policy disagreements.
Quick Start
- Gather intake (Checkpoint A below)
- Establish governance and backward timeline from filing deadline
- Align positions via Issue-Framing Memo
- Draft under single-pen authority with controlled circulation
- Resolve conflicts; escalate if needed
- Execute two-step sign-off protocol
- Verify disclosures, format cover/caption, file
Defaults (when user says "use defaults" or "just draft"): forum-agnostic draft with [VERIFY FORUM] markers; single-pen authority with lead counsel; sign-off cutoff 48 hours before filing deadline.
Checkpoint A: Pre-Draft Intake
Gather before drafting. Do not proceed until collected or gaps flagged.
- Docket — court, case number, caption, all deadlines
- Parties' briefs — opening, response, reply (as available); key orders
- Forum rules — word/page limits, disclosure requirements, consent/leave rules, cover formatting, e-filing specs
[VERIFY per forum]
- Coalition roster — full legal names, jurisdiction of incorporation, display names, entity types
- Approval pathways — authorized signatory per org, internal review chain, lead time
- Red lines — positions each org cannot support or endorse
- Counsel-of-record — names, bar numbers, addresses; pro hac vice needs
- Disclosure inputs — per FRAP 29(a)(4)(E) / Rule 37.6: who authored, who funded
- Posture — supporting which party (or neither); consent status or need for leave motion
Core Workflow
1. Governance and Timeline
| Element |
Action |
| Single-pen authority |
Lead counsel controls narrative; coalition provides input, not co-drafting |
| Authority map |
Per org: who commits to join, who approves final text, who speaks publicly |
| Backward timeline |
Filing deadline → sign-off cutoff → final proof → near-final draft → outline |
| Hard cutoff |
No sign-off by cutoff = excluded. No "pending approval" listings |
Send Workflow Memo at kickoff requiring: (1) one consolidated comment set by deadline, (2) written authorization by cutoff. State that absent authorization, the org will not be listed.
2. Position Alignment
- Gather each org's desired emphasis (economic, technical, historical, policy)
- Cross-check against parties' briefs to eliminate duplication
- Produce Issue-Framing Memo (1-2 pages): proposed argument headings, key factual propositions with citations, empirical/technical materials, posture
- Solicit red lines in writing before full draft
3. Draft Management
| Rule |
Rationale |
| One official draft, one sender |
Prevents version proliferation |
Naming: AmicusCoalition_Brief_Draft[N]_YYYYMMDD |
Version integrity |
| One point person per org, one consolidated comment set |
Avoids conflicting markups |
| Triage: (a) legal/argument, (b) factual/citation, (c) policy/branding |
Legal clarity governs over branding |
| All markup confidential (Model Rule 1.6) |
No forwarding outside coalition |
| Late new sections require equal-length cut |
Word-limit discipline |
4. Conflict Resolution
Conflict types:
- Core (org cannot be associated with the position) — narrow the position, modularize language, or allow withdrawal
- Expressive (emphasis/phrasing disagreement) — favor legal clarity and court credibility
Compromise patterns:
- Statutory avoidance: resolve on statutory grounds; address constitutional only if reached
- Narrow consensus: "Amici take no position on outer bounds of [test], but under any formulation, [party] prevails"
- Procedural framing: reframe around procedural deficiency vs. substantive policy
Escalation: Written issue log (contested text, positions, proposed resolution, deadline) → lead attorney → supported party's counsel if needed. Treat log as privileged work product.
Never draft language suggesting consensus where none exists (Model Rule 3.3).
5. Sign-Off Protocol
Two-step authorization:
- Join authorization on near-final draft — written confirmation from authorized person that org joins the brief substantially as circulated, with counsel authorized for non-substantive edits
- Final confirmation on filing version (if time permits)
| Rule |
Detail |
| Written only |
No verbal approvals |
| Verify signatory authority |
Policy staff enthusiasm ≠ institutional authorization |
| Track entity names precisely |
Distinguish association from its foundation |
| Re-confirm after substantive changes |
Post-sign-off changes require new authorization |
| Default to exclusion |
Missed cutoff = not listed |
6. Filing
Cover format [VERIFY per forum]:
BRIEF OF [LEAD AMICUS] AND [N] OTHER ORGANIZATIONS AS AMICI CURIAE
IN SUPPORT OF [PARTY]
Disclosures checklist:
Filing checklist:
Internal filing certification — record: authorizations received, orgs removed for missed cutoff, final word/page count, disclosure verification, filing method.
Checkpoint B: Post-Draft Review
After delivering initial draft, confirm:
- All orgs confirmed sign-off authority and review timeline?
- Remaining red-line conflicts needing escalation?
- Cover/caption format matches forum requirements?
- All disclosure inputs (authorship, funding) collected from every member?
Jurisdiction Notes
| Forum |
Key Requirements |
| Federal circuits |
FRAP 29; word limit varies by circuit; local rules on covers, e-filing, corporate disclosures; D.C. Circuit strict on non-duplication |
| U.S. Supreme Court |
Rule 37, Rule 33.1 (booklet format), green cover for merits; Rule 37.3 timing strictly enforced |
| State appellate |
Varies dramatically; many require motion for leave; different disclosure regimes [VERIFY] |
| Admin tribunals |
Unique rules/customs; require rule-based confirmation, not inference |
Always retrieve and cite current official rules for the specific forum. Flag all unverifiable procedural statements with [VERIFY].
Common Pitfalls
- Unauthorized listing — never list an org without timely written authorization from a verified signatory
- Disclosure gaps — collect authorship/funding info from every member, not just lead org
- Name mismatches — verify entity names character-by-character across all brief sections
- Fabricated consensus — do not attribute positions to orgs that have not approved them (Model Rule 3.3)
- Restating party briefs — brief must deliver unique contribution the parties' briefs do not
- Hallucinated rules — never fabricate forum rules or filing requirements; use
[VERIFY] for unconfirmed details
Guidelines
- Ethics: Treat each amicus as client for conflicts (Model Rules 1.7-1.10) and confidentiality (1.6); check conflicts before accepting any org
- Citations: Every non-record factual claim needs a pinpoint citation; flag unverifiable with
[VERIFY]
- Adversarial lens: Before filing, ask whether opponent could move to strike based on misstatements, undisclosed funding, or noncompliance
- Anti-hallucination: Use
[VERIFY] for all unconfirmed procedural details
- Attorney review required: All outputs require attorney review before filing
1---2name: amicus-coalition3description: Manages end-to-end workflow for multi-organization amicus coalition briefs in appellate courts. Covers single-pen drafting governance, position alignment, conflict resolution, documented sign-offs, FRAP 29/Rule 37.6 disclosures, FRAP 26.1 corporate disclosures, cover formatting for multiple amici, and compliant filing. Use when coordinating coalition amicus briefs, managing sign-offs, drafting joint friend-of-court briefs, handling multi-amici filing, or resolving inter-organization conflicts. Triggers on phrases like "coalition brief," "12 orgs joining this amicus," or "coordinate the amicus."4---5
6# Amicus Coalition Management
7
8Coordinates multi-organization amicus briefs from intake through filing. Prevents the most common coalition failures: unauthorized org listings, missed sign-off deadlines, incomplete disclosures, version proliferation, and unresolved policy disagreements.
9
10## Quick Start
11
121. Gather intake (Checkpoint A below)
132. Establish governance and backward timeline from filing deadline
143. Align positions via Issue-Framing Memo
154. Draft under single-pen authority with controlled circulation
165. Resolve conflicts; escalate if needed
176. Execute two-step sign-off protocol
187. Verify disclosures, format cover/caption, file
19
20**Defaults** (when user says "use defaults" or "just draft"): forum-agnostic draft with `[VERIFY FORUM]` markers; single-pen authority with lead counsel; sign-off cutoff 48 hours before filing deadline.
21
22## Checkpoint A: Pre-Draft Intake
23
24Gather before drafting. Do not proceed until collected or gaps flagged.
25
261. **Docket** — court, case number, caption, all deadlines
272. **Parties' briefs** — opening, response, reply (as available); key orders
283. **Forum rules** — word/page limits, disclosure requirements, consent/leave rules, cover formatting, e-filing specs `[VERIFY per forum]`
294. **Coalition roster** — full legal names, jurisdiction of incorporation, display names, entity types
305. **Approval pathways** — authorized signatory per org, internal review chain, lead time
316. **Red lines** — positions each org cannot support or endorse
327. **Counsel-of-record** — names, bar numbers, addresses; pro hac vice needs
338. **Disclosure inputs** — per FRAP 29(a)(4)(E) / Rule 37.6: who authored, who funded
349. **Posture** — supporting which party (or neither); consent status or need for leave motion
35
36## Core Workflow
37
38### 1. Governance and Timeline
39
40| Element | Action |
41|---|---|
42| Single-pen authority | Lead counsel controls narrative; coalition provides input, not co-drafting |
43| Authority map | Per org: who commits to join, who approves final text, who speaks publicly |
44| Backward timeline | Filing deadline → sign-off cutoff → final proof → near-final draft → outline |
45| Hard cutoff | No sign-off by cutoff = excluded. No "pending approval" listings |
46
47Send Workflow Memo at kickoff requiring: (1) one consolidated comment set by deadline, (2) written authorization by cutoff. State that absent authorization, the org will not be listed.
48
49### 2. Position Alignment
50
511. Gather each org's desired emphasis (economic, technical, historical, policy)
522. Cross-check against parties' briefs to eliminate duplication
533. Produce **Issue-Framing Memo** (1-2 pages): proposed argument headings, key factual propositions with citations, empirical/technical materials, posture
544. Solicit red lines in writing before full draft
55
56### 3. Draft Management
57
58| Rule | Rationale |
59|---|---|
60| One official draft, one sender | Prevents version proliferation |
61| Naming: `AmicusCoalition_Brief_Draft[N]_YYYYMMDD` | Version integrity |
62| One point person per org, one consolidated comment set | Avoids conflicting markups |
63| Triage: (a) legal/argument, (b) factual/citation, (c) policy/branding | Legal clarity governs over branding |
64| All markup confidential (Model Rule 1.6) | No forwarding outside coalition |
65| Late new sections require equal-length cut | Word-limit discipline |
66
67### 4. Conflict Resolution
68
69**Conflict types:**
70- **Core** (org cannot be associated with the position) — narrow the position, modularize language, or allow withdrawal
71- **Expressive** (emphasis/phrasing disagreement) — favor legal clarity and court credibility
72
73**Compromise patterns:**
74- Statutory avoidance: resolve on statutory grounds; address constitutional only if reached
75- Narrow consensus: "Amici take no position on outer bounds of [test], but under any formulation, [party] prevails"
76- Procedural framing: reframe around procedural deficiency vs. substantive policy
77
78**Escalation:** Written issue log (contested text, positions, proposed resolution, deadline) → lead attorney → supported party's counsel if needed. Treat log as privileged work product.
79
80Never draft language suggesting consensus where none exists (Model Rule 3.3).
81
82### 5. Sign-Off Protocol
83
84**Two-step authorization:**
85
861. **Join authorization** on near-final draft — written confirmation from authorized person that org joins the brief substantially as circulated, with counsel authorized for non-substantive edits
872. **Final confirmation** on filing version (if time permits)
88
89| Rule | Detail |
90|---|---|
91| Written only | No verbal approvals |
92| Verify signatory authority | Policy staff enthusiasm ≠ institutional authorization |
93| Track entity names precisely | Distinguish association from its foundation |
94| Re-confirm after substantive changes | Post-sign-off changes require new authorization |
95| Default to exclusion | Missed cutoff = not listed |
96
97### 6. Filing
98
99**Cover format** `[VERIFY per forum]`:
100```
101BRIEF OF [LEAD AMICUS] AND [N] OTHER ORGANIZATIONS AS AMICI CURIAE
102IN SUPPORT OF [PARTY]
103```
104
105**Disclosures checklist:**
106- [ ] FRAP 29(a)(4)(E) / Rule 37.6 authorship and funding — every member
107- [ ] FRAP 26.1 corporate disclosure — every corporate amicus
108- [ ] Consent of parties stated, or motion for leave attached
109
110**Filing checklist:**
111- [ ] Consent/leave requirements verified `[VERIFY]`
112- [ ] Service requirements confirmed (all parties, method, paper copies)
113- [ ] Final cite-check — every citation verified
114- [ ] All listed amici have timely written authorization
115- [ ] Counsel info complete; bar admissions satisfy forum requirements
116- [ ] PDF requirements met (bookmarks, fonts, OCR, color covers)
117- [ ] Word/page count within limits
118- [ ] Amicus list consistent across cover, interest statement, signature block, disclosures
119
120**Internal filing certification** — record: authorizations received, orgs removed for missed cutoff, final word/page count, disclosure verification, filing method.
121
122## Checkpoint B: Post-Draft Review
123
124After delivering initial draft, confirm:
125
1261. All orgs confirmed sign-off authority and review timeline?
1272. Remaining red-line conflicts needing escalation?
1283. Cover/caption format matches forum requirements?
1294. All disclosure inputs (authorship, funding) collected from every member?
130
131## Jurisdiction Notes
132
133| Forum | Key Requirements |
134|---|---|
135| **Federal circuits** | FRAP 29; word limit varies by circuit; local rules on covers, e-filing, corporate disclosures; D.C. Circuit strict on non-duplication |
136| **U.S. Supreme Court** | Rule 37, Rule 33.1 (booklet format), green cover for merits; Rule 37.3 timing strictly enforced |
137| **State appellate** | Varies dramatically; many require motion for leave; different disclosure regimes `[VERIFY]` |
138| **Admin tribunals** | Unique rules/customs; require rule-based confirmation, not inference |
139
140Always retrieve and cite current official rules for the specific forum. Flag all unverifiable procedural statements with `[VERIFY]`.
141
142## Common Pitfalls
143
144- **Unauthorized listing** — never list an org without timely written authorization from a verified signatory
145- **Disclosure gaps** — collect authorship/funding info from every member, not just lead org
146- **Name mismatches** — verify entity names character-by-character across all brief sections
147- **Fabricated consensus** — do not attribute positions to orgs that have not approved them (Model Rule 3.3)
148- **Restating party briefs** — brief must deliver unique contribution the parties' briefs do not
149- **Hallucinated rules** — never fabricate forum rules or filing requirements; use `[VERIFY]` for unconfirmed details
150
151## Guidelines
152
153- **Ethics**: Treat each amicus as client for conflicts (Model Rules 1.7-1.10) and confidentiality (1.6); check conflicts before accepting any org
154- **Citations**: Every non-record factual claim needs a pinpoint citation; flag unverifiable with `[VERIFY]`
155- **Adversarial lens**: Before filing, ask whether opponent could move to strike based on misstatements, undisclosed funding, or noncompliance
156- **Anti-hallucination**: Use `[VERIFY]` for all unconfirmed procedural details
157- **Attorney review required**: All outputs require attorney review before filing
CaseMark