Exceptions

All Exceptions require additional documentation. See I04 Exception Documentation Summary Table.

PL-014 Projects with No Parking

Projects that do not include on-site parking are not required to include EV charging stations. However, projects that are not installing any EV charging stations must advocate to the local jurisdiction to support or install EV charging stations in the community surrounding the project. Documentation of advocacy to the local jurisdiction to support or install EV charging stations is required.

The project team must also provide a narrative that identifies the expected modes of transit to be used by building occupants and that explains how the project can thrive without the use of single-occupancy vehicles and on-site parking.

PL-015 Surface Parking and Code Requirements

The maximum surface parking area listed in this Imperative may be exceeded when it is mandated by code, the project team is unable to get a variance, and structured parking is not viable. In order to use this Exception, the project team must propose a design that meets the requirements of this Imperative to the Authority Having Jurisdiction (AHJ) and, if that alternative is rejected, advocate to the AHJ or other mandating authority to request a change in the requirement.

Project teams that use this Exception may install impervious surface parking only up to the maximum area prescribed by this Imperative for the project’s Transect. The remaining parking area required by code must be pervious (e.g., grasscrete, gravel, or other surfaces that serve the dual purposes of stormwater management and parking) and include infrastructure (e.g., bike racks, preferential carpool parking) and signage encouraging the use of alternative transportation.

Additionally, any and all surface parking incorporated into the project remains subject to the maximum dimensions stipulated in this Imperative before a separation with planting is required on three sides.

PL-016 Surface Parking in Campus Settings

Use of this exception requires ILFI approval in advance; see details below.

An Exception to the maximum area of surface parking allowed in this Imperative may be granted, on a case-by-case basis, for projects in campus settings (typically Transect L3), provided that project teams exhaust all opportunities for Scale Jumping and are able to demonstrate a functional necessity for additional surface parking. Other Imperative requirements must still be met.

Project teams must get preapproval to use this Exception through a Request for Ruling. Project teams should include a narrative explaining why parking requirements cannot functionally be met by parking structures or underground lots.

PL-017 Remote Gathering Places

Use of this exception requires ILFI approval in advance; see details below.

Projects in remote areas that are intended to serve as gathering spaces for large groups of people may exceed the maximum percentage of Project Area allowed for surface parking stipulated in this Imperative if the restrictions will prevent the project from serving its intended purpose. For example, if a site is not served by public transit and the only option for visitors to get to the site is to use personal transport, it may be impractical to comply with the Imperative requirements relating to parking areas. In such circumstances, project teams that use this Exception may install impervious surface parking only up to the maximum area prescribed by this Imperative for the project’s Transect. The remaining parking area required by code must be pervious (e.g., grasscrete, gravel, or other surfaces that serve the dual purposes of stormwater management and parking) and include infrastructure (e.g., bike racks, preferential carpool parking) and signage encouraging the use of alternative transportation.

Project teams must get pre-approval to use this Exception through a Request for Ruling. Project teams that use this Exception must demonstrate that the amount of surface parking exceeds the requirements of this Imperative by the minimum possible to still meet the project’s need, and that the scale and any potential negative impact of the parking area has been reduced as much as possible.

PL-021 Solar Canopy Separation of Existing Parking

Solar canopies may be used instead of planted areas to meet the requirement to separate any surface parking area larger than 20m x 30m (65ft x 98ft) with planted areas if all of the following conditions are met:

• Parking is existing;
• Disturbance of the surface is not otherwise in the project scope; and
• The runoff from the area occupied by the solar canopies is treated
  

Exception documentation will need to include drawings and calculations detailing runoff treatment.

PL-022 Surface Cover Requirements for Oversized Vehicles

Where the essential function of a project requires parking and maneuvering areas for trucks or oversized vehicles that cannot be accommodated within the maximum dimensions of uninterrupted surface cover, those dimensions may be exceeded if all of the following conditions are met:

• The area of uninterrupted surface cover is no more than the minimum needed to perform the essential function;
• The area is not used for passenger vehicle parking;
• The area devoted to passenger vehicle parking meets requirements for total surface cover and separation dimensions; and
• The design incorporates at least one intentional Human Scale element. It can address either gathering places or the project edge, and may include plantings that provide visual and experiential buffers to the expanse of impervious surface.

