← All d.c. tools

D.C. Tool 8: Drafting the due process complaint on the D.C. model form

Reviewed previewThis page shows the reviewed public portion and the exact outline of the member edition.What the labels mean

THE RULE

Every District due process complaint starts from the same document: the OSSE due process complaint model form, currently the version revised January 12, 2022 (DC-Tool 8 rests on 34 C.F.R. §§ 300.508(b), 300.509; ODR SOP § 401.A; the current OSSE model form). The form is voluntary in the sense that federal law does not require you to use the state's model, but in D.C. practice it is where nearly every complaint begins, because it already contains the elections the SOP regime asks you to make and skipping it means reconstructing those elections from scratch in prose.

The federal content floor is six elements: the child's name; the child's address of residence; the name of the school the child attends; for a homeless child or youth, available contact information for the child and the name of the school the child is attending, in place of a fixed address; a description of the nature of the problem, including facts relating to the problem; and a proposed resolution of the problem, to the extent known and available to the party at the time (34 C.F.R. § 300.508(b)). The District adds to that floor rather than substituting for it. The controlling local-content citation is 5-A DCMR § 3049.2, not the SOP's restatement of the federal six elements, and it requires the parent's own name and address (not only the child's), a clear statement of which LEA the child is enrolled in versus which LEA or agency the complaint is filed against when the two differ, and identification of both the school the child is attending and the school the complaint is filed against, if that is a different school. Where a proposition in an earlier draft of this rule cited SOP § 405.C for the D.C.-specific additions, that citation was corrected: SOP § 405.C only restates the federal six elements, and the local additions live in the DCMR.

The form's respondent field is not a formality, it is the decision from DC-Tool 7 made concrete. You will name DCPS, or the specific charter LEA, or OSSE as the state agency, or DYRS for a committed youth housed at New Beginnings or the Youth Services Center, or some combination when the facts touch more than one. Get this wrong and you have filed a complaint against an entity that owes your child nothing, while the entity that does owe your child something has never been served.

Three elections live inside the form itself, and each is a decision this Part teaches in its own tool. The mediation election asks whether you want ODR to schedule mediation alongside or instead of the resolution session; DC-Tool 13 tells you honestly how often that produces anything. The resolution-period waiver checkbox asks whether you want the 30-day resolution window to run its course or whether you and the respondent have already agreed in writing to skip it and accelerate the clock toward hearing; DC-Tool 12 is built entirely around that choice. The expedited flag marks a complaint arising from discipline, which routes to Volume I, this field manual's discipline-track sibling, rather than the ordinary hearing track this volume, Volume II, covers (DC-Tool 1).

Once filed, the complaint fixes your issues. A party may not raise issues at the due process hearing that were not raised in the complaint unless the other party agrees (34 C.F.R. § 300.511(d); 20 U.S.C. § 1415(f)(3)(B)). D.C. practice holds this line strictly absent written consent paired with a resolution-meeting opportunity, or IHO permission to amend granted no later than five days before the hearing begins (DC-Tool 8 rests, on this point, on the confirmed rule that issue preclusion attaches at filing absent that consent-and-opportunity pairing or a timely IHO-permitted amendment). Everything in your claim inventory from DC-Tool 2 that you intend to litigate has to be on this page, in this filing, or it does not exist for the hearing officer.

WHY IT MATTERS

The complaint is the only document in the entire proceeding that a hearing officer with no subpoena power, no discovery, and a five-business-day disclosure deadline (DC-Tool 20) can be certain both sides have read closely before the case moves. Everything downstream, the LEA's response, the resolution session's agenda, the prehearing order's issue list, the burden allocation itself, is built off what this document says. A vague complaint produces a vague case, because there is no discovery process in the District to sharpen it later.

The respondent field carries a cost that the New York manuscript's readers never had to price. In a single-district system, naming the wrong party is a clerical error the district's answer corrects. In the District's two-sector system, naming the wrong charter LEA, or naming DCPS when a charter school is your child's own LEA, or missing the DYRS obligation for a committed youth, can mean weeks lost while ODR and the parties sort out who was actually supposed to be sued, against a resolution and hearing clock that does not pause to wait (DC-Tool 7).

The issue-preclusion rule punishes the same instinct Part I already warned about: naming every grievance to be safe. A complaint that names ten issues to protect against missing one arrives at the resolution session and the prehearing conference carrying nine issues nobody has time to actually prepare, and the strongest claim gets diluted rather than sharpened. The fix is not caution, it is precision: name what your inventory supports, cite what supports it, and leave the door open for amendment under 34 C.F.R. § 300.508(d) rather than trying to plead every possibility on day one.