	<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://policymanual.mdot.maryland.gov/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mnemphos</id>
	<title>MDOT Policy Manual - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://policymanual.mdot.maryland.gov/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mnemphos"/>
	<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=Special:Contributions/Mnemphos"/>
	<updated>2026-04-30T08:20:38Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.5</generator>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6514</id>
		<title>MDOT 657.2 Joint Development Roles and Responsibilities</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6514"/>
		<updated>2025-07-28T16:44:38Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT 657.22 (1).pdf| Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key responsibilities of internal and external stakeholders and highlights the partnerships necessary for effective Joint Development project execution. Joint Development projects involve complex coordination between the federal government, State agencies, local jurisdictions, private developers, and the community. This section describes the roles and responsibilities of those parties and the necessary partnerships for successful Joint Development projects, as well as State policies that relate to Joint Development. &lt;br /&gt;
&lt;br /&gt;
The following matrix provides an overview of key stakeholders, both internal and external to MDOT, who participate in the Joint Development process. Additional information on how MDOT collaborates with these partners is provided below. For a detailed breakdown of the Joint Development process and key stakeholders roles and responsibilities, see Appendix A – Joint Development Roles and Responsibilities Matrix.&lt;br /&gt;
&lt;br /&gt;
The core project team for each Joint Development project consists of the Joint Development Partner, MDOT’s Office of Real Estate and Economic Development (“ORED”), the Maryland Transit Administration (“MTA”), and the Office of the Attorney General (“OAG”). Together, these entities collaborate to oversee the planning, evaluation, negotiation, design, and implementation of Joint Development projects, ensuring alignment with MDOT’s strategic goals and objectives, policies, and regulatory requirements.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Stakeholder&lt;br /&gt;
! Role Summary&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
! Internal to MDOT&lt;br /&gt;
&lt;br /&gt;
|- &lt;br /&gt;
| Office of Real Estate and Economic Development (“ORED”)&lt;br /&gt;
| Located within The MDOT Secretary’s Office, ORED will lead and coordinate MDOT’s Joint Development efforts including executing planning efforts, solicitations, and agreements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Transit Administration (“MTA”)&lt;br /&gt;
| As the transit operator, MTA will define transit infrastructure requirements, standards, and specifications. MTA will be a key stakeholder in the Development Plan, detailed design review and approval; and construction to ensure the proposed development is integrated with the transit infrastructure, that the future service supports new development, that there are minimal disruptions to transit operations throughout construction, and that the assets are designed and delivered in accordance with the requirements, standards, and specifications. MTA will also be responsible for inspection during construction, commissioning, and handover of the transit infrastructure assets.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)	As the owner and maintainer of state roads, SHA will be a key partner in ensuring that local road capacity supports intended development, as well as providing early input into defining requirements and assisting with analysis in defining needs improvements and permitting. &lt;br /&gt;
To manage risk associated with Joint Development projects, SHA shall evaluate planning-level concepts of potential Joint Development projects to estimate potential SHA positions on future permitting. MDOT will seek to engage local roadway owners in this process as well. This process is outlined in the document TIS for Early Planning Coordination on Joint Developments (JD).&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Aviation Administration (“MAA”) &lt;br /&gt;
| The MAA owns and operates the Baltimore/Washington International Thurgood Marshall (BWI) and Martin State airports. MAA will be a key partner to ensure development adjacent to either of these MARC stations conforms with all airport requirements and operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Office of Attorney General (“OAG”)&lt;br /&gt;
| The OAG is the legal counsel to MDOT and is involved in reviewing solicitations and the drafting and negotiations of development agreements.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other MDOT Modal Departments&lt;br /&gt;
| As the owner and operator of State-owned land within ½ mile of transit station, other MDOT Modal Departments may be a key stakeholder in Joint Development projects. Any impacted modes will be a key partner to ensure development does not impact modal infrastructure or operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! External to MDOT&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other State Agencies&lt;br /&gt;
| Other State Agencies	MDOT will partner with other state agencies, as appropriate, to advance Joint Development projects.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Federal Transit Administration (“FTA”)&lt;br /&gt;
| FTA-assisted Joint Development is any Joint Development project that uses FTA funding or property acquired with FTA funding. MDOT coordinates its Joint Development as applicable with FTA to ensure that the project satisfies FTA’s Joint Development requirements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Jurisdictions &lt;br /&gt;
| Local jurisdictions are the local land use authority over State land and often control adjacent road networks and public space. Local jurisdictions are a key partner in developing site requirements and early site strategies to ensure potential future development meets local zoning and other regulations, as well as conforming with land use and comprehensive planning. &lt;br /&gt;
Local jurisdictions should closely coordinate with MDOT to ensure Master Developments that involve Joint Development uphold the State goals for TOD and Joint Development while also administering its own development approval process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Communities &lt;br /&gt;
| Residents, community-based organizations, and businesses in communities adjacent to Joint Development projects are key stakeholders throughout the process. MDOT and its Joint Development partners will engage local communities throughout the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other Rail Authorities Having Jurisdiction	&lt;br /&gt;
| MDOT will seek to coordinate with other rail authorities having jurisdiction to define requirements and processes for external review should the proposed joint development project potentially have impacts to the rail corridor or its zone of influence.  &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
;Partnerships with Local Jurisdictions&lt;br /&gt;
&lt;br /&gt;
In the pursuit of Joint Development, MDOT will work with local jurisdictions to coordinate pre-solicitation planning and site infrastructure needs and funding opportunities, defining community and jurisdictional goals and guiding principles, leveraging local economic development tools and strategies as well as resolving feasibility issues prior to solicitation as much as practically possible. For example, where amending land use and zoning regulations to better align with TOD objectives is necessary, MDOT may: &lt;br /&gt;
* Advocate for or initiate zoning amendments,&lt;br /&gt;
* Participate in and/or fund any necessary studies; and &lt;br /&gt;
* Provide technical assistance.&lt;br /&gt;
Through the course of planning and executing Joint Development, MDOT will work to include local development goals as well as community needs such as community and public service facilities as feasible. Defining these goals will occur in coordination with local jurisdictions and community partners through the pre-planning process.&lt;br /&gt;
&lt;br /&gt;
;Coordination with State Agencies&lt;br /&gt;
MDOT will coordinate with key State agency partners outside of MDOT to bring state resource support for realizing TOD through Joint Development. &lt;br /&gt;
&lt;br /&gt;
;Joint Development Partners&lt;br /&gt;
MDOT will be seeking, through Joint Development proposals, qualified development partners who have aligned interests in developing transit-oriented, mixed-use, mixed-income development at appropriate densities. MDOT views working with qualified developer partners as a key tool to advance TOD projects with shared costs and shared benefits to both parties. While MDOT will seek various methods to fund and finance the public infrastructure necessary to enable Joint Development, in collaboration with its local jurisdictional partners, MDOT expects its Joint Development partners to deliver high-quality TOD in accordance with the&lt;br /&gt;
MDOT 657 Joint Development Policy and applicable local laws and land use policies.&lt;br /&gt;
&lt;br /&gt;
==Appendix==&lt;br /&gt;
[[File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg|link=|1500px]]&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
[[MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT_657.3.pdf&amp;diff=6513</id>
		<title>File:Signed Supporting Document MDOT 657.3.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT_657.3.pdf&amp;diff=6513"/>
		<updated>2025-07-28T16:38:04Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6512</id>
		<title>MDOT 657.1 Joint Development Principles</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6512"/>
		<updated>2025-07-28T16:37:45Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 23, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT.pdf| Signed Supporting Document MDOT 657.1]]&lt;br /&gt;
