← D.C. Law 26-188 · All reviewed explanations

D.C. Law 26-188 · DC District of Columbia · Section 8

Pretrial reports and prearrest-diversion task-force dates

When it was enacted

Enacted 2026-07-02 · Effective 2026-10-02 · Permanent law.

Official record dates

Before

Actual pre-October2 Code already contained the September 30, 2026 detention-report dates/comparisons under earlier temporary Law 26-125, and the June 2025/July 31, 2026 task-force dates under earlier emergency or temporary versions including Act 26-386 and Law 26-95. LEARNS repeats these changes permanently; it does not first establish CJCC reports or the task force. The underlying amendment replaces relative applicability-based deadlines and specified comparison references, not the entire reporting or diversion framework.

Earlier official source

After

Part (a) sets September 30, 2026 for the CJCC defendant and juvenile pretrial-detention reports to the Mayor and Council and repeats the specified effective-date comparison changes described for Law 26-125 section 2. Part (b) requires the Prearrest Diversion Task Force’s initial meeting no later than June 2025 and its initial recommendations no later than July 31, 2026 for the specified misdemeanor offenses and categories of people identified under section 22-4237(f)(5).

Enacted source

In plain English

The retained defendant report includes the number and percentage with charges subject to the detention provisions, release and rearrest figures by the required offense categories, and time to rearrest for dangerous crimes or crimes of violence by underlying offense. The juvenile report concerns juveniles found to have a substantial probability of having committed a covered crime; it includes the relevant number/percentage, release or youth-shelter placement before factfinding/disposition, rearrests in those settings by underlying/rearrest offense, and time to rearrest for the specified serious offenses, with required offense breakdowns. The amendment changes reporting dates and comparison wording, not the legal test for detention, a finding of guilt, or a new duty for each defendant to file data. The named before/after periods should not be assumed to be mutually exclusive statistical windows. Actual report delivery, data quality, methodology, effects of detention policies, individual cases and complete current law remain unverified. The task force’s retained rule requires at least monthly meetings after the initial meeting until initial recommendations are issued, then meetings at the chair’s chosen frequency. Existing duties include assessing diversion practices and making program, resource and legislative recommendations, as well as the retained implementation and service-linkage functions. This section’s date changes do not themselves require that a particular person be diverted or guarantee avoidance of arrest. “No later than June 2025” supplies a month without specifying a day here. Actual meeting records, recommendations, program implementation and complete later/current law remain unreviewed.

Timing and applicability

Recorded effective October 2, 2026. Section 10(d) expressly applies section 8(a), the detention-report amendments, as of January 1, 2025. It does not assign that date to section 8(b), the task-force amendments. Section 10(a)’s fiscal gate covers sections 2 and 3, not section 8. The named report, meeting and recommendation dates precede the permanent law’s effective date; repetition does not restart them at October effect or prove timely performance, noncompliance or a particular legal remedy. Earlier emergency/temporary versions have separate dates and durations.

Explanation reviewed 2026-10-27.

Read the official section text
8 The Criminal Justice Coordinating Council for the District of Columbia Establishment Act of 2001, effective October 3, 2001 (D.C. Law 14-28; D.C. Official Code § 22-4231 et seq. ), is amended as follows: (a) Section 1505 (D.C. Official Code § 22-4234) is amended as follows: (1) Subsection (b-9) is amended as follows: (A) The lead-in language is amended by striking the phrase "no later than 180 days after the applicability date of section 30(f), (g), and (h) of the Secure DC Omnibus Amendment Act of 2024, passed on 2nd reading on March 5, 2024 (Enrolled version of Bill 24-345) ("Secure DC Omnibus")" and inserting the phrase "no later than September 30, 2026" in its place. (B) Paragraph (2) is amended by striking the phrase "and after the effective date of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (C) Paragraph (3) is amended by striking the phrase "and after the effective date of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (D) Paragraph (4) is amended by striking the phrase "and after the effective date of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (2) Subsection (b-10) is amended as follows: (A) The lead-in language is amended by striking the phrase "for juveniles" and inserting the phrase "for juveniles, no later than September 30, 2026" in its place. (B) Paragraph (2) is amended by striking the phrase "and after the applicability date of section 28 of the Secure DC Omnibus" and inserting the phrase "after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (C) Paragraph (3) is amended by striking the phrase "and after the applicability date of section 28 of the Secure DC Omnibus" and inserting the phrase "after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (D) Paragraph (4) is amended by striking the phrase "and after the applicability date of section 28 of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (E) Paragraph (5) is amended by striking the phrase "and after the applicability date of section 28 of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (F) Paragraph (6) is amended by striking the phrase "and after the applicability date of section 28 of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (G) Paragraph (7) is amended by striking the phrase "and after the applicability date of section 28 of the Secure DC Omnibus" and inserting the phrase ", after the effective date of the Prioritizing Public Safety Emergency, and after the effective date of the Secure DC Omnibus" in its place. (b) Section 1507 (D.C. Official Code § 22-4237) is amended as follows: (1) Subsection (g) is amended by striking the phrase "Within 3 months after the applicability date of section 29 of the Secure DC Omnibus Amendment Act of 2024, passed on 2nd reading on March 5, 2024 (Enrolled version of Bill 25-345)," and inserting the phrase "No later than June 2025," in its place. (2) Subsection (h) is amended by striking the phrase "Within one year after the applicability date of section 29 of the Secure DC Omnibus Amendment Act of 2024, passed on 2nd reading on March 5, 2024 (Enrolled version of Bill 25-345)," and inserting the phrase "No later than July 31, 2026," in its place.
Pinned official bulk source

Interpretations & later changes

Later-law and court review may be incomplete. Absence of an entry does not establish that the original provision remains in force.

No separately reviewed later development is published here yet.

Read the complete law guide and review status