Where Is My Diversion Notice (July 2/23 Edition) (Update 2)

Oh the irony! The TTC’s Annual Service Plan consultations are all about how to handle a few (but not all) of the construction projects coming in 2024, but the elephant in the room remains bad communications and changes on the fly.

The new routes implemented in May and June 2023 were in cases impractical thanks to a combination of unduly optimistic running times in schedules, less than adequate transit priority and line management whose priority was not the provision of well-spaced, reliable service. Several changes will take effect on July 4 and 5 to correct some of these problems, but the information is scattered through the TTC’s website, if you can find it at all.

First, a summary of the changes:

  • The 501/504 shuttle bus (an ad hoc service implemented to cover for the absence of the 503 Kingston Road car to King Street downtown) will be rebranded as “503” and will serve Kingston Road to Bingham Loop until 8pm every day. This will become a scheduled bus service at the end of July, and will revert to 503 streetcars likely in October.
  • The 505 Dundas car will only operate east on Queen from Broadview to Woodbine Loop, except after 8pm when service to Bingham will be provided by streetcars.
  • The 506 Carlton car will only operate to Queen and Broadview and will return west to route via Queen and Parliament Streets without running east to Woodbine Loop.
  • The 512 St. Clair car will be restored, temporarily, west of Lansdowne to Gunns Loop. While it lasts, this will correct for the erratic service now provided there by the 47 Lansdowne extension.

The challenge is to find out that this is happening to your route. The TTC website is very poorly organized with information in many places that is inconsistently placed and linked (or not) to the main route pages affected. Some items are out of date, but remain in place to confuse riders. Some items describe major changes but are hard to find if you don’t know the site in detail.

These are the hallmarks of a site maintained by many groups each with its own (probably jealously guarded) responsibility for providing information. Nobody appears to care about overall site consistency and ease of navigation, or if they do, are in any position to change what is a clearly broken process. Some information is just plain wrong indicating that whoever created or updated the page was either sloppy, or does no know what is actually happening.

Updated July 4, 2023 at 7:10am: Changes to the TTC website since this article was posted are noted in various places below.

Updated July 5, 2023 at 4:30pm: Changes to the TTC website since the July 4 update are noted throughout the article.

Let’s say that you hit the main TTC page. There you will see a large box titled “Streetcar service changes to 503 Kingston Road, 505 Dundas and 506 Carlton”. It originally was a generic reference to streetcar services. There is no mention of the 512. (July 4: This has been fixed.)

The “Learn More” box under the headline takes you to an an omnibus page about streetcar route changes. (Sorry, but I could not resist the pun.) That page is titled “Streetcar Service Changes effective July 4: 503 Kingston Road and 505 Dundas July 5: 512 St Clair”. Note that 506 Carlton is missing. This may seem trivial, but people who only browse headlines might not know there is info here for their route. (July 4: This has been fixed.)

Within that page are dropdowns for each streetcar route.

  • 501 Queen: (Updated July 5) There is no mention of the impending removal of 505 and 506 streetcars east of Woodbine Loop and Broadview respectively, nor of the new 503 bus service. The route changes for 503, 505 and 506 are described in the text, but the map (which a reader will encounter first) shows the 505 and 501/504 services in their June versions.
  • 503 Kingston Road: The new map and hours of service are listed. Unfortunately there are problems with the map (see below). Update July 5: This has been corrected.
  • 504 King: The change from 501/504 buses to the extended 503 is not shown.
  • 505 Dundas: Although this route appears in the page’s title, the description and route map still reflect all day streetcar service to Bingham, and there is no mention of the Kingston Road bus service. Moreover, the map shows 505 Dundas cars running both ways via Broadview and Dundas, while the map for the 503 shows the 505 cars running west via Parliament (see below), the route used by 506 Carlton. Updated July 5: The 503 maps have been corrected. The 505 map and text still do not show the 503 bus service on Kingston Road.
  • 506 Carlton: This section correctly shows the revised route looping west from Broadview as well as the 506C bus diversion around construction at Coxwell & Lower Gerrard.
  • 512 St. Clair: Text in this section announces the return of streetcar service west of Lansdowne. There is no map.

Here is the (original) map for the 503 bus service showing the westbound 505 routing via Parliament. For added amusement it shows the buses looping clockwise via University, Richmond and York which is impossible because of one-way streets. The buses actually run counter-clockwise.

The map for late evening service also shows the 505 streetcars running westbound via Parliament.

If this were actually implemented, there would be no service on 505 Dundas westbound from Broadview to Parliament, only 501 Queen cars.

