Getting Around Boston Without Losing Your Mind
Boston's public transit system is old, inconsistent, and occasionally wonderful. The MBTA carries roughly 1.2 million riders on a good weekday. Some days it works beautifully. Other days you will be standing on a Platform reading a delay sign that says "20 minutes" and watching it tick to 45. This guide covers the trip planner and how to actually use it when things go wrong, because things will go wrong. The MBTA trip planner lives at mbta.com/realtimeplanner. You enter a starting point, a destination, and optionally a desired departure time. It returns a sequence of subway lines, bus routes, transfer walks, and estimated arrival times. That sounds straightforward. It is not straightforward in practice. Here is how I actually use it. First, I open the planner on my phone while I am still at my desk. I enter the destination and set the time for 10 minutes later than I need to arrive. The output usually shows two or three options. I pick the one with fewer transfers, not the fastest one. Fewer transfers means less chance of a missed connection or a platform change mid-walk.
Then I check the Real-Time tab. The planner does not bake live data into its base suggestions. The times you see are schedule-based predictions. When there is a delay, the Real-Time layer updates them. If I am leaving in under 15 minutes, I always refresh the Real-Time tab after I get the initial results. That single step saves people from showing up at a closed station or waiting for a train that already left. I also run a second search a few minutes later, sometimes with a slightly earlier departure. The planner can suggest different routing when the input window shifts, and occasionally the earlier option uses a bus that the later search drops because of timing quirks in the schedule model.
What the Planner Gets Wrong Regularly
The biggest blind spot is weekend service changes. The MBTA publishes alert calendars, but the trip planner does not always reflect every track work detour. On a Saturday in April, the planner routed me from Back Bay to South Station via the Red Line. The Red Line was shut down for track work between those stations. The alert was live on the website. The planner still offered it as a valid option with an estimated 12-minute travel time. It took me 38 minutes to walk the detour. I learned to cross-check the Service Alerts page before committing to a suggestion that involves any weekend segment of the Red, Orange, or Green Lines. Another issue is bus scheduling confidence. Buses show up with green reliability badges sometimes and gray ones other times. A gray badge means the planner could not predict arrival within a reasonable window. You will still get a suggested time, but treat it like an estimate with wide bounds. During morning rush on the 55 or the 66, a 12-minute predicted wait can become a 28-minute wait if the bus is running behind schedule. In those cases I switch to a walking or bike option if the distance is under two miles.
Get the Full Details
Transfer Walks Are the Hidden Time Cost
The planner shows transfer times, but it does not always capture how long a physical walk takes with stairs, elevators out of service, or confused signage. Park Street to Green Line takes about four minutes if the escalator near the Red Line exit is working. If it is not, you are doing stairs with luggage or a stroller, and that walk stretches to nine or ten minutes. I keep a small list of known weak transfers: Porter to the bus plaza, Back Bay to the Railyard bus stops, Forest Hills to the bus loop. When the planner suggests any of those, I add five minutes to the displayed transfer time myself. It is faster than guessing at the platform and realizing you picked the wrong exit.
When the Planner Fails Completely
There are scenarios where the tool offers no useful answer. Late night service between midnight and 5 a.m. is sparse. If you need a ride at 1:15 a.m. from Dorchester to Cambridge, the planner will show you a route that involves a bus and a subway and takes over an hour. It will not show you the shuttle bus options that sometimes replace segments, and it will not include rideshare pricing or availability. In those cases I call the MBTA at 617-222-3200 and ask about night service. The automated system is slow, but a live operator can tell you which shuttles are running that night. The planner also struggles with multi-modal trips that mix ferry, subway, and bus in ways the schedule database does not cover cleanly. The Charlestown Ferry to Long Wharf is a good example. The ferry schedule is fixed and short, and the planner does not always align it with the connecting bus or subway in a way that feels coherent. I build those routes by hand: look up the ferry time first, then plug the arrival time into the planner as the departure input.
Practical Details That Matter
Offline access. The mobile app stores your recent searches locally. The web planner does not. If you are in an area with spotty signal, like parts of the Blue Line tunnels or the elevated sections near Airport station, your phone may lose connectivity for 30 seconds to two minutes. Save your planned route before you board, or take a screenshot. The app refreshes automatically when you reconnect, but screenshots are faster when you are moving through a turnstile. Accessibility mode. There is a checkbox for accessible routes that avoids stairs. It is useful if you have a mobility issue, a stroller, or heavy luggage. The trade-off is longer travel times and more bus segments. I use it only when necessary because it often routes you through stations with elevator access that add a minute or two of walking compared to the default path. Alert preferences. The app lets you follow specific lines and stations. Set alerts for your usual routes. A delay notification three minutes before you reach the platform is actionable. A notification five minutes after the train already passed is not. I turn on alerts for the Red Line and the 57 bus because those are the routes where delays cluster most often.
A Specific Workaround I Use Daily
Last winter, the Green Line had a prolonged outage between Copley and Kenmore due to signal work. The planner kept suggesting that segment with a projected wait and a transfer at Copley that required crossing underground to the Red Line and back up. That route added 18 minutes and a confusing staircase swap. I stopped using the planner for that corridor during the work window and routed myself via the 57 bus from Huntington Avenue instead. The bus was slower per mile, but it was direct and predictable. Once the line reopened, I switched back to the planner. That experience taught me a useful rule: if the planner keeps suggesting a route that feels awkward or long, check the service alerts and consider a bus alternative. The planner optimizes for schedule adherence, not for construction realities that are still being resolved.
Final Notes
Use the planner as a starting point, not an oracle. Refresh with Real-Time data. Cross-check weekend routes against the alert calendar. Add a few minutes for known bad transfers. Keep a screenshot handy when signal is unreliable. When the tool cannot handle late-night ferry connections or broken elevator routes, fall back to the phone line or a quick look at the mobile app's alert feed. Boston transit is navigable once you understand where the gaps are. The planner covers most of them. The rest you learn by riding enough to notice the patterns.