&lt;br /&gt;
MDOT will evaluate Joint Development proposals and the Development Plan based on the following joint development principles. While the below points are all important priorities, specific joint development opportunities may place greater emphasis on selected priorities based on context and needs. In each respective Joint Development project, MDOT will specify which elements will receive greater emphasis over others as outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:1. Transit Integration - Proposed development must consider integration with the transit serving the proposed Joint Development site. This not only includes any rail station or bus stop but also connecting other modes to the site. Ensuring connectivity and universal accessibility to all the on-site or adjacent transit modes should be fundamental to any Development Plan. If present, different transit modes should be located as close together as possible to facilitate efficient intermodal connections.&lt;br /&gt;
&lt;br /&gt;
:2. Replacement Facilities - When transit facilities are modified or replaced as part of a Joint Development project, MDOT will seek to right-size, modernize, and improve station access as part of the project. In evaluating the scope and size of replacement of transit facilities affected by Joint Development, the proposed Joint Development plan should take into account:&lt;br /&gt;
&lt;br /&gt;
:::i. The future need of the transit facilities based on the existing and projected number of boardings and alightings at the Transit station, estimated number of new transit riders resulting from Joint Development; and estimated ridership from new development reasonably expected within the half-mile walkshed of a Transit station;&lt;br /&gt;
:::ii. Avoidance of unreasonable impacts to transit operations, service, vehicular and passenger flow, and customer experience;&lt;br /&gt;
:::iii. Cost effectiveness and life-cycle costs for facilities and operations; and,&lt;br /&gt;
:::iv. Long-term asset management plan(s) for MDOT’s facilities.&lt;br /&gt;
&lt;br /&gt;
::MDOT may consider reducing the replacement of existing facilities based on projected changes in ridership, access needs, and long-term multimodal strategy. Any such proposal to reduce the quantity of a replacement facility (e.g., a reduction in parking spaces) must be supported by a comprehensive justification that includes, but is not limited to:&lt;br /&gt;
:::i. The financial case, which considers the combined projected revenue from Joint Development (e.g., ground lease payments, participatory rent, etc.) and any revenue increases generated by induced ridership from the joint development. &lt;br /&gt;
:::ii. The strategic case, including alignment with MDOT’s goals, objectives, and principles. &lt;br /&gt;
:::iii. The economic case, such as broader community benefits, state and local tax generation impacts, and the private investment enabled by the joint development project.&lt;br /&gt;
:::iv.  The operational case, ensuring that multimodal access is maintained and that users can continue to access transit conveniently via other modes (e.g., biking, walking, bus, drop-off).&lt;br /&gt;
:::In all cases, proposals to reduce replacement facilities (e.g., fewer parking spaces than currently exist) must demonstrate that the total projected financial and non-financial benefits outweigh the value or utility of maintaining existing facility levels.&lt;br /&gt;
&lt;br /&gt;
:3. Density and Mix of Uses - Proposed Development Plans must reflect a level of density that will drive transit ridership and activity for the site. MDOT encourages that density levels be at the higher range of allowable density in the applicable land use or zoning requirements. Projects should allow for a mix of uses, with specific priority given to residential use, while also providing appropriate commercial use and other amenities that not only support activity within the station area but also draw transit riders. MDOT discourages automobile-dependent uses (e.g., vehicle repair businesses, drive-thrus, etc.).&lt;br /&gt;
&lt;br /&gt;
:4. Housing - Ensuring that Joint Development projects provide residential components that advance State housing goals is a key priority for MDOT. Given the diversity of markets and jurisdictional goals in the State, MDOT does not establish specific affordability targets in this document, however providing affordable units is a priority. MDOT will seek and evaluate affordability targets for any development proposal and subsequently work with the Joint Development partner, the Department of Housing and Community Development (DHCD), and the local jurisdiction to ensure that any Development Plan and subsequent build-out include a meaningful component of affordable units while maintaining the financial feasibility of the project.&lt;br /&gt;
&lt;br /&gt;
:5. Parking - MDOT is looking for a rationalized and efficient approach to parking. Providing rationalized parking is a critical component to successful TOD. The joint development project should not provide parking over what is minimally needed for the site. Development Plans must consider several factors when planning for parking on Joint Development sites. These factors include:&lt;br /&gt;
:::i. The amount of parking required to support transit ridership, and the initial location(s) for where that parking may be located will be determined pre-solicitation and may be provided as part of the Joint Development Solicitation, if applicable.&lt;br /&gt;
:::ii. The amount and location of parking provided for the development must consider the type of transit service serving the site. If the transit serving the site is a high-capacity transit service such as Metro Subway or Light Rail, MDOT expects a lower provision of parking to support the development. Joint development sites should target a ratio of less than 1 space per unit. However, if the site is served by commuter rail, additional parking for development may be required and a 1 space per unit ratio could be justifiable. MDOT will seek to coordinate with local jurisdictions prior to solicitation to reconcile zoning regulations that require minimum parking ratios above target levels conducive of TOD. &lt;br /&gt;
:::iii. Location of parking facilities should give priority to bus, pick-up &amp;amp; drop-off, micromobility, and pedestrian facilities. &lt;br /&gt;
:::iv. Opportunities for shared and/or structured parking are preferred, so long as they do not negatively impact passenger or vehicular traffic flow, safety, transit operations, and lifecycle costs. Such approaches should be considered and proposed by the Joint Development partner for MDOT’s review and approval, if not specified as part of the Joint Development solicitation.&lt;br /&gt;
:::v. Parking for the private development should not negatively impact flow or accessibility to the transit and meet [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines.]&lt;br /&gt;
&lt;br /&gt;
:6. Value Capture - MDOT will seek to achieve fair market value of real property in all joint development transactions. The fair market value of real property will be determined through consultation with real estate advisory firms and/or qualified third-party appraisers.. MDOT will contemplate discounts to land value and/or ground rent to achieve the goals, objectives, and principles of the Joint Development project or to fund improvements to transit facilities as needed based on a case-by-case basis. Any proposed reduction in fair market value must demonstrate that the value of the asset contributed to the joint development is equal to or greater than the fair share of the costs of the joint development project, or that MDOT will receive benefits (including non-monetary) equal to or greater than FMV. MDOT will also seek to participate in any monetization opportunities as a result of the Joint Development project.&lt;br /&gt;
&lt;br /&gt;
:7. Operations and Maintenance Costs - MDOT will seek to allocate operations and maintenance responsibilities associated with parking, open space, stormwater management, landscaping, cleaning, general maintenance, snow and ice removal, and graffiti removal to the Joint Development partner, or an approved designee, in a manner that is consistent with applicable MDOT Modal standards and does not increase MDOT’s administrative burden. &lt;br /&gt;
&lt;br /&gt;
:8. Electric Vehicle Charging Facilities - Wherever possible, Joint Development projects should provide electric vehicle charging as part of a parking program for transit customers, which requirements will be outlined within the Joint Development solicitation. Providing charging stations promotes the use of electric vehicles and is a major step towards achieving the State’s climate goals and clean vehicle mandates. Where practical, a parking program should incentivize electric vehicle use by allocating priority parking spaces (such as those immediately adjacent to transit station entrances, or multiple spaces on the ground level of a parking garage) for electric vehicle charging with compliant signage indicating the designated electric vehicle charging spaces. Joint Development proposals should consider the necessary infrastructure for electric vehicle charging stations, such as electric grid capacity for both near-term installations as well as future proofing for future installations. Note that the Americans with Disabilities Act requires provision of a “reasonable number” of accessible electric vehicle charging stations in an electric vehicle parking facility but does not specify an exact number or ratio. Where a requirement for the number of accessible electric vehicle charging stations exists, developers must provide at least that minimum number. Developers should reference federal and state guidelines for further guidance on the provision and design of accessible electric vehicle parking or to the local authority having jurisdictions standards and specifications. &lt;br /&gt;
&lt;br /&gt;
:9. Micromobility Facilities - As TOD aim to reduce car-dependence and promote multi-modal options, Joint Development projects are encouraged to incorporate facilities that promote micromobility access for bicycle and scooter travel. These amenities include protected shared use paths and connections to the local transportation system as well as secure and dedicated parking with electric charging stations for e-bikes and scooters which will be defined within the Joint Development solicitation. Joint Development projects should include micromobility facilities as identified in the local jurisdiction’s bicycle and pedestrian master plans, bicycle and pedestrian priority action plan, comprehensive plans, standards, and specifications. Developers should refer to the [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines] for further guidance on bicycle and scooter parking. To determine an appropriate bicycle facility, please reference Appendix D: Bicycle Facility Selection Guide of the [https://www.mdot.maryland.gov/OPCP/MDOT_State_Bike_Ped_Master_Plan_FULL_FINAL_VERSION.pdf 2050 Maryland Bicycle &amp;amp; Pedestrian Master Plan.] For the development of bicycle and scooter parking, please reference the Association of Pedestrian &amp;amp; Bicycle Professionals (“APBP”) Essentials of Bike Parking: Selecting and Installing Bike Parking That Works.&lt;br /&gt;
&lt;br /&gt;
:10. Site and Area Connectivity Improvements - The Development Plan for Joint Development projects should promote convenient, accessible intermodal access to the transit service. What this means in practice will depend on site context, though it could include:&lt;br /&gt;
:::i. Parking garages, pick-up and drop-off areas, and micromobility facilities should be located proximate to the station and transit facilities but give deference and space for overall pedestrian flow, public spaces and wayfinding to the station for all users.  Pedestrian pathways should be safe and direct to walk from the parking facility to the station platform or other transit boarding area.&lt;br /&gt;
:::ii. Passengers with limited mobility should have an accessible, direct route to transit service entrances with limited detours. &lt;br /&gt;
:::iii. Infrastructure should, to the extent possible, not interrupt the flow of people to and from the transit station.&lt;br /&gt;
&lt;br /&gt;
::Joint Development projects are a significant investment with potential community-wide impacts. Pedestrian and cyclist infrastructure built as part of a Joint Development project can serve as a foundation for further sidewalk and bike lane networks, for instance. MDOT will seek to collaborate with local jurisdictions, using Joint Development projects as a catalyst to achieve pedestrian, cyclist, and other “alternative mobility” goals, and advance pedestrian, cyclist, and other alternative mobility infrastructure projects laid out in local comprehensive plans, pedestrian/bike plans, “Vision Zero” plans, and other similar local planning documents. Some Joint Development projects may require roadway capital projects or improvements in State-owned rights-of-way. In such cases, these improvements must adhere to MDOT 750 Complete Streets Policy and such requirements will be outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:11. Urban Design, Placemaking, Wayfinding, and Branding/Identity - In general, a Joint Development project should aim to adhere to the urban design principles laid out in MTA’s Designing for Transit: Transit-Oriented Development Guidelines. Please see the development guidelines for more information, including detailed and context-dependent design guidelines. Joint Development projects should also adhere to any applicable local urban design guidelines. The branding, marketing, and identity of Joint Development projects – both development and wayfinding elements – should have a direct relationship to the transit station on which they are centered. For example, developers could incorporate the name of the transit station into the name of development projects where practical. The aim is for the development to promote and encourage its relationship to the mode of transit which serves that project. Wayfinding elements should clearly and prominently guide both pedestrians and drivers – whether they are area residents, workers, or visitors – to key station area assets including but not limited to the transit station, retail and other activity centers, and any public services and open space. Wayfinding elements can include signs, lighting, and surface finishes that promote legibility of the public realm. They should have a consistent visual identity (e.g., typefaces, colors) across separate wayfinding elements such that visitors to an area are able to easily identify them. &lt;br /&gt;
&lt;br /&gt;
:12. Public Space - MDOT aims to enhance and expand public space in communities through its Joint Development program. Developers may be required to construct or improve public spaces as part of a Joint Development project. These requirements will be outlined in the Joint Development solicitation and may include elements such as parks, plazas, squares, sidewalks, and shared-use paths. MDOT’s priority is that public spaces created through Joint Development are welcoming, safe, and vibrant, serving the joint development, broader TOD, and the community. To support placemaking and reinforce the role of the station as a community anchor, developers should prioritize locating required open space near or adjacent to station entrances to create an active and enticing focal point. To minimize long-term costs to the State, public spaces should be conveyed to the local jurisdiction or operated and maintained by the Joint Development partner, or an approved designee such as the ground lessee, homeowners’ association, or residents’ association. Public space design must not obstruct access to the station or impede clear sightlines and should comply with the standards and specifications of the authority having jurisdiction. When new public spaces are proposed, developers are expected to coordinate closely with MDOT, MTA, and local jurisdictions to define programming and activation plans, and to establish clear roles and responsibilities for ongoing operations and maintenance.&lt;br /&gt;
&lt;br /&gt;
:13. Phasing and Implementation - Joint Development project phasing will typically involve the upfront or concurrent completion of infrastructure projects, followed by vertical development. However, MDOT will consider alternative Joint Development project phasing that balances the ongoing needs of transit riders with the market viability of vertical development. Any construction activities should minimize disruption to the transit operations. Any disruptions or changes in transit service needed for construction must be approved by MTA.&lt;br /&gt;
&lt;br /&gt;
:14. Construction of MDOT Facilities - As part of a Joint Development project, it  may be required to modify or construct replacement transit facilities such as parking and bus facilities, roads, pick up and drop off spaces, station ingress and egress, and potentially other types of transit infrastructure in order to achieve an optimized TOD. Design for all MDOT facilities will be approved by the mode that either owns or operates the facility. Allowing for the design and construction or improvement of MDOT facilities to be led by developers can benefit both parties. MDOT benefits from cost and time efficiencies derived from a single entity being responsible for all capital improvements. Developers benefit because: &lt;br /&gt;
:::i. Developers have increased control over the timeline of infrastructure delivery (and therefore when vertical development may begin).&lt;br /&gt;
:::ii. Transit facilities may be better integrated into the overall development, which increases overall development potential and making it more attractive to prospective tenants and increase achievable rents.&lt;br /&gt;
::MTA, or the applicable mode, must approve of the design, construction, and delivery of its facilities in accordance with the mode’s design and construction standards and specifications. Construction activities will commence after MDOT issues a notice to proceed to the developer, and the developer has received all other necessary State and local permits. These will likely include a permit for the use of State property with agreements on maintenance of traffic, maintenance of station activities, and more. The developer will execute design and construction contracts with its subcontractors necessary to deliver the transit facilities.&lt;br /&gt;
&lt;br /&gt;
:15. Continuing Control - MDOT strongly prefers to structure its transactions as ground leases rather than fee simple sales as it creates regular compensation for MDOT to offset transit operations and better enables MDOT to realize long-term value to offset its investment in transit infrastructure. Exceptions to this preference may be considered and may include instances where practical, site or legal reasons require fee simple sale, such as for home ownership opportunities, or if such a transaction can create significant added value for MDOT or be necessary to inject upfront capital to fund infrastructure improvements. To ensure Federal Transit Administration (FTA) continuing control requirements are met on FTA-assisted properties, MDOT will require certain assurances such as restrictive covenants, as applicable. &lt;br /&gt;
&lt;br /&gt;
:16. Community and Stakeholder Engagement - MDOT will consult and work collaboratively with the community, state stakeholders, local jurisdictions and developers to encourage transit-supportive, high-quality development at transit stations and surrounding properties. Once a successful Joint Development partner is selected, the developer must actively and productively engage local communities with interest in the Joint Development site during planning and delivery of the project.&lt;br /&gt;
&lt;br /&gt;
:17. Local Planning and Approvals - All Joint Development projects must follow local laws and land use policies of the jurisdiction in which they are located. MDOT will proactively engage with local jurisdictions to gather input on preliminary development concepts, gain local support, and to the extent possible and where appropriate, secure any necessary zoning changes prior to publication of the Joint Development solicitation. The Joint Development partner will be responsible for securing all necessary permits and entitlements from the relevant local jurisdiction and any other authorities having jurisdiction.&lt;br /&gt;
&lt;br /&gt;
:18. Sustainability - Joint Development projects must meet local building sustainability requirements. In the absence of a local requirement, MDOT will require that the project meet a nationally recognized sustainability standard, such as LEED Silver, or equivalent, to be specified in the Joint Development solicitation. &lt;br /&gt;
&lt;br /&gt;
:19. MBE/DBE/SBE Contracting Goals - The State of Maryland’s Minority Business Enterprise (“MBE”), Disadvantaged Business Enterprise (“DBE”), and Small Business Enterprise (“SBE”) Programs are designed to provide contracting opportunities to MBE, DBE, and SBE businesses in both State and federally funded projects in accordance with State law. MBE/DBE/SBE Contracting Goals  may be defined in the Joint Development solicitation. Maryland MBEs, DBEs, and SBEs must complete the certification process with MDOT to be recognized as such for contracting purposes. Working with the awarded developer, MDOT will assist Joint Development partners in identifying opportunities for MBE, DBE, or SBE participation in the development and construction of the project. &lt;br /&gt;
&lt;br /&gt;
:20. Workforce Development and Labor Provisions - Joint Developments may qualify as “large-scale public work contract” under [https://governor.maryland.gov/Lists/ExecutiveOrders/Attachments/51/01.01.2024.18%20-%20FINAL%20EO%20-%20PLAs%20Apprenticeship%20Agreements%20and%20Community%20Hiring%20-%205.31.24%20%5bCLEAN%20COPY%5d.pdf Executive Order 01.01.2024.18] regarding project labor agreements, apprenticeships, and community hiring. Certain projects may be subject to [https://www.dol.gov/agencies/whd/government-contracts/construction Davis-Bacon Act] or [https://www.labor.maryland.gov/labor/prev/prevoverview.shtml Maryland Prevailing Wage] requirements. Contractors and subcontractors awarded contracts by the State of Maryland or its political subdivisions for the construction of public works that fall within the State’s statutory requirements must compensate covered workers as governed by Maryland’s Prevailing Wage Law. These requirements will be further described in the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:21. Americans with Disabilities Act - The Americans with Disabilities Act (“ADA”) prohibits discrimination against people with disabilities in employment, transportation, public accommodation, communications, and government activities. The development must comply with ADA requirements. Regarding infrastructure, where it is located will determine which requirements will apply. For WMATA and MTA-controlled stations, all spaces must meet at least Americans with Disabilities Access Guidelines (“ADAAG”) and FTA ADA Guidelines. Any improvements along State Highway Administration (SHA)managed facilities must meet SHA’s Accessibility Policy and Guidelines, which can be found in [https://www.roads.maryland.gov/mdotsha/pages/Index.aspx?PageId=26 SHA’s Accessibility Policy and Guidelines for Pedestrian Facilities Along State Highways.]&lt;br /&gt;
&lt;br /&gt;
:22. Transfer or Assignment of Development Agreements - MDOT understands that the developer or members of the development team may change during the term of a Joint Development project. Any changes to developer ownership following execution of the joint development agreements will be subject to MDOT’s approval at its sole and absolute discretion (including, where required, the approval of the Board of Public Works).&lt;br /&gt;
&lt;br /&gt;
:23. Business Ethics and Conflict of Interest - All Joint Development partners must comply with applicable State law requirements relating to conflict of interest, political contribution disclosure, and financial disclosures as part of the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6511</id>
		<title>MDOT 657.2 Joint Development Roles and Responsibilities</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6511"/>
		<updated>2025-07-28T16:37:17Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Appendix */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT 657.22 (1).pdf| Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key responsibilities of internal and external stakeholders and highlights the partnerships necessary for effective Joint Development project execution. Joint Development projects involve complex coordination between the federal government, State agencies, local jurisdictions, private developers, and the community. This section describes the roles and responsibilities of those parties and the necessary partnerships for successful Joint Development projects, as well as State policies that relate to Joint Development. &lt;br /&gt;
&lt;br /&gt;
The following matrix provides an overview of key stakeholders, both internal and external to MDOT, who participate in the Joint Development process. Additional information on how MDOT collaborates with these partners is provided below. For a detailed breakdown of the Joint Development process and key stakeholders roles and responsibilities, see Appendix A – Joint Development Roles and Responsibilities Matrix.&lt;br /&gt;
&lt;br /&gt;
The core project team for each Joint Development project consists of the Joint Development Partner, MDOT’s Office of Real Estate and Economic Development (“ORED”), the Maryland Transit Administration (“MTA”), and the Office of the Attorney General (“OAG”). Together, these entities collaborate to oversee the planning, evaluation, negotiation, design, and implementation of Joint Development projects, ensuring alignment with MDOT’s strategic goals and objectives, policies, and regulatory requirements.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Stakeholder&lt;br /&gt;
! Role Summary&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
! Internal to MDOT&lt;br /&gt;
&lt;br /&gt;
|- &lt;br /&gt;
| Office of Real Estate and Economic Development (“ORED”)&lt;br /&gt;
| Located within The MDOT Secretary’s Office, ORED will lead and coordinate MDOT’s Joint Development efforts including executing planning efforts, solicitations, and agreements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Transit Administration (“MTA”)&lt;br /&gt;
| As the transit operator, MTA will define transit infrastructure requirements, standards, and specifications. MTA will be a key stakeholder in the Development Plan, detailed design review and approval; and construction to ensure the proposed development is integrated with the transit infrastructure, that the future service supports new development, that there are minimal disruptions to transit operations throughout construction, and that the assets are designed and delivered in accordance with the requirements, standards, and specifications. MTA will also be responsible for inspection during construction, commissioning, and handover of the transit infrastructure assets.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)	As the owner and maintainer of state roads, SHA will be a key partner in ensuring that local road capacity supports intended development, as well as providing early input into defining requirements and assisting with analysis in defining needs improvements and permitting. &lt;br /&gt;
To manage risk associated with Joint Development projects, SHA shall evaluate planning-level concepts of potential Joint Development projects to estimate potential SHA positions on future permitting. MDOT will seek to engage local roadway owners in this process as well. This process is outlined in the document TIS for Early Planning Coordination on Joint Developments (JD).&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Aviation Administration (“MAA”) &lt;br /&gt;
| The MAA owns and operates the Baltimore/Washington International Thurgood Marshall (BWI) and Martin State airports. MAA will be a key partner to ensure development adjacent to either of these MARC stations conforms with all airport requirements and operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Office of Attorney General (“OAG”)&lt;br /&gt;
| The OAG is the legal counsel to MDOT and is involved in reviewing solicitations and the drafting and negotiations of development agreements.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other MDOT Modal Departments&lt;br /&gt;
| As the owner and operator of State-owned land within ½ mile of transit station, other MDOT Modal Departments may be a key stakeholder in Joint Development projects. Any impacted modes will be a key partner to ensure development does not impact modal infrastructure or operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! External to MDOT&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other State Agencies&lt;br /&gt;
| Other State Agencies	MDOT will partner with other state agencies, as appropriate, to advance Joint Development projects.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Federal Transit Administration (“FTA”)&lt;br /&gt;
| FTA-assisted Joint Development is any Joint Development project that uses FTA funding or property acquired with FTA funding. MDOT coordinates its Joint Development as applicable with FTA to ensure that the project satisfies FTA’s Joint Development requirements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Jurisdictions &lt;br /&gt;
| Local jurisdictions are the local land use authority over State land and often control adjacent road networks and public space. Local jurisdictions are a key partner in developing site requirements and early site strategies to ensure potential future development meets local zoning and other regulations, as well as conforming with land use and comprehensive planning. &lt;br /&gt;
Local jurisdictions should closely coordinate with MDOT to ensure Master Developments that involve Joint Development uphold the State goals for TOD and Joint Development while also administering its own development approval process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Communities &lt;br /&gt;
| Residents, community-based organizations, and businesses in communities adjacent to Joint Development projects are key stakeholders throughout the process. MDOT and its Joint Development partners will engage local communities throughout the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other Rail Authorities Having Jurisdiction	&lt;br /&gt;
| MDOT will seek to coordinate with other rail authorities having jurisdiction to define requirements and processes for external review should the proposed joint development project potentially have impacts to the rail corridor or its zone of influence.  &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
;Partnerships with Local Jurisdictions&lt;br /&gt;
&lt;br /&gt;
In the pursuit of Joint Development, MDOT will work with local jurisdictions to coordinate pre-solicitation planning and site infrastructure needs and funding opportunities, defining community and jurisdictional goals and guiding principles, leveraging local economic development tools and strategies as well as resolving feasibility issues prior to solicitation as much as practically possible. For example, where amending land use and zoning regulations to better align with TOD objectives is necessary, MDOT may: &lt;br /&gt;
* Advocate for or initiate zoning amendments,&lt;br /&gt;
* Participate in and/or fund any necessary studies; and &lt;br /&gt;
* Provide technical assistance.&lt;br /&gt;
Through the course of planning and executing Joint Development, MDOT will work to include local development goals as well as community needs such as community and public service facilities as feasible. Defining these goals will occur in coordination with local jurisdictions and community partners through the pre-planning process.&lt;br /&gt;
&lt;br /&gt;
;Coordination with State Agencies&lt;br /&gt;
MDOT will coordinate with key State agency partners outside of MDOT to bring state resource support for realizing TOD through Joint Development. &lt;br /&gt;
&lt;br /&gt;
;Joint Development Partners&lt;br /&gt;
MDOT will be seeking, through Joint Development proposals, qualified development partners who have aligned interests in developing transit-oriented, mixed-use, mixed-income development at appropriate densities. MDOT views working with qualified developer partners as a key tool to advance TOD projects with shared costs and shared benefits to both parties. While MDOT will seek various methods to fund and finance the public infrastructure necessary to enable Joint Development, in collaboration with its local jurisdictional partners, MDOT expects its Joint Development partners to deliver high-quality TOD in line with the Goals, Objectives, and Principles outlined within MDOT ### Joint Development Policy, MDOT 657 Joint  Development Principles, the respective Joint Development solicitation as well as in accordance with applicable local laws and land use policies. &lt;br /&gt;
&lt;br /&gt;
==Appendix==&lt;br /&gt;
[[File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg|link=|1500px]]&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
[[MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg&amp;diff=6510</id>
		<title>File:Signed Supporting Document MDOT 657.22 Page 4.jpg</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg&amp;diff=6510"/>
		<updated>2025-07-28T16:37:15Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6509</id>
		<title>MDOT 657.2 Joint Development Roles and Responsibilities</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6509"/>
		<updated>2025-07-28T16:36:50Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Additional Authorized Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT 657.22 (1).pdf| Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key responsibilities of internal and external stakeholders and highlights the partnerships necessary for effective Joint Development project execution. Joint Development projects involve complex coordination between the federal government, State agencies, local jurisdictions, private developers, and the community. This section describes the roles and responsibilities of those parties and the necessary partnerships for successful Joint Development projects, as well as State policies that relate to Joint Development. &lt;br /&gt;
&lt;br /&gt;
The following matrix provides an overview of key stakeholders, both internal and external to MDOT, who participate in the Joint Development process. Additional information on how MDOT collaborates with these partners is provided below. For a detailed breakdown of the Joint Development process and key stakeholders roles and responsibilities, see Appendix A – Joint Development Roles and Responsibilities Matrix.&lt;br /&gt;
&lt;br /&gt;
The core project team for each Joint Development project consists of the Joint Development Partner, MDOT’s Office of Real Estate and Economic Development (“ORED”), the Maryland Transit Administration (“MTA”), and the Office of the Attorney General (“OAG”). Together, these entities collaborate to oversee the planning, evaluation, negotiation, design, and implementation of Joint Development projects, ensuring alignment with MDOT’s strategic goals and objectives, policies, and regulatory requirements.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Stakeholder&lt;br /&gt;
! Role Summary&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
! Internal to MDOT&lt;br /&gt;
&lt;br /&gt;
|- &lt;br /&gt;
| Office of Real Estate and Economic Development (“ORED”)&lt;br /&gt;
| Located within The MDOT Secretary’s Office, ORED will lead and coordinate MDOT’s Joint Development efforts including executing planning efforts, solicitations, and agreements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Transit Administration (“MTA”)&lt;br /&gt;
| As the transit operator, MTA will define transit infrastructure requirements, standards, and specifications. MTA will be a key stakeholder in the Development Plan, detailed design review and approval; and construction to ensure the proposed development is integrated with the transit infrastructure, that the future service supports new development, that there are minimal disruptions to transit operations throughout construction, and that the assets are designed and delivered in accordance with the requirements, standards, and specifications. MTA will also be responsible for inspection during construction, commissioning, and handover of the transit infrastructure assets.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)	As the owner and maintainer of state roads, SHA will be a key partner in ensuring that local road capacity supports intended development, as well as providing early input into defining requirements and assisting with analysis in defining needs improvements and permitting. &lt;br /&gt;
To manage risk associated with Joint Development projects, SHA shall evaluate planning-level concepts of potential Joint Development projects to estimate potential SHA positions on future permitting. MDOT will seek to engage local roadway owners in this process as well. This process is outlined in the document TIS for Early Planning Coordination on Joint Developments (JD).&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Aviation Administration (“MAA”) &lt;br /&gt;
| The MAA owns and operates the Baltimore/Washington International Thurgood Marshall (BWI) and Martin State airports. MAA will be a key partner to ensure development adjacent to either of these MARC stations conforms with all airport requirements and operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Office of Attorney General (“OAG”)&lt;br /&gt;
| The OAG is the legal counsel to MDOT and is involved in reviewing solicitations and the drafting and negotiations of development agreements.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other MDOT Modal Departments&lt;br /&gt;
| As the owner and operator of State-owned land within ½ mile of transit station, other MDOT Modal Departments may be a key stakeholder in Joint Development projects. Any impacted modes will be a key partner to ensure development does not impact modal infrastructure or operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! External to MDOT&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other State Agencies&lt;br /&gt;
| Other State Agencies	MDOT will partner with other state agencies, as appropriate, to advance Joint Development projects.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Federal Transit Administration (“FTA”)&lt;br /&gt;
| FTA-assisted Joint Development is any Joint Development project that uses FTA funding or property acquired with FTA funding. MDOT coordinates its Joint Development as applicable with FTA to ensure that the project satisfies FTA’s Joint Development requirements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Jurisdictions &lt;br /&gt;
| Local jurisdictions are the local land use authority over State land and often control adjacent road networks and public space. Local jurisdictions are a key partner in developing site requirements and early site strategies to ensure potential future development meets local zoning and other regulations, as well as conforming with land use and comprehensive planning. &lt;br /&gt;
Local jurisdictions should closely coordinate with MDOT to ensure Master Developments that involve Joint Development uphold the State goals for TOD and Joint Development while also administering its own development approval process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Communities &lt;br /&gt;
| Residents, community-based organizations, and businesses in communities adjacent to Joint Development projects are key stakeholders throughout the process. MDOT and its Joint Development partners will engage local communities throughout the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other Rail Authorities Having Jurisdiction	&lt;br /&gt;
| MDOT will seek to coordinate with other rail authorities having jurisdiction to define requirements and processes for external review should the proposed joint development project potentially have impacts to the rail corridor or its zone of influence.  &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
;Partnerships with Local Jurisdictions&lt;br /&gt;
&lt;br /&gt;
In the pursuit of Joint Development, MDOT will work with local jurisdictions to coordinate pre-solicitation planning and site infrastructure needs and funding opportunities, defining community and jurisdictional goals and guiding principles, leveraging local economic development tools and strategies as well as resolving feasibility issues prior to solicitation as much as practically possible. For example, where amending land use and zoning regulations to better align with TOD objectives is necessary, MDOT may: &lt;br /&gt;
* Advocate for or initiate zoning amendments,&lt;br /&gt;
* Participate in and/or fund any necessary studies; and &lt;br /&gt;
* Provide technical assistance.&lt;br /&gt;
Through the course of planning and executing Joint Development, MDOT will work to include local development goals as well as community needs such as community and public service facilities as feasible. Defining these goals will occur in coordination with local jurisdictions and community partners through the pre-planning process.&lt;br /&gt;
&lt;br /&gt;
;Coordination with State Agencies&lt;br /&gt;
MDOT will coordinate with key State agency partners outside of MDOT to bring state resource support for realizing TOD through Joint Development. &lt;br /&gt;
&lt;br /&gt;
;Joint Development Partners&lt;br /&gt;
MDOT will be seeking, through Joint Development proposals, qualified development partners who have aligned interests in developing transit-oriented, mixed-use, mixed-income development at appropriate densities. MDOT views working with qualified developer partners as a key tool to advance TOD projects with shared costs and shared benefits to both parties. While MDOT will seek various methods to fund and finance the public infrastructure necessary to enable Joint Development, in collaboration with its local jurisdictional partners, MDOT expects its Joint Development partners to deliver high-quality TOD in line with the Goals, Objectives, and Principles outlined within MDOT ### Joint Development Policy, MDOT 657 Joint  Development Principles, the respective Joint Development solicitation as well as in accordance with applicable local laws and land use policies. &lt;br /&gt;
&lt;br /&gt;
==Appendix==&lt;br /&gt;
[[File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg|link=|1500px]]&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
[[MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6508</id>
		<title>MDOT 657.2 Joint Development Roles and Responsibilities</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6508"/>
		<updated>2025-07-28T16:36:42Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Additional Authorized Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT 657.22 (1).pdf| Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key responsibilities of internal and external stakeholders and highlights the partnerships necessary for effective Joint Development project execution. Joint Development projects involve complex coordination between the federal government, State agencies, local jurisdictions, private developers, and the community. This section describes the roles and responsibilities of those parties and the necessary partnerships for successful Joint Development projects, as well as State policies that relate to Joint Development. &lt;br /&gt;
&lt;br /&gt;
The following matrix provides an overview of key stakeholders, both internal and external to MDOT, who participate in the Joint Development process. Additional information on how MDOT collaborates with these partners is provided below. For a detailed breakdown of the Joint Development process and key stakeholders roles and responsibilities, see Appendix A – Joint Development Roles and Responsibilities Matrix.&lt;br /&gt;
&lt;br /&gt;
The core project team for each Joint Development project consists of the Joint Development Partner, MDOT’s Office of Real Estate and Economic Development (“ORED”), the Maryland Transit Administration (“MTA”), and the Office of the Attorney General (“OAG”). Together, these entities collaborate to oversee the planning, evaluation, negotiation, design, and implementation of Joint Development projects, ensuring alignment with MDOT’s strategic goals and objectives, policies, and regulatory requirements.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Stakeholder&lt;br /&gt;
! Role Summary&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
! Internal to MDOT&lt;br /&gt;
&lt;br /&gt;
|- &lt;br /&gt;
| Office of Real Estate and Economic Development (“ORED”)&lt;br /&gt;
| Located within The MDOT Secretary’s Office, ORED will lead and coordinate MDOT’s Joint Development efforts including executing planning efforts, solicitations, and agreements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Transit Administration (“MTA”)&lt;br /&gt;
| As the transit operator, MTA will define transit infrastructure requirements, standards, and specifications. MTA will be a key stakeholder in the Development Plan, detailed design review and approval; and construction to ensure the proposed development is integrated with the transit infrastructure, that the future service supports new development, that there are minimal disruptions to transit operations throughout construction, and that the assets are designed and delivered in accordance with the requirements, standards, and specifications. MTA will also be responsible for inspection during construction, commissioning, and handover of the transit infrastructure assets.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)	As the owner and maintainer of state roads, SHA will be a key partner in ensuring that local road capacity supports intended development, as well as providing early input into defining requirements and assisting with analysis in defining needs improvements and permitting. &lt;br /&gt;
To manage risk associated with Joint Development projects, SHA shall evaluate planning-level concepts of potential Joint Development projects to estimate potential SHA positions on future permitting. MDOT will seek to engage local roadway owners in this process as well. This process is outlined in the document TIS for Early Planning Coordination on Joint Developments (JD).&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Aviation Administration (“MAA”) &lt;br /&gt;
| The MAA owns and operates the Baltimore/Washington International Thurgood Marshall (BWI) and Martin State airports. MAA will be a key partner to ensure development adjacent to either of these MARC stations conforms with all airport requirements and operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Office of Attorney General (“OAG”)&lt;br /&gt;
| The OAG is the legal counsel to MDOT and is involved in reviewing solicitations and the drafting and negotiations of development agreements.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other MDOT Modal Departments&lt;br /&gt;
| As the owner and operator of State-owned land within ½ mile of transit station, other MDOT Modal Departments may be a key stakeholder in Joint Development projects. Any impacted modes will be a key partner to ensure development does not impact modal infrastructure or operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! External to MDOT&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other State Agencies&lt;br /&gt;
| Other State Agencies	MDOT will partner with other state agencies, as appropriate, to advance Joint Development projects.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Federal Transit Administration (“FTA”)&lt;br /&gt;
| FTA-assisted Joint Development is any Joint Development project that uses FTA funding or property acquired with FTA funding. MDOT coordinates its Joint Development as applicable with FTA to ensure that the project satisfies FTA’s Joint Development requirements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Jurisdictions &lt;br /&gt;
| Local jurisdictions are the local land use authority over State land and often control adjacent road networks and public space. Local jurisdictions are a key partner in developing site requirements and early site strategies to ensure potential future development meets local zoning and other regulations, as well as conforming with land use and comprehensive planning. &lt;br /&gt;
Local jurisdictions should closely coordinate with MDOT to ensure Master Developments that involve Joint Development uphold the State goals for TOD and Joint Development while also administering its own development approval process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Communities &lt;br /&gt;
| Residents, community-based organizations, and businesses in communities adjacent to Joint Development projects are key stakeholders throughout the process. MDOT and its Joint Development partners will engage local communities throughout the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other Rail Authorities Having Jurisdiction	&lt;br /&gt;
| MDOT will seek to coordinate with other rail authorities having jurisdiction to define requirements and processes for external review should the proposed joint development project potentially have impacts to the rail corridor or its zone of influence.  &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
;Partnerships with Local Jurisdictions&lt;br /&gt;
&lt;br /&gt;
In the pursuit of Joint Development, MDOT will work with local jurisdictions to coordinate pre-solicitation planning and site infrastructure needs and funding opportunities, defining community and jurisdictional goals and guiding principles, leveraging local economic development tools and strategies as well as resolving feasibility issues prior to solicitation as much as practically possible. For example, where amending land use and zoning regulations to better align with TOD objectives is necessary, MDOT may: &lt;br /&gt;
* Advocate for or initiate zoning amendments,&lt;br /&gt;
* Participate in and/or fund any necessary studies; and &lt;br /&gt;
* Provide technical assistance.&lt;br /&gt;
Through the course of planning and executing Joint Development, MDOT will work to include local development goals as well as community needs such as community and public service facilities as feasible. Defining these goals will occur in coordination with local jurisdictions and community partners through the pre-planning process.&lt;br /&gt;
&lt;br /&gt;
;Coordination with State Agencies&lt;br /&gt;
MDOT will coordinate with key State agency partners outside of MDOT to bring state resource support for realizing TOD through Joint Development. &lt;br /&gt;
&lt;br /&gt;
;Joint Development Partners&lt;br /&gt;
MDOT will be seeking, through Joint Development proposals, qualified development partners who have aligned interests in developing transit-oriented, mixed-use, mixed-income development at appropriate densities. MDOT views working with qualified developer partners as a key tool to advance TOD projects with shared costs and shared benefits to both parties. While MDOT will seek various methods to fund and finance the public infrastructure necessary to enable Joint Development, in collaboration with its local jurisdictional partners, MDOT expects its Joint Development partners to deliver high-quality TOD in line with the Goals, Objectives, and Principles outlined within MDOT ### Joint Development Policy, MDOT 657 Joint  Development Principles, the respective Joint Development solicitation as well as in accordance with applicable local laws and land use policies. &lt;br /&gt;
&lt;br /&gt;
==Appendix==&lt;br /&gt;
[[File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg|link=|1500px]]&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
[MDOT 657.1 Joint Development Principles]&lt;br /&gt;
&lt;br /&gt;
[MDOT 657.3 Joint Development Implementation]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6507</id>
		<title>MDOT 657.2 Joint Development Roles and Responsibilities</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6507"/>
		<updated>2025-07-28T16:36:30Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT 657.22 (1).pdf| Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key responsibilities of internal and external stakeholders and highlights the partnerships necessary for effective Joint Development project execution. Joint Development projects involve complex coordination between the federal government, State agencies, local jurisdictions, private developers, and the community. This section describes the roles and responsibilities of those parties and the necessary partnerships for successful Joint Development projects, as well as State policies that relate to Joint Development. &lt;br /&gt;
&lt;br /&gt;
The following matrix provides an overview of key stakeholders, both internal and external to MDOT, who participate in the Joint Development process. Additional information on how MDOT collaborates with these partners is provided below. For a detailed breakdown of the Joint Development process and key stakeholders roles and responsibilities, see Appendix A – Joint Development Roles and Responsibilities Matrix.&lt;br /&gt;
&lt;br /&gt;
The core project team for each Joint Development project consists of the Joint Development Partner, MDOT’s Office of Real Estate and Economic Development (“ORED”), the Maryland Transit Administration (“MTA”), and the Office of the Attorney General (“OAG”). Together, these entities collaborate to oversee the planning, evaluation, negotiation, design, and implementation of Joint Development projects, ensuring alignment with MDOT’s strategic goals and objectives, policies, and regulatory requirements.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Stakeholder&lt;br /&gt;
! Role Summary&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
! Internal to MDOT&lt;br /&gt;
&lt;br /&gt;
|- &lt;br /&gt;
| Office of Real Estate and Economic Development (“ORED”)&lt;br /&gt;
| Located within The MDOT Secretary’s Office, ORED will lead and coordinate MDOT’s Joint Development efforts including executing planning efforts, solicitations, and agreements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Transit Administration (“MTA”)&lt;br /&gt;
| As the transit operator, MTA will define transit infrastructure requirements, standards, and specifications. MTA will be a key stakeholder in the Development Plan, detailed design review and approval; and construction to ensure the proposed development is integrated with the transit infrastructure, that the future service supports new development, that there are minimal disruptions to transit operations throughout construction, and that the assets are designed and delivered in accordance with the requirements, standards, and specifications. MTA will also be responsible for inspection during construction, commissioning, and handover of the transit infrastructure assets.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)	As the owner and maintainer of state roads, SHA will be a key partner in ensuring that local road capacity supports intended development, as well as providing early input into defining requirements and assisting with analysis in defining needs improvements and permitting. &lt;br /&gt;
To manage risk associated with Joint Development projects, SHA shall evaluate planning-level concepts of potential Joint Development projects to estimate potential SHA positions on future permitting. MDOT will seek to engage local roadway owners in this process as well. This process is outlined in the document TIS for Early Planning Coordination on Joint Developments (JD).&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Aviation Administration (“MAA”) &lt;br /&gt;
| The MAA owns and operates the Baltimore/Washington International Thurgood Marshall (BWI) and Martin State airports. MAA will be a key partner to ensure development adjacent to either of these MARC stations conforms with all airport requirements and operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Office of Attorney General (“OAG”)&lt;br /&gt;
| The OAG is the legal counsel to MDOT and is involved in reviewing solicitations and the drafting and negotiations of development agreements.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other MDOT Modal Departments&lt;br /&gt;
| As the owner and operator of State-owned land within ½ mile of transit station, other MDOT Modal Departments may be a key stakeholder in Joint Development projects. Any impacted modes will be a key partner to ensure development does not impact modal infrastructure or operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! External to MDOT&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other State Agencies&lt;br /&gt;
| Other State Agencies	MDOT will partner with other state agencies, as appropriate, to advance Joint Development projects.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Federal Transit Administration (“FTA”)&lt;br /&gt;
| FTA-assisted Joint Development is any Joint Development project that uses FTA funding or property acquired with FTA funding. MDOT coordinates its Joint Development as applicable with FTA to ensure that the project satisfies FTA’s Joint Development requirements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Jurisdictions &lt;br /&gt;
| Local jurisdictions are the local land use authority over State land and often control adjacent road networks and public space. Local jurisdictions are a key partner in developing site requirements and early site strategies to ensure potential future development meets local zoning and other regulations, as well as conforming with land use and comprehensive planning. &lt;br /&gt;
Local jurisdictions should closely coordinate with MDOT to ensure Master Developments that involve Joint Development uphold the State goals for TOD and Joint Development while also administering its own development approval process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Communities &lt;br /&gt;
| Residents, community-based organizations, and businesses in communities adjacent to Joint Development projects are key stakeholders throughout the process. MDOT and its Joint Development partners will engage local communities throughout the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other Rail Authorities Having Jurisdiction	&lt;br /&gt;
| MDOT will seek to coordinate with other rail authorities having jurisdiction to define requirements and processes for external review should the proposed joint development project potentially have impacts to the rail corridor or its zone of influence.  &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
;Partnerships with Local Jurisdictions&lt;br /&gt;
&lt;br /&gt;
In the pursuit of Joint Development, MDOT will work with local jurisdictions to coordinate pre-solicitation planning and site infrastructure needs and funding opportunities, defining community and jurisdictional goals and guiding principles, leveraging local economic development tools and strategies as well as resolving feasibility issues prior to solicitation as much as practically possible. For example, where amending land use and zoning regulations to better align with TOD objectives is necessary, MDOT may: &lt;br /&gt;
* Advocate for or initiate zoning amendments,&lt;br /&gt;
* Participate in and/or fund any necessary studies; and &lt;br /&gt;
* Provide technical assistance.&lt;br /&gt;
Through the course of planning and executing Joint Development, MDOT will work to include local development goals as well as community needs such as community and public service facilities as feasible. Defining these goals will occur in coordination with local jurisdictions and community partners through the pre-planning process.&lt;br /&gt;
&lt;br /&gt;
;Coordination with State Agencies&lt;br /&gt;
MDOT will coordinate with key State agency partners outside of MDOT to bring state resource support for realizing TOD through Joint Development. &lt;br /&gt;
&lt;br /&gt;
;Joint Development Partners&lt;br /&gt;
MDOT will be seeking, through Joint Development proposals, qualified development partners who have aligned interests in developing transit-oriented, mixed-use, mixed-income development at appropriate densities. MDOT views working with qualified developer partners as a key tool to advance TOD projects with shared costs and shared benefits to both parties. While MDOT will seek various methods to fund and finance the public infrastructure necessary to enable Joint Development, in collaboration with its local jurisdictional partners, MDOT expects its Joint Development partners to deliver high-quality TOD in line with the Goals, Objectives, and Principles outlined within MDOT ### Joint Development Policy, MDOT 657 Joint  Development Principles, the respective Joint Development solicitation as well as in accordance with applicable local laws and land use policies. &lt;br /&gt;
&lt;br /&gt;
==Appendix==&lt;br /&gt;
[[File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg|link=|1500px]]&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
MDOT 657.1 Joint Development Principles&lt;br /&gt;
&lt;br /&gt;
MDOT 657.3 Joint Development Implementation&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT_657.22_(1).pdf&amp;diff=6506</id>
		<title>File:Signed Supporting Document MDOT 657.22 (1).pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT_657.22_(1).pdf&amp;diff=6506"/>
		<updated>2025-07-28T16:35:59Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6505</id>
		<title>MDOT 657.1 Joint Development Principles</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6505"/>
		<updated>2025-07-28T16:35:39Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Additional Authorized Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Records Management]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 23, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT.pdf| Signed Supporting Document MDOT 657.1]]&lt;br /&gt;
