regulatory-complaint-drafting

name

regulatory-complaint-drafting

description

Drafts structured regulatory complaints, demand letters, and multi-recipient filing packages with jurisdiction-appropriate citation and first-person assertive voice. Use when the user needs to draft, revise, or format complaints to any government agency, regulatory body, or institutional grievance channel. Covers ADA Title II/III complaints, HIPAA/OCR filings, state medical board complaints, Ohio pre-suit notices, demand letters, FDCPA disputes, CFPB complaints, FTA complaints, and multi-agency escalation packages. Also use when the user says "file a complaint," "draft a demand letter," "write to the agency," "escalate this," or references any regulatory body by name. If the user describes being wronged by an institution, this skill applies.

Regulatory Complaint Drafting

Rules

IF the user provides facts about an institutional wrong: THEN identify the target recipient(s) before drafting. Each recipient gets only the statutes, regulations, and exhibits within their authority.

IF multiple recipients are involved: THEN build a core facts memo first. All derivative letters share one factual chronology. Vary only jurisdiction statement, legal basis, relief requested, and exhibit scope.

IF the user does not specify a recipient: THEN infer from the facts. Medical provider misconduct routes to the State Medical Board of Ohio. Privacy violations route to HHS OCR Region V. Institutional policy failures route to ODH. Disability discrimination routes to DOJ or HHS OCR depending on entity type. State the inference and proceed.

IF drafting for OCR (HIPAA): THEN never use criminal framing. Cite 45 C.F.R. Part 164 subsections. State the date the user first learned of each violation (180-day timeliness under 45 C.F.R. 160.306(b)(3)).

IF drafting for the State Medical Board of Ohio: THEN never request monetary relief. Frame as a request for investigation under Ohio Rev. Code 4731.22.

IF drafting an Ohio pre-suit notice of intent: THEN keep the notice procedural. Do not include detailed allegations. The notice triggers tolling under Ohio Rev. Code 2305.113(B). Reserve allegations for the civil complaint.

IF the record is incomplete: THEN return a recipient-ready outline, issue list, and missing-facts checklist. Do not invent allegations to fill gaps.

Structure

Draft recipient letters in this order:

1. Header: complainant identity, address, date, recipient address.
2. Introduction: respondent, complaint type, requested relief (2-3 sentences).
3. Jurisdiction statement: statute or regulation establishing authority.
4. Factual background: chronological. Use a table when multiple incidents or actors are involved.
5. Legal basis: number each violation. Tie each to a dated fact and supporting exhibit.
6. Exhibits: list only exhibits relevant to that recipient.
7. Relief requested: only remedies that recipient can provide.
8. Attestation and signature block.

Voice

First-person assertive. Direct. No hedging unless the user requests softer language. No em dashes. Use colons or semicolons for parenthetical context.

Filing order (multi-recipient)

1. Internal grievance (preserves records, exhausts informal remedies).
2. Ohio Department of Health (institutional review).
3. State Medical Board of Ohio (individual licensure review).
4. HHS OCR Region V (federal privacy and access review).
5. Pre-suit notice of intent (tolls civil SOL, preserves civil track).

Validation

Before delivery, confirm:

• Each complaint stays within the named recipient's authority.
• Each violation ties to a dated fact and supporting exhibit.
• Dates, actor names, and institutional names are consistent across the package.
• The output includes the draft, exhibit list, and any missing-facts note.

References

• references/recipient-system.md: Full recipient-by-recipient authority, filing rules, coordination matrix, and current statutory citations for the Ohio Project five-recipient workflow.