Retired · October 25, 2026
Active work on this project ended on October 25, 2026. The published material remains available as a dated archive. Retirement does not mean that unresolved questions have been answered or requests fulfilled.
TRAP is no longer soliciting signatures, submissions, outreach, testimony, or recurring follow-up. The Portland Porch and CALL WAITING remain active.
The research below was reviewed October 7, 2026. That date is separate from this retirement notice. Later correspondence, including Metro replies on October 13 and 14, exists and must not be treated as no response. This archive does not claim a complete re-review through October 25.
Historical project record · reviewed October 7, 2026
Portland Transportation Recovery Accountability Plan
I need a way to get around Portland. Residents should be able to see who owns the work, what can happen now, and what would have to change for service to recover.
TRAP began with public testimony to JPACT on September 17, 2026. This project followed the institutional record from that appearance into written requests, agency responses and the documents behind transportation decisions. The aim is a usable public account of responsibility and recovery.
The original 60-day checkpoint was November 16. It was my requested follow-up, not a statutory deadline or an agency promise. That follow-up is retired; the October 7 countdown is no longer current.
Read the historical petition · Read the original framework · Follow the published encounter history
The Recovery Accountability Ask
TRAP asked for a simple public implementation record. An explanation of the budget matters, but residents also need to see the decisions, owners and measures attached to the work.
| What the public needs to see | What would answer it |
|---|---|
| Who owns the work | A named institution and responsible decision owner. |
| What can happen now | Specific actions available under existing authority and resources. |
| What depends on someone else | The institution, funding or approval needed, and who owns the handoff. |
| What recovery means | A defined service baseline, measure and threshold for restoration or mitigation. |
| When the public can check again | The next public decision or reporting date. |
| How decisions were reached | The recommendation, alternatives, final decision, approving authority and documented reason. |
| Where resident participation appears | Confirmation and a locator for inclusion in the official public record. |
These fields were the checkpoint tests. The records responses below provide evidence to examine some of them. They do not by themselves supply a recovery plan.
What Changed On October 6
TriMet's records custodian responded to all three filed requests. The records work has moved from waiting for a response to assessing the response and the offered documents. Each request has a different outcome.
The two productions offered through TriMet's portal have not yet been retrieved or reviewed. This page attributes the availability notices to TriMet and does not characterize the unseen files.
Bus Stop Rules And Authority
Request M000018-092826. Response received October 6 at 11:32 a.m. Pacific.
The request sought current rules for placing, moving, rejecting, removing or consolidating bus stops, including authority, approval requirements and documentation rules as in effect September 25.
TriMet says it reviewed its files, located responsive records and made them available through its Public Records Center. It waived fees because the total cost was under $10. Its notice states that this automatic waiver is limited to one per requester per consecutive 90-day period.
Finding recorded October 7: responsive records have been offered. Their contents and completeness have not been assessed.
What the review needs to establish: who may recommend and approve a stop decision, which rider-access and safety criteria apply, what exceptions require, how decisions are recorded, and what reconsideration route exists. Written rules and compliance in a particular decision are separate questions.
Departures From Technical Planning Recommendations
Request M000020-092826. Response received October 6 at 11:24 a.m. Pacific.
The request sought existing requirements for approving and documenting a decision that changes, rejects, delays or otherwise departs from a technical Service Planning recommendation about routes, stops or service levels.
TriMet says it has no records responsive to that specific request. It points to Chapter 18 of its Code as a partial response.
Chapter 18 sets out procedures for route, schedule and fare changes, including hearing thresholds and exceptions. Section 18.20(E) requires timely public comments to be provided to the Board before final action on changes requiring a hearing, and permits several forms of presenting those comments. Section 18.30 addresses documented Title VI equity analysis.
Finding recorded October 7: the cited Code is a relevant policy reference. It does not, on its face, establish the full requested trail connecting an original staff recommendation, a changed outcome, an approving person and a recorded rationale.
What remains open: whether other existing delegation or documentation rules address that trail, and which repositories TriMet searched. The response does not establish an undocumented practice or improper influence.
Feedback Records And The JPACT Briefing
Request M000019-092826. Response received October 6 at 12:05 p.m. Pacific.
The request sought final public-feedback summaries, existing comment-count tables, categorization methodology and briefing material prepared or supplied for the September 17 JPACT Transit Work Group discussion, including the records used to assess negative feedback and the balance of service-reduction choices.
TriMet says it has no records responsive to that specific request. It separately offers a September 17 briefing touching on service reductions through its portal, at no cost.
Finding recorded October 7: related briefing material has been offered. The offered material must be reviewed before saying whether it supplies any requested counts, definitions or analytical basis.
TriMet's published outreach page separately reports 8,138 winter 2026 survey responses and changes to proposals affecting twelve bus lines. Those published totals do not answer how feedback was counted or characterized for a particular later discussion. They also mean this investigation cannot accurately claim that TriMet collected no feedback.
What remains open: the relevant reporting period, channels, category definitions, treatment of duplicate comments and the relationship between the briefing and any public characterization. Any attribution of exact spoken language will require verification against the meeting recording.
Work left unfinished at retirement
Document review, clarifications, further outreach, and follow-up on the recovery request were planned. They are not being carried forward. The existing records and unresolved questions remain available; retirement does not establish completion or success.
Who Controls What
TriMet was the focus of this review because its service decisions, operating rules and decision records are central to these requests. Its Board considers changes within its authority; staff and management hold relevant planning, delegation and implementation records. This inquiry needs the responsibilities documented precisely.
Portland, Metro and other institutions will enter the next action only when the evidence identifies something they control, fund or approve. A corridor project may involve several road or funding authorities. That does not make every regional meeting an appropriate place to repeat the same demand.
Retired checkpoints
The weekly TRAP reviews, proposed October meeting participation, and November 16 follow-up are retired. No new appearance, records request, reporting cycle, or deadline is promised.
The Encounter History
The published ledger preserves the earlier testimony, submissions, administrative replies and commitments. Its existing nine entries were released September 26 and retain their individual verification dates. The October 7 release adds the October 6 responses without rewriting those earlier encounters.
Sending, receipt and inclusion in an official meeting record are separate facts. An invitation or administrative acknowledgment does not reset the waiting interval for a substantive implementation response. A message without a stated response date is pending, rather than automatically overdue.
The generated chronology and approved redacted supporting excerpts are available in the published encounter history linked above.
Sources And Review Method
This update uses TriMet's October 6 records-custodian responses, the filed request scope, TriMet Code Chapter 18, TriMet's records process and its service-cut outreach page. Published correspondence excerpts are redacted and approved for release. Private communications and confidential leads are excluded.
The review date is October 7, 2026. Portal productions are unreviewed. The records responses do not resolve the separate question of official inclusion of the September 23 updated testimony. No claim about wrongdoing or the cause of an individual decision is made here.
For a factual correction to this archive, email hi@kaitlinquinn.com with the subject “Portland TRAP archive correction,” the affected page, and the correction and source. This is not intake for new project work, and no investigation or response schedule is promised.