A visible lane or driveway does not prove that an accessory dwelling has legal access or meets emergency-service requirements. Before treating a route as usable, establish who owns and maintains it, whether the parcel has a legal right to use it, and which authority decides vehicle, pedestrian, and fire access.

Establish the route and its authority

Check the parcel survey, title and easement records, street or lane classification, and current site plan. Aerial imagery can help locate a route, but it cannot show whether a lane is public, whether a driveway easement exists, or whether a fire apparatus can reach the required point. Shared drives and private lanes may need documents or consent that are not visible on a map.

Separate the questions that are often grouped under “access”:

  • Does zoning require frontage, a lane, a driveway, or a particular vehicle connection?
  • Is the route public or private, and does the owner have a legal right to use it?
  • What dimensions, grade, turning area, overhead clearance, and surface does the reviewing authority require?
  • Is there a continuous pedestrian route, and does emergency access follow a different standard?
  • Which road, planning, building, or fire authority reviews each item?

Requirements can depend on the unit’s location, distance from the street, sprinkler design, hydrant location, adjoining-property agreements, and project form. Obtain the authority’s current measurement method and show the route on a site plan. Do not infer compliance from a nominal driveway width or from the fact that another building uses the same route.

Toronto examples are form-specific

Toronto publishes separate fire-access guidance for laneway suites and garden suites. Its laneway-suite page describes a path at least 0.9 m wide and 2.1 m high, with a maximum ordinary travel distance of 45 m; a longer route has additional conditions. Its garden-suite guidance distinguishes minimum widths by sprinkler status and describes a conditional route up to 90 m with an additional City-acceptable fire-safety measure. These are Toronto-specific review criteria for the named forms, not general ADU dimensions or an approval of any particular site.

Where a route crosses a neighbouring property, a City process may require a registered agreement. Toronto’s guidance explains that a fire-access agreement is not general tenant access and does not guarantee a building permit. Legal access, zoning, building-code compliance, and final fire review remain separate checks.

Check easements as well as the route

Nashville’s detached-ADU guidance is one example of why a visible route is not enough: it says a DADU cannot be placed over an easement or platted setback and points applicants to utility agencies for easement information. That is a Nashville-specific siting check, not a rule for other cities. Review the survey, title, utility records, and current local setback rules before locating a structure. If the site plan depends on a narrow passage, see the separate Albuquerque casita access check and Edmonton secondary-suite site-plan guide; their local submission or zoning criteria do not certify fire access.

Prepare for a property-specific review

Bring a current survey or measured site plan, route dimensions, driveway and lane information, easement or title documents, building locations, hydrant details where relevant, and the proposed unit form. Ask each authority what it reviews and whether a site visit or revised plan is needed. If the route depends on a neighbour, confirm the legal instrument and registration process before relying on it.

For city-specific garden-suite fire-access dimensions and alternatives, see Toronto garden-suite fire-department access. Check parking rules separately: a parking waiver does not remove access or emergency-route requirements.