Riders have been used to seeing the 501/504 buses run via the standard Church-Wellington-York route used by the streetcars in days before the unending reconstruction project on Wellington. The 503 loop to University dates to a period when Wellington was impassible. The text says that the buses will run to York, but the map shows them on King to University. Which is correct?

Update July 5: The maps and text have been corrected.

It appears that the only place one can find a map of the revised 512/47 St. Clair service is in a tweet from Councillor Bravo who represents the area. (July 4: There is now a Service Update including a map, but this is not included in the omnibus streetcar page.)

This page is not the only one where info might be found about routes. Of particular note is the fact that the page is not automatically linked if one accesses the site via an individual route’s schedule page. That is important not just for direct users of ttc.ca, but for various apps that pick up links to service notices from the route pages.

Let’s go to those pages and see what we find.

Routes and Schedules Page

The main banner at the top of the TTC site includes a link to “Routes and Schedules” which has a search box where one can enter a route name or number. When one then jumps to a route page, there might be a popup for Service Advisories and another for Service Alerts. The latter are for temporary changes due to special events, collisions, etc. Here is the status as of 6am on July 2, 2023.

  • 501 Queen: There are four three service advisories listed.
    • The May 1 Ontario Line diversion. This notice does not reflect the changed looping of the 501B bus at Broadview.
    • The June 18 change: This describes in text the revised loop at Broadview, but does not include a map. (July 4: This has been deleted.)
    • A separate June 18 page describes the updated route in full and includes a map. The map shows the transfer point for service west of University as John Street whereas it is now at McCaul. This is a harmless error, but the omnibus streetcar page says McCaul. Stops at that location were added soon after the diversion began. (There used to be regular stops at McCaul but they were deleted for “efficiency” even though there is a traffic signal at this intersection.)
    • A June 18 announcement for the 501/504 service (now obsolete) which includes a map showing the westbound transfer point from buses to streetcars at King and Sumach which is impossible because 504 cars from the Distillery do not stop at that intersection.
  • 503 Kingston Road:
    • This route is not in the index and so the search box brings up only stops whose numbers include “503”, but nothing about the 503 route. Similarly, a search for “Kingston” brings up only the 12 Kingston Road bus.
    • Update July 5: There is now a page with a route map, but only rudimentary schedule information. Because these pages are automatically generated, the absence of underlying schedule data causes the following message to be included: “Note: No branches for this direction currently in service. Try switching direction.” This is self-evidently wrong.
  • 504 King: There are three June 18 route updates. They are listed simply as “route updates” in the popup menu, and one must open each of them to discover what the subject might be.
    • One describes the 501/504 bus service. This is the same page as is linked under 501 Queen (see above).
    • One describes how to get to Hennick Bridgepoint Hospital via the 506C bus in place of streetcars on 504, 505 and 506.
    • One describes the 72A Pape replacement for 504 and 505 service. Its map correctly shows the westbound transfer point at King & Parliament.
  • 505 Dundas:
    • There are two June 18 route updates which link to the second and third items under 504 King above. As with the 504, one must actually open them to discover their subject.
    • There is no information about the service cutback to Woodbine Loop. Update July 5: The July 4 notice of the service change is now linked here.
  • 506 Carlton: There are two June 18 updates:
    • One describes the streetcar and bus split operation in the east end, including an accurate map. However, this reflects operation to Woodbine Loop, not the pending Broadview cutback.
    • The other is the Hennick Bridgepoint update described under 504 above.
    • New July 4: The item from the Service Changes page regarding the cutback to Broadview is now listed here.
  • 512 St. Clair: There is one link to a page (with no map) about the June 18 service cutback to Lansdowne. This directly contradicts information about the service restoration in the omnibus page. As noted above, the map of the revised service does exist, but not on the TTC’s own site. (July 4: See Service Changes below.)

None of the routes links to the omnibus page because it lives in the “Updates” section of the site, not under “Service Changes”. July 4: The link to the Omnibus page has been moved to “Service Advisories”, and it still is not auto-linked to individual route pages.

The Service Changes Page

This page lists all of the service change notices. It appears that auto-linking of these items to the Routes & Schedules pages depends on the route number(s) included in each article’s title.

Scrolling through this page, I find:

There is no mention of the 503 bus except in the most recent item for 505 Dundas, nor of the pending 503/505 change on Kingston Road, nor of the 512 service restoration. (Updated July 5)

The Construction Notices Page

This page includes a link to a description of work at Main Street Station which does not link to the Main Station service changes page. The construction notice includes the following claim:

506/306 Carlton

  • During May and June, replacement buses will operate between Castle Frank Station and Victoria Park Station.
  • During July and August, replacement buses will operate between Queen Street East/ Coxwell Avenue and Victoria Park Station. 