Projects using this exception must still comply with the other Human Scale, Proportion, and Signage requirements of this Imperative.

Documentation must include a narrative and calculations demonstrating the minimum area of surface cover required to perform the essential function, as well as drawings and a narrative identifying the additional human-scaled elements.

PL-023 Unsafe Bicycle Network

Where biking is unsafe or infeasible due to remoteness or road speeds and unprotected lanes, projects may use this exception to undertake advocacy and direct support of bike infrastructure improvements in the local region instead of providing facilities to encourage human-powered transport and bike storage at the project per the Advocacy and Improvement guidance below.
To use this exception, project teams need to provide a narrative clearly describing why biking to the site is infeasible or unsafe or both.

Safety

Unsafe conditions vary but will typically be covered by the following conditions. Within 7 miles (11 km) of the site, all routes between primary anticipated departure zones and the site require either:

• Use of a roadway frequented by trucks, buses, or other large heavy vehicles; or
• Use of a roadway that has a posted speed limit higher than 30 mph (50 kph) and having at least one of the following characteristics:
  • Marked centerlines with more than one lane of traffic in each direction and lacking designated bike infrastructure (roadway design features, such as physically separated lanes, painted lanes, or painted sharrows, specifically designed to increase awareness and safety for bicyclists); or
  • No shoulder or safe width to accommodate both motorized vehicles and cyclists (minimum distance from the curb of 14.5ft (4.4m) where there is parking or 5.5ft (1.5m) where there is no parking).

Generally, a road without a marked centerline and a speed limit at or below 25 mph (40 kph) would be considered safe whether or not bike infrastructure is present.

Remoteness

Project teams in Transects L1 and L2 may demonstrate eligibility for this pathway based on remoteness if the project site is: 7 miles (11 km) or more from the nearest residential neighborhood or reasonably anticipated starting point for more than half of the users of the building.

Advocacy and Improvement

Project teams using this exception must assess the barriers and opportunities related to safe bicycle transportation in the local region and undertake two activities between the start of the design process and completion of the project’s performance period to address the barriers or opportunities identified. As long as the activities are designed to have a meaningful impact on the issues identified in the analysis, project teams may propose other types of actions, but appropriate activities can generally be classified as either advocacy or direct support of regional improvements.

Advocacy:

• Examples of appropriate advocacy include:
  • Both advocating in writing and providing testimony at a public meeting for:
    • Implementing infrastructure to create safe bikeways at specific locations;
    • Adopting a plan to improve conditions, including a network of bike lanes and safe intersections following the SPRINT principles or the Design Manual for Bicycle Traffic (Netherlands);
    • State Department of Transportation inclusion of paved shoulders on all its rural highways;
    • Implementation of a Local Complete Streets ordinance or resolution; or
    • Development of a local cycling-specific ordinance that specifically requires the construction or upgrade of context-appropriate, low-stress bicycle facilities when streets are being reconstructed.
  • Organizing an advocacy campaign in support of expanding safe biking networks.

Regional Improvements:

• Examples of appropriate regional improvements include:
  • Direct support, such as a donation of funds, in-kind services, or material toward improving bike facilities in the local region. Examples of appropriate support include:
    • Organizing volunteer opportunities to improve amenities, such as trail maintenance or community bike counts, staffing a bike valet station at a public event, etc.;
    • Donating property or easements to improve the public trail network;
    • Donating funding for the construction of bicycle amenities, such as bike share stations, trails, parking corrals, bike valet service at a local public event, etc.;
    • Donating funds or in-kind services toward development of bicycle amenities specifically in low-income/traditionally underserved communities;
    • Donating design, engineering, or facilitation services toward development of trails or bikeways; and
    • Assisting the community to apply for a Bicycle Friendly Community designation, or an international equivalent, or develop improvements to meet requirements.

Documentation Requirements

• Narrative substantiating through reference to the remote or unsafe conditions in the exception or other relevant documentation, including maps or photos as appropriate, that biking to the site is unsafe or infeasible;
• Written analysis of the barriers and opportunities related to bicycle transport in the local region; and
• Documentation of the two advocacy or improvement activities completed through copies of letters, testimony, presentation slides, meeting notes, deliverables for in-kind services, photos of participation in events, donation receipts, or other clear evidence.