&lt;br /&gt;
MDOT will evaluate Joint Development proposals and the Development Plan based on the following joint development principles. While the below points are all important priorities, specific joint development opportunities may place greater emphasis on selected priorities based on context and needs. In each respective Joint Development project, MDOT will specify which elements will receive greater emphasis over others as outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:1. Transit Integration - Proposed development must consider integration with the transit serving the proposed Joint Development site. This not only includes any rail station or bus stop but also connecting other modes to the site. Ensuring connectivity and universal accessibility to all the on-site or adjacent transit modes should be fundamental to any Development Plan. If present, different transit modes should be located as close together as possible to facilitate efficient intermodal connections.&lt;br /&gt;
&lt;br /&gt;
:2. Replacement Facilities - When transit facilities are modified or replaced as part of a Joint Development project, MDOT will seek to right-size, modernize, and improve station access as part of the project. In evaluating the scope and size of replacement of transit facilities affected by Joint Development, the proposed Joint Development plan should take into account:&lt;br /&gt;
&lt;br /&gt;
:::i. The future need of the transit facilities based on the existing and projected number of boardings and alightings at the Transit station, estimated number of new transit riders resulting from Joint Development; and estimated ridership from new development reasonably expected within the half-mile walkshed of a Transit station;&lt;br /&gt;
:::ii. Avoidance of unreasonable impacts to transit operations, service, vehicular and passenger flow, and customer experience;&lt;br /&gt;
:::iii. Cost effectiveness and life-cycle costs for facilities and operations; and,&lt;br /&gt;
:::iv. Long-term asset management plan(s) for MDOT’s facilities.&lt;br /&gt;
&lt;br /&gt;
::MDOT may consider reducing the replacement of existing facilities based on projected changes in ridership, access needs, and long-term multimodal strategy. Any such proposal to reduce the quantity of a replacement facility (e.g., a reduction in parking spaces) must be supported by a comprehensive justification that includes, but is not limited to:&lt;br /&gt;
:::i. The financial case, which considers the combined projected revenue from Joint Development (e.g., ground lease payments, participatory rent, etc.) and any revenue increases generated by induced ridership from the joint development. &lt;br /&gt;
:::ii. The strategic case, including alignment with MDOT’s goals, objectives, and principles. &lt;br /&gt;
:::iii. The economic case, such as broader community benefits, state and local tax generation impacts, and the private investment enabled by the joint development project.&lt;br /&gt;
:::iv.  The operational case, ensuring that multimodal access is maintained and that users can continue to access transit conveniently via other modes (e.g., biking, walking, bus, drop-off).&lt;br /&gt;
:::In all cases, proposals to reduce replacement facilities (e.g., fewer parking spaces than currently exist) must demonstrate that the total projected financial and non-financial benefits outweigh the value or utility of maintaining existing facility levels.&lt;br /&gt;
&lt;br /&gt;
:3. Density and Mix of Uses - Proposed Development Plans must reflect a level of density that will drive transit ridership and activity for the site. MDOT encourages that density levels be at the higher range of allowable density in the applicable land use or zoning requirements. Projects should allow for a mix of uses, with specific priority given to residential use, while also providing appropriate commercial use and other amenities that not only support activity within the station area but also draw transit riders. MDOT discourages automobile-dependent uses (e.g., vehicle repair businesses, drive-thrus, etc.).&lt;br /&gt;
&lt;br /&gt;
:4. Housing - Ensuring that Joint Development projects provide residential components that advance State housing goals is a key priority for MDOT. Given the diversity of markets and jurisdictional goals in the State, MDOT does not establish specific affordability targets in this document, however providing affordable units is a priority. MDOT will seek and evaluate affordability targets for any development proposal and subsequently work with the Joint Development partner, the Department of Housing and Community Development (DHCD), and the local jurisdiction to ensure that any Development Plan and subsequent build-out include a meaningful component of affordable units while maintaining the financial feasibility of the project.&lt;br /&gt;
&lt;br /&gt;
:5. Parking - MDOT is looking for a rationalized and efficient approach to parking. Providing rationalized parking is a critical component to successful TOD. The joint development project should not provide parking over what is minimally needed for the site. Development Plans must consider several factors when planning for parking on Joint Development sites. These factors include:&lt;br /&gt;
:::i. The amount of parking required to support transit ridership, and the initial location(s) for where that parking may be located will be determined pre-solicitation and may be provided as part of the Joint Development Solicitation, if applicable.&lt;br /&gt;
:::ii. The amount and location of parking provided for the development must consider the type of transit service serving the site. If the transit serving the site is a high-capacity transit service such as Metro Subway or Light Rail, MDOT expects a lower provision of parking to support the development. Joint development sites should target a ratio of less than 1 space per unit. However, if the site is served by commuter rail, additional parking for development may be required and a 1 space per unit ratio could be justifiable. MDOT will seek to coordinate with local jurisdictions prior to solicitation to reconcile zoning regulations that require minimum parking ratios above target levels conducive of TOD. &lt;br /&gt;
:::iii. Location of parking facilities should give priority to bus, pick-up &amp;amp; drop-off, micromobility, and pedestrian facilities. &lt;br /&gt;
:::iv. Opportunities for shared and/or structured parking are preferred, so long as they do not negatively impact passenger or vehicular traffic flow, safety, transit operations, and lifecycle costs. Such approaches should be considered and proposed by the Joint Development partner for MDOT’s review and approval, if not specified as part of the Joint Development solicitation.&lt;br /&gt;
:::v. Parking for the private development should not negatively impact flow or accessibility to the transit and meet [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines.]&lt;br /&gt;
&lt;br /&gt;
:6. Value Capture - MDOT will seek to achieve fair market value of real property in all joint development transactions. The fair market value of real property will be determined through consultation with real estate advisory firms and/or qualified third-party appraisers.. MDOT will contemplate discounts to land value and/or ground rent to achieve the goals, objectives, and principles of the Joint Development project or to fund improvements to transit facilities as needed based on a case-by-case basis. Any proposed reduction in fair market value must demonstrate that the value of the asset contributed to the joint development is equal to or greater than the fair share of the costs of the joint development project, or that MDOT will receive benefits (including non-monetary) equal to or greater than FMV. MDOT will also seek to participate in any monetization opportunities as a result of the Joint Development project.&lt;br /&gt;
&lt;br /&gt;
:7. Operations and Maintenance Costs - MDOT will seek to allocate operations and maintenance responsibilities associated with parking, open space, stormwater management, landscaping, cleaning, general maintenance, snow and ice removal, and graffiti removal to the Joint Development partner, or an approved designee, in a manner that is consistent with applicable MDOT Modal standards and does not increase MDOT’s administrative burden. &lt;br /&gt;
&lt;br /&gt;
:8. Electric Vehicle Charging Facilities - Wherever possible, Joint Development projects should provide electric vehicle charging as part of a parking program for transit customers, which requirements will be outlined within the Joint Development solicitation. Providing charging stations promotes the use of electric vehicles and is a major step towards achieving the State’s climate goals and clean vehicle mandates. Where practical, a parking program should incentivize electric vehicle use by allocating priority parking spaces (such as those immediately adjacent to transit station entrances, or multiple spaces on the ground level of a parking garage) for electric vehicle charging with compliant signage indicating the designated electric vehicle charging spaces. Joint Development proposals should consider the necessary infrastructure for electric vehicle charging stations, such as electric grid capacity for both near-term installations as well as future proofing for future installations. Note that the Americans with Disabilities Act requires provision of a “reasonable number” of accessible electric vehicle charging stations in an electric vehicle parking facility but does not specify an exact number or ratio. Where a requirement for the number of accessible electric vehicle charging stations exists, developers must provide at least that minimum number. Developers should reference federal and state guidelines for further guidance on the provision and design of accessible electric vehicle parking or to the local authority having jurisdictions standards and specifications. &lt;br /&gt;
&lt;br /&gt;
:9. Micromobility Facilities - As TOD aim to reduce car-dependence and promote multi-modal options, Joint Development projects are encouraged to incorporate facilities that promote micromobility access for bicycle and scooter travel. These amenities include protected shared use paths and connections to the local transportation system as well as secure and dedicated parking with electric charging stations for e-bikes and scooters which will be defined within the Joint Development solicitation. Joint Development projects should include micromobility facilities as identified in the local jurisdiction’s bicycle and pedestrian master plans, bicycle and pedestrian priority action plan, comprehensive plans, standards, and specifications. Developers should refer to the [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines] for further guidance on bicycle and scooter parking. To determine an appropriate bicycle facility, please reference Appendix D: Bicycle Facility Selection Guide of the [https://www.mdot.maryland.gov/OPCP/MDOT_State_Bike_Ped_Master_Plan_FULL_FINAL_VERSION.pdf 2050 Maryland Bicycle &amp;amp; Pedestrian Master Plan.] For the development of bicycle and scooter parking, please reference the Association of Pedestrian &amp;amp; Bicycle Professionals (“APBP”) Essentials of Bike Parking: Selecting and Installing Bike Parking That Works.&lt;br /&gt;
&lt;br /&gt;
:10. Site and Area Connectivity Improvements - The Development Plan for Joint Development projects should promote convenient, accessible intermodal access to the transit service. What this means in practice will depend on site context, though it could include:&lt;br /&gt;
:::i. Parking garages, pick-up and drop-off areas, and micromobility facilities should be located proximate to the station and transit facilities but give deference and space for overall pedestrian flow, public spaces and wayfinding to the station for all users.  Pedestrian pathways should be safe and direct to walk from the parking facility to the station platform or other transit boarding area.&lt;br /&gt;
:::ii. Passengers with limited mobility should have an accessible, direct route to transit service entrances with limited detours. &lt;br /&gt;
:::iii. Infrastructure should, to the extent possible, not interrupt the flow of people to and from the transit station.&lt;br /&gt;
&lt;br /&gt;
::Joint Development projects are a significant investment with potential community-wide impacts. Pedestrian and cyclist infrastructure built as part of a Joint Development project can serve as a foundation for further sidewalk and bike lane networks, for instance. MDOT will seek to collaborate with local jurisdictions, using Joint Development projects as a catalyst to achieve pedestrian, cyclist, and other “alternative mobility” goals, and advance pedestrian, cyclist, and other alternative mobility infrastructure projects laid out in local comprehensive plans, pedestrian/bike plans, “Vision Zero” plans, and other similar local planning documents. Some Joint Development projects may require roadway capital projects or improvements in State-owned rights-of-way. In such cases, these improvements must adhere to MDOT 750 Complete Streets Policy and such requirements will be outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:11. Urban Design, Placemaking, Wayfinding, and Branding/Identity - In general, a Joint Development project should aim to adhere to the urban design principles laid out in MTA’s Designing for Transit: Transit-Oriented Development Guidelines. Please see the development guidelines for more information, including detailed and context-dependent design guidelines. Joint Development projects should also adhere to any applicable local urban design guidelines. The branding, marketing, and identity of Joint Development projects – both development and wayfinding elements – should have a direct relationship to the transit station on which they are centered. For example, developers could incorporate the name of the transit station into the name of development projects where practical. The aim is for the development to promote and encourage its relationship to the mode of transit which serves that project. Wayfinding elements should clearly and prominently guide both pedestrians and drivers – whether they are area residents, workers, or visitors – to key station area assets including but not limited to the transit station, retail and other activity centers, and any public services and open space. Wayfinding elements can include signs, lighting, and surface finishes that promote legibility of the public realm. They should have a consistent visual identity (e.g., typefaces, colors) across separate wayfinding elements such that visitors to an area are able to easily identify them. &lt;br /&gt;
&lt;br /&gt;
:12. Public Space - MDOT aims to enhance and expand public space in communities through its Joint Development program. Developers may be required to construct or improve public spaces as part of a Joint Development project. These requirements will be outlined in the Joint Development solicitation and may include elements such as parks, plazas, squares, sidewalks, and shared-use paths. MDOT’s priority is that public spaces created through Joint Development are welcoming, safe, and vibrant, serving the joint development, broader TOD, and the community. To support placemaking and reinforce the role of the station as a community anchor, developers should prioritize locating required open space near or adjacent to station entrances to create an active and enticing focal point. To minimize long-term costs to the State, public spaces should be conveyed to the local jurisdiction or operated and maintained by the Joint Development partner, or an approved designee such as the ground lessee, homeowners’ association, or residents’ association. Public space design must not obstruct access to the station or impede clear sightlines and should comply with the standards and specifications of the authority having jurisdiction. When new public spaces are proposed, developers are expected to coordinate closely with MDOT, MTA, and local jurisdictions to define programming and activation plans, and to establish clear roles and responsibilities for ongoing operations and maintenance.&lt;br /&gt;
&lt;br /&gt;
:13. Phasing and Implementation - Joint Development project phasing will typically involve the upfront or concurrent completion of infrastructure projects, followed by vertical development. However, MDOT will consider alternative Joint Development project phasing that balances the ongoing needs of transit riders with the market viability of vertical development. Any construction activities should minimize disruption to the transit operations. Any disruptions or changes in transit service needed for construction must be approved by MTA.&lt;br /&gt;
&lt;br /&gt;
:14. Construction of MDOT Facilities - As part of a Joint Development project, it  may be required to modify or construct replacement transit facilities such as parking and bus facilities, roads, pick up and drop off spaces, station ingress and egress, and potentially other types of transit infrastructure in order to achieve an optimized TOD. Design for all MDOT facilities will be approved by the mode that either owns or operates the facility. Allowing for the design and construction or improvement of MDOT facilities to be led by developers can benefit both parties. MDOT benefits from cost and time efficiencies derived from a single entity being responsible for all capital improvements. Developers benefit because: &lt;br /&gt;
:::i. Developers have increased control over the timeline of infrastructure delivery (and therefore when vertical development may begin).&lt;br /&gt;
:::ii. Transit facilities may be better integrated into the overall development, which increases overall development potential and making it more attractive to prospective tenants and increase achievable rents.&lt;br /&gt;
::MTA, or the applicable mode, must approve of the design, construction, and delivery of its facilities in accordance with the mode’s design and construction standards and specifications. Construction activities will commence after MDOT issues a notice to proceed to the developer, and the developer has received all other necessary State and local permits. These will likely include a permit for the use of State property with agreements on maintenance of traffic, maintenance of station activities, and more. The developer will execute design and construction contracts with its subcontractors necessary to deliver the transit facilities.&lt;br /&gt;
&lt;br /&gt;
:15. Continuing Control - MDOT strongly prefers to structure its transactions as ground leases rather than fee simple sales as it creates regular compensation for MDOT to offset transit operations and better enables MDOT to realize long-term value to offset its investment in transit infrastructure. Exceptions to this preference may be considered and may include instances where practical, site or legal reasons require fee simple sale, such as for home ownership opportunities, or if such a transaction can create significant added value for MDOT or be necessary to inject upfront capital to fund infrastructure improvements. To ensure Federal Transit Administration (FTA) continuing control requirements are met on FTA-assisted properties, MDOT will require certain assurances such as restrictive covenants, as applicable. &lt;br /&gt;
&lt;br /&gt;
:16. Community and Stakeholder Engagement - MDOT will consult and work collaboratively with the community, state stakeholders, local jurisdictions and developers to encourage transit-supportive, high-quality development at transit stations and surrounding properties. Once a successful Joint Development partner is selected, the developer must actively and productively engage local communities with interest in the Joint Development site during planning and delivery of the project.&lt;br /&gt;
&lt;br /&gt;
:17. Local Planning and Approvals - All Joint Development projects must follow local laws and land use policies of the jurisdiction in which they are located. MDOT will proactively engage with local jurisdictions to gather input on preliminary development concepts, gain local support, and to the extent possible and where appropriate, secure any necessary zoning changes prior to publication of the Joint Development solicitation. The Joint Development partner will be responsible for securing all necessary permits and entitlements from the relevant local jurisdiction and any other authorities having jurisdiction.&lt;br /&gt;
&lt;br /&gt;
:18. Sustainability - Joint Development projects must meet local building sustainability requirements. In the absence of a local requirement, MDOT will require that the project meet a nationally recognized sustainability standard, such as LEED Silver, or equivalent, to be specified in the Joint Development solicitation. &lt;br /&gt;
&lt;br /&gt;
:19. MBE/DBE/SBE Contracting Goals - The State of Maryland’s Minority Business Enterprise (“MBE”), Disadvantaged Business Enterprise (“DBE”), and Small Business Enterprise (“SBE”) Programs are designed to provide contracting opportunities to MBE, DBE, and SBE businesses in both State and federally funded projects in accordance with State law. MBE/DBE/SBE Contracting Goals  may be defined in the Joint Development solicitation. Maryland MBEs, DBEs, and SBEs must complete the certification process with MDOT to be recognized as such for contracting purposes. Working with the awarded developer, MDOT will assist Joint Development partners in identifying opportunities for MBE, DBE, or SBE participation in the development and construction of the project. &lt;br /&gt;
&lt;br /&gt;
:20. Workforce Development and Labor Provisions - Joint Developments may qualify as “large-scale public work contract” under [https://governor.maryland.gov/Lists/ExecutiveOrders/Attachments/51/01.01.2024.18%20-%20FINAL%20EO%20-%20PLAs%20Apprenticeship%20Agreements%20and%20Community%20Hiring%20-%205.31.24%20%5bCLEAN%20COPY%5d.pdf Executive Order 01.01.2024.18] regarding project labor agreements, apprenticeships, and community hiring. Certain projects may be subject to [https://www.dol.gov/agencies/whd/government-contracts/construction Davis-Bacon Act] or [https://www.labor.maryland.gov/labor/prev/prevoverview.shtml Maryland Prevailing Wage] requirements. Contractors and subcontractors awarded contracts by the State of Maryland or its political subdivisions for the construction of public works that fall within the State’s statutory requirements must compensate covered workers as governed by Maryland’s Prevailing Wage Law. These requirements will be further described in the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:21. Americans with Disabilities Act - The Americans with Disabilities Act (“ADA”) prohibits discrimination against people with disabilities in employment, transportation, public accommodation, communications, and government activities. The development must comply with ADA requirements. Regarding infrastructure, where it is located will determine which requirements will apply. For WMATA and MTA-controlled stations, all spaces must meet at least Americans with Disabilities Access Guidelines (“ADAAG”) and FTA ADA Guidelines. Any improvements along State Highway Administration (SHA)managed facilities must meet SHA’s Accessibility Policy and Guidelines, which can be found in [https://www.roads.maryland.gov/mdotsha/pages/Index.aspx?PageId=26 SHA’s Accessibility Policy and Guidelines for Pedestrian Facilities Along State Highways.]&lt;br /&gt;
&lt;br /&gt;
:22. Transfer or Assignment of Development Agreements - MDOT understands that the developer or members of the development team may change during the term of a Joint Development project. Any changes to developer ownership following execution of the joint development agreements will be subject to MDOT’s approval at its sole and absolute discretion (including, where required, the approval of the Board of Public Works).&lt;br /&gt;
&lt;br /&gt;
:23. Business Ethics and Conflict of Interest - All Joint Development partners must comply with applicable State law requirements relating to conflict of interest, political contribution disclosure, and financial disclosures as part of the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6504</id>
		<title>MDOT 657.1 Joint Development Principles</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6504"/>
		<updated>2025-07-28T16:35:31Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Additional Authorized Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Records Management]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 23, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT.pdf| Signed Supporting Document MDOT 657.1]]&lt;br /&gt;
