Durham Region Transit

SERIES-EXISTS (GOV-ATLAS-SERIESAUDIT-d1 2026-08-02): prior no-series note OVERTURNED; 1 doc row(s) located and verified. Prior note: DRT is a Durham Region division not separate corp

Current this library's internal records: Five Year Service Strategy 2026 to 2030 (2026)

Completeness

• Document shelf: 1 row (1 archived · 0 staged · 0 pending · 0 missing)
• Backgrounder: on file
• Strategy-evolution brief: on file
• Custody audit: 1 of 1 row(s) audited, all clean
• Last verified: 2026-08-03 · this org has NOT had a full discovery-verification pass (our discovery-verification log)

Endpoints

• Website
• Open data
• API: checked — none found
• RSS: checked — none found
• Newsroom
• FOI / access requests: checked — none found

Document shelf (1 row)

Backgrounder

Source: this library's internal records — a mechanical research draft, not independently reviewed for publication; reproduced as-is.

Durham Region Transit - backgrounder

Backgrounder / 2026-08-02 / registry row: durh-durham-region-transit (this library's government-document registry) / lens file for this org's series briefs

Mandate & statutory basis

Durham Region Transit (DRT) is a division of The Regional Municipality of Durham, an upper-tier municipality, not a separately incorporated body (registry row: durh-durham-region-transit, org_type: division, parent_org: durh-durham-region; notes: "DRT is a Durham Region division not separate corp"). Its statutory basis is the Region's general municipal authority to provide services, including transportation systems, under the Municipal Act, 2001, S.O. 2001, c. 25 (https://www.ontario.ca/laws/statute/01m25); the Act's "local board" definition covers bodies such as transportation commissions "established or exercising any power under any Act with respect to the affairs or purposes of one or more municipalities" (fetched 2026-08-02), though DRT itself is organized as a Regional department under Council rather than an arm's-length commission. ⚠️ still being checked — the specific by-law establishing DRT (Durham Region amalgamated several local transit systems into DRT in 2006, per general public-record knowledge) was not independently confirmed against a primary source this review.

Roles, responsibilities & scope

DRT plans and operates conventional and specialized transit service across Durham Region's eight local municipalities. The Region's captured planning document for DRT — the 2023-2032 Transit Service and Financing Strategy — was only recoverable via Internet Archive and returned a stub (445 characters, insufficient for content extraction; this library's internal records), so its substantive service-scope claims are not independently confirmed here. DRT publishes a Five Year Service Strategy (2026 to 2030) per the registry (registry row: durh-durham-region-transit, plan title/url fields), not independently read in full this review beyond the registry citation.

Governance & reporting line

As a Regional division, DRT has no independent board; it reports through Regional administrative staff to Durham Regional Council (registry row: durh-durham-region-transit, parent_org: durh-durham-region). DRT's budget and business plan are approved annually by Regional Council as part of the Region's consolidated budget process, alongside other Regional programs (2022 Durham Region Transit Business Plan and Budget, within: Proposed 2022 Property Tax Supported Business Plans and Budgets, Report #2022-F-4, https://www.durham.ca/media/3calh04a/proposed-2022-property-tax-supported-business-plans-and-budgets.pdf, fetched 2026-08-03).

Budget scale

The 2022 Business Plan and Budget for Durham Region Transit was approved at a total net property tax requirement of $68,089,000, with a 2022 Capital Program of $16,100,000 gross and a 2023-2031 Capital Forecast of $390,650,000 (Report #2022-F-4, Recommendations U-W, https://www.durham.ca/media/3calh04a/proposed-2022-property-tax-supported-business-plans-and-budgets.pdf, fetched 2026-08-03). ⚠️ still being checked — a current (2026) DRT operating budget figure was not located in the captured document set this review; the 2022 figure is the most recent confirmed from primary sources on file.

Institutional history

⚠️ still being checked — DRT's founding date and predecessor-agency history were not independently confirmed against a primary source this review.

Strategy evolution brief

Source: this library's internal records — a mechanical research draft, not independently reviewed for publication; reproduced as-is.

Durham Region Transit - strategy evolution

2026-08-02 / registry: durh-durham-region-transit / grounded in archived copies (cited document id + sha256) / read through our research file for that body

TL;DR: This brief cannot report a priority addition or drop — the single archived document for this org is not the report it claims to be. durh-durham-region-transit-sr-2023 (711c52188c14) is a captured Wayback Machine landing/calendar page for the 2023-2032 Region of Durham Transit Service and Financing Strategy (Report #2023-F-5), not the underlying PDF report itself — 445 characters of Internet Archive UI chrome ("Wayback Machine / 6 captures / 02 Jun 2023 - 19 Aug 2025 / ... success / fail / About this capture / COLLECTED BY / Collection: Canada Domain Harvest 2025..."), with zero characters of the actual transit strategy document's content. This is a 0-usable-document record: 1 registry row, 1 archived row, 0 TRUE usable. The stub detector correctly flagged this as stub-suspected (reason: "below char-count floor for doc_type='subject-report' (445 < 2500 chars)") and that call is confirmed correct on read. No claim about DRT's stated priorities, service strategy, or financing plan can be made from this record. The open, load-bearing fact for a future capture pass: the locating lane reports that Durham Region's committee-document host (escribemeetings.com) 403s on every direct fetch, which is gating real committee-report series for multiple GTA orgs, including this one — see Residuals & gaps.

Backgrounder summary

This org now has its own backgrounder, our research file for that body (Wave 1, 2026-08-02), which did not exist when this brief was first written. The backgrounder confirms DRT is a division of The Regional Municipality of Durham, not a separately incorporated body, operating under the Region's general municipal authority to provide transportation systems under the Municipal Act, 2001; as a Regional division it has no independent board and reports through Regional administrative staff to Durham Regional Council. Critically, the backgrounder was able to establish content this brief's own document (a Wayback Machine landing-page capture failure, see below) could not: citing a different primary source (Report #2022-F-4, "Proposed 2022 Property Tax Supported Business Plans and Budgets"), it records a 2022 DRT Business Plan and Budget approved at a total net property tax requirement of $68,089,000, a 2022 Capital Program of $16,100,000 gross, and a 2023-2031 Capital Forecast of $390,650,000 — figures this brief cannot independently confirm from its own single, unreadable document but does not contradict either. The backgrounder flags the same structural access problem this brief's Residuals section identifies independently: Durham's committee-document host difficulties gate primary-source access for DRT and other Durham-area bodies alike. ⚠️ still being checked (backgrounder): a current (2026) DRT operating budget figure was not located; 2022 is the most recent confirmed figure on file anywhere in this corpus for this org.

Series inventory

_index.json: 0 ok / 1 stub-suspected / 0 extract-failed.

Registry (our document registry): boot-message facts state 1 row for this org, 1 archived, 0 TRUE usable / 1 stub-suspected. No staged or missing rows were reported beyond this single archived-but-unusable row.

ZERO USABLE DOCS → honest archive-failure record, per LANE_SPEC §Format / that batch’s own build note §A2, using the CPPIB (fed-canada-pension-plan-investment-board) template. All seven required section headers are retained below; the evolution sections state plainly that no evolution narrative is possible and do not speculate about the target document's content.

Priority evolution

⚠️ still being checked — no priority-evolution narrative can be constructed from this archived record. The single captured document (durh-durham-region-transit-sr-2023, 711c52188c14) is not the 2023-2032 Region of Durham Transit Service and Financing Strategy itself; it is a Wayback Machine capture-index page describing that document's URL and capture history, containing no report text. Because no report text was read, this brief makes no claims — sourced or otherwise — about DRT's stated service priorities, financing strategy, or any change in them. Any such narrative would have to be invented rather than grounded in text actually read, which the task's hard rules prohibit.

Priorities added, dropped, renamed

⚠️ still being checked — not determinable from the archived record. No doc in this org's series yielded readable report content (see Priority evolution and Residuals & gaps), so no additions, drops, or renamings of DRT service priorities, routes, or financing mechanisms can be traced or cited to a document id/sha256 for this review.

Budget & mandate inflection points

⚠️ still being checked — the archived record yielded no budget, service-level, or mandate figures for Durham Region Transit in this review. The document's title alone ("2023-2032 Region of Durham Transit Service and Financing Strategy," Report #2023-F-5, Finance and Administration Committee) implies the underlying report would contain a ten-year service and financing plan, but no figure from that plan was actually read, so none is asserted here. No external, non-archived source was consulted to fill this gap, consistent with the task's grounding rules.

Ontario/Toronto relevance

⚠️ still being checked — cannot be substantively established from the archived record. What can be said without speculation: Durham Region Transit is, by its own document title and registry classification, the transit agency of the Regional Municipality of Durham, a GTA regional municipality directly east of Toronto (711c52188c14, title field). No further Toronto-specific relevance (e.g., named GO Transit integration, cross-boundary routes into Toronto, or Metrolinx coordination) can be confirmed because no report content was read in this review. This brief does not assert direct or indirect Toronto relevance beyond DRT's basic institutional identity as a GTA regional-municipal transit body, since asserting more would require content not actually read.

Residuals & gaps

• Capture failure, sole document in series: durh-durham-region-transit-sr-2023 (711c52188c14) was captured as a Wayback Machine landing/calendar-interstitial page rather than the target PDF's rendered content. The archived url field (https://web.archive.org/web/20250819093931/https://www.durham.ca/en/resources/2023---2032-Region-of-Durham-Transit-Service-and-Financing-Strategy-2023-F-5-.pdf) points at a Wayback Machine "capture calendar" wrapper around the target PDF rather than a direct memento fetch of the PDF bytes; the recorded content_type is text/html, confirming the crawler captured the IA UI wrapper, not the PDF. The visible captured text is entirely Internet Archive chrome: capture-count ("6 captures"), a capture-date timeline (Jun 2023-Aug 2025), a "success/fail" capture-status legend, a "Canada Domain Harvest 2025" collection description, and a repeated timestamp/URL line — no transit-strategy content of any kind.
• Detector call confirmed correct. The stub detector flagged this document stub-suspected with stub_reason: "below char-count floor for doc_type='subject-report' (445 < 2500 chars)". On read, this call is fully correct — the 445 characters are exclusively IA interface text, zero of which is report content. No disagreement with the detector found in either direction for this org's one-document set.
• Root cause, as far as observable from the file: this looks like a specific Wayback Machine capture-mechanics failure (the crawler fetched the IA calendar/landing wrapper URL rather than resolving through to a direct memento of the PDF) rather than a bot-wall or interstitial-notice pattern (contrast the LAC/publications.gc.ca "Information Archived on the Web" pattern seen in the StatCan and CPPIB reference briefs, which is a different failure mode). A future capture pass should retry against a direct Wayback memento URL for the PDF (typically of the form https://web.archive.org/web/<timestamp>if_/https://www.durham.ca/...pdf, using the if_ iframe-content modifier or an explicit content-type-aware fetch) rather than the bare capture-history URL currently recorded.
• Committee-document host blocker, named per the locating lane's report: Durham Region's committee-document host, escribemeetings.com, returns HTTP 403 on every direct fetch attempted by the locating lane. This is gating real committee-report series (agendas, staff reports, and committee minutes that would carry primary DRT service/financing content) for multiple GTA-area organizations, not just this one. Until that 403 is resolved — via an alternate access path, a different crawl user-agent/header strategy, or a negotiated feed — committee-sourced primary documents for Durham-area transit and related bodies will continue to be unreachable by direct fetch, and any archived copies will have to come from third-party mirrors or Wayback Machine captures (with the capture-mechanics caveat above also applying).
• Registry status until 2026-08-02: per the lane's boot-message facts, this org had no recorded document series prior to this review. The prior absence was not a disclosure gap on DRT's part — the underlying 2023-2032 Service and Financing Strategy report demonstrably exists (it has a title, a Regional report number #2023-F-5, and a Durham.ca URL) — it is a capture/archival gap: the crawl pipeline reached a Wayback Machine wrapper page instead of the report's actual content, and no other path to the report has yet been captured.
• Recommended remediation (not performed in this review): (1) re-fetch the target PDF via a direct Wayback memento URL rather than the capture-calendar page; (2) attempt a direct fetch of durham.ca's hosted copy of the report if still live; (3) once the escribemeetings.com 403 is resolved, check whether the Finance and Administration Committee's original agenda package (which would have transmitted Report #2023-F-5) is retrievable there as an alternate source. Until one of these succeeds, this org's strategy-evolution history remains entirely unestablished.
• ⚠️ Still being checked: no claim in this brief beyond DRT's basic institutional identity (a Durham Region transit body) and the capture-failure diagnosis above is grounded in text actually read — everything else about DRT's mandate, service area, budget, or strategic priorities remains unknown from this review.
• ⚠️ still being checked (carried from backgrounder): a current (2026) DRT operating budget figure was not located anywhere in this corpus; the backgrounder's 2022 figures ($68,089,000 net property tax requirement; $16,100,000 2022 capital program; $390,650,000 2023-2031 capital forecast) are the most recent confirmed, sourced from Report #2022-F-4 rather than this brief's own (unreadable) sr-2023 document.
• Backgrounder reconciliation, 2026-08-02: this brief was written before the org's Wave-1 backgrounder existed. The backgrounder now exists and does not contradict anything in this brief — this brief made no substantive claims to contradict, since its sole document is a capture failure. The backgrounder does add grounded content this brief lacked (2022 DRT budget figures, sourced independently from Report #2022-F-4) and corroborates this brief's own diagnosis of a structural Durham committee-document access problem. Only the Backgrounder summary section was rewritten to cite and summarize the org's own backgrounder; the zero-usable-document finding and capture-failure diagnosis in the rest of this brief stand unchanged, since the boot-message hard constraints bar re-analysis of documents and this is a reconciliation pass, not a rewrite.