<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
@font-face
{font-family:"Aptos Display";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;
mso-ligatures:standardcontextual;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:.25in;
margin-right:0in;
margin-bottom:4.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:20.0pt;
font-family:"Aptos Display",sans-serif;
color:#0F4761;
mso-ligatures:standardcontextual;
font-weight:normal;}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
margin-top:8.0pt;
margin-right:0in;
margin-bottom:4.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:16.0pt;
font-family:"Aptos Display",sans-serif;
color:#0F4761;
mso-ligatures:standardcontextual;
font-weight:normal;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Aptos Display",sans-serif;
color:#0F4761;}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Aptos Display",sans-serif;
color:#0F4761;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#467886" vlink="#96607D" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Hi everyone,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>The saga continues. Remember all those routes that were on the chopping block, like, yesterday? Turns out all that was just for illustrative purposes. Sadly, this is no joke. See the below article.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>But what’s also not a joke is that 10% cuts will be on the table at the July 28 Board meeting. That said, the vote detailing which routes will actually get cut won’t happen until September.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Here’s what’s been going on over the past few days:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>On Tuesday, the Finance Committee met to vote for one of the scenarios outlined in my previous update. They chose to recommend no cuts at all.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>The Operations, Safety and Security Committee met last night, (Wednesday,) and they chose to recommend 10% route/service cuts.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>But again, the specific routes that would be cut under such a scenario won’t be voted on until probably September.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Meantime, on July 28, the Board will meet to decide which of these scenarios they will pursue, anything from no cuts at all to cuts of 20%.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>So, the Board still needs to hear from us on the 28<sup>th</sup>, and what they need to hear is:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>#1. If RTD wants to go to the voters in 2028 and ask for more money, they’ll have much better luck making that ask as an agency that has done its utmost to avoid cutting services. They should exhaust every other available option before they even start pondering which routes to cut.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>#2. Paratransit eligibility as it stands today must be locked in place, at least until the mandated independent paratransit study is completed and fully analyzed, which probably won’t happen until sometime in 2028.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Below, I’ll paste the article that was published in the Denver Post today. As you’ll read, it contains a doozy of a quote from Manager/CEO Deborah Johnson calling all those routes staff specified as merely illustrative of the cuts that would be required by each of the scenarios.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Bottom line: We still need you on July 28, but not to fight for particular routes, just to make it abundantly clear to the Board that cuts should be the absolute last thing they consider, and that paratransit riders should be insulated from any cuts they do make by locking in their eligibility as it stands today, at least until the independent paratransit study has been fully analyzed, which probably won’t happen until sometime in 2028.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>If they do decide to cut routes, they must direct staff to give them an analysis showing how many paratransit riders would be affected by each route or timespan cut they make.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I swear, I’m gonna have a heart attack by the end of the year at this rate.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Tim Keenan<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>State Transportation Chair<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>National Federation of The Blind of Colorado<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>P.s. Here’s the article:<o:p></o:p></span></p><h1>RTD panel recommends 10% bus, light-rail service cuts to save $31 million<o:p></o:p></h1><h2>RTD Board of Directors set to meet on budget on July 28, which could determine the future of the 16th Street FreeRide<o:p></o:p></h2><p class=MsoNormal><span style='font-size:11.0pt'>A committee of Regional Transportation District leaders voted Wednesday to recommend a 10% cut to bus and light-rail service to save the agency $31 million as the organization faces a steep budget deficit heading into the next fiscal year.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>RTD leaders this week also took a step back from a list of possible service cuts, including the 16th Street FreeRide and several light-rail lines, compiled by agency staffers after the Board of Directors asked for cost-saving scenarios to solve the $200 million shortfall.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>That list caused several Front Range residents to speak up during public comment at the agency’s operations committee meeting Wednesday night. The meeting was held virtually.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Doug Tisdale, leader of the Denver Downtown Development Authority and a former RTD director, spoke with disbelief at the idea that the agency would ever cut FreeRide, calling it “an exercise in magical thinking.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>“For decades it’s been the economic and logistical lifeline of downtown Denver,” Tisdale said. “We didn’t just endure a massive, multiyear rebuild of the 16th Street transit way to abandon it now.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Agency leaders repeatedly emphasized that the cuts detailed in the public documents are hypothetical. General manager and chief executive Debra Johnson described them as “just for illustrative purposes.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>“The board is not approving any cuts to any service at this time. Any service reductions will be proposed formally in the future and will be subject to public review,” Director Ian Harwick said, adding that what was compiled by staffers and what will be approved will be “very different.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>The committee’s recommendation will be passed on to the full RTD board, which is set to meet at the end of the month.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Even if the RTD board approves service cuts, directors won’t decide which specific lines and services to eliminate until a later time, likely September.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>The 5-2 vote from RTD’s operations committee stands in contrast to the finance committee’s occasionally contentious meeting Tuesday night, where directors rejected a proposed recommendation for $20 million in service cuts and instead voted for zero cuts.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>The finance committee also directed agency staffers to find ways to generate up to $12 million more in revenue through fare increases.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Several directors on the operations committee on Wednesday said they also support zero service cuts because they hope voters will pass a ballot measure to increase funding and solve the deficit while the agency could take on more debt or spend down reserves in the meantime.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>But that did not convince a majority of the committee.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Director Chris Nicholson said the only thing worse than making cuts now would be running out of money or making cuts while asking voters to approve a funding measure.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>“I’m not willing to play Russian roulette with the agency’s finances under the assumption that we pass a ballot measure in 2028,” he said.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>RTD’s Board of Directors is scheduled for a hybrid virtual and in-person meeting at 5:30 p.m. July 28 at agency headquarters, 1660 Blake St. in Denver.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p></div></body></html>