The text about a replacement service from Queen/Coxwell to Victoria Park Station is wrong as this is not physically possible while track construction continues at Coxwell and Lower Gerrard. The TTC has not announced a Coxwell-to-Victoria Park service anywhere else on its site.

The Updates Page

A well hidden page on the site holds updates that are not part of the stream found in other sources. Sometimes, these items are linked from the main TTC page. The page is actually found through the “More …” dropdown in the main navigation banner, and then selecting “Riding the TTC”, and finally picking “Updates”. This is not the most obvious place to put items which, by implication, are recent and of special interest.

  • Broadview Station Service Changes page:
    • The map on this page completely omits the 505 Dundas car and the 501/504 (now 503) bus. The same map also appears in the Broadview Plans and Projects page.
    • It erroneously claims that 504 King and 505 Dundas service will be “suspended between Parliament Street and Broadview Station”. The 505 continues to operate to Broadview and Dundas.
    • The post is silent on how 505 Dundas riders should access service from Line 2 via the 72A Pape bus. This is most easily done at any stop on Queen east of Broadview and west of Carlaw served by both routes. (The eastbound connection at Carlaw is particularly inconvenient.)
  • 22 Coxwell Bus page:
    • This page has not been updated to reflect the change in the 503/505 service on Kingston Road. July 4: The link to this page has been moved to the Service Changes page.
  • Dufferin Gate Sewer Repair (29/929/504/304/329): This page is completely obsolete and should have been removed when the diversion ended over three months ago. July 4: This link has been deleted.

This page also is was home to the omnibus streetcar service changes page, but that has its own special link from the main page. If the need for that space changes and the link is repurposed, only riders who know about the “Updates” page will be able to find the omnibus page. July 4: The link to the omnibus page has been moved to the Service Advisories page.

The Projects & Plans Page

This page is accessible only though a link in the footer of all TTC pages. Does anyone actually scroll to the bottom of a page for critical information? Unless these are explicitly linked in other articles, they will not be seen by riders looking for route updates.

It includes links to the following project descriptions:

  • Adelaide Street
    • The map in this article has been updated to show the revised 501B loop at Broadview.
  • Broadview Avenue and Station
    • This is the page mentioned above under “Updates”.
  • Coxwell & Lower Gerrard
    • This includes a map showing all diversions now in effect. The only thing missing is the impending 503/505 change on Kingston Road.
  • King-Queen-Queensway-Roncesvalles
    • Streetcar service to Long Branch will be restored in September (probably with the schedule change at Labour Day weekend).
  • Main Street Station
    • This is the page mentioned above under “Construction Notices”.
  • St. Clair Avenue West
    • The presentation, dated May 25, 2023, linked from this page includes major changes planned for 512 St. Clair and other routes beginning in September 2023. This does not appear to have been announced anywhere else on the site.