&lt;br /&gt;
MDOT will evaluate Joint Development proposals and the Development Plan based on the following joint development principles. While the below points are all important priorities, specific joint development opportunities may place greater emphasis on selected priorities based on context and needs. In each respective Joint Development project, MDOT will specify which elements will receive greater emphasis over others as outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:1. Transit Integration - Proposed development must consider integration with the transit serving the proposed Joint Development site. This not only includes any rail station or bus stop but also connecting other modes to the site. Ensuring connectivity and universal accessibility to all the on-site or adjacent transit modes should be fundamental to any Development Plan. If present, different transit modes should be located as close together as possible to facilitate efficient intermodal connections.&lt;br /&gt;
&lt;br /&gt;
:2. Replacement Facilities - When transit facilities are modified or replaced as part of a Joint Development project, MDOT will seek to right-size, modernize, and improve station access as part of the project. In evaluating the scope and size of replacement of transit facilities affected by Joint Development, the proposed Joint Development plan should take into account:&lt;br /&gt;
&lt;br /&gt;
:::i. The future need of the transit facilities based on the existing and projected number of boardings and alightings at the Transit station, estimated number of new transit riders resulting from Joint Development; and estimated ridership from new development reasonably expected within the half-mile walkshed of a Transit station;&lt;br /&gt;
:::ii. Avoidance of unreasonable impacts to transit operations, service, vehicular and passenger flow, and customer experience;&lt;br /&gt;
:::iii. Cost effectiveness and life-cycle costs for facilities and operations; and,&lt;br /&gt;
:::iv. Long-term asset management plan(s) for MDOT’s facilities.&lt;br /&gt;
&lt;br /&gt;
::MDOT may consider reducing the replacement of existing facilities based on projected changes in ridership, access needs, and long-term multimodal strategy. Any such proposal to reduce the quantity of a replacement facility (e.g., a reduction in parking spaces) must be supported by a comprehensive justification that includes, but is not limited to:&lt;br /&gt;
:::i. The financial case, which considers the combined projected revenue from Joint Development (e.g., ground lease payments, participatory rent, etc.) and any revenue increases generated by induced ridership from the joint development. &lt;br /&gt;
:::ii. The strategic case, including alignment with MDOT’s goals, objectives, and principles. &lt;br /&gt;
:::iii. The economic case, such as broader community benefits, state and local tax generation impacts, and the private investment enabled by the joint development project.&lt;br /&gt;
:::iv.  The operational case, ensuring that multimodal access is maintained and that users can continue to access transit conveniently via other modes (e.g., biking, walking, bus, drop-off).&lt;br /&gt;
:::In all cases, proposals to reduce replacement facilities (e.g., fewer parking spaces than currently exist) must demonstrate that the total projected financial and non-financial benefits outweigh the value or utility of maintaining existing facility levels.&lt;br /&gt;
&lt;br /&gt;
:3. Density and Mix of Uses - Proposed Development Plans must reflect a level of density that will drive transit ridership and activity for the site. MDOT encourages that density levels be at the higher range of allowable density in the applicable land use or zoning requirements. Projects should allow for a mix of uses, with specific priority given to residential use, while also providing appropriate commercial use and other amenities that not only support activity within the station area but also draw transit riders. MDOT discourages automobile-dependent uses (e.g., vehicle repair businesses, drive-thrus, etc.).&lt;br /&gt;
&lt;br /&gt;
:4. Housing - Ensuring that Joint Development projects provide residential components that advance State housing goals is a key priority for MDOT. Given the diversity of markets and jurisdictional goals in the State, MDOT does not establish specific affordability targets in this document, however providing affordable units is a priority. MDOT will seek and evaluate affordability targets for any development proposal and subsequently work with the Joint Development partner, the Department of Housing and Community Development (DHCD), and the local jurisdiction to ensure that any Development Plan and subsequent build-out include a meaningful component of affordable units while maintaining the financial feasibility of the project.&lt;br /&gt;
&lt;br /&gt;
:5. Parking - MDOT is looking for a rationalized and efficient approach to parking. Providing rationalized parking is a critical component to successful TOD. The joint development project should not provide parking over what is minimally needed for the site. Development Plans must consider several factors when planning for parking on Joint Development sites. These factors include:&lt;br /&gt;
:::i. The amount of parking required to support transit ridership, and the initial location(s) for where that parking may be located will be determined pre-solicitation and may be provided as part of the Joint Development Solicitation, if applicable.&lt;br /&gt;
:::ii. The amount and location of parking provided for the development must consider the type of transit service serving the site. If the transit serving the site is a high-capacity transit service such as Metro Subway or Light Rail, MDOT expects a lower provision of parking to support the development. Joint development sites should target a ratio of less than 1 space per unit. However, if the site is served by commuter rail, additional parking for development may be required and a 1 space per unit ratio could be justifiable. MDOT will seek to coordinate with local jurisdictions prior to solicitation to reconcile zoning regulations that require minimum parking ratios above target levels conducive of TOD. &lt;br /&gt;
:::iii. Location of parking facilities should give priority to bus, pick-up &amp;amp; drop-off, micromobility, and pedestrian facilities. &lt;br /&gt;
:::iv. Opportunities for shared and/or structured parking are preferred, so long as they do not negatively impact passenger or vehicular traffic flow, safety, transit operations, and lifecycle costs. Such approaches should be considered and proposed by the Joint Development partner for MDOT’s review and approval, if not specified as part of the Joint Development solicitation.&lt;br /&gt;
:::v. Parking for the private development should not negatively impact flow or accessibility to the transit and meet [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines.]&lt;br /&gt;
&lt;br /&gt;
:6. Value Capture - MDOT will seek to achieve fair market value of real property in all joint development transactions. The fair market value of real property will be determined through consultation with real estate advisory firms and/or qualified third-party appraisers.. MDOT will contemplate discounts to land value and/or ground rent to achieve the goals, objectives, and principles of the Joint Development project or to fund improvements to transit facilities as needed based on a case-by-case basis. Any proposed reduction in fair market value must demonstrate that the value of the asset contributed to the joint development is equal to or greater than the fair share of the costs of the joint development project, or that MDOT will receive benefits (including non-monetary) equal to or greater than FMV. MDOT will also seek to participate in any monetization opportunities as a result of the Joint Development project.&lt;br /&gt;
&lt;br /&gt;
:7. Operations and Maintenance Costs - MDOT will seek to allocate operations and maintenance responsibilities associated with parking, open space, stormwater management, landscaping, cleaning, general maintenance, snow and ice removal, and graffiti removal to the Joint Development partner, or an approved designee, in a manner that is consistent with applicable MDOT Modal standards and does not increase MDOT’s administrative burden. &lt;br /&gt;
&lt;br /&gt;
:8. Electric Vehicle Charging Facilities - Wherever possible, Joint Development projects should provide electric vehicle charging as part of a parking program for transit customers, which requirements will be outlined within the Joint Development solicitation. Providing charging stations promotes the use of electric vehicles and is a major step towards achieving the State’s climate goals and clean vehicle mandates. Where practical, a parking program should incentivize electric vehicle use by allocating priority parking spaces (such as those immediately adjacent to transit station entrances, or multiple spaces on the ground level of a parking garage) for electric vehicle charging with compliant signage indicating the designated electric vehicle charging spaces. Joint Development proposals should consider the necessary infrastructure for electric vehicle charging stations, such as electric grid capacity for both near-term installations as well as future proofing for future installations. Note that the Americans with Disabilities Act requires provision of a “reasonable number” of accessible electric vehicle charging stations in an electric vehicle parking facility but does not specify an exact number or ratio. Where a requirement for the number of accessible electric vehicle charging stations exists, developers must provide at least that minimum number. Developers should reference federal and state guidelines for further guidance on the provision and design of accessible electric vehicle parking or to the local authority having jurisdictions standards and specifications. &lt;br /&gt;
&lt;br /&gt;
:9. Micromobility Facilities - As TOD aim to reduce car-dependence and promote multi-modal options, Joint Development projects are encouraged to incorporate facilities that promote micromobility access for bicycle and scooter travel. These amenities include protected shared use paths and connections to the local transportation system as well as secure and dedicated parking with electric charging stations for e-bikes and scooters which will be defined within the Joint Development solicitation. Joint Development projects should include micromobility facilities as identified in the local jurisdiction’s bicycle and pedestrian master plans, bicycle and pedestrian priority action plan, comprehensive plans, standards, and specifications. Developers should refer to the [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines] for further guidance on bicycle and scooter parking. To determine an appropriate bicycle facility, please reference Appendix D: Bicycle Facility Selection Guide of the [https://www.mdot.maryland.gov/OPCP/MDOT_State_Bike_Ped_Master_Plan_FULL_FINAL_VERSION.pdf 2050 Maryland Bicycle &amp;amp; Pedestrian Master Plan.] For the development of bicycle and scooter parking, please reference the Association of Pedestrian &amp;amp; Bicycle Professionals (“APBP”) Essentials of Bike Parking: Selecting and Installing Bike Parking That Works.&lt;br /&gt;
&lt;br /&gt;
:10. Site and Area Connectivity Improvements - The Development Plan for Joint Development projects should promote convenient, accessible intermodal access to the transit service. What this means in practice will depend on site context, though it could include:&lt;br /&gt;
:::i. Parking garages, pick-up and drop-off areas, and micromobility facilities should be located proximate to the station and transit facilities but give deference and space for overall pedestrian flow, public spaces and wayfinding to the station for all users.  Pedestrian pathways should be safe and direct to walk from the parking facility to the station platform or other transit boarding area.&lt;br /&gt;
:::ii. Passengers with limited mobility should have an accessible, direct route to transit service entrances with limited detours. &lt;br /&gt;
:::iii. Infrastructure should, to the extent possible, not interrupt the flow of people to and from the transit station.&lt;br /&gt;
&lt;br /&gt;
::Joint Development projects are a significant investment with potential community-wide impacts. Pedestrian and cyclist infrastructure built as part of a Joint Development project can serve as a foundation for further sidewalk and bike lane networks, for instance. MDOT will seek to collaborate with local jurisdictions, using Joint Development projects as a catalyst to achieve pedestrian, cyclist, and other “alternative mobility” goals, and advance pedestrian, cyclist, and other alternative mobility infrastructure projects laid out in local comprehensive plans, pedestrian/bike plans, “Vision Zero” plans, and other similar local planning documents. Some Joint Development projects may require roadway capital projects or improvements in State-owned rights-of-way. In such cases, these improvements must adhere to MDOT 750 Complete Streets Policy and such requirements will be outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:11. Urban Design, Placemaking, Wayfinding, and Branding/Identity - In general, a Joint Development project should aim to adhere to the urban design principles laid out in MTA’s Designing for Transit: Transit-Oriented Development Guidelines. Please see the development guidelines for more information, including detailed and context-dependent design guidelines. Joint Development projects should also adhere to any applicable local urban design guidelines. The branding, marketing, and identity of Joint Development projects – both development and wayfinding elements – should have a direct relationship to the transit station on which they are centered. For example, developers could incorporate the name of the transit station into the name of development projects where practical. The aim is for the development to promote and encourage its relationship to the mode of transit which serves that project. Wayfinding elements should clearly and prominently guide both pedestrians and drivers – whether they are area residents, workers, or visitors – to key station area assets including but not limited to the transit station, retail and other activity centers, and any public services and open space. Wayfinding elements can include signs, lighting, and surface finishes that promote legibility of the public realm. They should have a consistent visual identity (e.g., typefaces, colors) across separate wayfinding elements such that visitors to an area are able to easily identify them. &lt;br /&gt;
&lt;br /&gt;
:12. Public Space - MDOT aims to enhance and expand public space in communities through its Joint Development program. Developers may be required to construct or improve public spaces as part of a Joint Development project. These requirements will be outlined in the Joint Development solicitation and may include elements such as parks, plazas, squares, sidewalks, and shared-use paths. MDOT’s priority is that public spaces created through Joint Development are welcoming, safe, and vibrant, serving the joint development, broader TOD, and the community. To support placemaking and reinforce the role of the station as a community anchor, developers should prioritize locating required open space near or adjacent to station entrances to create an active and enticing focal point. To minimize long-term costs to the State, public spaces should be conveyed to the local jurisdiction or operated and maintained by the Joint Development partner, or an approved designee such as the ground lessee, homeowners’ association, or residents’ association. Public space design must not obstruct access to the station or impede clear sightlines and should comply with the standards and specifications of the authority having jurisdiction. When new public spaces are proposed, developers are expected to coordinate closely with MDOT, MTA, and local jurisdictions to define programming and activation plans, and to establish clear roles and responsibilities for ongoing operations and maintenance.&lt;br /&gt;
&lt;br /&gt;
:13. Phasing and Implementation - Joint Development project phasing will typically involve the upfront or concurrent completion of infrastructure projects, followed by vertical development. However, MDOT will consider alternative Joint Development project phasing that balances the ongoing needs of transit riders with the market viability of vertical development. Any construction activities should minimize disruption to the transit operations. Any disruptions or changes in transit service needed for construction must be approved by MTA.&lt;br /&gt;
&lt;br /&gt;
:14. Construction of MDOT Facilities - As part of a Joint Development project, it  may be required to modify or construct replacement transit facilities such as parking and bus facilities, roads, pick up and drop off spaces, station ingress and egress, and potentially other types of transit infrastructure in order to achieve an optimized TOD. Design for all MDOT facilities will be approved by the mode that either owns or operates the facility. Allowing for the design and construction or improvement of MDOT facilities to be led by developers can benefit both parties. MDOT benefits from cost and time efficiencies derived from a single entity being responsible for all capital improvements. Developers benefit because: &lt;br /&gt;
:::i. Developers have increased control over the timeline of infrastructure delivery (and therefore when vertical development may begin).&lt;br /&gt;
:::ii. Transit facilities may be better integrated into the overall development, which increases overall development potential and making it more attractive to prospective tenants and increase achievable rents.&lt;br /&gt;
::MTA, or the applicable mode, must approve of the design, construction, and delivery of its facilities in accordance with the mode’s design and construction standards and specifications. Construction activities will commence after MDOT issues a notice to proceed to the developer, and the developer has received all other necessary State and local permits. These will likely include a permit for the use of State property with agreements on maintenance of traffic, maintenance of station activities, and more. The developer will execute design and construction contracts with its subcontractors necessary to deliver the transit facilities.&lt;br /&gt;
&lt;br /&gt;
:15. Continuing Control - MDOT strongly prefers to structure its transactions as ground leases rather than fee simple sales as it creates regular compensation for MDOT to offset transit operations and better enables MDOT to realize long-term value to offset its investment in transit infrastructure. Exceptions to this preference may be considered and may include instances where practical, site or legal reasons require fee simple sale, such as for home ownership opportunities, or if such a transaction can create significant added value for MDOT or be necessary to inject upfront capital to fund infrastructure improvements. To ensure Federal Transit Administration (FTA) continuing control requirements are met on FTA-assisted properties, MDOT will require certain assurances such as restrictive covenants, as applicable. &lt;br /&gt;
&lt;br /&gt;
:16. Community and Stakeholder Engagement - MDOT will consult and work collaboratively with the community, state stakeholders, local jurisdictions and developers to encourage transit-supportive, high-quality development at transit stations and surrounding properties. Once a successful Joint Development partner is selected, the developer must actively and productively engage local communities with interest in the Joint Development site during planning and delivery of the project.&lt;br /&gt;
&lt;br /&gt;
:17. Local Planning and Approvals - All Joint Development projects must follow local laws and land use policies of the jurisdiction in which they are located. MDOT will proactively engage with local jurisdictions to gather input on preliminary development concepts, gain local support, and to the extent possible and where appropriate, secure any necessary zoning changes prior to publication of the Joint Development solicitation. The Joint Development partner will be responsible for securing all necessary permits and entitlements from the relevant local jurisdiction and any other authorities having jurisdiction.&lt;br /&gt;
&lt;br /&gt;
:18. Sustainability - Joint Development projects must meet local building sustainability requirements. In the absence of a local requirement, MDOT will require that the project meet a nationally recognized sustainability standard, such as LEED Silver, or equivalent, to be specified in the Joint Development solicitation. &lt;br /&gt;
&lt;br /&gt;
:19. MBE/DBE/SBE Contracting Goals - The State of Maryland’s Minority Business Enterprise (“MBE”), Disadvantaged Business Enterprise (“DBE”), and Small Business Enterprise (“SBE”) Programs are designed to provide contracting opportunities to MBE, DBE, and SBE businesses in both State and federally funded projects in accordance with State law. MBE/DBE/SBE Contracting Goals  may be defined in the Joint Development solicitation. Maryland MBEs, DBEs, and SBEs must complete the certification process with MDOT to be recognized as such for contracting purposes. Working with the awarded developer, MDOT will assist Joint Development partners in identifying opportunities for MBE, DBE, or SBE participation in the development and construction of the project. &lt;br /&gt;
&lt;br /&gt;
:20. Workforce Development and Labor Provisions - Joint Developments may qualify as “large-scale public work contract” under [https://governor.maryland.gov/Lists/ExecutiveOrders/Attachments/51/01.01.2024.18%20-%20FINAL%20EO%20-%20PLAs%20Apprenticeship%20Agreements%20and%20Community%20Hiring%20-%205.31.24%20%5bCLEAN%20COPY%5d.pdf Executive Order 01.01.2024.18] regarding project labor agreements, apprenticeships, and community hiring. Certain projects may be subject to [https://www.dol.gov/agencies/whd/government-contracts/construction Davis-Bacon Act] or [https://www.labor.maryland.gov/labor/prev/prevoverview.shtml Maryland Prevailing Wage] requirements. Contractors and subcontractors awarded contracts by the State of Maryland or its political subdivisions for the construction of public works that fall within the State’s statutory requirements must compensate covered workers as governed by Maryland’s Prevailing Wage Law. These requirements will be further described in the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:21. Americans with Disabilities Act - The Americans with Disabilities Act (“ADA”) prohibits discrimination against people with disabilities in employment, transportation, public accommodation, communications, and government activities. The development must comply with ADA requirements. Regarding infrastructure, where it is located will determine which requirements will apply. For WMATA and MTA-controlled stations, all spaces must meet at least Americans with Disabilities Access Guidelines (“ADAAG”) and FTA ADA Guidelines. Any improvements along State Highway Administration (SHA)managed facilities must meet SHA’s Accessibility Policy and Guidelines, which can be found in [https://www.roads.maryland.gov/mdotsha/pages/Index.aspx?PageId=26 SHA’s Accessibility Policy and Guidelines for Pedestrian Facilities Along State Highways.]&lt;br /&gt;
&lt;br /&gt;
:22. Transfer or Assignment of Development Agreements - MDOT understands that the developer or members of the development team may change during the term of a Joint Development project. Any changes to developer ownership following execution of the joint development agreements will be subject to MDOT’s approval at its sole and absolute discretion (including, where required, the approval of the Board of Public Works).&lt;br /&gt;
&lt;br /&gt;
:23. Business Ethics and Conflict of Interest - All Joint Development partners must comply with applicable State law requirements relating to conflict of interest, political contribution disclosure, and financial disclosures as part of the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
&lt;br /&gt;
[[657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
&lt;br /&gt;
[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT.pdf&amp;diff=6503</id>
		<title>File:Signed Supporting Document MDOT.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_Supporting_Document_MDOT.pdf&amp;diff=6503"/>
		<updated>2025-07-28T16:35:12Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:01.01.2024.18_-.pdf&amp;diff=6502</id>
		<title>File:01.01.2024.18 -.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:01.01.2024.18_-.pdf&amp;diff=6502"/>
		<updated>2025-07-28T16:34:30Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6501</id>
		<title>MDOT 657 Joint Development</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6501"/>
		<updated>2025-07-28T16:34:06Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Authorized/Supporting Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: April, 30, 2025&lt;br /&gt;
 Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed MDOT 657 policy.pdf|MDOT 657 Joint Development Signed Hard Copy]]&lt;br /&gt;
&lt;br /&gt;
==Purpose==&lt;br /&gt;
The purpose of this Policy is to:&lt;br /&gt;
# Define MDOT’s Joint Development Program’s goals, objectives, and principles;&lt;br /&gt;
# Establish roles and responsibilities;&lt;br /&gt;
# Establish and maintain processes and procedures; and&lt;br /&gt;
# Ensure consistent compliance across MDOT.&lt;br /&gt;
&lt;br /&gt;
==Reference(s)==&lt;br /&gt;
[[media:01.01.2024.18 -.pdf| Executive Order 01.01.2024.18]]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Transportation Article, §7–101, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-102&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, §7–102, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[[media:MDOT-750-Complete-Streets-Signed.pdf|MDOT 750 Complete Streets Policy ]]&lt;br /&gt;
&lt;br /&gt;
[https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines]&lt;br /&gt;
&lt;br /&gt;
==Scope==&lt;br /&gt;
This Policy is applicable to all existing and future Joint Development projects on State-owned property that is adjacent to a planned or existing transit station; property, any part of which is located within one-half mile of a planned or existing transit station; and property that is adjacent to a planned or existing transit corridor.&lt;br /&gt;
&lt;br /&gt;
This Policy is applicable to all modal administrations, MDOT employees, contract employees, contractors, and consultants.  &lt;br /&gt;
&lt;br /&gt;
==Responsible Party==&lt;br /&gt;
The Assistant Secretary for Project Development and Delivery.&lt;br /&gt;
&lt;br /&gt;
==Policy Statement==&lt;br /&gt;
&lt;br /&gt;
# MDOT will aim to reach the goals and objectives set forth herein. These goals and objectives will serve as the overarching guiding framework for Joint Development projects throughout the Joint Development process, particularly in the evaluation of Joint Development proposals. It is important to recognize that the relative priority of these goals may be adjusted based on the unique context of each site, which will be outlined as part of the Joint Development solicitation.&lt;br /&gt;
#:* Increase Transit Ridership and reduce single occupancy Vehicle Miles Travelled: MDOT aims to grow transit ridership through new development in station areas facilitated by its Joint Development Program, providing station area residents, workers, and visitors access to transit.&lt;br /&gt;
#:* Increase Housing Supply (Including Affordable Housing) and Jobs: MDOT seeks to foster sustainable regional growth by creating new housing and business opportunities near transit. &lt;br /&gt;
#:* Maximize the return on the State’s transportation infrastructure investments: MDOT aims to prioritize higher-density and mixed-use transit-oriented development (TOD) around transit stations maximizes the State’s historic $2 billion infrastructure investment in MTA’s core service area. TOD increases transit ridership, reduces congestion, and drives economic growth by creating walkable, accessible communities. This approach ensures long-term returns while advancing Governor Moore’s State Plan.&lt;br /&gt;
#:* Improve Transit Facilities: Where improvement, modification, or relocation of transit facilities will allow for a better development program, MDOT may require developers to relocate, reconfigure, or improve transit facilities as part of a Joint Development project. Additionally, MDOT may also seek to improve or expand transit facilities as part of the project and seek Joint Development partners in delivering those facilities. The intent is to enable better development and improved transit facilities. In any case, modification of transit facilities or any aspect of Joint Development should seek to minimize operating costs and seek capital cost avoidance for MDOT, where feasible.&lt;br /&gt;
#:* Enhance Station Access and Connectivity: New development should be integrated seamlessly with the surrounding street and mobility networks as well as with the surrounding public spaces. Ensuring connectivity to and through development to the transit infrastructure is a key goal. Improvements and responsibility to implement those improvements will vary depending on location (on-site vs. off-site) and breadth of the improvements. &lt;br /&gt;
#:* Support Long-Term Economic Development and Revenue Goals: MDOT’s Joint Development program is dedicated to advancing economic growth and generating sustainable revenue for the State and local jurisdictions over the long term by generating new state and local taxes on formerly undeveloped and tax-exempt land. Long-term economic development goals and ridership generation are considered top priority in implementing Joint Development projects, however MDOT will seek to participate in other revenue generating activities as feasible within a Joint Development project.&lt;br /&gt;
#:* Support Local Development Goals and Community Needs: MDOT recognizes the importance of aligning Joint Development efforts with local development goals and addressing community needs. Joint Development projects will aim to enhance the quality of life for residents while supporting broader transit and economic objectives.&lt;br /&gt;
#:* Seek to Minimize Risks: Joint Development projects should minimize financial, operational, and safety risks to MDOT and their Joint Development partners, by establishing a predictable and transparent process with clear expectations and requirements. &lt;br /&gt;
#:* Be a Trusted Business Partner: MDOT will act as a competent and reliable business partner, retaining risks it can manage most appropriately and effectively and seek out partners with proven track records of quality development.&lt;br /&gt;
&lt;br /&gt;
==Definitions==&lt;br /&gt;
For the purposes of this Policy, the following words have the following meanings:&lt;br /&gt;
&lt;br /&gt;
# Joint Development means a public transportation project that integrally relates to, and often co-locates with commercial, residential, mixed-use, or other non-transit development. Joint Development may include partnerships for public or private development associated with any mode of transit system that is being improved through new construction, renovation, or extension. Joint Development may also include intermodal facilities, intercity bus and rail facilities, transit malls, or historic transportation facilities. &lt;br /&gt;
# Transit Corridor means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit-Oriented Development (TOD) means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit station means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
&lt;br /&gt;
==Authorized/Supporting Documents==&lt;br /&gt;
&lt;br /&gt;
*[[MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
*[[MDOT 657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
*[[MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6500</id>
		<title>MDOT 657 Joint Development</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6500"/>
		<updated>2025-07-28T16:33:35Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Authorized/Supporting Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: April, 30, 2025&lt;br /&gt;
 Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed MDOT 657 policy.pdf|MDOT 657 Joint Development Signed Hard Copy]]&lt;br /&gt;
&lt;br /&gt;
==Purpose==&lt;br /&gt;
The purpose of this Policy is to:&lt;br /&gt;
# Define MDOT’s Joint Development Program’s goals, objectives, and principles;&lt;br /&gt;
# Establish roles and responsibilities;&lt;br /&gt;
# Establish and maintain processes and procedures; and&lt;br /&gt;
# Ensure consistent compliance across MDOT.&lt;br /&gt;
&lt;br /&gt;
==Reference(s)==&lt;br /&gt;
[[media:01.01.2024.18 -.pdf| Executive Order 01.01.2024.18]]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Transportation Article, §7–101, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-102&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, §7–102, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[[media:MDOT-750-Complete-Streets-Signed.pdf|MDOT 750 Complete Streets Policy ]]&lt;br /&gt;
&lt;br /&gt;
[https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines]&lt;br /&gt;
&lt;br /&gt;
==Scope==&lt;br /&gt;
This Policy is applicable to all existing and future Joint Development projects on State-owned property that is adjacent to a planned or existing transit station; property, any part of which is located within one-half mile of a planned or existing transit station; and property that is adjacent to a planned or existing transit corridor.&lt;br /&gt;
&lt;br /&gt;
This Policy is applicable to all modal administrations, MDOT employees, contract employees, contractors, and consultants.  &lt;br /&gt;
&lt;br /&gt;
==Responsible Party==&lt;br /&gt;
The Assistant Secretary for Project Development and Delivery.&lt;br /&gt;
&lt;br /&gt;
==Policy Statement==&lt;br /&gt;
&lt;br /&gt;
# MDOT will aim to reach the goals and objectives set forth herein. These goals and objectives will serve as the overarching guiding framework for Joint Development projects throughout the Joint Development process, particularly in the evaluation of Joint Development proposals. It is important to recognize that the relative priority of these goals may be adjusted based on the unique context of each site, which will be outlined as part of the Joint Development solicitation.&lt;br /&gt;
#:* Increase Transit Ridership and reduce single occupancy Vehicle Miles Travelled: MDOT aims to grow transit ridership through new development in station areas facilitated by its Joint Development Program, providing station area residents, workers, and visitors access to transit.&lt;br /&gt;
#:* Increase Housing Supply (Including Affordable Housing) and Jobs: MDOT seeks to foster sustainable regional growth by creating new housing and business opportunities near transit. &lt;br /&gt;
#:* Maximize the return on the State’s transportation infrastructure investments: MDOT aims to prioritize higher-density and mixed-use transit-oriented development (TOD) around transit stations maximizes the State’s historic $2 billion infrastructure investment in MTA’s core service area. TOD increases transit ridership, reduces congestion, and drives economic growth by creating walkable, accessible communities. This approach ensures long-term returns while advancing Governor Moore’s State Plan.&lt;br /&gt;
#:* Improve Transit Facilities: Where improvement, modification, or relocation of transit facilities will allow for a better development program, MDOT may require developers to relocate, reconfigure, or improve transit facilities as part of a Joint Development project. Additionally, MDOT may also seek to improve or expand transit facilities as part of the project and seek Joint Development partners in delivering those facilities. The intent is to enable better development and improved transit facilities. In any case, modification of transit facilities or any aspect of Joint Development should seek to minimize operating costs and seek capital cost avoidance for MDOT, where feasible.&lt;br /&gt;
#:* Enhance Station Access and Connectivity: New development should be integrated seamlessly with the surrounding street and mobility networks as well as with the surrounding public spaces. Ensuring connectivity to and through development to the transit infrastructure is a key goal. Improvements and responsibility to implement those improvements will vary depending on location (on-site vs. off-site) and breadth of the improvements. &lt;br /&gt;
#:* Support Long-Term Economic Development and Revenue Goals: MDOT’s Joint Development program is dedicated to advancing economic growth and generating sustainable revenue for the State and local jurisdictions over the long term by generating new state and local taxes on formerly undeveloped and tax-exempt land. Long-term economic development goals and ridership generation are considered top priority in implementing Joint Development projects, however MDOT will seek to participate in other revenue generating activities as feasible within a Joint Development project.&lt;br /&gt;
#:* Support Local Development Goals and Community Needs: MDOT recognizes the importance of aligning Joint Development efforts with local development goals and addressing community needs. Joint Development projects will aim to enhance the quality of life for residents while supporting broader transit and economic objectives.&lt;br /&gt;
#:* Seek to Minimize Risks: Joint Development projects should minimize financial, operational, and safety risks to MDOT and their Joint Development partners, by establishing a predictable and transparent process with clear expectations and requirements. &lt;br /&gt;
#:* Be a Trusted Business Partner: MDOT will act as a competent and reliable business partner, retaining risks it can manage most appropriately and effectively and seek out partners with proven track records of quality development.&lt;br /&gt;
&lt;br /&gt;
==Definitions==&lt;br /&gt;
For the purposes of this Policy, the following words have the following meanings:&lt;br /&gt;
&lt;br /&gt;
# Joint Development means a public transportation project that integrally relates to, and often co-locates with commercial, residential, mixed-use, or other non-transit development. Joint Development may include partnerships for public or private development associated with any mode of transit system that is being improved through new construction, renovation, or extension. Joint Development may also include intermodal facilities, intercity bus and rail facilities, transit malls, or historic transportation facilities. &lt;br /&gt;
# Transit Corridor means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit-Oriented Development (TOD) means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit station means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
&lt;br /&gt;
==Authorized/Supporting Documents==&lt;br /&gt;
&lt;br /&gt;
[[Signed Supporting Document MDOT 657.1]]&lt;br /&gt;
&lt;br /&gt;
[[Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
[[Signed Supporting Document MDOT 657.3]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6499</id>
		<title>MDOT 657 Joint Development</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6499"/>
		<updated>2025-07-28T16:33:18Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Authorized/Supporting Documents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: April, 30, 2025&lt;br /&gt;
 Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed MDOT 657 policy.pdf|MDOT 657 Joint Development Signed Hard Copy]]&lt;br /&gt;
&lt;br /&gt;
==Purpose==&lt;br /&gt;
The purpose of this Policy is to:&lt;br /&gt;
# Define MDOT’s Joint Development Program’s goals, objectives, and principles;&lt;br /&gt;
# Establish roles and responsibilities;&lt;br /&gt;
# Establish and maintain processes and procedures; and&lt;br /&gt;
# Ensure consistent compliance across MDOT.&lt;br /&gt;
&lt;br /&gt;
==Reference(s)==&lt;br /&gt;
[[media:01.01.2024.18 -.pdf| Executive Order 01.01.2024.18]]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Transportation Article, §7–101, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-102&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, §7–102, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[[media:MDOT-750-Complete-Streets-Signed.pdf|MDOT 750 Complete Streets Policy ]]&lt;br /&gt;
&lt;br /&gt;
[https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines]&lt;br /&gt;
&lt;br /&gt;
==Scope==&lt;br /&gt;
This Policy is applicable to all existing and future Joint Development projects on State-owned property that is adjacent to a planned or existing transit station; property, any part of which is located within one-half mile of a planned or existing transit station; and property that is adjacent to a planned or existing transit corridor.&lt;br /&gt;
&lt;br /&gt;
This Policy is applicable to all modal administrations, MDOT employees, contract employees, contractors, and consultants.  &lt;br /&gt;
&lt;br /&gt;
==Responsible Party==&lt;br /&gt;
The Assistant Secretary for Project Development and Delivery.&lt;br /&gt;
&lt;br /&gt;
==Policy Statement==&lt;br /&gt;
&lt;br /&gt;
# MDOT will aim to reach the goals and objectives set forth herein. These goals and objectives will serve as the overarching guiding framework for Joint Development projects throughout the Joint Development process, particularly in the evaluation of Joint Development proposals. It is important to recognize that the relative priority of these goals may be adjusted based on the unique context of each site, which will be outlined as part of the Joint Development solicitation.&lt;br /&gt;
#:* Increase Transit Ridership and reduce single occupancy Vehicle Miles Travelled: MDOT aims to grow transit ridership through new development in station areas facilitated by its Joint Development Program, providing station area residents, workers, and visitors access to transit.&lt;br /&gt;
#:* Increase Housing Supply (Including Affordable Housing) and Jobs: MDOT seeks to foster sustainable regional growth by creating new housing and business opportunities near transit. &lt;br /&gt;
#:* Maximize the return on the State’s transportation infrastructure investments: MDOT aims to prioritize higher-density and mixed-use transit-oriented development (TOD) around transit stations maximizes the State’s historic $2 billion infrastructure investment in MTA’s core service area. TOD increases transit ridership, reduces congestion, and drives economic growth by creating walkable, accessible communities. This approach ensures long-term returns while advancing Governor Moore’s State Plan.&lt;br /&gt;
#:* Improve Transit Facilities: Where improvement, modification, or relocation of transit facilities will allow for a better development program, MDOT may require developers to relocate, reconfigure, or improve transit facilities as part of a Joint Development project. Additionally, MDOT may also seek to improve or expand transit facilities as part of the project and seek Joint Development partners in delivering those facilities. The intent is to enable better development and improved transit facilities. In any case, modification of transit facilities or any aspect of Joint Development should seek to minimize operating costs and seek capital cost avoidance for MDOT, where feasible.&lt;br /&gt;
#:* Enhance Station Access and Connectivity: New development should be integrated seamlessly with the surrounding street and mobility networks as well as with the surrounding public spaces. Ensuring connectivity to and through development to the transit infrastructure is a key goal. Improvements and responsibility to implement those improvements will vary depending on location (on-site vs. off-site) and breadth of the improvements. &lt;br /&gt;
#:* Support Long-Term Economic Development and Revenue Goals: MDOT’s Joint Development program is dedicated to advancing economic growth and generating sustainable revenue for the State and local jurisdictions over the long term by generating new state and local taxes on formerly undeveloped and tax-exempt land. Long-term economic development goals and ridership generation are considered top priority in implementing Joint Development projects, however MDOT will seek to participate in other revenue generating activities as feasible within a Joint Development project.&lt;br /&gt;
#:* Support Local Development Goals and Community Needs: MDOT recognizes the importance of aligning Joint Development efforts with local development goals and addressing community needs. Joint Development projects will aim to enhance the quality of life for residents while supporting broader transit and economic objectives.&lt;br /&gt;
#:* Seek to Minimize Risks: Joint Development projects should minimize financial, operational, and safety risks to MDOT and their Joint Development partners, by establishing a predictable and transparent process with clear expectations and requirements. &lt;br /&gt;
#:* Be a Trusted Business Partner: MDOT will act as a competent and reliable business partner, retaining risks it can manage most appropriately and effectively and seek out partners with proven track records of quality development.&lt;br /&gt;
&lt;br /&gt;
==Definitions==&lt;br /&gt;
For the purposes of this Policy, the following words have the following meanings:&lt;br /&gt;
&lt;br /&gt;
# Joint Development means a public transportation project that integrally relates to, and often co-locates with commercial, residential, mixed-use, or other non-transit development. Joint Development may include partnerships for public or private development associated with any mode of transit system that is being improved through new construction, renovation, or extension. Joint Development may also include intermodal facilities, intercity bus and rail facilities, transit malls, or historic transportation facilities. &lt;br /&gt;
# Transit Corridor means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit-Oriented Development (TOD) means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit station means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
&lt;br /&gt;
==Authorized/Supporting Documents==&lt;br /&gt;
&lt;br /&gt;
[[Signed Supporting Document MDOT 657.1.pdf| MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
&lt;br /&gt;
[[Signed Supporting Document MDOT 657.2.pdf | MDOT 657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
&lt;br /&gt;
[[Signed Supporting Document MDOT 657.3.pdf| MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_MDOT_657_policy.pdf&amp;diff=6498</id>
		<title>File:Signed MDOT 657 policy.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Signed_MDOT_657_policy.pdf&amp;diff=6498"/>
		<updated>2025-07-28T16:32:53Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Picture1.jpg&amp;diff=6497</id>
		<title>File:Picture1.jpg</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Picture1.jpg&amp;diff=6497"/>
		<updated>2025-07-28T16:31:27Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.3_Joint_Development_Implementation&amp;diff=6496</id>
		<title>MDOT 657.3 Joint Development Implementation</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.3_Joint_Development_Implementation&amp;diff=6496"/>
		<updated>2025-07-28T16:31:02Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: Created page with &amp;quot;Category:Real Estate  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the si...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media: Signed Supporting Document MDOT 657.3.pdf | Signed Supporting Document MDOT 657.3]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key processes, procedures, MDOT’s reserved rights, and approvals that govern MDOT’s Joint Development Program. It establishes the framework for prioritizing Joint Development projects, managing solicited and unsolicited proposals, negotiating commercial agreements, and securing necessary project approvals. By adhering to these guidelines, MDOT ensures that Joint Development projects are in line with the goals, objectives, and principles outlined within MDOT ### Joint Development Policy and MDOT ###.1 Joint Development Principles.&lt;br /&gt;
&lt;br /&gt;
1. Joint Development Prioritization&lt;br /&gt;
&lt;br /&gt;
:MDOT will seek to assess its real estate portfolio to identify and evaluate opportunities on a consistent basis to develop State-owned and other public land for Joint Development. Key factors in determining prioritization, in addition to the consideration of the Joint Development Goals and Objectives, include:&lt;br /&gt;
&lt;br /&gt;
:* Enabling local land use and zoning, particularly where zoning allows dense, mixed-use development;&lt;br /&gt;
:* Development potential (i.e., physical conditions such as site size, topography, and environmental conditions, as well as regulatory conditions such as appropriate local zoning);&lt;br /&gt;
:* Support of the local jurisdiction;&lt;br /&gt;
:* Infrastructure needs; &lt;br /&gt;
:* Adequate market potential to meet State of Maryland and local TOD goals and objectives; &lt;br /&gt;
:* Existence of adequate transit capacity or planned new or expanded capacity;&lt;br /&gt;
:* Community support; &lt;br /&gt;
:* Opportunities for future connectivity; and &lt;br /&gt;
:* Funding and financing opportunities to close any infrastructure or development funding gaps needed to realize meaningful TOD.&lt;br /&gt;
&lt;br /&gt;
2. Joint Development Process&lt;br /&gt;
&lt;br /&gt;
:The Joint Development process is managed by MDOT’s Office of Real Estate and Development and will follow the process and procedures outlined in MDOT XXX Join Development  Policy. The Policy allows for both solicited and unsolicited joint development proposals from interested third parties for commercial, residential, mixed-use, or other development on State-owned land that integrates with and/or co-locates with existing or planned State transportation infrastructure, including the potential to acquire, construct, improve, maintain, and/or operate elements of the land infrastructure as part of the development. The major steps involved in evaluating, selecting, and implementing Joint Development projects are similar for both solicited and unsolicited proposals. &lt;br /&gt;
&lt;br /&gt;
:The subject property must have been declared as available for use for TOD through the Internal Clearance process of the MDOT modal unit (e.g., MTA, SHA, MAA) that owns the underlying land prior to solicitation or as part of the Unsolicited Joint Development process. &lt;br /&gt;
&lt;br /&gt;
:The competitive solicitation process will consider the protection of any proprietary information that is identified as such and included in the unsolicited proposal. Upon request for information from a third party, MDOT will make an independent determination whether the information may be disclosed under applicable law, including but not limited to the Maryland Public Information Act, Title 4 of the General Provisions Article of the Annotated Code of Maryland.&lt;br /&gt;
&lt;br /&gt;
:Generally, the Joint Development process will adhere to the following high-level sequence of steps shown in Figure 1, which will be subject to change based on the needs and complexity of each Joint Development project. The approximate timelines reflect a combination of MDOT-driven and jointly coordinated activities. They are provided as general guidance and assume that both parties are committed to advancing the project in good faith and in a timely manner. For a detailed breakdown of the Joint Development process and workflow, see Appendix A – Joint Development Process.&lt;br /&gt;
&lt;br /&gt;
;Figure 1 | High-Level Process and Timelines of the Joint Development Process&lt;br /&gt;
&lt;br /&gt;
[[File:Picture1.jpg|link=|900px]]&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! #&lt;br /&gt;
! Step&lt;br /&gt;
! Description&lt;br /&gt;
!Timeframe&lt;br /&gt;
!Lead Agencies &amp;amp; Stakeholders&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Identified Opportunity&lt;br /&gt;
|MDOT will seek to assess its real estate portfolio to identify and evaluate opportunities on a consistent basis to develop State-owned and other public land for Joint Development.&lt;br /&gt;
|Continuous&lt;br /&gt;
|&lt;br /&gt;
* MDOT (ORED, MTA)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|TOD Site Strategy &lt;br /&gt;
|Initial planning and defining of site specific goals, objectives, and requirements for Joint Development projects. This may include community engagement prior to solicitation.&lt;br /&gt;
|6-12 months &lt;br /&gt;
|&lt;br /&gt;
*MDOT (ORED, MTA, SHA)&lt;br /&gt;
*DHCD&lt;br /&gt;
*Local jurisdictions&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Solicitation &lt;br /&gt;
|Public and competitive solicitation leading to the selection of a Joint Development Partner. &lt;br /&gt;
|6 months&lt;br /&gt;
|&lt;br /&gt;
*MDOT (ORED, MTA, SHA, OAG)&lt;br /&gt;
*Developers&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|4A&lt;br /&gt;
|Exclusive Negotiating Period and Development Plan Design&lt;br /&gt;
|Parties to execute an Exclusive Negotiating Privilege Agreement and establish term sheet leading to Master Development Agreement terms. The Developer to complete due diligence and advance master planning and the design of the Development Plan. This step takes place concurrently with Step 4B.&lt;br /&gt;
|6 months&lt;br /&gt;
|&lt;br /&gt;
*MDOT (ORED, MTA, OAG, SHA)&lt;br /&gt;
*DHCD&lt;br /&gt;
*Local jurisdictions&lt;br /&gt;
*Joint Development Partner&lt;br /&gt;
*Community &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| 4B&lt;br /&gt;
| 4.B - Master Developer Agreement (MDA) Negotiations&lt;br /&gt;
| This is the timeframe allotted to negotiate terms for the MDA, Master Ground Lease, and the forms for associated Phase Ground Lease(s), Purchase Agreement(s), Reciprocal Easement and Operating Agreement(s), Construction Agreement and other agreements necessary for the delivery of the project, as applicable,&lt;br /&gt;
| 6-12 Months&lt;br /&gt;
|&lt;br /&gt;
* MDOT (ORED, MTA, OAG)&lt;br /&gt;
* Joint Development Partner&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
| Project Approvals and MDA Execution &lt;br /&gt;
|Seek FTA concurrence and Board of Public Works approval of the MDA, conveyance agreements and Development Plan. &lt;br /&gt;
&lt;br /&gt;
Execute MDA and associated agreements with preferred Joint Development Partner.&lt;br /&gt;
|2-4 Months&lt;br /&gt;
|&lt;br /&gt;
* MDOT (ORED, MTA)&lt;br /&gt;
* Joint Development Partner&lt;br /&gt;
* Board of Public Works (Approval Required)&lt;br /&gt;
* FTA (Concurrence Required)&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Detailed Design &amp;amp; Closing&lt;br /&gt;
|Completion of detailed design review of the transit infrastructure and private infrastructure to advance construction/delivery of the project. &lt;br /&gt;
&lt;br /&gt;
Closing, or Phased Closing, of the transaction, as applicable.&lt;br /&gt;
|6-12 Months (Developer-driven timeline)&lt;br /&gt;
|&lt;br /&gt;
* MDOT (ORED, MTA, SHA)&lt;br /&gt;
* Joint Development Partner&lt;br /&gt;
*Community&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Construction &amp;amp; Operations &lt;br /&gt;
|Joint Development Partner to advance to construction of the project, supported by ongoing community engagement.&lt;br /&gt;
&lt;br /&gt;
Applicable mode to undertake construction inspection, commissioning, close-out, and handover of the infrastructure.&lt;br /&gt;
|Project specific timelines&lt;br /&gt;
|&lt;br /&gt;
* MDOT (ORED, MTA, SHA)&lt;br /&gt;
* Local jurisdictions&lt;br /&gt;
* Joint Development Partner&lt;br /&gt;
* Community &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
3. Solicited Joint Development Proposals&lt;br /&gt;
&lt;br /&gt;
:MDOT may issue Joint Development solicitations which will include the information developed as part of MDOT’s TOD Site Strategy planning and due diligence efforts and which will reflect community feedback. MDOT will publish the solicitation on MDOT’s website and will seek to promote it through press releases and social media channels. &lt;br /&gt;
&lt;br /&gt;
:While conditions may warrant a single-step RFP process, MDOT prefers to utilize the following two-step solicitation process for Joint Development.&lt;br /&gt;
# A Request for Qualifications (RFQ), leading to &lt;br /&gt;
# A Request for Proposals (RFP) limited to the qualified entities selected from the RFQ process.&lt;br /&gt;
&lt;br /&gt;
:The solicitation will outline the minimum qualifications and evaluation criteria, which will be required of interested developers. Proposers will be instructed as to the format in which to submit proposals and what minimum information and materials must be submitted in order for the proposal to be considered complete. The solicitation process may include a pre-bid meeting, questions and answers period, and a site visit with interested development entities as well as the local jurisdiction, as deemed appropriate. &lt;br /&gt;
&lt;br /&gt;
:Following the deadline for submissions, proposals will be evaluated based on Section 5 Proposal Evaluation and Selection Criteria.&lt;br /&gt;
&lt;br /&gt;
4. Unsolicited Joint Development Proposals &lt;br /&gt;
&lt;br /&gt;
:MDOT is open to receiving, evaluating and advancing solicitations for unsolicited proposals from third parties at any time for Joint Development on State-owned land, in accordance with these policies. &lt;br /&gt;
&lt;br /&gt;
:If any MDOT facilities intend to be relocated or impacted in any by the proposed development, the proposer must mitigate or accommodate such facilities, including all relevant requirements, as part of their development including covering all expenses for the design and construction of such facilities. All designs for the facilities must be approved by the appropriate mode. The developer will also be required to perform any site planning and due diligence for what would otherwise be completed as part of a TOD Site Strategy to define transit infrastructure requirements and at their own expense. These activities may include, but is not limited to, a site survey, title search, environmental assessments, and site analysis, in addition to the reimbursement of MDOT’s internal fees relating to drafting and producing the requirements, standards, and procedures for the project, and the State’s fees relating to internal cost recovery for design review, construction management, inspection, commissioning, and hangover/acceptance of the infrastructure assets, if applicable. &lt;br /&gt;
&lt;br /&gt;
:Third parties interested in pursuing a Joint Development project that includes State-owned should submit an electronic proposal as specified in 4.1 below to: TODprogram@mdot.maryland.gov. All requested information must be submitted. Proposers failing to submit all information requested for the Preliminary Assessment may be given an opportunity to submit promptly missing information or may be rejected, in MDOT’s sole discretion. MDOT is open to meeting with third parties in advance to discuss potential unsolicited proposals.&lt;br /&gt;
&lt;br /&gt;
4.1. Unsolicited Joint Development Proposal Assessment&lt;br /&gt;
&lt;br /&gt;
::4.1.1. Concept Proposal&lt;br /&gt;
&lt;br /&gt;
:The Unsolicited Joint Development Proposal Assessment begins with the submittal of a high-level concept proposal to determine technical feasibility, which must include the following information:&lt;br /&gt;
&lt;br /&gt;
::* Project Overview:&lt;br /&gt;
::::- Project Information: Station location, facility type, proposed uses, property size, and a high-level development program summary.&lt;br /&gt;
::::- Existing Use: Overview of current infrastructure, land use compatibility, zoning compliance, access points, and any discrepancies that may require amendments or variances between plans and zoning requirements. &lt;br /&gt;
::::- Justification: Explanation of how the proposal aligns with MDOT's Joint Development Goals and Objectives (Section 4) and the Joint Development Principles (Section 5). &lt;br /&gt;
::::- Proposed Changes to State-owned Property: Summary of changes to state-owned property, including station, rail, parking, bus facilities, pick-up drop-off facilities, access, road network, pedestrian facilities, bicycle facilities, utilities, and stormwater management facilities.&lt;br /&gt;
::::- Impacts Summary: Identification of key impacts to transit operations, maintenance, vehicular traffic, pedestrian flow, safety, customer experience, and lifecycle costs. &lt;br /&gt;
::::- Ownership and Realty Interest: Outline potential ownership structure and any realty interest in State-owned land. &lt;br /&gt;
::::- Maintenance Responsibilities: Identify maintenance responsibilities for public and private improvements. &lt;br /&gt;
::::- Community Benefits: List any community benefits to the jurisdiction or state.&lt;br /&gt;
::* Concept Plan: Provide available maps, site plans, and/or drawings of the property and proposed improvements and impacts to existing facilities.&lt;br /&gt;
&lt;br /&gt;
:Once the concept proposal is received and is deemed complete, the submittal will be circulated to internal MDOT stakeholders and will be evaluated based on the proposal’s ability to demonstrate technical feasibility and to determine if there are any technical fatal flaws that must be addressed. If the concept proposal is deemed to be technically feasible, MDOT will provide a response to the proposer and, where appropriate, arrange a meeting with the proposer and relevant internal stakeholders to review any issues or deficiencies identified in the Concept Proposal submission. Depending on the nature and severity of the issues, the proposer may be invited to address them as part of a comprehensive proposal, or the submission may be declined if the issues cannot be reasonably mitigated.&lt;br /&gt;
&lt;br /&gt;
:: 4.1.2. Comprehensive Proposal&lt;br /&gt;
&lt;br /&gt;
::The purpose of this phase is to address the fatal flaws identified in the concept proposal, finalize the technical and operational requirements, and demonstrate the financial feasibility of the project. The comprehensive proposal must include:&lt;br /&gt;
&lt;br /&gt;
::* Technical Feasibility Plan:&lt;br /&gt;
::::- Revised Project Overview: Updated to include any changes from the Concept Proposal.&lt;br /&gt;
::::- Site Investigation Report: Detailed report on infrastructure, environmental considerations, utility availability and capacity, and traffic/transportation (including access and egress points) to identify constraints affecting the development. &lt;br /&gt;
::::- Station Multi-Modal Demand Analysis: Confirm future ridership to determine transit infrastructure requirements as part of the Joint Development project, if applicable.&lt;br /&gt;
::::- Ridership Analysis: Analysis of how the development will increase transit ridership and calculation of increased fare revenue.&lt;br /&gt;
::::- Legal and Ownership Considerations: Verification of ownership status of the proposed site and any legal encumbrances that might impact development. Identification of any required easements for utilities, access, or public infrastructure.&lt;br /&gt;
::::- Response to MDOT’s Operational Concerns: Address operational impacts identified during the Preliminary Assessment phase, including strategies for maintaining operational continuity during and after construction.&lt;br /&gt;
::* Updated Concept Plan: Revised maps, site plans, and drawings addressing MDOT’s feedback.&lt;br /&gt;
::* Financial Feasibility and Implementation Plan:&lt;br /&gt;
::::- Preliminary Construction Cost Estimates: Estimations for public and private infrastructure improvements. &lt;br /&gt;
::::- Market Analysis &amp;amp; Financial Pro-Forma: Includes land value, local and state fiscal impact analysis, and financial projections. &lt;br /&gt;
::::- Financing Plan: Identify potential funding sources, financial tools, and strategies for closing funding gaps. &lt;br /&gt;
::::- Project Schedule &amp;amp; Phasing: High-level project timeline, including conceptual phasing plan.&lt;br /&gt;
&lt;br /&gt;
:Once the comprehensive proposal is received and is deemed complete, the submittal will be circulated to internal MDOT stakeholders to determine the proposal’s technical and financial feasibility, to ensure that MDOT’s technical and operational concerns have been addressed, and to identify the transit and public infrastructure requirements. Subject to determining that the proposal meets these criteria, MDOT will deem it a viable Joint Development opportunity and will proceed to the next step, issuing a request for alternative proposals to bring the project to market. Depending on the nature and severity of any identified issues, the proposer may be invited to address them as part of the comprehensive proposal review process, or the submission may be declined if the issues cannot be reasonably mitigated. If a proposal is not deemed technically or financially feasible but contributes significant strategic or operationally value, MDOT may, at its discretion, may propose to refine the approach and seek to advance to the next step.&lt;br /&gt;
&lt;br /&gt;
4.2. Request for Alternative Proposals&lt;br /&gt;
&lt;br /&gt;
:If the unsolicited Joint Development proposal is deemed to be technically and financially feasible and has merit, MDOT will create any necessary solicitation materials based on the identified transit and public requirements, and publish a notice and the solicitation package on MDOT’s website notifying the public that the proposal has been received and inviting others to submit competing proposals. The solicitation will outline the minimum qualifications to meet MDOT’s goals, objectives, and requirement and will outline the evaluation criteria, which will be required of interested developers. The deadline for MDOT’s receipt of any competing proposals will be provided in the notice, but in any case, it will be no less than forty-five (45) days from publication of the notice. The deadline will depend on the complexity of the project. The solicitation process may include a pre-bid meeting, a questions and answers period, interviews, and a site visit with interested development entities, as well as with the local jurisdiction, as deemed appropriate.&lt;br /&gt;
&lt;br /&gt;
:The unsolicited proposer will also have the opportunity to submit a proposal as part of the Request for Alternative Proposals.&lt;br /&gt;
&lt;br /&gt;
:Following the deadline for submissions, proposals will be evaluated based on the criteria outlined in Section 5, Proposal Evaluation and Selection Criteria.&lt;br /&gt;
&lt;br /&gt;
5. Proposal Evaluation and Selection Criteria&lt;br /&gt;
:Joint Development proposals will be evaluated based on criteria outlined within the Joint Development solicitation. Following a completeness review of all proposals received, submittals will be circulated and reviewed by a selected evaluation panel consisting of MDOT staff and may include other external members at MDOT’s sole discretion. MDOT may discuss the proposals with other stakeholders, including the Federal Transit Administration, partner agencies, and the local jurisdiction. The evaluation panel will review all proposals and recommend a preferred developer for the final decision to be made by the MDOT Chief of Transit Oriented Development.&lt;br /&gt;
&lt;br /&gt;
6. Exclusive Negotiating Period and Development Plan Design&lt;br /&gt;
&lt;br /&gt;
:Following the selection and notice of award to the Joint Development Partner, MDOT and the Joint Development Partner will enter into an Exclusive Negotiating Privilege (ENP) Agreement, which will outline the process and time limits for the developer to advance the design of the Development Plan and for the parties to execute the MDA. The ENP also outlines the developer’s responsibilities relating to conducting due diligence, site planning to advance the design of the Development Plan. The Development Plan is in addition to the Joint Development Partner seeking any local land use and site plan approvals required by the appropriate local jurisdiction. &lt;br /&gt;
&lt;br /&gt;
:The Development Plan is a comprehensive and master design document that outlines the key elements and requirements of the Joint Development project which will form the basis for compliance throughout detailed design of each phase, as applicable. The Development Plan will be reviewed in accordance with the requirements, standards and specifications outlined within the Joint Development solicitation and the ENP agreement and based on the Development Plan’s ability to achieve the intent of the Joint Development Goals and Objectives outlined in Section 4 and to meet the Joint Development Policies established in Section 5. Development Plans will generally include, but will not be limited to the following deliverables, which will be further outlined within the Joint Development Solicitation and MDA: site plans which includes existing conditions and siting of the transit and public infrastructure improvements, massing plans with building envelopes, subdivision plans, multi-modal transportation and site circulation plans (including road dimensions, sections, and auto-turns), parking management plans, streetscaping and building designs, signage and wayfinding plans, community engagement plan, utility plans, phasing and sequencing plans, stormwater management plans, maintenance of traffic plans, and anticipated financing and sequencing of the infrastructure improvements for the entire joint development site and each of the proposed phases, if applicable.&lt;br /&gt;
&lt;br /&gt;
:The Development Plan will be appended as a schedule to the Master Developer Agreement.&lt;br /&gt;
&lt;br /&gt;
7. MDA and Project Approvals&lt;br /&gt;
&lt;br /&gt;
:MDOT will negotiate a Master Ground Lease (or other instrument of conveyance) and a MDA with the selected developer, which will include as applicable the Form for Phase Ground Lease(s), Purchase Agreement(s), Reciprocal Easement and Operating Agreement(s), Construction Agreement, Parking Lease(s), and other agreements necessary for the delivery of the project, as required. The MDA is a binding agreement between MDOT and the Joint Development partner which outlines the requirements, commercial terms, and value exchange for the project. It will also include provisions relating to assemblage of any necessary financing; execution of design and construction contracts; securing any necessary permits and entitlements; and completing an approved final design. Once the MDA and Development Plan have been finalized, MDOT will seek approval of the MDA from the Board of Public Works and FTA, if applicable.  &lt;br /&gt;
&lt;br /&gt;
:Following BPW approval, the Developer will advance detailed design of the Development Plan for MDOT’s review and approval prior to MDOT providing a Notice to Proceed with construction.&lt;br /&gt;
&lt;br /&gt;
8. Amendments&lt;br /&gt;
&lt;br /&gt;
:The long-term nature of Joint Development projects, changing market conditions, shifts in project feasibility, and the evolving needs of multi-phased developments may necessitate adjustments or amendments to the executed agreement(s). In these instances, MDOT may, at its sole discretion, consider proposed amendments from developers for Joint Development projects that have an executed ground lease in place. Any such proposal to amend existing agreements must be formally submitted to MDOT for review and must include sufficient information to allow for a thorough evaluation. The developer must provide a detailed written amendment proposal that includes: &lt;br /&gt;
::*A clear justification for the proposed modification;&lt;br /&gt;
::*A financial analysis demonstrating the impact of the proposed change, including projected costs, benefits, and any revenue implications for MDOT;&lt;br /&gt;
::*A description of the proposed improvements or modifications, including scope, estimated costs, and expected benefits;&lt;br /&gt;
::*Supporting documentation such as market studies, engineering assessments, or other relevant analyses; and &lt;br /&gt;
::*A timeline for implementation and completion of the proposed changes.&lt;br /&gt;
&lt;br /&gt;
:MDOT will evaluate the developer’s amendment proposal to amend an executed agreement based on its consistency with the original and current Joint Development goals and objectives, financial and operational impacts on MDOT and transit services, potential public benefit and alignment with existing agreements, principles, regulatory compliance, and legal considerations, among other factors.&lt;br /&gt;
&lt;br /&gt;
:MDOT reserves the right at its sole discretion to approve, reject, or request modifications to the proposal to amend an existing agreement. If the proposal to amend an existing agreement is deemed viable, MDOT may require further negotiations or amendments before granting final approval, which may require BPW approval. &lt;br /&gt;
&lt;br /&gt;
9. MDOT’s Reserved Rights&lt;br /&gt;
&lt;br /&gt;
:MDOT reserves the right, without limitation, in its sole and unfettered discretion to the following:&lt;br /&gt;
&lt;br /&gt;
::*Reject any and all proposals at any time.&lt;br /&gt;
::*To charge an application fee for the processing and review of Unsolicited Joint Development Proposals and will be determined based on the review of the Concept Plan proposal which will depend on the proposal’s scope and complexity.&lt;br /&gt;
::*Suspend, discontinue and/or terminate agreement negotiations with any respondent or selected Developer at any time prior to the actual authorized execution of such agreement by all parties.&lt;br /&gt;
::*Negotiate with a proposer without being bound by any provision in its proposal.&lt;br /&gt;
::*Request or obtain additional information about any proposals or solicitation submissions.&lt;br /&gt;
::*Issue addenda to and/or cancel any solicitation.&lt;br /&gt;
::*Revise, supplement, or withdraw all or any part of these policies.&lt;br /&gt;
::*Request revisions to conceptual or detailed proposals.&lt;br /&gt;
&lt;br /&gt;
:Under no circumstances shall MDOT be liable for, or reimburse, the costs incurred by proposers, whether or not selected for negotiations, in developing proposals or in negotiating agreements. Any and all information MDOT makes available to proposers shall be as a convenience to the proposer and without representation or warranty of any kind. Proposers may not rely upon any oral responses to inquiries.&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
MDOT 657.1 Joint Development Principles&lt;br /&gt;
&lt;br /&gt;
MDOT 657.2 Joint Development Roles and Responsibilities&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6495</id>
		<title>MDOT 657.2 Joint Development Roles and Responsibilities</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.2_Joint_Development_Roles_and_Responsibilities&amp;diff=6495"/>
		<updated>2025-07-28T16:30:40Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: Created page with &amp;quot;Category:Real Estate  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the si...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Real Estate]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT 657.22.pdf| Signed Supporting Document MDOT 657.2]]&lt;br /&gt;
&lt;br /&gt;
This supporting document outlines the key responsibilities of internal and external stakeholders and highlights the partnerships necessary for effective Joint Development project execution. Joint Development projects involve complex coordination between the federal government, State agencies, local jurisdictions, private developers, and the community. This section describes the roles and responsibilities of those parties and the necessary partnerships for successful Joint Development projects, as well as State policies that relate to Joint Development. &lt;br /&gt;
&lt;br /&gt;
The following matrix provides an overview of key stakeholders, both internal and external to MDOT, who participate in the Joint Development process. Additional information on how MDOT collaborates with these partners is provided below. For a detailed breakdown of the Joint Development process and key stakeholders roles and responsibilities, see Appendix A – Joint Development Roles and Responsibilities Matrix.&lt;br /&gt;
&lt;br /&gt;
The core project team for each Joint Development project consists of the Joint Development Partner, MDOT’s Office of Real Estate and Economic Development (“ORED”), the Maryland Transit Administration (“MTA”), and the Office of the Attorney General (“OAG”). Together, these entities collaborate to oversee the planning, evaluation, negotiation, design, and implementation of Joint Development projects, ensuring alignment with MDOT’s strategic goals and objectives, policies, and regulatory requirements.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Stakeholder&lt;br /&gt;
! Role Summary&lt;br /&gt;
|- &lt;br /&gt;
&lt;br /&gt;
! Internal to MDOT&lt;br /&gt;
&lt;br /&gt;
|- &lt;br /&gt;
| Office of Real Estate and Economic Development (“ORED”)&lt;br /&gt;
| Located within The MDOT Secretary’s Office, ORED will lead and coordinate MDOT’s Joint Development efforts including executing planning efforts, solicitations, and agreements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Transit Administration (“MTA”)&lt;br /&gt;
| As the transit operator, MTA will define transit infrastructure requirements, standards, and specifications. MTA will be a key stakeholder in the Development Plan, detailed design review and approval; and construction to ensure the proposed development is integrated with the transit infrastructure, that the future service supports new development, that there are minimal disruptions to transit operations throughout construction, and that the assets are designed and delivered in accordance with the requirements, standards, and specifications. MTA will also be responsible for inspection during construction, commissioning, and handover of the transit infrastructure assets.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)&lt;br /&gt;
| Maryland State Highway Administration (“SHA”)	As the owner and maintainer of state roads, SHA will be a key partner in ensuring that local road capacity supports intended development, as well as providing early input into defining requirements and assisting with analysis in defining needs improvements and permitting. &lt;br /&gt;
To manage risk associated with Joint Development projects, SHA shall evaluate planning-level concepts of potential Joint Development projects to estimate potential SHA positions on future permitting. MDOT will seek to engage local roadway owners in this process as well. This process is outlined in the document TIS for Early Planning Coordination on Joint Developments (JD).&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Maryland Aviation Administration (“MAA”) &lt;br /&gt;
| The MAA owns and operates the Baltimore/Washington International Thurgood Marshall (BWI) and Martin State airports. MAA will be a key partner to ensure development adjacent to either of these MARC stations conforms with all airport requirements and operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Office of Attorney General (“OAG”)&lt;br /&gt;
| The OAG is the legal counsel to MDOT and is involved in reviewing solicitations and the drafting and negotiations of development agreements.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other MDOT Modal Departments&lt;br /&gt;
| As the owner and operator of State-owned land within ½ mile of transit station, other MDOT Modal Departments may be a key stakeholder in Joint Development projects. Any impacted modes will be a key partner to ensure development does not impact modal infrastructure or operations. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
! External to MDOT&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other State Agencies&lt;br /&gt;
| Other State Agencies	MDOT will partner with other state agencies, as appropriate, to advance Joint Development projects.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Federal Transit Administration (“FTA”)&lt;br /&gt;
| FTA-assisted Joint Development is any Joint Development project that uses FTA funding or property acquired with FTA funding. MDOT coordinates its Joint Development as applicable with FTA to ensure that the project satisfies FTA’s Joint Development requirements. &lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Jurisdictions &lt;br /&gt;
| Local jurisdictions are the local land use authority over State land and often control adjacent road networks and public space. Local jurisdictions are a key partner in developing site requirements and early site strategies to ensure potential future development meets local zoning and other regulations, as well as conforming with land use and comprehensive planning. &lt;br /&gt;
Local jurisdictions should closely coordinate with MDOT to ensure Master Developments that involve Joint Development uphold the State goals for TOD and Joint Development while also administering its own development approval process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Local Communities &lt;br /&gt;
| Residents, community-based organizations, and businesses in communities adjacent to Joint Development projects are key stakeholders throughout the process. MDOT and its Joint Development partners will engage local communities throughout the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
|-&lt;br /&gt;
| Other Rail Authorities Having Jurisdiction	&lt;br /&gt;
| MDOT will seek to coordinate with other rail authorities having jurisdiction to define requirements and processes for external review should the proposed joint development project potentially have impacts to the rail corridor or its zone of influence.  &lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
;Partnerships with Local Jurisdictions&lt;br /&gt;
&lt;br /&gt;
In the pursuit of Joint Development, MDOT will work with local jurisdictions to coordinate pre-solicitation planning and site infrastructure needs and funding opportunities, defining community and jurisdictional goals and guiding principles, leveraging local economic development tools and strategies as well as resolving feasibility issues prior to solicitation as much as practically possible. For example, where amending land use and zoning regulations to better align with TOD objectives is necessary, MDOT may: &lt;br /&gt;
* Advocate for or initiate zoning amendments,&lt;br /&gt;
* Participate in and/or fund any necessary studies; and &lt;br /&gt;
* Provide technical assistance.&lt;br /&gt;
Through the course of planning and executing Joint Development, MDOT will work to include local development goals as well as community needs such as community and public service facilities as feasible. Defining these goals will occur in coordination with local jurisdictions and community partners through the pre-planning process.&lt;br /&gt;
&lt;br /&gt;
;Coordination with State Agencies&lt;br /&gt;
MDOT will coordinate with key State agency partners outside of MDOT to bring state resource support for realizing TOD through Joint Development. &lt;br /&gt;
&lt;br /&gt;
;Joint Development Partners&lt;br /&gt;
MDOT will be seeking, through Joint Development proposals, qualified development partners who have aligned interests in developing transit-oriented, mixed-use, mixed-income development at appropriate densities. MDOT views working with qualified developer partners as a key tool to advance TOD projects with shared costs and shared benefits to both parties. While MDOT will seek various methods to fund and finance the public infrastructure necessary to enable Joint Development, in collaboration with its local jurisdictional partners, MDOT expects its Joint Development partners to deliver high-quality TOD in line with the Goals, Objectives, and Principles outlined within MDOT ### Joint Development Policy, MDOT 657 Joint  Development Principles, the respective Joint Development solicitation as well as in accordance with applicable local laws and land use policies. &lt;br /&gt;
&lt;br /&gt;
==Appendix==&lt;br /&gt;
[[File:Signed_Supporting_Document_MDOT_657.22_Page_4.jpg|link=|1500px]]&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
MDOT 657.1 Joint Development Principles&lt;br /&gt;
&lt;br /&gt;
MDOT 657.3 Joint Development Implementation&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6494</id>
		<title>MDOT 657.1 Joint Development Principles</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657.1_Joint_Development_Principles&amp;diff=6494"/>
		<updated>2025-07-28T16:30:21Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: Created page with &amp;quot;Category:Records Management  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 23, 2025  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Records Management]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective Date: May 23, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed Supporting Document MDOT.pdf| Signed Supporting Document MDOT 657.1]]&lt;br /&gt;
&lt;br /&gt;
MDOT will evaluate Joint Development proposals and the Development Plan based on the following joint development principles. While the below points are all important priorities, specific joint development opportunities may place greater emphasis on selected priorities based on context and needs. In each respective Joint Development project, MDOT will specify which elements will receive greater emphasis over others as outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:1. Transit Integration - Proposed development must consider integration with the transit serving the proposed Joint Development site. This not only includes any rail station or bus stop but also connecting other modes to the site. Ensuring connectivity and universal accessibility to all the on-site or adjacent transit modes should be fundamental to any Development Plan. If present, different transit modes should be located as close together as possible to facilitate efficient intermodal connections.&lt;br /&gt;
&lt;br /&gt;
:2. Replacement Facilities - When transit facilities are modified or replaced as part of a Joint Development project, MDOT will seek to right-size, modernize, and improve station access as part of the project. In evaluating the scope and size of replacement of transit facilities affected by Joint Development, the proposed Joint Development plan should take into account:&lt;br /&gt;
&lt;br /&gt;
:::i. The future need of the transit facilities based on the existing and projected number of boardings and alightings at the Transit station, estimated number of new transit riders resulting from Joint Development; and estimated ridership from new development reasonably expected within the half-mile walkshed of a Transit station;&lt;br /&gt;
:::ii. Avoidance of unreasonable impacts to transit operations, service, vehicular and passenger flow, and customer experience;&lt;br /&gt;
:::iii. Cost effectiveness and life-cycle costs for facilities and operations; and,&lt;br /&gt;
:::iv. Long-term asset management plan(s) for MDOT’s facilities.&lt;br /&gt;
&lt;br /&gt;
::MDOT may consider reducing the replacement of existing facilities based on projected changes in ridership, access needs, and long-term multimodal strategy. Any such proposal to reduce the quantity of a replacement facility (e.g., a reduction in parking spaces) must be supported by a comprehensive justification that includes, but is not limited to:&lt;br /&gt;
:::i. The financial case, which considers the combined projected revenue from Joint Development (e.g., ground lease payments, participatory rent, etc.) and any revenue increases generated by induced ridership from the joint development. &lt;br /&gt;
:::ii. The strategic case, including alignment with MDOT’s goals, objectives, and principles. &lt;br /&gt;
:::iii. The economic case, such as broader community benefits, state and local tax generation impacts, and the private investment enabled by the joint development project.&lt;br /&gt;
:::iv.  The operational case, ensuring that multimodal access is maintained and that users can continue to access transit conveniently via other modes (e.g., biking, walking, bus, drop-off).&lt;br /&gt;
:::In all cases, proposals to reduce replacement facilities (e.g., fewer parking spaces than currently exist) must demonstrate that the total projected financial and non-financial benefits outweigh the value or utility of maintaining existing facility levels.&lt;br /&gt;
&lt;br /&gt;
:3. Density and Mix of Uses - Proposed Development Plans must reflect a level of density that will drive transit ridership and activity for the site. MDOT encourages that density levels be at the higher range of allowable density in the applicable land use or zoning requirements. Projects should allow for a mix of uses, with specific priority given to residential use, while also providing appropriate commercial use and other amenities that not only support activity within the station area but also draw transit riders. MDOT discourages automobile-dependent uses (e.g., vehicle repair businesses, drive-thrus, etc.).&lt;br /&gt;
&lt;br /&gt;
:4. Housing - Ensuring that Joint Development projects provide residential components that advance State housing goals is a key priority for MDOT. Given the diversity of markets and jurisdictional goals in the State, MDOT does not establish specific affordability targets in this document, however providing affordable units is a priority. MDOT will seek and evaluate affordability targets for any development proposal and subsequently work with the Joint Development partner, the Department of Housing and Community Development (DHCD), and the local jurisdiction to ensure that any Development Plan and subsequent build-out include a meaningful component of affordable units while maintaining the financial feasibility of the project.&lt;br /&gt;
&lt;br /&gt;
:5. Parking - MDOT is looking for a rationalized and efficient approach to parking. Providing rationalized parking is a critical component to successful TOD. The joint development project should not provide parking over what is minimally needed for the site. Development Plans must consider several factors when planning for parking on Joint Development sites. These factors include:&lt;br /&gt;
:::i. The amount of parking required to support transit ridership, and the initial location(s) for where that parking may be located will be determined pre-solicitation and may be provided as part of the Joint Development Solicitation, if applicable.&lt;br /&gt;
:::ii. The amount and location of parking provided for the development must consider the type of transit service serving the site. If the transit serving the site is a high-capacity transit service such as Metro Subway or Light Rail, MDOT expects a lower provision of parking to support the development. Joint development sites should target a ratio of less than 1 space per unit. However, if the site is served by commuter rail, additional parking for development may be required and a 1 space per unit ratio could be justifiable. MDOT will seek to coordinate with local jurisdictions prior to solicitation to reconcile zoning regulations that require minimum parking ratios above target levels conducive of TOD. &lt;br /&gt;
:::iii. Location of parking facilities should give priority to bus, pick-up &amp;amp; drop-off, micromobility, and pedestrian facilities. &lt;br /&gt;
:::iv. Opportunities for shared and/or structured parking are preferred, so long as they do not negatively impact passenger or vehicular traffic flow, safety, transit operations, and lifecycle costs. Such approaches should be considered and proposed by the Joint Development partner for MDOT’s review and approval, if not specified as part of the Joint Development solicitation.&lt;br /&gt;
:::v. Parking for the private development should not negatively impact flow or accessibility to the transit and meet [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines.]&lt;br /&gt;
&lt;br /&gt;
:6. Value Capture - MDOT will seek to achieve fair market value of real property in all joint development transactions. The fair market value of real property will be determined through consultation with real estate advisory firms and/or qualified third-party appraisers.. MDOT will contemplate discounts to land value and/or ground rent to achieve the goals, objectives, and principles of the Joint Development project or to fund improvements to transit facilities as needed based on a case-by-case basis. Any proposed reduction in fair market value must demonstrate that the value of the asset contributed to the joint development is equal to or greater than the fair share of the costs of the joint development project, or that MDOT will receive benefits (including non-monetary) equal to or greater than FMV. MDOT will also seek to participate in any monetization opportunities as a result of the Joint Development project.&lt;br /&gt;
&lt;br /&gt;
:7. Operations and Maintenance Costs - MDOT will seek to allocate operations and maintenance responsibilities associated with parking, open space, stormwater management, landscaping, cleaning, general maintenance, snow and ice removal, and graffiti removal to the Joint Development partner, or an approved designee, in a manner that is consistent with applicable MDOT Modal standards and does not increase MDOT’s administrative burden. &lt;br /&gt;
&lt;br /&gt;
:8. Electric Vehicle Charging Facilities - Wherever possible, Joint Development projects should provide electric vehicle charging as part of a parking program for transit customers, which requirements will be outlined within the Joint Development solicitation. Providing charging stations promotes the use of electric vehicles and is a major step towards achieving the State’s climate goals and clean vehicle mandates. Where practical, a parking program should incentivize electric vehicle use by allocating priority parking spaces (such as those immediately adjacent to transit station entrances, or multiple spaces on the ground level of a parking garage) for electric vehicle charging with compliant signage indicating the designated electric vehicle charging spaces. Joint Development proposals should consider the necessary infrastructure for electric vehicle charging stations, such as electric grid capacity for both near-term installations as well as future proofing for future installations. Note that the Americans with Disabilities Act requires provision of a “reasonable number” of accessible electric vehicle charging stations in an electric vehicle parking facility but does not specify an exact number or ratio. Where a requirement for the number of accessible electric vehicle charging stations exists, developers must provide at least that minimum number. Developers should reference federal and state guidelines for further guidance on the provision and design of accessible electric vehicle parking or to the local authority having jurisdictions standards and specifications. &lt;br /&gt;
&lt;br /&gt;
:9. Micromobility Facilities - As TOD aim to reduce car-dependence and promote multi-modal options, Joint Development projects are encouraged to incorporate facilities that promote micromobility access for bicycle and scooter travel. These amenities include protected shared use paths and connections to the local transportation system as well as secure and dedicated parking with electric charging stations for e-bikes and scooters which will be defined within the Joint Development solicitation. Joint Development projects should include micromobility facilities as identified in the local jurisdiction’s bicycle and pedestrian master plans, bicycle and pedestrian priority action plan, comprehensive plans, standards, and specifications. Developers should refer to the [https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines] for further guidance on bicycle and scooter parking. To determine an appropriate bicycle facility, please reference Appendix D: Bicycle Facility Selection Guide of the [https://www.mdot.maryland.gov/OPCP/MDOT_State_Bike_Ped_Master_Plan_FULL_FINAL_VERSION.pdf 2050 Maryland Bicycle &amp;amp; Pedestrian Master Plan.] For the development of bicycle and scooter parking, please reference the Association of Pedestrian &amp;amp; Bicycle Professionals (“APBP”) Essentials of Bike Parking: Selecting and Installing Bike Parking That Works.&lt;br /&gt;
&lt;br /&gt;
:10. Site and Area Connectivity Improvements - The Development Plan for Joint Development projects should promote convenient, accessible intermodal access to the transit service. What this means in practice will depend on site context, though it could include:&lt;br /&gt;
:::i. Parking garages, pick-up and drop-off areas, and micromobility facilities should be located proximate to the station and transit facilities but give deference and space for overall pedestrian flow, public spaces and wayfinding to the station for all users.  Pedestrian pathways should be safe and direct to walk from the parking facility to the station platform or other transit boarding area.&lt;br /&gt;
:::ii. Passengers with limited mobility should have an accessible, direct route to transit service entrances with limited detours. &lt;br /&gt;
:::iii. Infrastructure should, to the extent possible, not interrupt the flow of people to and from the transit station.&lt;br /&gt;
&lt;br /&gt;
::Joint Development projects are a significant investment with potential community-wide impacts. Pedestrian and cyclist infrastructure built as part of a Joint Development project can serve as a foundation for further sidewalk and bike lane networks, for instance. MDOT will seek to collaborate with local jurisdictions, using Joint Development projects as a catalyst to achieve pedestrian, cyclist, and other “alternative mobility” goals, and advance pedestrian, cyclist, and other alternative mobility infrastructure projects laid out in local comprehensive plans, pedestrian/bike plans, “Vision Zero” plans, and other similar local planning documents. Some Joint Development projects may require roadway capital projects or improvements in State-owned rights-of-way. In such cases, these improvements must adhere to MDOT 750 Complete Streets Policy and such requirements will be outlined within the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:11. Urban Design, Placemaking, Wayfinding, and Branding/Identity - In general, a Joint Development project should aim to adhere to the urban design principles laid out in MTA’s Designing for Transit: Transit-Oriented Development Guidelines. Please see the development guidelines for more information, including detailed and context-dependent design guidelines. Joint Development projects should also adhere to any applicable local urban design guidelines. The branding, marketing, and identity of Joint Development projects – both development and wayfinding elements – should have a direct relationship to the transit station on which they are centered. For example, developers could incorporate the name of the transit station into the name of development projects where practical. The aim is for the development to promote and encourage its relationship to the mode of transit which serves that project. Wayfinding elements should clearly and prominently guide both pedestrians and drivers – whether they are area residents, workers, or visitors – to key station area assets including but not limited to the transit station, retail and other activity centers, and any public services and open space. Wayfinding elements can include signs, lighting, and surface finishes that promote legibility of the public realm. They should have a consistent visual identity (e.g., typefaces, colors) across separate wayfinding elements such that visitors to an area are able to easily identify them. &lt;br /&gt;
&lt;br /&gt;
:12. Public Space - MDOT aims to enhance and expand public space in communities through its Joint Development program. Developers may be required to construct or improve public spaces as part of a Joint Development project. These requirements will be outlined in the Joint Development solicitation and may include elements such as parks, plazas, squares, sidewalks, and shared-use paths. MDOT’s priority is that public spaces created through Joint Development are welcoming, safe, and vibrant, serving the joint development, broader TOD, and the community. To support placemaking and reinforce the role of the station as a community anchor, developers should prioritize locating required open space near or adjacent to station entrances to create an active and enticing focal point. To minimize long-term costs to the State, public spaces should be conveyed to the local jurisdiction or operated and maintained by the Joint Development partner, or an approved designee such as the ground lessee, homeowners’ association, or residents’ association. Public space design must not obstruct access to the station or impede clear sightlines and should comply with the standards and specifications of the authority having jurisdiction. When new public spaces are proposed, developers are expected to coordinate closely with MDOT, MTA, and local jurisdictions to define programming and activation plans, and to establish clear roles and responsibilities for ongoing operations and maintenance.&lt;br /&gt;
&lt;br /&gt;
:13. Phasing and Implementation - Joint Development project phasing will typically involve the upfront or concurrent completion of infrastructure projects, followed by vertical development. However, MDOT will consider alternative Joint Development project phasing that balances the ongoing needs of transit riders with the market viability of vertical development. Any construction activities should minimize disruption to the transit operations. Any disruptions or changes in transit service needed for construction must be approved by MTA.&lt;br /&gt;
&lt;br /&gt;
:14. Construction of MDOT Facilities - As part of a Joint Development project, it  may be required to modify or construct replacement transit facilities such as parking and bus facilities, roads, pick up and drop off spaces, station ingress and egress, and potentially other types of transit infrastructure in order to achieve an optimized TOD. Design for all MDOT facilities will be approved by the mode that either owns or operates the facility. Allowing for the design and construction or improvement of MDOT facilities to be led by developers can benefit both parties. MDOT benefits from cost and time efficiencies derived from a single entity being responsible for all capital improvements. Developers benefit because: &lt;br /&gt;
:::i. Developers have increased control over the timeline of infrastructure delivery (and therefore when vertical development may begin).&lt;br /&gt;
:::ii. Transit facilities may be better integrated into the overall development, which increases overall development potential and making it more attractive to prospective tenants and increase achievable rents.&lt;br /&gt;
::MTA, or the applicable mode, must approve of the design, construction, and delivery of its facilities in accordance with the mode’s design and construction standards and specifications. Construction activities will commence after MDOT issues a notice to proceed to the developer, and the developer has received all other necessary State and local permits. These will likely include a permit for the use of State property with agreements on maintenance of traffic, maintenance of station activities, and more. The developer will execute design and construction contracts with its subcontractors necessary to deliver the transit facilities.&lt;br /&gt;
&lt;br /&gt;
:15. Continuing Control - MDOT strongly prefers to structure its transactions as ground leases rather than fee simple sales as it creates regular compensation for MDOT to offset transit operations and better enables MDOT to realize long-term value to offset its investment in transit infrastructure. Exceptions to this preference may be considered and may include instances where practical, site or legal reasons require fee simple sale, such as for home ownership opportunities, or if such a transaction can create significant added value for MDOT or be necessary to inject upfront capital to fund infrastructure improvements. To ensure Federal Transit Administration (FTA) continuing control requirements are met on FTA-assisted properties, MDOT will require certain assurances such as restrictive covenants, as applicable. &lt;br /&gt;
&lt;br /&gt;
:16. Community and Stakeholder Engagement - MDOT will consult and work collaboratively with the community, state stakeholders, local jurisdictions and developers to encourage transit-supportive, high-quality development at transit stations and surrounding properties. Once a successful Joint Development partner is selected, the developer must actively and productively engage local communities with interest in the Joint Development site during planning and delivery of the project.&lt;br /&gt;
&lt;br /&gt;
:17. Local Planning and Approvals - All Joint Development projects must follow local laws and land use policies of the jurisdiction in which they are located. MDOT will proactively engage with local jurisdictions to gather input on preliminary development concepts, gain local support, and to the extent possible and where appropriate, secure any necessary zoning changes prior to publication of the Joint Development solicitation. The Joint Development partner will be responsible for securing all necessary permits and entitlements from the relevant local jurisdiction and any other authorities having jurisdiction.&lt;br /&gt;
&lt;br /&gt;
:18. Sustainability - Joint Development projects must meet local building sustainability requirements. In the absence of a local requirement, MDOT will require that the project meet a nationally recognized sustainability standard, such as LEED Silver, or equivalent, to be specified in the Joint Development solicitation. &lt;br /&gt;
&lt;br /&gt;
:19. MBE/DBE/SBE Contracting Goals - The State of Maryland’s Minority Business Enterprise (“MBE”), Disadvantaged Business Enterprise (“DBE”), and Small Business Enterprise (“SBE”) Programs are designed to provide contracting opportunities to MBE, DBE, and SBE businesses in both State and federally funded projects in accordance with State law. MBE/DBE/SBE Contracting Goals  may be defined in the Joint Development solicitation. Maryland MBEs, DBEs, and SBEs must complete the certification process with MDOT to be recognized as such for contracting purposes. Working with the awarded developer, MDOT will assist Joint Development partners in identifying opportunities for MBE, DBE, or SBE participation in the development and construction of the project. &lt;br /&gt;
&lt;br /&gt;
:20. Workforce Development and Labor Provisions - Joint Developments may qualify as “large-scale public work contract” under [https://governor.maryland.gov/Lists/ExecutiveOrders/Attachments/51/01.01.2024.18%20-%20FINAL%20EO%20-%20PLAs%20Apprenticeship%20Agreements%20and%20Community%20Hiring%20-%205.31.24%20%5bCLEAN%20COPY%5d.pdf Executive Order 01.01.2024.18] regarding project labor agreements, apprenticeships, and community hiring. Certain projects may be subject to [https://www.dol.gov/agencies/whd/government-contracts/construction Davis-Bacon Act] or [https://www.labor.maryland.gov/labor/prev/prevoverview.shtml Maryland Prevailing Wage] requirements. Contractors and subcontractors awarded contracts by the State of Maryland or its political subdivisions for the construction of public works that fall within the State’s statutory requirements must compensate covered workers as governed by Maryland’s Prevailing Wage Law. These requirements will be further described in the Joint Development solicitation.&lt;br /&gt;
&lt;br /&gt;
:21. Americans with Disabilities Act - The Americans with Disabilities Act (“ADA”) prohibits discrimination against people with disabilities in employment, transportation, public accommodation, communications, and government activities. The development must comply with ADA requirements. Regarding infrastructure, where it is located will determine which requirements will apply. For WMATA and MTA-controlled stations, all spaces must meet at least Americans with Disabilities Access Guidelines (“ADAAG”) and FTA ADA Guidelines. Any improvements along State Highway Administration (SHA)managed facilities must meet SHA’s Accessibility Policy and Guidelines, which can be found in [https://www.roads.maryland.gov/mdotsha/pages/Index.aspx?PageId=26 SHA’s Accessibility Policy and Guidelines for Pedestrian Facilities Along State Highways.]&lt;br /&gt;
&lt;br /&gt;
:22. Transfer or Assignment of Development Agreements - MDOT understands that the developer or members of the development team may change during the term of a Joint Development project. Any changes to developer ownership following execution of the joint development agreements will be subject to MDOT’s approval at its sole and absolute discretion (including, where required, the approval of the Board of Public Works).&lt;br /&gt;
&lt;br /&gt;
:23. Business Ethics and Conflict of Interest - All Joint Development partners must comply with applicable State law requirements relating to conflict of interest, political contribution disclosure, and financial disclosures as part of the Joint Development process.&lt;br /&gt;
&lt;br /&gt;
==Additional Authorized Documents==&lt;br /&gt;
&lt;br /&gt;
MDOT 657.2 Joint Development Roles and Responsibilities&lt;br /&gt;
&lt;br /&gt;
MDOT 657.3 Joint Development Implementation&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6493</id>
		<title>MDOT 657 Joint Development</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_657_Joint_Development&amp;diff=6493"/>
		<updated>2025-07-28T16:29:52Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: Created page with &amp;quot; &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: April, 30, 2025  Effective Date: May 30, 2025  &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt; &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: April, 30, 2025&lt;br /&gt;
 Effective Date: May 30, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note:There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:Signed MDOT 657 policy.pdf|MDOT 657 Joint Development Signed Hard Copy]]&lt;br /&gt;
&lt;br /&gt;
==Purpose==&lt;br /&gt;
The purpose of this Policy is to:&lt;br /&gt;
# Define MDOT’s Joint Development Program’s goals, objectives, and principles;&lt;br /&gt;
# Establish roles and responsibilities;&lt;br /&gt;
# Establish and maintain processes and procedures; and&lt;br /&gt;
# Ensure consistent compliance across MDOT.&lt;br /&gt;
&lt;br /&gt;
==Reference(s)==&lt;br /&gt;
[[media:01.01.2024.18 -.pdf| Executive Order 01.01.2024.18]]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Transportation Article, §7–101, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-102&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, §7–102, Annotated Code of Maryland.]&lt;br /&gt;
&lt;br /&gt;
[[media:MDOT-750-Complete-Streets-Signed.pdf|MDOT 750 Complete Streets Policy ]]&lt;br /&gt;
&lt;br /&gt;
[https://s3.amazonaws.com/mta-website-staging/mta-website-staging/files/Transit%20Projects/TOD/TOD_Design_Guidelines_Jan2020.pdf MTA’s Designing for Transit: Transit-Oriented Development Guidelines]&lt;br /&gt;
&lt;br /&gt;
==Scope==&lt;br /&gt;
This Policy is applicable to all existing and future Joint Development projects on State-owned property that is adjacent to a planned or existing transit station; property, any part of which is located within one-half mile of a planned or existing transit station; and property that is adjacent to a planned or existing transit corridor.&lt;br /&gt;
&lt;br /&gt;
This Policy is applicable to all modal administrations, MDOT employees, contract employees, contractors, and consultants.  &lt;br /&gt;
&lt;br /&gt;
==Responsible Party==&lt;br /&gt;
The Assistant Secretary for Project Development and Delivery.&lt;br /&gt;
&lt;br /&gt;
==Policy Statement==&lt;br /&gt;
&lt;br /&gt;
# MDOT will aim to reach the goals and objectives set forth herein. These goals and objectives will serve as the overarching guiding framework for Joint Development projects throughout the Joint Development process, particularly in the evaluation of Joint Development proposals. It is important to recognize that the relative priority of these goals may be adjusted based on the unique context of each site, which will be outlined as part of the Joint Development solicitation.&lt;br /&gt;
#:* Increase Transit Ridership and reduce single occupancy Vehicle Miles Travelled: MDOT aims to grow transit ridership through new development in station areas facilitated by its Joint Development Program, providing station area residents, workers, and visitors access to transit.&lt;br /&gt;
#:* Increase Housing Supply (Including Affordable Housing) and Jobs: MDOT seeks to foster sustainable regional growth by creating new housing and business opportunities near transit. &lt;br /&gt;
#:* Maximize the return on the State’s transportation infrastructure investments: MDOT aims to prioritize higher-density and mixed-use transit-oriented development (TOD) around transit stations maximizes the State’s historic $2 billion infrastructure investment in MTA’s core service area. TOD increases transit ridership, reduces congestion, and drives economic growth by creating walkable, accessible communities. This approach ensures long-term returns while advancing Governor Moore’s State Plan.&lt;br /&gt;
#:* Improve Transit Facilities: Where improvement, modification, or relocation of transit facilities will allow for a better development program, MDOT may require developers to relocate, reconfigure, or improve transit facilities as part of a Joint Development project. Additionally, MDOT may also seek to improve or expand transit facilities as part of the project and seek Joint Development partners in delivering those facilities. The intent is to enable better development and improved transit facilities. In any case, modification of transit facilities or any aspect of Joint Development should seek to minimize operating costs and seek capital cost avoidance for MDOT, where feasible.&lt;br /&gt;
#:* Enhance Station Access and Connectivity: New development should be integrated seamlessly with the surrounding street and mobility networks as well as with the surrounding public spaces. Ensuring connectivity to and through development to the transit infrastructure is a key goal. Improvements and responsibility to implement those improvements will vary depending on location (on-site vs. off-site) and breadth of the improvements. &lt;br /&gt;
#:* Support Long-Term Economic Development and Revenue Goals: MDOT’s Joint Development program is dedicated to advancing economic growth and generating sustainable revenue for the State and local jurisdictions over the long term by generating new state and local taxes on formerly undeveloped and tax-exempt land. Long-term economic development goals and ridership generation are considered top priority in implementing Joint Development projects, however MDOT will seek to participate in other revenue generating activities as feasible within a Joint Development project.&lt;br /&gt;
#:* Support Local Development Goals and Community Needs: MDOT recognizes the importance of aligning Joint Development efforts with local development goals and addressing community needs. Joint Development projects will aim to enhance the quality of life for residents while supporting broader transit and economic objectives.&lt;br /&gt;
#:* Seek to Minimize Risks: Joint Development projects should minimize financial, operational, and safety risks to MDOT and their Joint Development partners, by establishing a predictable and transparent process with clear expectations and requirements. &lt;br /&gt;
#:* Be a Trusted Business Partner: MDOT will act as a competent and reliable business partner, retaining risks it can manage most appropriately and effectively and seek out partners with proven track records of quality development.&lt;br /&gt;
&lt;br /&gt;
==Definitions==&lt;br /&gt;
For the purposes of this Policy, the following words have the following meanings:&lt;br /&gt;
&lt;br /&gt;
# Joint Development means a public transportation project that integrally relates to, and often co-locates with commercial, residential, mixed-use, or other non-transit development. Joint Development may include partnerships for public or private development associated with any mode of transit system that is being improved through new construction, renovation, or extension. Joint Development may also include intermodal facilities, intercity bus and rail facilities, transit malls, or historic transportation facilities. &lt;br /&gt;
# Transit Corridor means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit-Oriented Development (TOD) means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
# Transit station means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Maryland Transportation Article §7–101.]&lt;br /&gt;
&lt;br /&gt;
==Authorized/Supporting Documents==&lt;br /&gt;
&lt;br /&gt;
[[media: Signed Supporting Document MDOT 657.1.pdf| MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
&lt;br /&gt;
[[media: Signed Supporting Document MDOT 657.2.pdf | MDOT 657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
&lt;br /&gt;
[[media: Signed Supporting Document MDOT 657.3.pdf| MDOT 657.3 Joint Development Implementation]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6492</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6492"/>
		<updated>2025-07-28T13:54:42Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
==Joint Development==&lt;br /&gt;
*[[MDOT 657 Joint Development]]&lt;br /&gt;
*[[MDOT 657.1 Joint Development Principles]]&lt;br /&gt;
*[[MDOT 657.2 Joint Development Roles and Responsibilities]]&lt;br /&gt;
*[[MDOT 657.3 Joint Development Implementation]]&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
*[[MDOT 750 Complete Streets]]&lt;br /&gt;
**[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
**[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6487</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6487"/>
		<updated>2025-02-28T17:40:30Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
*[[MDOT 750 Complete Streets]]&lt;br /&gt;
**[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
**[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6486</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6486"/>
		<updated>2025-02-28T17:40:19Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Complete Streets */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
[[MDOT 750 Complete Streets]]&lt;br /&gt;
[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6485</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6485"/>
		<updated>2025-02-28T17:39:55Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Complete Streets */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
[[MDOT 750 Complete Streets]]&lt;br /&gt;
&lt;br /&gt;
[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
&lt;br /&gt;
[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6484</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6484"/>
		<updated>2025-02-28T17:39:48Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: /* Complete Streets */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
[[MDOT 750 Complete Streets]]&lt;br /&gt;
[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6483</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6483"/>
		<updated>2025-02-28T17:39:14Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
[[MDOT 750 Complete Streets]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6482</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6482"/>
		<updated>2025-02-28T17:38:59Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;br /&gt;
&lt;br /&gt;
==Complete Streets==&lt;br /&gt;
[https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets MDOT 750 Complete Streets]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6481</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6481"/>
		<updated>2025-02-28T17:37:21Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf| Complete Streets Implementation Plan&lt;br /&gt;
***https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf| Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6480</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6480"/>
		<updated>2025-02-28T17:36:50Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***[https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf| Complete Streets Implementation Plan&lt;br /&gt;
***[https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf| Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6479</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6479"/>
		<updated>2025-02-28T17:36:23Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
**[https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf| Complete Streets Implementation Plan&lt;br /&gt;
**[https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf| Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6478</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6478"/>
		<updated>2025-02-28T17:36:16Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
**[https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf| Complete Streets Implementation Plan]&lt;br /&gt;
**[https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf| Complete Streets Executive Summary]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6477</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6477"/>
		<updated>2025-02-28T17:34:58Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
**[https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf Complete Streets Implementation Plan]&lt;br /&gt;
**[https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf Complete Streets Executive Summary]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6476</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6476"/>
		<updated>2025-02-28T17:34:41Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***[https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf Complete Streets Implementation Plan]&lt;br /&gt;
***[https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf Complete Streets Executive Summary]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6475</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6475"/>
		<updated>2025-02-28T17:34:05Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf Complete Streets Implementation Plan&lt;br /&gt;
***https://policymanual.mdot.maryland.gov/mediawiki/images/c/c7/2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6474</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6474"/>
		<updated>2025-02-28T17:33:40Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***https://policymanual.mdot.maryland.gov/mediawiki/images/8/8b/2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf Complete Streets Implementation Plan&lt;br /&gt;
***media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6473</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6473"/>
		<updated>2025-02-28T17:32:39Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan&lt;br /&gt;
***media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6472</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6472"/>
		<updated>2025-02-28T17:31:42Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Complete Streets&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan&lt;br /&gt;
***[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6471</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MediaWiki:Sidebar&amp;diff=6471"/>
		<updated>2025-02-28T17:31:21Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
* SEARCH&lt;br /&gt;
&lt;br /&gt;
* Navigation&lt;br /&gt;
** mainpage|mainpage-description&lt;br /&gt;
**MDOT Policy|MDOT Policy&lt;br /&gt;
** Engineering Policy|Engineering Policy&lt;br /&gt;
** https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=69|Public Information Act Requests (PIA)&lt;br /&gt;
** Readily Available Documents|Public Information Act-Readily Available Documents&lt;br /&gt;
&lt;br /&gt;
*Hot Topics&lt;br /&gt;
**https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets|Complete Streets Policy&lt;br /&gt;
***[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
***[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Help&lt;br /&gt;
** How to use the Policy Wiki | How to use the Policy Wiki&lt;br /&gt;
**Terminology|Terminology&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets&amp;diff=6470</id>
		<title>MDOT 750 Complete Streets</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_750_Complete_Streets&amp;diff=6470"/>
		<updated>2025-02-28T17:30:06Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
 [[Category:Complete Streets]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Effective June 1, 2024&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note: There may be formatting differences between the electronic document and the signed document. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
[[media:MDOT-750-Complete-Streets-Signed.pdf| MDOT 750 Complete Streets Signed Hard Copy]]&lt;br /&gt;
&lt;br /&gt;
==Purpose==&lt;br /&gt;
The purpose of this Policy is to:&lt;br /&gt;
&lt;br /&gt;
1.	Satisfy the statutory requirement to adopt a Statewide Complete Streets Policy for highway, transit, and airport facilities, as mandated under Transportation Article § 2-112, §5-408.1, §7-310, and §8-204.1;&lt;br /&gt;
&lt;br /&gt;
2.	Facilitate the planning, design, and construction of transportation options that are safer and more accessible to all users of all ages and abilities who bike, walk, take transit, drive or use electric personal assistive mobility devices (EPAMDs); &lt;br /&gt;
&lt;br /&gt;
3.	Accomplish four primary goals:&lt;br /&gt;
&lt;br /&gt;
:a)	Establish a framework for future Complete Streets guidance and assigns modal responsibilities that support equitable decision-making in Complete Streets implementation;&lt;br /&gt;
&lt;br /&gt;
:b)	Require the implementation of planning and design principles from Maryland Department of Transportation (MDOT) Maryland Transit Administration’s (MTA) Bus Stop Design Guide, and State Highway Administration’s (SHA) Context Driven: Access and Mobility for All Users Guide, or Context Guide, to address safety, access, and mobility for all users on all projects in MDOT right-of-way in the following cases;&lt;br /&gt;
::i.	When implementing a capital improvement project, such as construction or reconstruction of a roadway, intersection, or bridge.&lt;br /&gt;
&lt;br /&gt;
::ii.	When permitting new or reconstructed streets to access MDOT right-of-way; or&lt;br /&gt;
&lt;br /&gt;
::iii.	When there is an opportunity to improve safety for all users by applying proactive engineering safety countermeasures to resurfacing projects.&lt;br /&gt;
&lt;br /&gt;
:c)	Prioritize communication to staff, partner agencies, and the public to build awareness around safer interactions for transit, motorists, pedestrians, bicyclists, and those using EPAMDs and expand the implementation of the Context Guide in underserved communities; and&lt;br /&gt;
&lt;br /&gt;
:d)	Delegate authority to approve design waivers for bicycle and pedestrian accommodations to the Secretary of MDOT.&lt;br /&gt;
&lt;br /&gt;
4.	Define certain terms within the context of this Policy.&lt;br /&gt;
&lt;br /&gt;
==Reference(s)==&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=2-112&amp;amp;enactments=false%20 Transportation Article, § 2-112, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=2-602&amp;amp;enactments=false Transportation Article, § 2-602, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=5-101&amp;amp;enactments=false Transportation Article, § 5-101, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=5-408.1&amp;amp;enactments=false Transportation Article, § 5-408.1, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=7-101&amp;amp;enactments=false Transportation Article, § 7-101, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=7-102&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, § 7-102, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=7-310&amp;amp;enactments=false Transportation Article, § 7-310, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-101&amp;amp;enactments=false Transportation Article, § 8-101, Annotated Code of Maryland] &lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-102&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, § 8-102, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-204.1&amp;amp;enactments=false Transportation Article, § 8-204.1, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-629&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, § 8-629, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-630&amp;amp;enactments=False&amp;amp;archived=False Transportation Article, § 8-630, Annotated Code of Maryland] &lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-635&amp;amp;enactments=false Transportation Article, § 8-635, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-901&amp;amp;enactments=false Transportation Article, § 8-901, Annotated Code of Maryland] &lt;br /&gt;
&lt;br /&gt;
[http://mgaleg.maryland.gov/mgawebsite/laws/StatuteText?article=gtr&amp;amp;section=8-908&amp;amp;enactments=false Transportation Article, § 8-908, Annotated Code of Maryland]&lt;br /&gt;
&lt;br /&gt;
[https://highways.dot.gov/sites/fhwa.dot.gov/files/Safe_System_Approach_for_Speed_Management.pdf FHWA’s Safe System Approach for Speed Management]&lt;br /&gt;
&lt;br /&gt;
[https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.2050marylandbpmp.com%2F&amp;amp;data=05%7C02%7Cmnemphos%40mdot.maryland.gov%7C39e6630e481a44ac5df608dc6016363e%7Cb38cd27c57ca4597be2822df43dd47f1%7C0%7C0%7C638490895741105607%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;amp;sdata=AhkEjFpGmaG9DroE1pbpNt%2BuW8Quf8uVUZ3v%2BiAjdso%3D&amp;amp;reserved=0 Maryland Bicycle and Pedestrian Master Plan]&lt;br /&gt;
&lt;br /&gt;
[https://zerodeathsmd.gov/highway-safety-office/strategic-highway-safety-plan/ Maryland Strategic Highway Safety Plan]&lt;br /&gt;
&lt;br /&gt;
[https://zerodeathsmd.gov/highway-safety-office/strategic-highway-safety-plan/ Maryland Vulnerable Road User Assessment]&lt;br /&gt;
&lt;br /&gt;
[http://www.roads.maryland.gov/contextdriven SHA Context Driven: Access and Mobility for All Users Guide]&lt;br /&gt;
&lt;br /&gt;
[http://www.roads.maryland.gov/psap SHA Pedestrian Safety Action Plan]&lt;br /&gt;
&lt;br /&gt;
[https://www.transportation.gov/sites/dot.gov/files/2022-02/USDOT-National-Roadway-Safety-Strategy.pdf United States Department of Transportation National Roadway Safety Strategy]&lt;br /&gt;
&lt;br /&gt;
==Scope==&lt;br /&gt;
This Policy is applicable to all capital improvement projects within MDOT right-of-way, such as construction or reconstruction of a roadway, intersection, or structure, as well as resurfacing projects.  Pursuant to State statute, this policy does not apply to corridors where specific users are prohibited.  Applicable projects that have not completed the NEPA process or will not achieve 30 percent design within 6 months of the Policy effective date, are also subject to this Policy and shall be reevaluated for opportunities to establish a Complete Streets Objective Statement, or an equivalent statement of project intent, that addresses safe access for all users.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The Policy is applicable to the following modal administrations:&lt;br /&gt;
&lt;br /&gt;
:1.	The SHA, MTA, and the Maryland Aviation Administration (MAA) as defined by Maryland law.&lt;br /&gt;
&lt;br /&gt;
:2.	The Policy also applies to enforcement, driver education and licensing, and behavior modification monitoring of insured motorists administered by the Motor Vehicle Administration (MVA), as well as programs and initiatives supported by The Secretary’s Office (TSO) and the Maryland Port Administration (MPA).  For these MDOT modes, the Policy shall apply to the work of all employees, contract employees, contractors, consultants, local governments, developers and third parties, working within or on MDOT assets or rights-of-way.&lt;br /&gt;
&lt;br /&gt;
:3.	The Maryland Transportation Authority (MDTA) projects constructed in any section of MDOT right-of-way.  The MDTA will continue to refer to SHA guidelines and standards for the design of transportation facilities on Maryland’s network.  In cases where ramps, roads, and structures in MDOT right-of-way abut planned or existing multimodal connections, MDTA shall refer to the Policy.  &lt;br /&gt;
&lt;br /&gt;
This Policy rescinds all previous modal policies, processes, and procedures related to and including the 2012 SHA Complete Streets Policy and applicable sections of the [[MDOT 701 Practical Design Policy]].  Applicable sections include Roadways (A-I), Transit (A-C), and Bridge (A-B).  Akin to Practical Design, however, this requires the development of an objective statement that emphasizes safety, communication, and quality in planning and design.&lt;br /&gt;
&lt;br /&gt;
==Responsible Party==&lt;br /&gt;
Assistant Secretary of Planning and Project Development&lt;br /&gt;
&lt;br /&gt;
==Policy Statement==&lt;br /&gt;
&lt;br /&gt;
A.	The MDOT shall aim to create a safe, comprehensive, integrated, and connected network to accommodate all users in a manner that is suitable to the existing and planned land use context as defined by the Context Guide.  Consideration of the safety of all lawful users shall be included in the planning, design, construction, and reconstruction of any transportation facility within MDOT right-of-way.  The Maryland Strategic Highway Safety Plan and the United States Department of Transportation National Roadway Safety Strategy articulate broad roadway safety goals.&lt;br /&gt;
&lt;br /&gt;
B.	The MDOT recognizes “Complete Streets” as an approach to planning and designing for all modes of transportation.  Complete Streets focuses on creating a safe environment for all users including those who employ human-powered means of travel, which includes walking and bicycling with or without the use of mobility aids and may also include using other human-scaled or micro-mobility devices that may be electric-powered or electric-assisted, such as e-bikes and e-scooters.&lt;br /&gt;
&lt;br /&gt;
C.	The MDOT will apply “Complete Streets” to all projects within MDOT right-of-way that connect people walking, bicycling, or using e-bikes, scooters, or mobility devices to transportation options. &lt;br /&gt;
&lt;br /&gt;
D.	The MDOT projects should employ national best practices in Complete Streets design to provide opportunities for mode shift and improve access for all users consistent with Maryland’s Context Guide, Pedestrian Safety Action Plan, Vulnerable Road User Safety Assessment, Statewide Bicycle and Pedestrian Master Plan, and other MDOT guidance documents. &lt;br /&gt;
&lt;br /&gt;
E.	The MDOT Safe System approach empowers and encourages communities to claim ownership of safe streets and public spaces.  All modes shall review and update respective public involvement practices to incorporate capacity building approaches that emphasize outreach to underserved communities on applicable projects.  The six principles of the Safe System approach as defined by the Federal Highway Administration (FHWA) shall be incorporated as appropriate.  The six principles are:&lt;br /&gt;
&lt;br /&gt;
:i.	Death and serious injuries are unacceptable,&lt;br /&gt;
:ii.	Humans make mistakes,&lt;br /&gt;
:iii.	Humans are vulnerable,&lt;br /&gt;
:iv.	Responsibility is shared, &lt;br /&gt;
:v.	Safety is proactive, and &lt;br /&gt;
:vi.	Redundancy is crucial.&lt;br /&gt;
&lt;br /&gt;
==Complete Streets Implementation==&lt;br /&gt;
&lt;br /&gt;
A.	The Policy shall be implemented on applicable projects starting January 1, 2025.  Within six months of the adoption of this Policy, each mode shall develop a Complete Streets Implementation Approach in collaboration with the Office of Active Transportation and Micromobility at TSO, SHA, and MVA’s Highway Safety Office to identify appropriate context driven applications of this Policy that provide equitable access to safer crossings of highways, safer traversing along highways, access to transit, and convenient connections to healthy food and life’s opportunities.  These implementation plans will include review and update of related policies and guidelines to ensure full and consistent implementation of this Policy. &lt;br /&gt;
&lt;br /&gt;
B.	Implementation of the Policy will be framed by several policies, design guidelines, and project development protocols. &lt;br /&gt;
&lt;br /&gt;
C.	The MDOT will review current policies and guidelines and adopt a compliance process to ensure full and consistent implementation of this Policy.  Within '''90 days''' after adoption of this Policy, TSO shall complete an initial review of planning, design, and other guidance documents from MDOT modes for compliance with the Policy.  The results will be provided to the modes to assist in the development of their Complete Streets Implementation Plans.  The review will include, but not be limited to, the following documents:&lt;br /&gt;
&lt;br /&gt;
:i.	[https://roads.maryland.gov/mdotsha/pages/index.aspx?PageId=26 SHA Accessibility Policy &amp;amp; Guidelines for Pedestrian Facilities along State Highways ] &lt;br /&gt;
&lt;br /&gt;
:ii.	[https://roads.maryland.gov/ohd2/bike_policy_and_design_guide.pdf SHA Bicycle Policy and Design Guidelines]    &lt;br /&gt;
&lt;br /&gt;
:iii.	[https://roads.maryland.gov/mdotsha/pages/Index.aspx?PageId=393 State Highway Access Manual (including TIS Guidelines)] &lt;br /&gt;
&lt;br /&gt;
D.	Several aspects of Practical Design require design choices that may conflict with context driven principles.  Sections of the [https://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_701.01_Implementation_Guidance Practical Design Implementation Guidance], for applicable modal units and projects, shall be revised to prioritize, where lawful, improved safety opportunities for modal shift and increased access to diverse, affordable, and convenient transportation options for all users as core returns on investment.  &lt;br /&gt;
&lt;br /&gt;
E.	A Complete Streets Objective Statement, or equivalent statement of project intent, shall be adopted for all roadway projects in MDOT right of way where more than one mode is lawfully permitted.  For projects that have not previously progressed past 30 percent or have not completed the NEPA process, this objective statement shall be developed prior to 30 percent design or during the planning phase and shall be maintained throughout the project life cycle. &lt;br /&gt;
&lt;br /&gt;
:i.	Where bicycle use is planned or existing, the objective statement shall identify a target for an improved or maintained Bicycle Level of Traffic Stress (LTS) score via the latest available Statewide LTS model. &lt;br /&gt;
&lt;br /&gt;
:ii.	The objective statement shall evaluate safety for all users, to the extent such historical crash data are available, and identify opportunities to improve vulnerable road user access. &lt;br /&gt;
&lt;br /&gt;
:iii.	Other measures shall be considered for non-motorists, for example, pedestrian level of comfort (PLOC), as they are adopted by the modes.  All applicable measures for the relevant modes shall be addressed in the objective statement. &lt;br /&gt;
&lt;br /&gt;
F.	The MDOT will implement techniques based on FHWA’s Safe System Approach for Speed Management, which provides methods to help practitioners understand the impacts of speed on traffic safety and explore the link between speed management and the Safe System Approach.  When speed limits are proactively lowered to address safety risks and implemented alongside speed management treatments, practitioners can expect that operating speeds and crash frequency and severity will decrease.  All applicable projects will prioritize safer driving speeds and access for vulnerable road users, where permitted.  The SHA shall lead periodic evaluations of the impact of speed management techniques on crashes and document successful safety approaches as Context Driven Case Studies on the [http://www.roads.maryland.gov/contextdriven Context Driven Web Portal] for public viewing.&lt;br /&gt;
 &lt;br /&gt;
G.	Applicable MDOT projects shall define a measure of effectiveness for engaging key stakeholders, especially vulnerable road users and underserved communities, during planning and design.  When there are competing needs among users and/or modes, safety shall be the highest priority; particularly safety for the most vulnerable road users while adhering to the facility’s context and addressing mobility and accessibility for all permitted users. &lt;br /&gt;
&lt;br /&gt;
H.	When construction activities necessitate, temporary closures of bicycle and pedestrian routes shall be coordinated with local jurisdictions and pertinent partners to avoid unnecessary impacts to access to the extent practicable.  Permanent severance or elimination of an existing bicycle or pedestrian route shall not be considered unless the project provides for construction of a feasible alternative route, or such an alternative route already exists.  The MDOT shall work to ensure that transportation options for people walking, bicycling, taking transit, and or operating an EPAMD will not be negatively impacted by any new transportation project or improvement to an existing transportation facility, including impacts to complete bicycle and pedestrian networks from limited-access highway projects.  Expanding opportunities for short, non-motorized trips is critical to meeting the State’s safety and emissions targets.  Transit providers are encouraged to design and implement innovative treatments such as modular bike lanes, curb extensions, and floating bus stops to preserve bicycle and pedestrian connectivity on multimodal corridors and in dense communities.  &lt;br /&gt;
&lt;br /&gt;
I.	All modes shall work with the developer community, local governments, and respective Adequate Public Facilities Ordinances (APFO) to ensure Complete Streets design features are provided within MDOT right-of-way pursuant to this Policy, the Context Guide and the Context Driven Toolkit on all applicable projects.  Developers seeking access to MDOT right-of-way will be subject to policies in SHA’s Access Manual.  Developers shall be encouraged to incorporate Complete Streets design features outside MDOT right-of-way to the extent feasible.&lt;br /&gt;
&lt;br /&gt;
J.	To strengthen the connection between transportation investments and land use and address historical disinvestment in underserved communities, all modes shall coordinate with the Maryland Department of Planning (MDP) and the Maryland Department of Housing and Community Development (DHCD) through TSO on initiatives and programs that support or are impacted by Complete Streets.  The coordination shall inform an interagency Sustainable Growth Work Plan action item for the Subcabinet to determine how best practices in traffic safety and multimodal planning can expand access to housing, jobs, and healthy food.  &lt;br /&gt;
&lt;br /&gt;
K.	Appropriate bicycle and pedestrian accommodation at transit facilities and on transit modes will be provided.  Where facilities cannot be provided, a waiver is required to be submitted to TSO.  The MTA will coordinate with local jurisdictions and other partners to improve pedestrian and bicycle access to transit.  The Washington Metropolitan Area Transit Authority (WMATA) is also encouraged to apply sustainability and multimodal planning and design principles to projects to improve station access, increase transit usage, and further reduce vehicle trips.&lt;br /&gt;
&lt;br /&gt;
L.	The MDOT’s projects shall continue to be planned, designed, constructed, operated, and maintained in accordance with applicable [https://www.ada.gov/law-and-regs/design-standards/ Federal and State Americans with Disabilities Act (ADA) guidelines].  Other uses of the right-of-way, such as parking, loading, curbside management, and green infrastructure, should also be considered. &lt;br /&gt;
&lt;br /&gt;
M.	Applicable MDOT projects shall include prioritization and accommodation of transit-oriented development where supportive infrastructure for transit is existing or planned.  Modes shall evaluate local master plans for planned walking and bicycling connections to transit.  The responsible mode will ensure all projects within MDOT right-of-way including, to the extent the APFO permits, developer projects, provide accessible and convenient facilities for pedestrians connecting to bus, rail, and micromobility, where appropriate.&lt;br /&gt;
&lt;br /&gt;
N.	The SHA shall work with the Maryland Highway Safety Office to establish or develop more aggressive Safety Performance Functions (SPFs).  The SHA shall adopt related crash reduction or crash modification factors (CRF/CMF) for all Context-Driven Toolkit engineering safety countermeasures based on established SPFs and maintain a CRF/CMF clearinghouse when there is not an existing accepted industry CRF/CMF, including access management, advanced technology/ITS, bicyclists, pedestrians, roadway, and speed management.  While CMFs do not yet exist for many safety countermeasures, safety improvements should not be precluded simply because there is not yet an established CMF.&lt;br /&gt;
&lt;br /&gt;
O.	The MDTA projects shall also be designed in accordance with the Policy, when access to a transit, walking or bicycling facility, like a transit stop or a regional trail head, is planned or available within a reasonable distance of MDTA’s project limits. &lt;br /&gt;
 &lt;br /&gt;
P.	The MAA shall incorporate Complete Streets design features to the extent appropriate and feasible for airport facilities and shall ensure consistency with appropriate Federal Aviation Administration (FAA) requirements.  &lt;br /&gt;
&lt;br /&gt;
Q.	The justification for any exception is to be documented, approved, and signed by all appropriate modal representatives.  Justification should reflect consideration of the impacts to surrounding communities and identify safe alternate routes within the scope and objective of the transportation project for which exemption is sought.  This Policy requires the Secretary’s approval of all waivers and assigns the development of the framework for the waiver process leading up to the Secretary’s approval to the modes and MDTA.&lt;br /&gt;
&lt;br /&gt;
R.	A clear and specific Complete Streets Implementation and Waiver Process shall be developed or identified by each mode and MDTA and included in each Complete Streets Implementation Plan.  Thresholds for approved exceptions shall be defined by each mode in the Complete Streets Implementation and Waiver approach.  This process shall permit exceptions to the Policy which may be applicable where circumstances or laws exist that prohibit or limit the ability to provide favorable conditions for all modes.  A Complete Streets Waiver Process, an overview of roles and responsibilities for undertaking that process, and adequate public notice shall be published and monitored to ensure departmental accountability for implementation of this Policy.&lt;br /&gt;
&lt;br /&gt;
S.	Accommodations for cyclists and pedestrians will not be required where: &lt;br /&gt;
:i.	the use of the transportation facility by that user group is prohibited by law, &lt;br /&gt;
:ii.	the cost of new accommodation would be excessively disproportionate to the need or probable use,&lt;br /&gt;
:iii.	current and future need as determined by land use, user volumes, safety data, or population densities cannot be demonstrated, &lt;br /&gt;
:iv.	state or local governments do not include such accommodations in their bicycle/pedestrian master plans,&lt;br /&gt;
:v.	construction of bicycle/pedestrian accommodations is not constructable due to engineering design limitations,&lt;br /&gt;
&lt;br /&gt;
:vi.	construction of such accommodations would be unsafe for potential users.&lt;br /&gt;
&lt;br /&gt;
T.	Excessively disproportionate cost increases must be noted in the justification reviewed and approved by the Secretary.&lt;br /&gt;
&lt;br /&gt;
U.	When existing right-of-way is a limiting factor, projects shall balance accessibility and mobility for all users with consideration to the context of the project area and local needs. &lt;br /&gt;
&lt;br /&gt;
V.	The best approach to reducing the cost of maintaining bicycle and pedestrian facilities is to plan for future maintenance in the project design phase, selecting sustainable and resilient materials and effectively locating street trees.  Maintenance activities can also provide opportunities to comply with ADA and should be used to make facilities as accessible as possible.  Every effort must be made by the leading agency to address surface conditions, debris, encroaching vegetation, signage, and markings for the life of the project or the project agreement.  Where a lead agency is unable to participate in maintenance or cost share opportunities, the State shall perform its due diligence to investigate innovative alternatives or technical assistance to deliver and maintain the project.&lt;br /&gt;
&lt;br /&gt;
W.	On or before November 15 each year, each MDOT mode and MDTA shall submit a report to the Assistant Secretary for Planning and Project Development at TSO, providing status updates on all projects subject to the Policy, including reports on applicable safety and accessibility performance metrics and speed management case studies.&lt;br /&gt;
&lt;br /&gt;
==Definitions== &lt;br /&gt;
&lt;br /&gt;
For the purposes of this Policy, the following words have the following meanings:&lt;br /&gt;
&lt;br /&gt;
A.	Complete Streets means as defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=8-901&amp;amp;enactments=False&amp;amp;archived=False Maryland Transportation Article §8-901]&lt;br /&gt;
&lt;br /&gt;
B.	Complete Streets Design Features means design features that accommodate and facilitate safe and convenient access and mobility to facilities by all users, including bicyclists, motorists, pedestrians, and public transportation users.&lt;br /&gt;
&lt;br /&gt;
C.	Complete Streets Objective Statement means MDOT’s specific, objective statement of fact that articulates the transportation problem being addressed and what is needed to solve that problem.  Safety, accessibility, and mode shift are priority transportation problems to be addressed.  All applicable roadway projects lawfully permitting more than one mode of transportation will identify an objective statement which prioritizes multimodal options, improved accessibility, and the application of Complete Streets design features identified in the Context Guide and defined in [https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gtr&amp;amp;section=2-112&amp;amp;enactments=false Maryland Transportation Article § 2-112].&lt;br /&gt;
&lt;br /&gt;
==Authorized/Supporting Documents==&lt;br /&gt;
[[MDOT 701 Practical Design Policy]]&lt;br /&gt;
&lt;br /&gt;
[[media:2025-02-7-MDOT Complete Streets Implementation Plan_FINAL DRAFT.pdf |Complete Streets Implementation Plan]]&lt;br /&gt;
&lt;br /&gt;
[[media:2025-02-20-MDOT Complete Streets Implementation_Exec Summary_FINAL DRAFT_1.pdf| Complete Streets Executive Summary]]&lt;br /&gt;
&lt;br /&gt;
==Modal Administrator/Executive Director Endorsements==&lt;br /&gt;
&lt;br /&gt;
This Complete Streets Policy demonstrates MDOT’s commitment to providing safer, more accessible, and more convenient mobility options for all lawful users of Maryland’s transportation system.&lt;br /&gt;
&lt;br /&gt;
([[media:MDOT-750-Complete-Streets-Signed.pdf|Please see signed hard copy for endorsements]])&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[https://www.mdot.maryland.gov/tso/pages/Index.aspx?PageId=207 Complete Streets Homepage]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf&amp;diff=6469</id>
		<title>File:2025-02-20-MDOT Complete Streets Implementation Exec Summary FINAL DRAFT 1.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:2025-02-20-MDOT_Complete_Streets_Implementation_Exec_Summary_FINAL_DRAFT_1.pdf&amp;diff=6469"/>
		<updated>2025-02-28T17:28:29Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf&amp;diff=6468</id>
		<title>File:2025-02-7-MDOT Complete Streets Implementation Plan FINAL DRAFT.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:2025-02-7-MDOT_Complete_Streets_Implementation_Plan_FINAL_DRAFT.pdf&amp;diff=6468"/>
		<updated>2025-02-28T17:28:28Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_645_Management_of_Freight_Railroad_Corridors&amp;diff=6467</id>
		<title>MDOT 645 Management of Freight Railroad Corridors</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_645_Management_of_Freight_Railroad_Corridors&amp;diff=6467"/>
		<updated>2025-02-28T15:51:16Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Rail]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: February 25, 2025&lt;br /&gt;
 Revised: February 25, 2025&lt;br /&gt;
 Effective Date: February 28, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note: There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
&lt;br /&gt;
[[Media:MDOT 645 Management of Freight Railroad Corridors.pdf| MDOT 645 Management of Freight Railroad Corridors Signed Hardcopy]]&lt;br /&gt;
&lt;br /&gt;
==Supporting Documents==&lt;br /&gt;
&lt;br /&gt;
MDOT 645.1 Rail Information Manual&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_645_Management_of_Freight_Railroad_Corridors&amp;diff=6466</id>
		<title>MDOT 645 Management of Freight Railroad Corridors</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_645_Management_of_Freight_Railroad_Corridors&amp;diff=6466"/>
		<updated>2025-02-28T14:26:22Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Rail]]&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Original Date: February 25, 2025&lt;br /&gt;
 Revised: February 25, 2025&lt;br /&gt;
 Effective Date: February 28, 2025&lt;br /&gt;
 &amp;lt;font face=&amp;quot;arial&amp;quot;&amp;gt;Note: There may be formatting differences between the electronic policy and the signed policy. &lt;br /&gt;
 '''MDOT signed policy supersedes all information provided on this page.''' &lt;br /&gt;
 Printed copies of this page only valid for this date: {{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}&lt;br /&gt;
&lt;br /&gt;
[[Media:MDOT 645 Management of Freight Railroad Corridors.pdf| MDOT 645 Management of Freight Railroad Corridors Signed Hardcopy]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_645_Management_of_Freight_Railroad_Corridors&amp;diff=6465</id>
		<title>MDOT 645 Management of Freight Railroad Corridors</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_645_Management_of_Freight_Railroad_Corridors&amp;diff=6465"/>
		<updated>2025-02-28T14:25:28Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: Created page with &amp;quot; MDOT 645 Management of Freight Railroad Corridors Signed Hardcopy&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Media:MDOT 645 Management of Freight Railroad Corridors.pdf| MDOT 645 Management of Freight Railroad Corridors Signed Hardcopy]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:MDOT_645_Management_of_Freight_Railroad_Corridors.pdf&amp;diff=6464</id>
		<title>File:MDOT 645 Management of Freight Railroad Corridors.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:MDOT_645_Management_of_Freight_Railroad_Corridors.pdf&amp;diff=6464"/>
		<updated>2025-02-28T14:25:17Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Scan_Leonora_Conti_202502260900.pdf&amp;diff=6463</id>
		<title>File:Scan Leonora Conti 202502260900.pdf</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=File:Scan_Leonora_Conti_202502260900.pdf&amp;diff=6463"/>
		<updated>2025-02-28T14:21:49Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: File uploaded with MsUpload&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;File uploaded with MsUpload&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6462</id>
		<title>MDOT Policy</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=MDOT_Policy&amp;diff=6462"/>
		<updated>2025-02-28T14:21:37Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Facilities==&lt;br /&gt;
*[[MDOT 640 Bus Rapid Transit]]&lt;br /&gt;
*[[MDOT 645 Management of Freight Railroad Corridors]]&lt;br /&gt;
*[[MDOT 680 Facility Naming and Dedication]]&lt;br /&gt;
*[[Media:Factors of Consideration 680.2.pdf| MDOT 680.2 Factors of Consideration]]&lt;br /&gt;
*[[media:Dedication Request Form 680.3.pdf|MDOT 680.3 Dedication Request Form]]&lt;br /&gt;
*[[Media:Implementation 680.04.pdf|MDOT 680.4 Implementation]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Access Management==&lt;br /&gt;
*[[MDOT 720 Maryland State-Owned Roadway Access Management]]&lt;br /&gt;
**[[MDOT 720.1 Delegation of Authority]]&lt;br /&gt;
**[[MDOT 720.2 Guidelines for Traffic Impact Reports and Studies]]&lt;br /&gt;
**[[MDOT 720.3 Hydraulic-Hydrologic Guidelines]]&lt;br /&gt;
**[[MDOT 720.4 Access Point Standards]]&lt;br /&gt;
**[[MDOT 720.5 Entrance Design Standards]]&lt;br /&gt;
**[[MDOT 720.6 Street Connection Standards]]&lt;br /&gt;
**[[MDOT 720.7 Site Access Improvement Standards]]&lt;br /&gt;
**[[MDOT 720.8 Technical Design Standards]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
	<entry>
		<id>http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=Tunnels&amp;diff=6461</id>
		<title>Tunnels</title>
		<link rel="alternate" type="text/html" href="http://policymanual.mdot.maryland.gov/mediawiki/index.php?title=Tunnels&amp;diff=6461"/>
		<updated>2024-12-11T17:14:27Z</updated>

		<summary type="html">&lt;p&gt;Mnemphos: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;:* [[Tunnel Rehabilitation|Rehabilitation]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Practical Design Guidance]]&lt;/div&gt;</summary>
		<author><name>Mnemphos</name></author>
		
	</entry>
</feed>