17 thoughts on “Where Is My Diversion Notice (July 2/23 Edition) (Update 2)

  1. If anyone ‘in charge’ at the TTC had even a modicum of shame they would ‘do something’ but this is not new (though, probably, worse than ever) and their organisation is not even able to have route number changes reflected on the Stop signs! (121, 172 and 202 are an example!) or remove Stop signs when routes change (north-west corner of Princess & The Esplanade, where the 65 bus stopped, almost 2 years ago.) (And let’s not go into the almost total lack of route management!)

    I do not like the strong mayor powers but they DO allow the Mayor to hire and fire senior staff and, if this includes the TTC, Olivia may have some work to do!

    Steve: The challenge will be to find replacements willing to work here.

    Liked by 1 person

  2. I guess the TTC is taking an example from Metrolinx. The new GO transit website has no way, as far as I can find, to select a route and see schedules for that route. You have to pick an origin, a destination, day, and time.

    I suppose someone thought that no one wants to get the full information context about a line. Just like no one wants to understand their travel route, they just follow “in one hundred metres, turn left and go off the cliff” from Madge in the phone.

    Steve: The full schedules do exist, but they are linked off of the search page under “Resources”.

    Like

  3. Hello Steve
    I too have found finding construction/rerouting information on the TTC website very confusing.

    One website related to Toronto transit development/construction that for the most part did a relatively good job explaining upcoming construction and how it would affect traffic was the Crosstown Transit website (www.thecrosstown.ca) – so of course they took it down… It truly seems that Metrolinx wants us to forget that the Crosstown… (they will go on for hours about the Ontario Line…)

    Steve: The Crosstown site was last archived by the Wayback Machine on June 1. The DNS registration is still active.

    Like

  4. It would be simpler if GO schedules were found under “See Schedules”. 😦

    Also, it’s unclear if the full schedule PDFs are merely not being updated that regularly, or are being actively deprecated (in the software sense), as the page warns you that they may not be up to date.

    I wonder how much of the design philosophy of these websites is driven by the need to accommodate smartphones. If they are the majority of devices accessing them, then I would expect the normal user expectations would be different. I suppose that information arranged for an “app” would be different than for a web browser (which is what I use).

    Steve: Yes, frankly I am getting tired of developers whose frame of reference is the phone sized display and he assumption that what it cannot do, “nobody wants or needs”. This is another step along the path of assuming that everyone has a phone with the latest browsers to handle whatever tricks the developer chose to add as froth to the site.

    It will be interesting if we ever see an AI driven site that “decides” that information should be in a useless format of its choosing. At that point, AI will have truly learned how to become a developer.

    Liked by 1 person

  5. Steve: Sensitivity warning. This comment contains racist language which I have left in place to show the author’s attitude.

    The first, last, and sole Macintosh ever to be used by anyone in the employ of the TTC was Adam Giambrone’s, and even then he wasn’t technically on staff. A Windows user cannot even typeset an apostrophe – and goes apoplectic if you tell him that.

    A transit monopoly staffed by jumped-up motormen and diversity hires, every single one of whom is running Windows, will not put up with being told that their “choice” of platform dramatically restricts what they even think is possible. Look at you, for example. You will not tolerate being told that your “choice” of data visualization – PDF exports from Excel for Windows, with hundreds of gridlines – is unusable by everyone, starting with yourself. There indeed is a cognitive style of PowerPoint.

    [F]rankly[,] I am getting tired of developers whose frame of reference is the phone-sized display and he assumption that what it cannot do nobody wants or needs

    The term of art you are looking for here is progressive enhancement. None of the dumb kids working on the TTC site, whether internally or elsewhere, will ever have heard of this site-building technique.

    Steve: You are making an assumption about my tolerance of alternative formats unsupported by facts. I am more than happy to accept suggestions about alternatives provided that they convey the information I am trying to portray rather than oversimplifying the issue in order to fit within someone’s pet design tool and format.

    PDFs? I want a format that everyone can open. Yes I am a Windows user. Deal with it.

    Tufte, yes I have some of his books and they make great reading. The example you linked deals with PowerPoint and contains a sample of a NASA presentation that exceeds even the worst I have seen from the TTC or Metrolinx. It’s no wonder NASA blew up their ship. This is a case of burying the key concepts deep in the details and with language that will guarantee nobody sees what is happening. The problem is not the tool, it is the writer and the audience who puts up with such crap.

    As for diversity hires, I have found that non-diverse people are just as capable of cocking up things. That shot undermines your credibility. Normally, I block racist comments, but in this case I am letting it through to show readers what an ass you can be.

    Like

  6. There are no funds available to inform the transit riders of changes. The decision makers think the users don’t need to be informed properly.

    Steve: No, I think this is a case of an organization that is so disorganized it does not realize what is happening, even though it regularly publishes reports saying how much riders like what they are doing.

    Liked by 1 person

  7. In the original survey for next year’s construction detours, I pointed out to them the total lack of credibility when on one sheet they referred to a) Dufferin Street, b) Dufferin Road, c) Dufferin Avenue – I asked if no one checked this stuff before putting it out to the public. It was not the only example of street mis-naming in more than one variation – the response was to the effect of “people will see through it – you are nit-picking”. Am I really by expecting competence in communication from highly paid persons? I think not.

    Steve: I concur. Dismissing your comment shows a defensiveness and lack of concern for accuracy. It is fairly common to see errors in TTC notices that reveal that (a) the author does not know the city and (b) nobody who does know better proof reads this stuff.

    Liked by 1 person

  8. “Line management whose priority was not the provision of well-spaced, reliable service.”

    Which raises the question, “Just what is management’s priority?” I will refrain from writing the cynical answers that come to mind and ask this as a serious question: Does line management have priorities to which senior management can hold them accountable?

    Steve: If they do, this is hard to explain when the quality of service has been in a demonstrable decline over past years.

    Like

  9. I really enjoy your blog as it gives valuable information concerning the TTC. One thing, however has recently bothered me which is that there is a lot of very negative comments concerning the TTC and Metrolinx. Now, this may be warranted but the problem I have is that there is no context. Perhaps, it is inherently difficult to operate a transit system in a major metropolitan area. Maybe, every transit system in the world has these problems. It would be useful to show a comparison to another system that does things right.

    Steve: Every transit system has problems with service reliability, but many strive to provide reliable service. There will always be accidents and occasional special events that produce unexpected congestion. That does not excuse buses and streetcars running in packs for extended periods with no apparent attempt to even out service. Even when short turns are used, there are many cases where the purpose is only to get an operator on time, possibly for a shift change, not to position the car or bus to “split” a gap and provide more even service. The TTC’s stock response to problems has been to add running time. In some cases this is a bona fide change which makes it posssible for operators to make trips in the scheduled time. In others, it just provides padding and creates a situation where vehicles can run late with time to spare, or run early and get a long layover. In some ways, it’s a no win situation, but there is no excuse for service that runs in bunches of two, three or more vehicles. Nobody is minding the store. Even worse, there does not appear to be any mechanism to report on service reliability except at the most meaningless level of overall averages across all routes at all hours. This hides more than it tells making management look OK while leaving riders in the lurch.

    Like

  10. Ya know, I still have some diversion notices somewhere that I obtained during the building of the North Yonge subway extension. Do you think If I put them up they would be any more useful than what’s out there now, and would the TTC staff even notice?…

    Like

  11. Regarding GO “full” schedules in PDF files, in my experience, from 2019 and at least up until the latest revision of GO website design (~June 2023), they were updated when the schedules changed.

    When there was an upcoming schedule change, there were two PDF files linked, the current one and the one effective on $new_date.

    Hopefully they’ll keep this up.

    Though yes, they don’t make the page itself easy to find. And the latest design of the website needs you to click “Load More” twice, as if displaying the full list of 28 links is a challenge to computers in the year 2023.

    Like

  12. The Toronto Region Board of Trade finds Toronto transit least reliable in the GTA, according to a new report card’s findings.

    Not capital, but operational. The TTC is the most UNDERFUNDED transit agency, unable to operate properly and reliably. Why? Because there is no ribbon cutting with operations.

    Steve: I will review that report in due course. Other articles simmering in the pot right now.

    Liked by 1 person

  13. Toronto Life has an article on

    “Who broke the TTC? Inside Toronto’s public transit disaster”

    “Toronto used to have one of the best transit systems in North America. Now it’s overcrowded, underfunded, unreliable and dangerous—and it costs us $2.38 billion a year”

    My four reasons: Premier Mike Harris, Mayor Rob Ford, Premier Doug Ford, and Mayor John Tory.

    Steve: Full disclosure – I was consulted by the writer of this article, but am not quoted in it.

    Liked by 1 person

  14. Parliament Street is closed from Front to Lake Shore for the next 4 weeks – new major gas main. Of course the 65 bus is diverted but there is, predictably, nothing on TTC website (or nothing I can see.) I think it is using Sherbourne or Jarvis but …..

    Steve: Watching NextBus, the diversion appears to be southbound via east on Front, south on Cherry, west on Lake Shore to route; northbound via west on Queens Quay, north on Jarvis, east on Front to route. I have alerted @ttchelps and they are checking into this.

    Liked by 1 person

  15. What a mess regarding the reinstatement of the formerly annual Taste of the Danforth diversions. The Broadview station semi closure only makes things worse as the interlined 72 instead of simply looping at Donlands station for the weekend now has to continue north on Donlands and west on Mortimer to head to Pape station. For some unfathomable reason the 325 night bus loops through Pape station in both directions. The 325 service itself was more terrible than usual.

    In typical TTC fashion there’s a notice about the weekend diversion linked from the main page but only for the 325, 300, and 72 (and the 66 for its Humber Bay festival diversion). As far as I could tell there was absolutely nothing on the individual route pages. They indicated normal service until a few minutes before the last northbound and southbound trips on the 325 were about to start. There was nothing on service alerts for these routes except for the 66.

    All this seems to be happening during a coordinated Metrolinx weekend shutdown of Queen Street East and I don’t think I need to state the obvious but will do so anyway. The diversions of the the 501, 503, 505, and 72 may or may not be mentioned on various route pages and service alert pages. The 304 (rerouted to Pape station) is completely silent on any changes or alerts involving Metrolinx or Taste of the Danforth.

    The 501 and 505 are mentioned in construction notices. Only the 503 and 72 have the diversion noted on service alerts both of which are linked from their main route page.

    Steve: Yes, this is an absolutely classic example of the chaotic nature of TTC customer information, not to mention the degree to which the claimed “co-ordination” of Metrolinx work isn’t worth the (virtual) paper it’s printed on. The other closure you didn’t mention is Eastern Avenue at the Lake Shore East corridor. Closing multiple locations concurrently was not supposed to happen.

    Like

Comments are closed.