Title 14 – Department of Transportation
Current through 2026-01-20. Source: COBRA Register Volume 04, Issue 02. Published by the Baltimore City Department of Legislative Reference.
Subtitle 01 – Alley Gating
Chapter 01 – Documents Incorporated by Reference
Balt., Md., COBRA § 14.01.01.01 (2026)
Regulation .01 Documents Incorporated by Reference.LinkCopy Citation
All provisions of the Baltimore City Department of Transportation Book of Standards (2025) are incorporated by reference to <cite data-path="14">this Title</cite>.
Subtitle 02 – Dockless Vehicles
Chapter 01 – General Provisions
Balt., Md., COBRA § 14.02.01.01 (2026)
Regulation .01 Scope.LinkCopy Citation
<cite data-path="14.02.01">This chapter</cite> establishes rules and regulations for the operation of dockless vehicles in Baltimore City.
Balt., Md., COBRA § 14.02.01.02 (2026)
Regulation .02 Definitions.LinkCopy Citation
A.
In <cite data-path="14.02.01">this chapter</cite>, the following terms have the meanings indicated.
B.
Terms Defined.
(1)
Adaptive Dockless Vehicle.
(a)
“Adaptive dockless vehicle” means a dockless vehicle that is accessible to people with a physical disability.
(b)
“Adaptive dockless vehicle” includes a motorized or non-motorized:
(a)
Recumbent bicycle;
(b)
Tricycle; and
(c)
Hand cycle.
(2)
Alternative Deployment Location.
(a)
“Alternative deployment location” means an area other than a public street.
(b)
“Alternative deployment location” includes:
(i)
A park;
(ii)
A plaza;
(iii)
A parking lot;
(iv)
Private property; or
(v)
A transit station.
(3)
Applicant.
(a)
“Applicant” means a person applying for an initial dockless vehicle permit.
(b)
“Applicant” does not include a permit holder applying for the renewal of a dockless vehicle permit.
(4)
“Application Programming Interface endpoint (API)” means a protocol that enables a software application to:
(a)
Communicate with another platform; or
(b)
Exchange data.
(5)
“Beta endpoint” means an API endpoint that has been officially released in a testing mode by its regulatory authority but not formally adopted.
(6)
“Block face” means one side of a street between the intersection of two other streets, excluding an alleyway.
(7)
“Community event” means an event held by:
(a)
A community organization as recognized by the City’s Online Community Association Directory; or
(b)
Another organization as deemed appropriate by the Director.
(8)
“Compliance score” means a calculation of a permit holder’s compliance with the provisions of <cite data-path="14.02.01">this chapter</cite>.
(9)
“CPSC” means the U.S. Consumer Product Safety Commission.
(10)
“Department” means the Baltimore City Department of Transportation.
(11)
“Deployment” means the location where a dockless vehicle is placed by a permit holder when it is made available for rent.
(12)
“Deployment district” means a geographic area designated in the Department’s MDS Policy API for tracking the distribution of dockless vehicles.
(13)
“Director” means the Director of the Department of Transportation.
(14)
“Dockless corral” means a geographic location designated by the Department where a dockless vehicle may be parked.
(15)
“Dockless vehicle” has the meaning stated in <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(b)">City Code Article 31, § 38-1(b)</cite>.
(16)
“E-bike” has the meaning stated in <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(d)">City Code Article 31, § 38-1(d)</cite>.
(17)
"E-scooter" has the meaning stated in <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(e)">City Code Article 31, § 38-1(e)</cite>.
(18)
“Equitable access” means a process of making dockless vehicles available to the public by removing barriers to use including:
(a)
Geography;
(b)
Income;
(c)
Banking status; or
(d)
Inclusion in a federally protected class.
(19)
“Equity zone” means a geographic location where a dockless vehicle is deployed for equitable access as designated in the official document provided by the Department to a permit holder.
(20)
“Fleet” means the total number of dockless vehicles operated by a permit holder in Baltimore City, regardless of whether they are available for rent.
(21)
“Genetic information” means genetic markers related to a person’s medical history, including the manifestation of a:
(a)
Disease; or
(b)
Disorder.
(22)
“Geo-fencing” means a location-based service that uses GPS or cellular data to identify when a mobile device or dockless vehicle enters or exits a virtual geographic boundary.
(23)
“GitHub” means a code hosting platform.
(24)
“Low-income population” means a person whose family income is at or below 150 percent of the poverty line
(25)
“MDS” means Mobility Data Specification.
(26)
“MDS Policy API” means the Open Mobility Foundation standards and code available on GitHub for secure mobility data exchange.
(27)
“New permit holder” means a provider of dockless vehicles who has:
(a)
Not previously been issued a permit to operate on a public street by the Department; or
(b)
Not held a permit in the previous year.
(28)
Non-deployment Request.
(a)
“Non-deployment request” means a request from a member of the public to prevent the deployment of a dockless vehicle in front of their property.
(b)
“Non-deployment request” includes a vehicle deployed by a dockless vehicle permit holder.
(c)
“Non-deployment request” does not include a vehicle parked by a user.
(29)
“OMF” means Open Mobility Foundation.
(30)
“Overconcentration” means the deployment of more than 25 percent of a permit holder’s fleet in a single deployment district.
(31)
“Payment Card Industry Data Security Standards” means the set of guidelines designed to ensure companies that process credit card information maintain a secure environment.
(32)
“Parking corral” means an area designated by the Department where a dockless vehicle may be parked.
(33)
“Permit” means a dockless vehicle permit as provided in <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-8">City Code Article 31, § 38-8</cite>.
(34)
“Permit agreement” means a document that is entered into between the City and a permit holder that:
(a)
Stipulates required insurance coverage for a permit holder to operate in Baltimore City;
(b)
Stipulates that the permit holder is obligated to adhere to applicable laws and regulations to operate in Baltimore City; and
(c)
Outlines procedures for the cessation of operations prior to the end of a permit.
(35)
“Permit holder” means a provider of dockless vehicles who has been issued a permit by the Department to operate on a public street.
(36)
“Permit year” means the period from July 1 to June 30 annually.
(37)
“Person” has the meaning stated in <cite data-doc="Md. Code" data-path="ggp|1-107">General Provisions Article § 1-107, </cite>City Code.
(38)
“Referral agency” means a government assistance program that provides services to individuals who qualify as low-income.
(39)
<em>“</em>Remote shut down notice” means a written communication from the Department sent via e-mail to a permit holder instructing the permit holder to shut down the entirety or a portion of their fleet in Baltimore City.
(40)
Seizure.
(a)
“Seizure” means the act of removing a dockless vehicle in violation of <cite data-path="14.02.01">this chapter</cite> from:
(i)
City property; or
(ii)
An area inaccessible to a permit holder.
(b)
“Seizure” includes the act of:
(i)
Towing;
(ii)
Impoundment; and
(iii)
Retrieval from a body of water.
(41)
“Speed governor” means a device that ensures the motor of a dockless vehicle is incapable of traveling at a speed in excess of a mandated speed limit on level ground.
(42)
“Street” has the meaning stated in <cite data-doc="Md. Code" data-path="ggp|1-109">General Provisions Article § 1-109, </cite>City Code.
(43)
“Third-party” means a person that is not the permit holder that may access data related to the operation of dockless vehicles.
(44)
“Third-party aggregator” means an organization that processes data from one or more sources for use by the City.
(45)
“Towing Division” means the Baltimore City Department of Transportation’s Towing Division.
(46)
“Tree pit” means an area of the street where a tree is planted.
(47)
“Underserved population” means a group of people that:
(a)
Has limited or no access to resources; or
(b)
Is otherwise disenfranchised.
(48)
“Vehicle model” means a vehicle of the certain type, but with different features or appearance.
(49)
“Vehicle type” means a vehicle that meets specifications in the City’s vehicle code for that vehicle.
(50)
“Web Content Accessibility Guidelines (WCAG)” means guidelines published by the World Wide Web Consortium's Web Accessibility Initiative to make web content accessible.
Balt., Md., COBRA § 14.02.01.03 (2026)
Regulation .03 Permits - Applications.LinkCopy Citation
A.
An applicant shall submit an application for a dockless vehicle permit in accordance with the information published on the Department’s website regarding submission processes.
B.
At the time of submission, an applicant shall ensure their application contains:
(1)
An operations plan that includes:
(a)
Hours and days of operation, including relevant limitations;
(b)
Procedures for responding to extreme weather events;
(c)
Procedures for responding to special events;
(d)
Procedures for responding to complaints;
(e)
Procedures for ensuring availability of dockless vehicles in each deployment district; and
(f)
Procedures and avoiding overconcentration of the applicant’s fleet in a single deployment district; and
(2)
A maintenance plan that includes:
(a)
Procedures for ensuring that the applicant’s fleet is:
(i)
Safe for public use; and
(ii)
Well-maintained;
(b)
A schedule for inspection of the applicant’s fleet;
(c)
A description of the training method used for the applicant’s mechanics;
(d)
A description of the life expectancy for each component of a dockless vehicle; and
(e)
A method of long-term monitoring to ensure the condition of vehicles in the applicant’s fleet.
C.
An applicant shall notify the Department of a change to the noted requirements in <cite data-path="14.02.01.03|B.">§B of this regulation</cite>.
Balt., Md., COBRA § 14.02.01.04 (2026)
Regulation .04 Permits - Fees.LinkCopy Citation
A.
A permit holder shall remit a fee for the issuance of a revocable dockless vehicle permit within 30 days of being awarded the permit.
B.
The Board of Estimates shall:
(1)
Approve the cost of the fee, which will include the cost of:
(a)
Issuing the permit;
(b)
Program administration;
(c)
Associated infrastructure;
(d)
Education;
(e)
Enforcement; and
(f)
Program evaluation; and
(2)
Disclose the cost of the fee to a permit applicant before the application deadline.
C.
If a permit holder’s permit is revoked, the Department may not refund a permitting fee paid by the permit holder for the current permit cycle.
Balt., Md., COBRA § 14.02.01.05 (2026)
Regulation .05 Permits - Issuance.LinkCopy Citation
A.
The Department may issue up to three dockless vehicle permits annually through:
(1)
A renewal of an existing permit; or
(2)
A competitive application process.
B.
Except as provided in <cite data-path="14.02.01.05|C.">§C of this regulation</cite>, a permit holder shall maintain a daily fleet of two or more vehicle types.
C.
If a permit holder administers an adaptive vehicle program, the permit holder may maintain a fleet of a single vehicle type.
D.
If a permit holder fails to meet one or more of the standards in <cite data-path="14.02.01">this chapter</cite>, the Department shall:
(1)
Review the performance of the permit holder under the permit issued; and
(2)
Assess the violation for a citation in accordance with <cite data-path="14.02.01.26">regulation .26 of this chapter</cite>.
Balt., Md., COBRA § 14.02.01.06 (2026)
Regulation .06 Permits - Renewal.LinkCopy Citation
A.
Eligibility Requirements.
A permit holder shall be eligible to renew a permit if the permit holder:
(1)
Has not had a violation in the permit year prior; and
(2)
Is in good standing to conduct business in the State of Maryland.
B.
Renewal Process.
A permit holder may renew a permit by:
(1)
Signing a renewal agreement that includes current rules and regulations; and
(2)
Remitting an annual fee in accordance with <cite data-path="14.02.01.04">regulation .04 of this chapter</cite>.
C.
The Department may renew a permit if a permit holder meets the eligibility requirements in <cite data-path="14.02.01.06|A.">§A of this regulation</cite>.
Balt., Md., COBRA § 14.02.01.07 (2026)
Regulation .07 Permits - Revocation.LinkCopy Citation
A.
The Department may revoke a permit in accordance with <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-13">City Code Article 31, § 38-13</cite>.
B.
Revocation Hearing Procedures.
(1)
A permit holder may request a hearing to determine whether sufficient facts exist to revoke a permit.
(2)
The Department shall:
(a)
Designate a time and place for a revocation hearing;
(b)
Provide the permit holder with notice of the hearing at least ten business days before the scheduled date; and
(c)
Provide an opportunity for the permit holder to be heard at the hearing.
(3)
A permit holder may:
(a)
Waive the right to an in-person hearing for the revocation of a permit; and
(b)
Submit a written opposition to the revocation before the scheduled hearing date in accordance with <cite data-path="14.02.01.07|B.|(4)">§B(4) of this regulation</cite>.
(4)
A permit holder shall submit written opposition to:
(5)
Following the hearing or the review of a written opposition, the Department shall record its findings of fact in writing.
(6)
The Director may revoke a permit if:
(a)
The Department finds that sufficient grounds exist to revoke a permit; and
(b)
The Department provides at least five days’ written notice to the permit holder in advance of the revocation.
C.
A permit holder may appeal the revocation of a dockless vehicle permit to the Director.
Balt., Md., COBRA § 14.02.01.08 (2026)
Regulation .08 Deployment.LinkCopy Citation
A.
In General.
(1)
A permit holder shall ensure that a dockless vehicle is deployed in compliance with City Code Article 31, § 38-19, Unlawful Parking.
(2)
A permit holder shall provide an account for its mobile application to the Department so that Department employees can access a dockless vehicle for free for the purposes of:
(a)
Education;
(b)
A routine vehicle inspection; or
(c)
Vehicle repositioning.
(3)
A permit holder shall apply speed geo-fencing to a dockless vehicle by using a speed governor to establish a City-wide speed limit of 15 mph except for:
(a)
In a reduced speed zone as defined in the Department’s MDS Policy API where speeds are limited to eight mph; and
(b)
In a no ride zone as defined in the Department’s MDS Policy API where a dockless vehicle is limited to a speed of no more than three mph.
B.
Deployment District Requirements.
(1)
On each day of service, a permit holder shall deploy to each deployment district:
(a)
A minimum of 5 percent of their fleet; and
(b)
A maximum of 25 percent of their fleet.
(2)
Compliance.
The Department shall:
(a)
Evaluate daily compliance with the requirements in <cite data-path="14.02.01.08|B.|(1)">§B(1) of this regulation</cite> based on at least one hour of compliance between 5:00 a.m. and 9:0 a.m.; and
(b)
Notify a permit holder in violation of the requirements in <cite data-path="14.02.01.08|B.|(1)">§B(1) of this regulation</cite> via a compliance score notification.
(3)
A permit holder shall redistribute their fleet within three hours of receipt of a compliance score notification from the Department.
C.
Equitable Deployment Requirements.
(1)
A permit holder shall deploy a minimum of three dockless vehicles per day to each equity zone.
(2)
Compliance.
The Department shall:
(a)
Evaluate daily compliance based on at least one hour of compliance between 5:00 a.m. and 9:00 a.m; and
(b)
Notify a permit holder of in violation of <cite data-path="14.02.01.08|C.|(1)">§C(1)</cite><cite data-path="14.02.01.08|C.|(2)">-(2)</cite> of <cite data-path="14.02.01.08">this regulation</cite> via a compliance score notification.
D.
Prohibitions.
(1)
A permit holder may not deploy a dockless vehicle:
(a)
Outside of a parking corral on a block face that contains an official parking corral designated by the Department, except as provided in <cite data-path="14.02.01.08|D.|(2)">§D(2) of this regulation</cite>;
(b)
In a quantity greater than ten per block face, except as allowed by the Department to accommodate a special event;
(c)
On a block face which contains the front entrance to a K-8 school;
(d)
In a tree pit or otherwise landscaped area;
(e)
In front of a property with an approved non-deployment request in accordance with <cite data-path="14.02.01.08|E.">§E of this regulation</cite>; or
(f)
In a location the Department has notified the permit holder that they may not deploy to, beginning 48 hours after the notification.
(2)
If a parking corral is full, a permit holder may deploy a dockless vehicle on a block face outside of the parking corral.
(3)
Unless a permit holder receives approval from the Department, a permit holder may not designate a public street in Baltimore City as a:
(a)
No parking zone;
(b)
Reduced speed zone; or
(c)
No ride zone.
E.
Non-Deployment Requests.
(1)
A property owner or manager may submit a non-deployment request in writing to the Department for an area adjacent to their property.
(2)
The Department shall notify a permit holder:
(a)
Of an approved non-deployment request; and
(b)
That an approved non-deployment request will begin 48-hours after notification.
F.
Severe Weather and Emergencies.
(1)
If 24-hour advanced notice is provided, the Department may:
(a)
Suspend the requirements of <cite data-path="14.02.01.08">this regulation</cite>; or
(b)
Require the removal of:
(i)
An entire fleet; or
(ii)
A portion of a fleet in a defined geographic location.
(2)
The Department may require a permit holder to remove a dockless vehicle from:
(a)
An evacuation route prior to an emergency snow event; and
(b)
A low-lying area prior to an emergency flooding event.
G.
Special Events.
The Department may suspend the requirements of <cite data-path="14.02.01.08">this regulation</cite> during a special event.
H.
Temporary Exemptions from Deployment Regulations.
(1)
A permit holder may apply for a temporary exemption from the deployment requirements in <cite data-path="14.02.01">this chapter</cite>.
(2)
A permit holder shall include a plan for communicating operational changes to affected users and the public within the application for temporary exemption.
(3)
The Department shall review applications for temporary exemption:
(a)
Within 24 hours for an application based on an immediate safety concern; and
(b)
Within five business days for other exemption requests.
I.
Alternative Deployment Locations.
(1)
A permit holder shall obtain permission to deploy a dockless vehicle to an alternative deployment location from:
(a)
The Department;
(b)
A private property owner; or
(c)
Another City agency.
(2)
A permit holder shall communicate the permission to deploy a dockless vehicle in an alternative deployment location via:
(a)
Signage approved by the entity granting permission; or
(b)
A mobile or web application.
Balt., Md., COBRA § 14.02.01.09 (2026)
Regulation .09 Equitable Dockless Vehicle Access.LinkCopy Citation
A.
Cash Payment Plans.
(1)
A permit holder shall:
(a)
Provide the option to rent a dockless vehicle using a cash payment;
(b)
Offer at least one cash payment location in each deployment district;
(c)
Identify the following on its website and mobile application:
(i)
The process for making a cash payment; and
(ii)
The locations where a cash payment option is available;
(d)
Provide an instruction document to the Department that summarizes the process to sign up for a cash-payment plan; and
(e)
Inform a user of the availability of cash payment option:
(i)
During initial sign-up; and
(ii)
Via email at least twice annually.
(2)
The Department shall post the instruction document provided for in <cite data-path="14.02.01.09|A.|(1)|(d)">§A(1)(d) of this regulation</cite> to the Department website.
B.
Non-Smartphone Plans.
(1)
A permit holder shall:
(a)
Offer the option to rent a dockless vehicle without the use of a smartphone;
(b)
Identify the process to rent a dockless vehicle without using a smartphone on its website and mobile application;
(c)
Provide an instruction document to the Department that summarizes the process to sign up for a cash-payment plan; and
(d)
Inform a user of the availability of cash payment option:
(i)
During initial sign-up; and
(ii)
Via email at least twice annually.
(2)
The Department shall post the instruction document provided for in <cite data-path="14.02.01.09|B.|(1)|(c)">§B(1)(c) of this regulation</cite> to the Department website.
C.
Low-Income Plans.
(1)
A permit holder shall offer a low-income plan to users with an income level at or below 200 percent of the federal poverty guideline.
(2)
A permit holder shall approve a low-income user by obtaining:
(a)
Preapproval from a referral agency; or
(b)
Proof of assistance, including:
(i)
Local assistance;
(ii)
State assistance; or
(iii)
Federal assistance.
(3)
A permit holder shall ensure a low-income plan:
(a)
Waives an unlock fee for at least four rides per day; and
(b)
Offers a minimum 80 percent discount on rental fees for at least four rides per day.
(4)
A permit holder shall:
(a)
Describe the process to sign up for a low-income plan on the dockless vehicle:
(i)
Website; and
(ii)
Mobile application;
(b)
Notify the Department of a change to verification methods for low-income customer plans;
(c)
Provide an instruction document to the Department that summarizes the process to sign up for a low-income plan;
(d)
Inform a user of the availability of cash payment option:
(i)
During initial sign-up; and
(ii)
Via email at least twice annually.
(5)
The Department shall post the instruction document provided for in <cite data-path="14.02.01.09|C.|(4)|(c)">§C(4)(c) of this regulation</cite> to the Department website.
D.
Customer Service Phone Lines.
(1)
A permit holder shall maintain a live, multilingual 24-hour customer service phone line.
(2)
If a caller is required to leave a voicemail when calling the customer service phone line, a permit holder shall respond with a call back within two hours.
(3)
A permit holder shall provide a translation or call back within four hours when a message is left by a customer in:
(a)
Spanish;
(b)
French;
(c)
Mandarin Chinese; or
(d)
Korean.
E.
Web Accessibility.
Within 120 days of receiving a permit, a permit holder shall ensure that its software application used for vehicle rental and website are accessible to visually impaired individuals consistent with the latest WCAG standards.
Balt., Md., COBRA § 14.02.01.10 (2026)
Regulation .10 Compliance.LinkCopy Citation
A.
Compliance Scores – Calculation and Reporting.
The Department shall:
(1)
Calculate a compliance score to determine compliance for:
(a)
Equitable distribution of a dockless vehicle fleet; and
(b)
Parking of a dockless vehicle fleet; and
(2)
Report compliance scores to a permit holder twice per calendar month.
B.
Compliance Requirements – Distribution.
(1)
To remain compliant with the distribution requirements of <cite data-path="14.02.01">this chapter</cite>, a permit holder shall ensure a minimum compliance score of 85 percent for each reporting period in:
(a)
A deployment district; and
(b)
An equity zone.
C.
Compliance Requirements – Fleet Parking.
To remain compliant with fleet parking requirements, a permit holder shall ensure:
(1)
No more than 5 percent of a dockless vehicle fleet remains parked for longer than 5 days for the period from April 1 through November 30; and
(2)
No more than 10 percent of a dockless vehicle fleet remains parked for longer than 5 days for the period from December 1 through March 31.
D.
Eligibility for Fleet Cap Increase.
To be eligible for a fleet cap increase, a permit holder shall score a minimum of 90 percent compliance for each reporting period in
(1)
A deployment district; and
(2)
An equity zone.
E.
Winter Weather Compliance Exemptions.
On days for which the Baltimore City Public School System implements a modified schedule due to inclement weather, the Department shall grant compliance exemptions for violations of:
(1)
Distribution;
(2)
Equity; and
(3)
Five-day parking.
F.
Remote Shut Down Notice Exemptions.
When the Department has issued a remote shutdown notice to a permit holder, the Department shall grant compliance exemptions for violations of:
(1)
Distribution;
(2)
Equity; and
(3)
Five-day parking.
Balt., Md., COBRA § 14.02.01.11 (2026)
Regulation .11 Vehicle Standards.LinkCopy Citation
A.
Vehicle Approval.
(1)
A permit holder shall ensure a dockless vehicle model intended for deployment on a public street has been approved by the Director prior to its deployment on the public street.
(2)
To deploy a new vehicle model or vehicle type, a permit holder shall submit the following to the Department at least two weeks prior to intended deployment:
(a)
Vehicle specifications;
(b)
A safety certificate;
(c)
A deployment plan;
(d)
A change to an operations plan, if any; and
(e)
A change to a maintenance plan, if any.
(3)
A permit holder may not deploy a new vehicle model or type until receiving written approval from the Department.
B.
Required Features – In General.
A permit holder shall ensure a dockless vehicle deployed on a public street:
(1)
Weighs no more than 100 pounds;
(2)
Is equipped with an operational structural feature that allows the vehicle to be stably parked upright without needing to lean on another object;
(3)
Is equipped with built-in front and back lights that:
(a)
Illuminate while the dockless vehicle is in use; and
(b)
Are visible from a distance of at least 500 feet under normal atmospheric conditions at night;
(4)
Is equipped with a bell or noise emitting device;
(5)
Has tires with a diameter of at least nine inches;
(6)
Has tactile identification which:
(a)
Meets State requirements; and
(b)
Is located on the stem near the handlebars if handlebars are present; and
(7)
Has legible decals listing:
(a)
The name of the permit holder displayed in a minimum of 16-point font;
(b)
The following contact information for a permit holder displayed in a minimum of 16-point font:
(i)
A toll-free telephone number;
(ii)
An e-mail address; and
(iii)
A website address; and
(c)
A unique identification number displayed in:
(i)
A minimum of 48-point font; or
(ii)
Font that is at least 1 inch in height.
C.
Required Features – E-scooters.
A permit holder shall ensure that an e-scooter deployed on a public street:
(1)
Has a speedometer that is legible; and
(2)
Is equipped with a speed governor capable of throttling speeds to specific speed limits in geographical areas designated in the MDS Policy API.
D.
Data and Information.
A permit holder shall ensure a dockless vehicle and its associated apps do not provide false information, including:
(1)
An inaccurate speedometer reading; and
(2)
An alarm that announces that a vehicle can notify the police.
E.
Additional Requirements.
(1)
A permit holder shall certify that its deployed vehicles meet:
(a)
Applicable federal laws;
(b)
Applicable State laws;
(c)
Applicable provisions of City Code;
(d)
CPSC Safety Standards: ISO 43.150 for Pedal Bicycles; and
(e)
CPSC Public Law 107-319 for E-Scooters and E-Bicycles.
(2)
A permit holder shall certify that each dockless vehicle they deploy in the City are:
(a)
Free of defects in materials;
(b)
Free of defects in construction; and
(c)
Safe for members of the public to use in the ordinary course of usage.
Balt., Md., COBRA § 14.02.01.12 (2026)
Regulation .12 Vehicle Standards - Inspections and Notification.LinkCopy Citation
A.
The Department shall:
(1)
Perform regular vehicle inspections to ensure that a rentable dockless vehicle deployed on a public street is:
(a)
Functioning safely; and
(b)
Properly equipped; and
(2)
Provide advance notice to a permit holder about the details of an inspection to be performed.
B.
For vehicles found to be in violation of <cite data-path="14.02.01">this chapter</cite>, the Department shall notify a permit holder within 24 hours of inspection.
Balt., Md., COBRA § 14.02.01.13 (2026)
Regulation .13 Vehicle Standards – Timeline for Compliance.LinkCopy Citation
Upon notification of a violation in accordance with <cite data-path="14.02.01">this chapter</cite>, the Department shall calculate a timeline for compliance that is:
A.
Based on the extent of changes required to a permit holder’s fleet;
B.
No fewer than 60 days; and
C.
No more than 6 months.
Balt., Md., COBRA § 14.02.01.14 (2026)
Regulation .14 Remote Shutdown.LinkCopy Citation
A.
User Reported Safety Issue.
(1)
Upon the first report of a safety issue by a user, a permit holder shall remotely shut down the dockless vehicle so that it cannot be operated until repaired.
(2)
If a reported safety issue is due to an equipment malfunction which could be present in additional dockless vehicles, the permit holder shall:
(a)
Remove their entire fleet of vehicles from the street within 24 hours; and
(b)
Ensure the fleet remains off the street until:
(i)
Further investigation is completed; and
(ii)
Relaunch is approved by the City.
B.
Remote Shut Down Notice.
(1)
The Department may issue a remote shutdown notice if it is deemed necessary to protect:
(a)
The safety of a dockless vehicle user; or
(b)
Public safety.
(2)
The Department shall ensure a remote shutdown notice includes:
(a)
The duration of the shutdown period;
(b)
The reasoning behind the shutdown;
(c)
Which vehicle type the permit holder is instructed to shut down; and
(d)
The geographic area within Baltimore City in which the vehicles should be shut down.
(3)
Within two hours of receipt of a remote shutdown notice from the Department, a permit holder shall remotely shut down:
(a)
Part of their fleet, as specified in the notice; or
(b)
Their entire fleet, as specified in the notice.
Balt., Md., COBRA § 14.02.01.15 (2026)
Regulation .15 Fleet Size.LinkCopy Citation
A.
Minimum and Maximum Fleet Sizes.
(1)
For each permitted vehicle type, a permit holder may initially operate a fleet consisting of:
(a)
A minimum of 150 dockless vehicles; and
(b)
A maximum of 1500 dockless vehicles.
(2)
A permit holder’s total fleet may include a combination of vehicle types allowed by their permit if there is a minimum of 150 vehicles of each type.
B.
Adaptive Vehicle Exemptions.
(1)
The Department may exempt a permit holder that includes adaptive dockless vehicles in their fleet from:
(a)
The requirement to maintain a minimum of 150 vehicles for adaptive dockless vehicles; and
(b)
The requirement to maintain a minimum of 150 vehicles for other permitted dockless vehicle types.
(2)
A permit holder that includes an adaptive dockless vehicle in their fleet shall ensure the adaptive dockless vehicle:
(a)
Is officially approved by the Director; and
(b)
Is not included in the count for the maximum number of vehicles allowed in a permit holder’s fleet.
C.
Timelines for Reaching Minimum Fleet Size.
(1)
A permit holder permitted in the previous year shall reach the minimum fleet size per vehicle type within 20 days of permit issuance.
(2)
A new permit holder shall reach the minimum fleet size within 60 days of permit issuance.
(3)
A permit holder who introduces a new vehicle type shall reach the minimum fleet size within 60 days of receiving approval of the new vehicle type from the Department.
D.
Fleet Increases.
(1)
Each quarter, a permit holder may request a fleet increase of up to 250 vehicles in excess of the limits established in <cite data-path="14.02.01.15|A.">§A of this Regulation</cite>.
(2)
In reviewing a fleet increase request, the Department shall assess:
(a)
Performance during the period prior to the evaluation; and
(b)
Projections for the subsequent quarter.
(3)
The Department may:
(a)
Set an overall fleet cap; and
(b)
Revoke a fleet increase.
Balt., Md., COBRA § 14.02.01.16 (2026)
Regulation .16 Parking and Operation.LinkCopy Citation
A.
In General.
(1)
A permit holder shall instruct users to:
(a)
Park a dockless vehicle in compliance with <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-19">City Code Article 31, § 38-19</cite>;
(b)
Operate a dockless vehicle in compliance with <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-18">City Code Article 31, § 38-18</cite>; and
(c)
Provide end of trip pictures that show:
(i)
The location a vehicle was parked; and
(ii)
The manner in which a vehicle was parked.
(2)
A permit holder shall use end of trip pictures:
(i)
When a parking violation is reported by the Department; and
(ii)
To disable a user account when three or more end of trip pictures fail to provide the information required by <cite data-path="14.02.01.16|A.|(1)|(c)">§A(1)(c) of this regulation</cite>.
B.
Notice and Response.
(1)
Upon notification that a dockless vehicle is improperly parked, a permit holder shall reposition or remove the vehicle within:
(a)
Three hours of notification by the Department; and
(b)
Six hours of notification by a member of the public.
(2)
The Department may perform a check of parking complaint response times, during which the Department may:
(a)
Report an illegally parked vehicle officially; or
(b)
Anonymously report an illegally parked vehicle as a member of the public.
C.
Abandoned Vehicles.
If a dockless vehicle has been parked at the same location and not ridden for five consecutive days, a permit holder shall:
(1)
Perform a mechanical check of the dockless vehicle; and
(2)
Relocate the dockless vehicle to another block face.
D.
Mobile Application Requirements.
A permit holder shall:
(1)
Ensure a dockless vehicle mobile application displays:
(a)
Applicable operating laws within four menu selections from the home screen; and
(b)
The location of parking corrals installed by the Department; and
(2)
Provide a discount through the mobile application to a user who ends their trip by parking a dockless vehicle in a parking corral installed by the Department.
(3)
Upload the location of parking corrals installed by the Department to a dockless vehicle mobile application within 10 days of notification from the Department.
E.
No Parking Zones.
(1)
The Department may establish a no parking zone on the public street in accordance with <cite data-path="14.02.01.16|E.|(2)">§E(2) of this regulation</cite>.
(2)
For a no parking zone established in accordance with <cite data-path="14.02.01.16">this regulation</cite>, the Department shall:
(a)
Identify the no parking zone in the MDS Policy API; and
(b)
Notify a permit holder of the no parking zone through the MDS Policy API.
(3)
Within 72 hours of notification from the Department, a permit holder shall prohibit a user from ending a trip in a no parking zone.
F.
No Operation Zones.
(1)
The Department may establish a no operation zone on the public street in accordance with <cite data-path="14.02.01.16|F.|(2)">§F(2) of this regulation</cite>.
(2)
For a no operation zone established in accordance with <cite data-path="14.02.01.16">this regulation</cite>, the Department shall:
(a)
Identify the no operation zone in the MDS Policy API; and
(b)
Notify a permit holder of the no operation zone through the MDS Policy API.
(3)
The Department shall ensure compliance with a no operation zone via testing of vehicles.
(4)
Within 72 hours of notification from the Department, a permit holder shall ensure their vehicles lose electric assistance or drive when a user rides into a no operation zone.
G.
Reduced Speed Zones.
(1)
The Department may establish a reduced speed zone on a public street in accordance with <cite data-path="14.02.01.16|G.|(2)">§G(2) of this regulation</cite>.
(2)
For a reduced speed zone established in accordance with <cite data-path="14.02.01.16">this regulation</cite>, the Department shall:
(a)
Identify the reduced speed zone in the MDS Policy API; and
(b)
Notify a permit holder of the reduced speed zone through the MDS Policy API.
(3)
The Department shall ensure compliance with a reduced speed zone via testing of vehicles.
(4)
Within 72 hours of notification from the Department, a permit holder shall ensure their vehicles are limited to eight miles per hour when a user rides into a reduced speed zone.
H.
A permit holder will be subject to the compliance inspection process in <cite data-path="14.02.01">this chapter</cite>, including the issuance of a warning or citation, if a violation of the provisions of <cite data-path="14.02.01.16">this regulation</cite> occurs.
Balt., Md., COBRA § 14.02.01.17 (2026)
Regulation .17 Seizure and Recovery.LinkCopy Citation
A.
The Department may seize a dockless vehicle if:
(1)
A permit holder fails to comply with a request to reposition or remove a vehicle in accordance with <cite data-path="14.02.01">this chapter</cite>; or
(2)
A dockless vehicle is in a location where it cannot be accessed by a permit holder.
B.
At the time of seizure, the Department shall:
(1)
Notify the permit holder in accordance with <cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-24">City Code Article 31, § 38-24</cite>;
(2)
Take pictures that indicate that the dockless vehicle is in violation of <cite data-path="14.02.01">this chapter</cite>;
(3)
Record the identification number of the dockless vehicle; and
(4)
Record the property number assigned to the dockless vehicle by the Towing Division.
C.
If the Department seizes a dockless vehicle, the Department shall charge a permit holder the following fees from the refundable performance bond:
(1)
$220.00, for five or fewer e- scooters seized at the same time;
(2)
$220.00, for more than five e-scooters seized at the same time, plus $44.00 per each e-scooter beyond the fifth;
(3)
$220.00, for three or fewer bicycles or e-bicycles seized at the same time; and
(4)
$220.00, for more than three bicycles or e-bicycles seized at the same time, plus $73.33 per bicycle or e-bicycle beyond the third.
D.
After the first 48 hours from the initial seizure date, the Department may charge a permit holder $15.00 for each 24-hour period for each group of:
(1)
Up to five e-scooters; or
(2)
Up to three bicycles or e-bicycles.
E.
Recovery of Seized Vehicles.
(1)
A permit holder shall retrieve a seized dockless vehicle from:
(2)
A permit holder shall notify the Towing Division of the person who will retrieve a seized vehicle by calling 410-396-9958 or 410-545-3417.
Balt., Md., COBRA § 14.02.01.18 (2026)
Regulation .18 User Education.LinkCopy Citation
A.
A permit holder shall provide in-app user education on proper operation of a dockless vehicle by:
(1)
Developing an in-app quiz for new users that:
(a)
Contains a minimum of five questions approved by the Department pertaining to:
(i)
Parking;
(ii)
Operations; or
(iii)
General safety; and
(b)
Requires a score of at least 80 percent before the third rental of a dockless vehicle by a user; and
(2)
Displaying a banner on the app home screen for up to one week of each month that highlights relevant information determined by the Department.
B.
A permit holder shall provide in-person user education on proper operation of a dockless vehicle by:
(1)
Hosting or participating in a minimum of one community event per deployment district annually to display safety information;
(2)
Attending a minimum of two community events annually between November and February; and
(3)
Attending a minimum of four public meetings upon invitation by the Department.
C.
Access to Additional User Data.
(1)
A permit holder may request that users “opt in” to provide access to:
(a)
Location services; or
(b)
Files on a user’s phone.
(2)
A permit holder may not prevent use of a dockless vehicle based on a user’s decision to grant or deny the data noted in <cite data-path="14.02.01.18|C.|(1)">§C(1) of this regulation</cite>.
D.
Departmental Survey.
Within 10 days of notification by the Department, a permit holder shall:
(1)
Include a clickable link to a yearly Department survey in the mobile application; and
(2)
Send the survey link to active users via e-mail.
Balt., Md., COBRA § 14.02.01.19 (2026)
Regulation .19 Special Events.LinkCopy Citation
A.
The Department may require a permit holder to provide staffing for special events expecting over 5,000 attendants in accordance with <cite data-path="14.02.01.19">this regulation</cite>.
B.
Upon notification from the Department, a permit holder shall be required to:
(1)
Designate an individual as a staff contact for event organizers;
(2)
For events expecting 5,000-9,999 people in attendance, provide up to two staffers for:
(a)
Up to one hour before the event;
(b)
During the event; and
(c)
Up to one hour after the conclusion of the event;
(3)
For events expecting over 10,000 people in attendance, provide up to three staffers for:
(a)
Up to one hour before the event;
(b)
During the event; and
(c)
Up to one hour after the conclusion of the event.
Balt., Md., COBRA § 14.02.01.20 (2026)
Regulation .20 Pricing.LinkCopy Citation
A.
Except as provided in <cite data-path="14.02.01.20|B.">§B of this regulation</cite>, a permit holder may not:
(1)
Set a higher price for the use of a dockless vehicle in a certain part of the City; or
(2)
Base pricing on a users’:
(a)
Inclusion in a federally protected class;
(b)
Genetic information; or
(c)
Citizenship.
B.
A permit holder may use a pricing variation to:
(1)
Incentivize proper operation of a dockless vehicle; or
(2)
Increase usership among underserved or low-income populations.
Balt., Md., COBRA § 14.02.01.21 (2026)
Regulation .21 Advertising and User Engagement.LinkCopy Citation
A.
A permit holder shall ensure that user engagement, including participation at required community events, is inclusive of:
(1)
Underserved populations; and
(2)
Low-income populations.
B.
A permit holder may not:
(1)
Use the name of a City agency, including the Department, without prior written approval;
(2)
Use the logo of a City agency, including the Department, without prior written approval’ and
(3)
Use the following to display third-party advertising:
(a)
A dockless vehicle;
(b)
A mobile application;
(c)
A kiosk;
(d)
Related physical infrastructure; or
(e)
Related web-based infrastructure.
Balt., Md., COBRA § 14.02.01.22 (2026)
Regulation .22 Data and Reporting.LinkCopy Citation
A.
GPS.
A permit holder shall ensure each dockless vehicle in their fleet is equipped with on-board GPS technology that does not rely on a user’s mobile device to obtain spatial information.
B.
Publicly Accessible Application Program Interface (API).
(1)
The permit holder shall provide a publicly accessible API.
(2)
The permit holder shall ensure that:
(a)
The public API is in a gbfs.json file format;
(b)
There are no “stations” in the parlance of GBFS, therefore both station_status.json and station_information.json should return an empty list;
(c)
FreE-Bicycle-status.json is required;
(d)
The field “vehicle_type” is added to the public API to describe the vehicle type, which may be:
(i)
“Bicycle”;
(ii)
“E-Bicycle”;
(iii)
“Scooter”; or
(iv)
Another type of specified permitted vehicle;
(e)
The Department is instructed on how to request authentication, if the public API requires authentication;
(f)
The location of the public API is provided to the Department; and
(g)
A smart phone-based application used to rent dockless vehicles is not considered the public API program interface required by <cite data-path="14.02.01.22|B.|(1)">§B(1) of this regulation</cite>.
(3)
The permit holder shall provide access to at least 50 requests per hour.
(4)
The Department shall post the location of the public API to the Department’s website.
C.
Mobility Data Specification (MDS) Policy API.
(1)
A permit holder shall:
(a)
Provide an MDS Policy API to the Department for a dockless vehicle trip in Baltimore City, including trips which:
(i)
Start in Baltimore City;
(ii)
End in Baltimore City; or
(iii)
Pass through Baltimore City;
(b)
Adhere to an MDS of 1.0 or newer, as set by the OMF;
(c)
Post the MDS Policy API on GitHub under the OMF Mobility Data specification;
(d)
Provide API endpoints, including:
(i)
A trip;
(ii)
A status change;
(iii)
A vehicle; and
(iv)
Real-time data;
(e)
Update or add endpoints to the MDS Policy API within:
(i)
Sixty days of notification from the Department for required published endpoints; and
(ii)
Ninety days for beta endpoints;
(f)
Change vehicle status to ‘Unknown’ if a vehicle is suspected to be:
(i)
Vandalized; or
(ii)
Missing for five or more days;
(g)
Ensure GPS data are transmitted from a dockless vehicle on-trip at a minimum frequency of once per 30 seconds;
(h)
Develop and maintain a working Wi-Fi connection to ingest MDS Policy API endpoints provided by the Department; and
(i)
Share current data through the MDS Policy API at least once per 24 hours.
(2)
The Department may require additional or updated endpoints published by OMF.
(3)
The Department may share the MDS Policy API with a third-party aggregator in accordance with <cite data-path="14.02.01.22|C.|(4)">§C(4) of this regulation</cite> for the purpose of:
(a)
Secure data storage; and
(b)
Analysis.
(4)
To share data with a third-party aggregator in accordance with <cite data-path="14.02.01.22|C.|(3)">§C(3) of this regulation</cite>, the Department shall enter into a memorandum of understanding with a third-party aggregator that:
(a)
Includes a provision governing the public release of data by a third-party aggregator; and
(b)
Is made available for a permit holder to review prior to being finalized.
D.
Reporting.
(1)
Time Sensitive Reports.
A permit holder shall report the following to the Department within 24 hours of notice:
(a)
Non-deployment request at a location by an adjacent property owner for verification by the Department;
(b)
A vehicle that is in a location where the permit holder cannot retrieve it, including a body of water; and
(c)
An issue that could affect public safety, including:
(i)
A report of criminal activity involving a dockless vehicle;
(ii)
A report of a crash involving a dockless vehicle;
(iii)
Contact with the Baltimore City Police Department;
(iv)
Contact with the Baltimore City Fire Department; or
(v)
A defect in equipment.
(2)
Monthly Reports.
A permit holder shall provide the Department with a monthly report by the tenth business day following the final day of the month which:
(a)
Uses the Department’s reporting template;
(b)
Is in Excel or CSV format;
(c)
Includes:
(i)
A report of each dockless vehicle lost due to theft or vandalism;
(ii)
Aggregated repair information on a permit holder’s dockless vehicle fleet by model of vehicle and type of repair;
(iii)
Each illegal parking request from the public;
(iv)
Each customer complaint received with response time noted;
(v)
A record of attendance at a City meeting;
(vi)
The number of people in attendance at a community event;
(vii)
A summary of marketing efforts;
(viii)
The number of users that took a trip on a dockless vehicle during the reporting period;
(ix)
The number of rides by low-income pass users during the reporting period;
(x)
The number of rides by cash users during the reporting period;
(xi)
The number of rides by non-smart phone users during the reporting period;
(xii)
The number of users provided for in <cite data-path="14.02.01.22|D.|(2)|(c)|(ix)">§(2)(c)(ix)</cite><cite data-path="14.02.01.22|D.|(2)|(c)|(xi)">-(xi)</cite> of <cite data-path="14.02.01.22">this regulation</cite> disaggregated by the type of plan and user home zip code;
(xiii)
The number of users of the low-income pass; and
(xiv)
An update to maintenance or operational plan.
(3)
Software Issues and Hacking Events.
A permit holder shall:
(a)
Notify the Department of a change to a data portal, including a response to a notification from the Department regarding:
(i)
A software glitch;
(ii)
An issue with hacking; or
(iii)
A data portal;
(b)
Acknowledge a notification from the Department about data and reporting within 24 hours;
(c)
Provide the Department with a plan for addressing an identified problem;
(d)
Provide a progress update to the Department once per 48 hours while the problem persists; and
(e)
Permanently fix an issues within 60 days of receiving notice of the problem.
(4)
User Privacy.
A permit holder shall protect user privacy by:
(a)
Complying with Payment Card Industry Data Security Standards for an electronic payment;
(b)
Notifying a user of a mobile device feature that the mobile application accesses; and
(c)
Not releasing personal user data to an entity:
(i)
Unrelated to operations; or
(ii)
That intends to use the data in a commercial sale to a third party.
Balt., Md., COBRA § 14.02.01.23 (2026)
Regulation .23 Security Bond.LinkCopy Citation
A.
Security Bond.
(1)
A permit holder shall provide a security for performance in the amount of $10,000 to the Department.
(2)
A permit holder shall ensure the security is in the form of:
(a)
A performance bond;
(b)
A refundable bond; or
(c)
Another security acceptable to the City.
B.
Rental Taxes.
(1)
A permit holder shall remit a rental tax to the Department of Finance twice annually in accordance with <cite data-path="14.02.01.23">this section</cite>.
(2)
January – June.
(a)
The Department shall invoice a permit holder by July 15 for the tax provided for in <cite data-path="14.02.01.23|B.|(2)|(b)|(i)">§B(2)(b)(i) of this regulation</cite>.
(b)
The permit holder shall:
(i)
Pay a tax of $0.10 per rental for dockless vehicle rentals between January 1 and June 30 annually; and
(ii)
Remit the tax within one calendar month after receiving an invoice from the Department.
(3)
July – December.
(a)
The Department shall invoice a permit holder by January 15 for the tax provided for in <cite data-path="14.02.01.23|B.|(3)|(b)|(i)">§B(3)(b)(i) of this regulation</cite>.
(b)
The permit holder shall:
(i)
Pay a tax of $0.10 per rental for dockless vehicle rentals between July 1 and December 31 annually; and
(ii)
Remit the tax within one calendar month after receiving an invoice from the Department.
(4)
A permit holder shall submit the following to the Department with each remitment of the annual tax:
(a)
A list of the total number of transactions during the reporting period; and
(b)
A digital copy of:
(i)
Payments during the reporting period; and
(ii)
Transactions during the reporting period.
Balt., Md., COBRA § 14.02.01.24 (2026)
Regulation .24 Procedures for Claims Against Security Bond.LinkCopy Citation
A.
Authorization to Draw Against Security.
The City may deduct from the security provided by a permit holder to recover incurred costs if:
(1)
A permit holder fails to remove from the public street a dockless vehicle that is:
(a)
Unsafe;
(b)
Unpermitted; or
(c)
Abandoned;
(2)
The Department seizes a dockless vehicles due to a violation of these regulations; or
(3)
A permit holder’s dockless vehicle causes damage to public property.
B.
Notification.
If the City intends to deduct from a permit holder’s security as provided in <cite data-path="14.02.01.24|A.">§A of this regulation</cite> the Department shall provide written notice to a permit holder prior to the deduction which states:
(1)
The reason for the deduction;
(2)
The amount of the deduction;
(3)
Information on submission of an objection to a deduction in accordance with <cite data-path="14.02.01.24|C.">§C of this regulation</cite>.
C.
Objection Submission.
A permit holder may submit an objection to a planned deduction to their security bond:
(1)
In writing; and
(2)
Within 7 days of the date of the written notice.
D.
Notification of Outcome.
(1)
The Department shall provide a permit holder with written notification of a decision rendered regarding their objection which:
(a)
Provides the reason for denying the objection; or
(b)
Confirms acceptance of the objection.
(2)
The Department shall send the notification to the permit holder three days before a deduction is made.
Balt., Md., COBRA § 14.02.01.25 (2026)
Regulation .25 Insurance.LinkCopy Citation
A.
Required Insurance.
A permit holder shall procure and maintain the coverage required in the permit agreement during:
(1)
The term of an initial dockless vehicle permit; or
(2)
The renewal of a dockless vehicle permit:
B.
A permit holder shall name The Mayor and City Council of Baltimore as an additional insured on the permit holder’s:
(1)
Commercial general liability insurance; and
(2)
Commercial automobile liability policies.
C.
A permit holder shall indemnify the Mayor and City Council of Baltimore from liability relating to:
(1)
The issuance of a dockless vehicle; or
(2)
The provision of services under a dockless vehicle permit.
D.
The City shall notify a permit holder before resolution or settlement of claims for which the City will seek indemnification.
Balt., Md., COBRA § 14.02.01.26 (2026)
Regulation .26 Citations.LinkCopy Citation
A.
The Department may:
(1)
Issue a citation under <cite data-doc="City of Baltimore, Md., Code" data-path="|1|§40-14">City Code Article 1, § 40-14</cite> to a permit holder found to be in violation of:
(a)
<cite data-path="14.02.01">This chapter</cite>; or
(b)
<cite data-doc="City of Baltimore, Md., Code" data-path="|31">City Code Article 31</cite>, Subtitle 38; or
(2)
Issue a citation under <cite data-doc="City of Baltimore, Md., Code" data-path="|1|§41-14">City Code Article 1, § 41-14</cite> to a permit holder found to be in violation of:
(a)
<cite data-path="14.02.01">This chapter</cite>; or
(b)
<cite data-doc="City of Baltimore, Md., Code" data-path="|31">City Code Article 31</cite>, Subtitle 38.
B.
Notification of Violation.
If a permit holder is found to be in violation during a compliance inspection, the Department shall:
(1)
Issue a first warning to the permit holder noting the violation;
(2)
Issue a second warning to a permit holder if the violation recurs within 60 days of the first warning; and
(3)
Issue a citation if the violation recurs within 60 days of the second warning.
C.
Abatement Period.
The Department shall:
(1)
Grant an abatement period to a permit holder to fix a violation; and
(2)
Issue an additional citation to a permit holder who commits an additional violation within 60 days of a granted abatement period.
D.
Appeals
(1)
A permit holder may appeal:
(a)
A civil citation to the District Court of Baltimore City; or
(b)
An environmental citation to Environmental Control Board.
(2)
For a citation issued in accordance with <cite data-path="14.02.01.26|D.|(1)|(b)">§ D(1)(b) of this regulation</cite>, a permit holder may appeal a decision rendered by the Environmental Control Board to the Circuit Court.
Subtitle 03 – Right of Way
Chapter 01 – Street Cuts
Balt., Md., COBRA § 14.03.01.01 (2026)
Regulation .01 Adoption, Applicability and Scope of Regulations.LinkCopy Citation
A.
These rules and regulations are promulgated by the Baltimore City Department of Transportation (“DOT”) pursuant to <cite data-doc="City of Baltimore, Md., Code" data-path="|26">City Code Article 26</cite>, Subtitle 15.
B.
These rules and regulations are in addition to all applicable laws found in <cite data-doc="City of Baltimore, Md., Code" data-path="|26">Baltimore City Code Article 26</cite>, other applicable sections of Baltimore City Code, and Maryland State Code.
C.
Scope of Regulations.
(1)
These rules and procedures are intended to ensure proper excavation of the public way;
(2)
These rules and procedures are intended to ensure complete restoration of the public way to match preexisting conditions; and
(3)
These rules and procedures are intended to ensure the proper use of the public way while work is ongoing.
Balt., Md., COBRA § 14.03.01.02 (2026)
Regulation .02 Definitions.LinkCopy Citation
A.
In <cite data-path="14.03.01">this chapter</cite>, the following terms have the meanings indicated.
B.
Terms Defined.
(1)
"ADA" means the federal Americans with Disabilities Act.
(2)
Bicycle Facility.
(a)
"Bicycle facility" means infrastructure to accommodate or encourage bicycling.
(b)
"Bicycle facility" includes a:
(i)
Bike lane;
(ii)
Bike parking facility;
(iii)
Storage facility; or
(iv)
Shared roadway specifically designated for bicycle use.
(3)
"Blanket permit" means an authorization that allows a person to undertake an action related to a street cut in the right-of-way without first applying for a street-cut permit for that location.
(4)
"Book of Standards" means the Baltimore City Department of Transportation Book of Standards, which is incorporated by reference into <cite data-path="14">this title</cite>.
(5)
"Crosswalk" means a pedestrian crossing delineated by:
(a)
A pavement marking; or
(b)
Signage.
(6)
"Decorative surface" means a non-functional, ADA-compliant element installed to aesthetically enhance or otherwise embellish a right-of-way.
(7)
"Demarcation materials" means a warning surface treatment applied to an affected roadway, including a:
(a)
Flex post;
(b)
Monolithic curb; or
(c)
Vertical barrier.
(8)
"Department" means the Baltimore City Department of Transportation.
(9)
"Directional boring" means a trenchless method of installing underground conduit and facilities with minimal impact along a prescribed underground path.
(10)
"Director" means the Director of Transportation or the Director's designee.
(11)
"Duration" means the time during which an activity required by a street cut occurs.
(12)
"Emergency" means a situation that arises as the result of an unforeseen event in which excavation is needed to abate imminent potential danger to life, health, or property.
(13)
"Excavation" has the meaning stated in <cite data-doc="City of Baltimore, Md., Code" data-path="|26|§15-1|(d)">City Code Article 26, §15-1(d)</cite>.
(14)
Facility.
(a)
"Facility" means utility infrastructure used for the provision of services.
(b)
"Facility" includes infrastructure for the transportation of:
(i)
Water;
(ii)
Energy; and
(iii)
Telecommunications.
(15)
"Landscaped area" means an outdoor space improved with living vegetation or synthetic material designed to be visually appealing.
(16)
"Pavement marking" means a device or material that is used on a road to demarcate lanes and conduct traffic.
(17)
"Pavement type" means a reference to the material from which a road is constructed, including:
(a)
Flexible material;
(b)
Rigid material; or
(c)
Composite material.
(18)
"Performance security" means a:
(a)
A performance bond;
(b)
An irrevocable letter of credit;
(c)
A cash deposit; or
(d)
A combination of the items noted in <cite data-path="14.03.01.02|B.|(18)|(a)">§B(18)(a)</cite><cite data-path="14.03.01.02|B.|(18)|(c)">-(c)</cite> of <cite data-path="14.03.01.02">this Regulation</cite>.
(19)
Person.
(a)
"Person" has the meaning stated in <cite data-doc="City of Baltimore, Md., Code" data-path="|general|§1-107">City Code General Provisions Article, §1-107</cite>.
(b)
"Person" includes a government entity that performs work on the right-of-way.
(20)
"Primary street" means an arterial road as defined by the Department.
(21)
"PROWAG" means the Federal Public Rights-of-Way Accessibility Guidelines.
(22)
Right-of-Way (ROW).
(a)
"Right-of-way" means an area intended to facilitate the movement of pedestrians that falls within the boundary lines of a public:
(i)
Street, including a curb;
(ii)
Alley;
(iii)
Sidewalk;
(iv)
Footway; or
(v)
Property otherwise owned or controlled by the City of Baltimore.
(b)
"Right-of-way" includes a public way as it is referred to in <cite data-doc="City of Baltimore, Md., Code" data-path="|31">Article 31 of the Baltimore City Code</cite>.
(23)
"Right-of-Way (ROW) permit" means a permit, including a street-cut permit, issued by the Department that allows temporary use of the public right-of-way to perform work related to facilities.
(24)
"Separate offense" means each day that a violation continues.
(25)
"Stop work order" means the issuance of an administrative order by the Department to cease work at an excavation site due to a violation of:
(a)
The Baltimore City Code;
(b)
A regulation adopted under the Code of Baltimore Regulations Annotated; or
(c)
A condition of the permit until the violation is abated.
(26)
"Street cut" means work which involves excavating a road.
(27)
"Street-cuts permit" means a permit required by or issued under <cite data-doc="City of Baltimore, Md., Code" data-path="|26|15">subtitle 15, of Article 26 of the Baltimore City Code</cite>.
(28)
"Traffic Control Plan (TCP)" means an arrangement intended to preserve safe pedestrian and vehicular traffic to the greatest extent possible for the duration of work in a road.
(29)
"TMC" means the Department's Transportation Management Center.
(30)
"Traffic control channelization device" means a device used to:
(a)
Warn roadway users of conditions created by work activities in or near the road; and
(b)
Guide roadway users for the duration of the work.
(31)
"Unsafe condition" means an unsatisfactory physical condition existing at a street cut location that has the potential to result in injury, death, or property damage if not corrected.
(32)
"Utility" means a person that owns or operates facilities used to provide a transmittable service to customers, including:
(a)
Electrical service;
(b)
Gas service;
(c)
Water service;
(d)
Sewer service, including stormwater drainage; or
(e)
Telecommunication networks.
Balt., Md., COBRA § 14.03.01.03 (2026)
Regulation .03 Exceptions to Street-cuts Permits.LinkCopy Citation
A.
Unless the work qualifies as an emergency excavation under <cite data-doc="City of Baltimore, Md., Code" data-path="|26">City Code Article 26</cite>, §15-13, no person, including a City agency, may excavate in a Public Way without first obtaining a Street-cuts permit.
B.
Directional Drilling is not permitted within the City Right-of-Way
(1)
for electrical utilities and facilities,
(2)
for other utilities and facilities, including sanitary and gas lines, without prior written approval from the Director.
Balt., Md., COBRA § 14.03.01.04 (2026)
Regulation .04 Applications for a Street-cuts Permit.LinkCopy Citation
A.
An application for a Street-cuts Permit
(1)
shall include the following information:
(a)
applicant name and contact information;
(b)
contractor name and contact information;
(c)
work location and address;
(d)
description of proposed work;
(e)
information for the Street-cut including:
(i)
requested start date and time;
(ii)
requested end date and time;
(iii)
street lane, bicycle facility or sidewalk closures;
(iv)
use of steel plates;
(v)
length, depth and width of any trench;
(vi)
work which will occur on weekends;
(vii)
work which will occur at night;
(viii)
a Traffic Control Plan (“TCP”), if required;
(ix)
estimated number of Street-cuts; and
(x)
drawing showing the location, type, size, and TCP.
(2)
shall provide evidence of Performance Security in an amount specified on the DOT website at transportation.baltimorecity.gov/
(a)
A single Performance Security may be used for multiple permits by the same contractor as allowed by the Department.
(b)
Contractors who fail to maintain a minimum Performance Security, as determined by the Director, shall be prohibited from working in the Public Way, unless specifically authorized by the Director.
(3)
shall provide a point of contact in case of emergency that includes:
(a)
a name, email address, and phone number;
(b)
someone who is available on a 24-hour basis.
B.
An applicant shall be required to submit the following for a permit:
(1)
Drawings or acceptable sketches which shall include or identify:
(a)
the size and location of each Street-Cut;
(b)
pavement restoration details;
(c)
pavement type; and
(d)
work that impacts any traffic on one of the following roadway classes, as defined by Roadway Functional Classification map located at https://transportation.baltimorecity.gov:
(i)
Collector,
(ii)
Minor Arterial,
(iii)
Other Principal Arterial,
(iv)
Freeway and Expressway, or
(v)
Interstate Principal Arterial.
(e)
a final pavement marking plan consistent with the applicable requirements for pavement marking as set forth in the Book of Standards issued by the Department of Transportation and the Department of Public Works (“DPW”) (the “Green Book”), including:
(i)
bicycle facilities;
(ii)
parking facilities;
(iii)
crosswalks; and
(iv)
other pedestrian pavement marking.
(2)
Within 5 days of application submission, an applicant shall submit a color photograph including:
(a)
the current pavement condition of the right-of-way;
(b)
the date; and
(c)
a time stamp.
C.
An applicant is required to submit a Traffic Control Plan (“TCP”).
(1)
Traffic Control Plans are required when any of the following conditions exist:
(a)
sidewalk closure or detour;
(b)
bicycle facility closure or detour; or
(c)
roadway closure or detour on a roadway.
(2)
All lanes in the roadway shall be treated as travel lanes, unless clearly marked as a parking lane by a solid white line.
(3)
A TCP shall include:
(a)
a site plan covering 2 to 3 blocks in each direction from the construction site;
(b)
the installation and location of advanced warning signs which include:
(i)
for any roadway lane closure, a minimum of the following three advanced warning signs installed at least 300 feet apart, unless a request to change the spacing is submitted for prior approval:
(A)
Road Work Ahead,
(B)
Right/Left/Center Lane Closed Ahead, and
(C)
a transition sign for the lane being closed.
(ii)
for a parking lane closure, no arrow board is required; however, the following three advanced warning signs shall be installed at least 300 feet apart:
(A)
Road Work Ahead,
(B)
Curb Lane Closed Ahead, and
(C)
a transition sign for the lane being closed.
(iii)
for the closure of multiple roadway lanes
(A)
an arrow board is required for each lane being closed, and
(B)
the placement of advanced warning signs as required by the Manual on Uniform Traffic Control Devices (“MUTCD”).
(c)
a flagging operation and multiple lane closure for utility cuts and work areas that extend more than 10 feet from the curb lane;
(d)
when a flagging operation is provided for by the applicant or required by the Department:
(i)
all directions of travel must be controlled by a flagger;
(ii)
it must be noted on your application when working at a signalized intersection; and
(iii)
advanced warning signage must include Flagman Ahead signs;
(e)
road closure detours shall
(i)
be clearly signed to direct traffic around the road closure and reestablish travel back to the road after the closure;
(ii)
include the following advanced warning signs:
(A)
Road Closed Ahead,
(B)
Detour ahead, and
(C)
Road Closed;
(iii)
include a physical barrier at the actual road closure for all directions of travel;
(f)
roadway classification;
(g)
a note to contact TMC each work morning prior to start of work and each afternoon at end of work;
(h)
all affected bicycle and pedestrian facilities and the traffic control for each;
(i)
traffic control channelization devices to be used;
(j)
location of all steel plates in the area affected;
(k)
information as to any pedestrian detours which shall:
(i)
maintain a minimum 4 foot ADA accessible path for pedestrians when work is conducted on a sidewalk:
(A)
the ADA accessible pathway may be located in a parking lane, and
(B)
shall have an appropriate physical barrier between vehicles and pedestrians;
(ii)
if a sidewalk is to be closed, the closure must be at the nearest intersection crosswalk with signs directing pedestrians across the street, and
(A)
the sidewalk on the opposite side of the street must be ADA accessible, and
(B)
must include a ramp and 4-foot pedestrian pathway;
(l)
information as to any bicycle facility detours which shall provide for or adhere to the following:
(i)
lane and road closures include lane transitions for bicyclists, and
(ii)
if the bicycle lane cannot be maintained, an explanation of why it cannot be maintained and an alternate route for the bicyclist; and
(iii)
if a bicyclist must use the sidewalk as an alternate route, warning signage must include:
(A)
Bike Lane Closure, and
(B)
Dismount and Walk Bicycle on Sidewalk;
(m)
any other TCP control needed for unique locations or work;
(n)
for Emergency work performed under a blanket permit, a trained and certified emergency traffic manager shall be on-site at all times until the contractor has provided the Department with a TCP which is approved.
(4)
The following conditions, if not immediately corrected, constitute a violation of the Street-cuts permit and may result in a fine or issuance of a Stop work order:
(a)
failure to obtain an approved TCP when required to do so,
(b)
failure to maintain at the work site a copy of the approved TCP for inspection, or
(c)
failure to adhere to the conditions of the TCP.
(5)
No equipment, materials, or other construction matter is permitted to be staged or stored, in bicycle facilities, on sidewalks, or within other non-motorized travel facilities unless the contractor obtains
(a)
prior written approval, and
(b)
any additional required permits.
D.
Applications for a Street-cuts permit are
(1)
processed through the DOT Right-of-Way Permits Section which is located at 401 East Fayette Street, Lower Level, Baltimore, Maryland 21202;
(2)
on the DOT website under Quick Forms; and
(3)
submitted by email with all required information to <u>row.permit.documents@baltimorecity.gov</u>.
E.
The applicant listed on a Temporary Use Right-of-Way Permit
(1)
is responsible for all work performed under the permit, including but not limited to any subcontractor; and
(2)
will receive any notice from the Department concerning the work.
Balt., Md., COBRA § 14.03.01.05 (2026)
Regulation .05 Issuance of a Street-cuts Permit.LinkCopy Citation
A.
A Street-cuts permit shall be issued upon
(1)
the provision of the required information,
(2)
receipt by DOT of the required permit fees,
(3)
payment of the required Performance Security, and
(4)
correction of outstanding or unresolved deficiencies with existing permits.
B.
It is the contractor’s responsibility to
(1)
schedule the work, and
(2)
notify DOT of completion of the work
(a)
with sufficient time for the work to be inspected and approved prior to the expiration of the permit; and
(b)
sufficient time constitutes notice to DOT a minimum of 48 hours prior to the expiration date of the permit.
C.
Notice to DOT of an Emergency Excavation shall be made by
(1)
calling the Street-cuts Section, at 410-396-2889, between the hours of 7 am and 4:30 pm Monday-Friday;
(2)
calling the TMC, at 443-984-2189, 24 hours a day; or
(3)
email to <u>streetcuts@baltimorecity.gov</u>, 24 hours a day.
D.
A Blanket Permit shall be issued to a utility provider or the Department of Public Works (“DPW”) for Emergency Excavations only.
(1)
A Utility provider with a Blanket Permit shall complete a permit application within
(a)
18 hours of beginning the emergency excavation, or
(b)
the next business day.
(2)
Emergency Excavations shall be inspected by DOT Street-cuts Section prior to backfilling of the excavation.
(a)
The utility provider shall notify DOT Street-cuts Section that the excavation is ready for inspection.
(b)
Notice shall be made as set forth in <cite data-path="14.03.01.05|C.">Regulation .05.C</cite>.
E.
A Street-cut permit fee shall be assessed in accordance with a fee schedule, established by the Director and approved by the Board of Estimates (“BOE”).
(1)
Street-cut permit fees are in addition to the Temporary Use of the Right-of-Way Permit fee.
(2)
Current Street-cut permit fees are posted on the DOT website at transportation.baltimore.gov/quick-forms.
(3)
Additional fees may be assessed as provided in these regulations and allowed by law.
Balt., Md., COBRA § 14.03.01.06 (2026)
Regulation .06 Performance Schedule and Standards.LinkCopy Citation
A.
Any person doing excavation work shall:
(1)
always maintain the Street-cut permit on site, and
(2)
exhibit the permit when requested to do so by the Department.
B.
If an excavation is interrupted by an agency of Baltimore City, the permittee shall
(1)
notify DOT Street-cuts Section immediately, and provide the following information:
(a)
permit number,
(b)
location of excavation,
(c)
City agency involved in the interruption,
(d)
City agency contact person,
(e)
City agency work order number,
(f)
expected length of the interruption, and
(g)
procedures taken to secure the site.
(2)
Upon verification of an interruption caused by an agency of Baltimore City, the Street-cuts Section shall notify the permittee of
(a)
additional time allowed under the permit to account for the interruption, and
(b)
any additional requirements pertaining to the permit.
C.
Prior to being given permission to disturb existing bicycle facilities, an applicant for a Street-cut permit shall provide proof that no alternative to such action is available. D. When restoring an open Street-cut a permittee must:
(1)
comply with all conditions and requirements of the permit;
(2)
conform with current rules, regulations, and standards of Baltimore City; and
(3)
ensure restoration matches preexisting conditions.
D.
Prior to beginning work in any roadway, the permittee shall
(1)
meet with the Traffic Division to review and develop a pavement marking plan for the affected roadway; and
(2)
where the affected roadway has bicycle facilities, meet with the Traffic Division and the Bicycle Planning Section to review and develop
(a)
a pavement marking plan, and
(b)
demarcation materials.
E.
When an Order to Remove or Relocate a Pole is issued by the Department it shall:
(1)
be in writing and signed by the Director or the Director’s designee; and contain the following:
(a)
name of the permit holder,
(b)
facts that support issuing a pole removal or relocation order, and
(c)
the location of the pole.
(2)
The Order shall be served by:
(a)
delivery to any employee, agent, contractor, or sub-contractor of the permit holder on site;
(b)
mailing or emailing a copy of the order to the address on file for the permit holder; or
(c)
sending a facsimile to the permit holder to the fax number on file for the permit holder.
(3)
The location of the pole shall not create non-compliance with the ADA.
Balt., Md., COBRA § 14.03.01.07 (2026)
Regulation .07 Pavement Repairs and Restoration.LinkCopy Citation
A.
Regardless of cut type, repairs will be done in accordance with Baltimore City DOT Standards.
(1)
The Book of Standards is located on DOT’s website at:
<u>https://transportation.baltimorecity.gov/transportation/bookofstandards</u>.
(2)
The DOT Street Cuts Section has the authority to increase the requirements of pavement restoration beyond minimum standards shown in the standard details based on
(a)
site conditions, and
(b)
Street-cuts permit application information.
B.
Applicants and contractors shall adhere to the Street-cuts policies contained in these regulations; however,
(1)
the Director has the discretion to permit exceptions to this policy under special circumstances; and
(2)
such exceptions shall be approved by the Director in writing.
C.
The following are additional requirements for pavement repairs:
(1)
when a utility cut is within 5 feet of a new or preexisting cut, both cuts shall be encapsulated into a single patch
(a)
by milling away the intervening existing surface to allow for a single surface patch when one cut is preexisting and one cut is new; or
(b)
by combining the cuts into a single full-depth patch when both cuts are new; and
(c)
combined patches are subject to applicable Baltimore City DOT Standards.
(2)
During resurfacing, the longitudinal pavement joints shall be constructed within 6 inches of the lane lines and not within the travel lanes.
(3)
If more than 50 percent of an asphalt or asphalt overlaid (composite) roadway is disturbed during longitudinal or transverse trenching, the entire block shall be milled and resurfaced
(a)
from curb to curb, or
(b)
to the median curb, if applicable.
(4)
The entire intersection must be milled and resurfaced if
(a)
an asphalt or asphalt overlaid (composite) intersection is trenched diagonally, or
(b)
more than 50 percent of the intersection is disturbed during longitudinal and/or transverse trenching.
(5)
All utility cuts must be backfilled and compacted in accordance with
(a)
Baltimore City Standards outlined in Article 32.01.10 of the City of Baltimore Department of Public Works Specifications for Materials, Highways, Bridges, Utilities, and Incidental Structures (the “Green Book’);
(b)
the standards are found at <u>https://generalservices.baltimorecity.gov/gs-majorprojects/greenbook</u>.
(6)
Suitable fill material must be placed in 6-inch lifts and tamped with a mechanical tamper; and
(a)
material one foot below subgrade must be compacted to 92 percent,
(b)
material in the top one foot must be compacted to 97percent; and
(c)
compaction of all material must be per the Modified Proctor ASTM D1557 (“AASHTO T180”).
(i)
In lieu of borrow, CR-6 or excavation fills, #57 stone may be used; and
(ii)
it must be placed in no greater than one-foot lifts and tamped with a mechanical tamper.
(7)
Crusher Run Aggregate (“CR-6”) or Graded Aggregate Base (“GAB”) must be used for the proposed roadway paving sub-base, and
(a)
must meet the requirements of Article 32 11 23.10 of the Green Book; and
(b)
Recycled Concrete (“RC-6”) may not be used for the sub-base material.
(8)
The Contractor must supply compaction testing results for
(a)
any paving patch greater than 1,000 square feet in area, and
(b)
any trench longer than 100 feet.
(9)
A permittee must submit to the Department, at streetcuts@baltimorecity.gov, within 24 hours of the compaction:
(a)
a copy of the compaction test results;
(b)
relevant location;
(c)
work date(s), and
(d)
designated permit number
D.
Final pavement restorations must include:
(1)
removal of temporary backfill;
(2)
properly squaring off all Street-cuts to the bottom of the sub-base;
(3)
proper permanent backfills and compaction as specified in <cite data-path="14.03.01.07|C.|(5)">Regulation .07.C(5)</cite>;
(4)
permanent street restoration as specified in
(a)
these Street-cuts regulations;
(b)
the City of Baltimore DOT Standards; and
(c)
the DPW Green Book;
(5)
the patch must be installed so that it will remain flush with the surrounding pavement for 1 year after the work has been completed, inspected, and approved.
E.
For utility upgrades and repairs that are performed in advance of a scheduled DOT contract, DOT may, at its sole discretion, allow the permit holder to provide temporary pavement repairs
(1)
based upon the timing of the work in relation to the DOT contract schedule and the extent of the proposed trench excavations necessary for the utility work;
(2)
the type of temporary repair to be allowed will be decided by the Department on a case-by-case basis; and
(3)
the temporary pavement trench repair must conform to the current backfill procedures.
F.
If the permittee uses steel plates to secure the public way during construction, they shall conform to:
(1)
the Green Book; and
(2)
Baltimore City DOT Book of Standards.
G.
Crosswalks.
In executing a street cut that disturbs a crosswalk, a person shall ensure that:
(1)
The crosswalk is restored in accordance with the "Continental Crosswalk" style standards outlined in the Book of Standards;
(2)
Notwithstanding the provisions of <cite data-path="14.03.01.07|G.|(1)">§G(1) of this regulation</cite>, the crosswalk is restored with a decorative surface that:
(a)
Matches the characteristics of a preexisting decorative surface; and
(b)
Is in accordance with standards provided by the Department when applicable;
(3)
Each portion of a disturbed crosswalk is restored, including a portion of a disturbed crosswalk that is:
(a)
Faded;
(b)
Missing; or
(c)
Otherwise noncompliant with an expected standard.
(4)
The crosswalk is restored from curb to curb, unless the undisturbed portion of the crosswalk is:
(a)
Compliant with the Book of Standards; and
(b)
In good condition, meaning it is:
(i)
In new or like-new condition;
(ii)
Free of fading;
(iii)
Free of peeling; and
(iv)
Not otherwise defective in a way that reduces its visibility;
(5)
Notwithstanding the provisions of <cite data-path="14.03.01.07|G.|(4)">§G(4) of this regulation</cite>, the crosswalk is restored from curb to curb when trenching is done lengthwise through the crosswalk; and
(6)
When required by the Department to resurface an intersection in its entirety, each abutting crosswalk is restored as required by <cite data-path="14.03.01.07|G.|(4)">§G(4) of this regulation</cite>.
Balt., Md., COBRA § 14.03.01.08 (2026)
Regulation .08 Work by Utilities in Advance of a Scheduled DOT Contract.LinkCopy Citation
A.
If a public or private utility owns a facility, or is planning to perform work, in a right-of- way that is scheduled to be repaved by the Department of Transportation, the utility shall:
(1)
notify the Department of any planned utility work scheduled for the current fiscal year or the next 2 fiscal years within the limits of the Department’s scheduled repaving work;
(2)
coordinate such utility work with the Department;
(3)
investigate, test, repair and upgrade the utility’s existing facilities so that future maintenance or replacement will not be required for a minimum of 5 years after the right-of-way is repaved; and
(4)
immediately notify the Department of any emergency work that takes place in a rightof-way scheduled by the Department to be repaved during the current calendar year.
B.
When DOT submits plans for its proposed work to all utilities several times during the design process, each utility shall consider and inform the Department of all the improvements it will need to make based on:
(1)
uploads from DOT which will include scheduled roadways and repaving limits to the utility coordination platforms/software;
(2)
communication about scheduled roadways at the monthly utility coordination meetings held at DOT; and
(3)
any other communications between the Department and utility providers regarding scheduled roadway repaving locations.
C.
When properly advised by a utility pursuant to <cite data-path="14.03.01.08|B.">Regulation .08.B</cite>, DOT will consider delaying the advertisement, or altering the contract, to allow utility work to be completed first.
Balt., Md., COBRA § 14.03.01.09 (2026)
Regulation .09 Violations and Fines.LinkCopy Citation
A.
The following fineable offenses are for work being performed in a Public Way:
<table>
<thead>
<tr>
<th>Violation</th>
<th>Occurrence</th>
</tr>
</thead>
<tbody>
<tr>
<td>Failure to obtain a Street Cuts permit prior to beginning work or, in an emergency where permit cannot be obtained ahead of work, within 18 hours of an emergency street-cut (Absence of a permit at jobsite)</td>
<td>Daily</td>
</tr>
<tr>
<td>Unsafe job site, TCP setup, or other unsafe condition</td>
<td>Daily</td>
</tr>
<tr>
<td>Not reporting intended work forty-eight (48) hours prior and/or steel plate placement as required on permit</td>
<td>Daily</td>
</tr>
<tr>
<td>Compaction testing not performed</td>
<td>Daily</td>
</tr>
<tr>
<td>Non-compliant installation of steel plates</td>
<td>Daily</td>
</tr>
<tr>
<td>Not clearing away construction debris</td>
<td>Daily</td>
</tr>
<tr>
<td>Not providing for temporary patching or plating until full restoration is completed</td>
<td>Daily</td>
</tr>
<tr>
<td>Patch not flush with the surrounding pavement</td>
<td>Daily</td>
</tr>
<tr>
<td>Absence of identification markings (if faded, they must be refreshed daily)</td>
<td>Daily</td>
</tr>
<tr>
<td>Blocked travel lanes before 9:00 AM or after 3:00 PM on weekdays without prior written DOT authorization</td>
<td>Daily</td>
</tr>
<tr>
<td>Incorrect traffic control (TCP) setup and/or absence of the approved TCP in site</td>
<td>Daily</td>
</tr>
<tr>
<td>Use of unapproved materials</td>
<td>Daily</td>
</tr>
<tr>
<td>Failure to construct to Baltimore City standards</td>
<td>Daily</td>
</tr>
<tr>
<td>Final striping not completed within 15 calendar days of permanent restoration</td>
<td>Daily</td>
</tr>
<tr>
<td>Street Cuts not fully restored to be permanent within one hundred twenty (120) days from start of work in the public way</td>
<td>
<p>Daily (beginning day 121 and each day until permanent restoration is</p>
<p>complete)</p>
</td>
</tr>
<tr>
<td>Steel plates extending beyond thirty (30) days in the public right-of-way without an approved extension</td>
<td>Daily (beginning day 31 and each day until steel plating is removed and replaced with temporary patching or until full and permanent restoration is complete)</td>
</tr>
<tr>
<td>Permanent patch failure within the one-year warranty period if not corrected with thirty (30) days of notice</td>
<td>
<p>Daily (beginning day 31 and each day</p>
<p>until permanent restoration is</p>
<p>complete)</p>
</td>
</tr>
</tbody>
</table>
B.
A schedule of fines as previously approved by the BOE for the violations set forth in <cite data-path="14.03.01.09|A.">Regulation .09.A</cite> are
(1)
posted on the DOT website at transportation.baltimorecity.gov; and
(2)
subject to amendment by the Director with the approval of the Board of Estimates.
C.
Unless specifically provided, fines may be imposed by DOT without provision of a Pre-Fine Notice.
(1)
The Street-cuts Section is not required to issue a Pre-Fine Notice for any violation observed during inspection operations; and
(2)
DOT will not issue a Pre-Fine Notice for failure to complete permanent restoration within 120 days.
D.
In the case of failure to complete full restoration of the Public Way within 120 days of the start of work;
(1)
the total fine amount imposed will be equal to:
(a)
the number of days past 120 days until the restoration is completed (b) times the daily fine amount per violation.
(2)
The following time periods are not included in the calculation of the 120-day period within which full restoration must be completed:
(a)
the winter season, which is defined generally as the period from November 15 to March 15, or
(b)
when paving plants are closed as determined by the Department.
(3)
Any permit holder that is not able to complete full restoration within the 120-day period must
(a)
make a written request for an extension to the Street-cuts Section prior to the expiration of the 120-day period, and
(b)
demonstrate good cause for the extension.
(4)
The Street-cuts Section may then grant written extension for a reasonable time to the permit holder.
(5)
When no request for an extension of the 120-day period has been granted:
(a)
Street-cuts not completed within the 120-day restoration period are required to apply for a new permit;
(b)
the new permit start date is the expiration date of the previous permit;
(c)
the new permit expiration date is the expected date that permanent restoration will be complete for the street cut; and
(d)
the permit fee owed to the City is for the entire timeframe.
(e)
these requirements are in addition to any fines imposed.
E.
Steel plates may not extend beyond 30 days in the public way unless
(1)
an extension has been granted by the Department; and
(2)
the extension notification can be found at <u>https://transportation.baltimorecity.gov/quick-forms.</u>
F.
Permanent patch failure within the 1-year warranty period will be given a 30-day notice for repairs:
(1)
a new permit is required for the repair;
(2)
beyond the 30-day notice period, a fine will be imposed until such time as the patch is repaired and approved; and
(3)
an additional 1-year warranty will take effect starting from the day of final approval of the repair.
G.
The following unsafe conditions existing at a Street-cut may result in a fine:
(1)
utility trench, permanent patch within the warranty phase, or utility cut where paving restoration is left:
(a)
1 inch or more below existing grade, or
(b)
2 inches or more above existing grade;
(2)
Utility trench, permanent patch within the warranty phase, or utility cut on roadways with bicycle facilities where paving restoration is left:
(a)
¼ inch or more below existing grade, or
(b)
½ inch or more above existing grade;
(3)
debris left onsite by a contractor for 24 hours or more;
(4)
wooden boards placed over utility cut;
(5)
fenced site where the fence has collapsed;
(6)
an exposed excavation left unattended;
(7)
blocking of a bicycle facility by equipment, debris, vehicles, signs or other obstruction;
(8)
blocking a pedestrian walkway, crosswalk, curb ramp or other facility by equipment, debris, vehicles, signs or other obstruction; and
(9)
any circumstance where the contractor has left work in a state considered to be a substantial threat to public safety.
Balt., Md., COBRA § 14.03.01.10 (2026)
Regulation .10 Stop Work Orders.LinkCopy Citation
A.
The Director or the Director’s designee may issue a stop work order for work conducted on public right-of-way when it is determined that a violation of any of the following has occurred:
(1)
State law or code;
(2)
City Code
(3)
DOT regulation; or
(4)
the requirements imposed by a permit issued for the project.
B.
The Director or the Director’s designee may also issue a stop work order for any of the following:
(1)
a project that endangers public health or safety; or
(2)
failing to abate a violation in a timely manner for which a notice was issued.
C.
A stop work order shall
(1)
be in writing;
(2)
signed by the Director or the Director’s designee; and
(3)
contain the following:
(a)
name of the violator;
(b)
facts that support issuing a stop work order;
(c)
the location at which the violation occurred;
(d)
reference to the specific provision of law, regulation, or permit that has been violated; and
(e)
the remedial measures required for to abate the violation.
D.
The Department must serve a stop work order by
(1)
delivering it to any employee, agent, contractor, or sub-contractor of the permit holder on site;
(2)
mailing or emailing a copy of the order to the address on file for the permit holder; or
(3)
sending a facsimile to the permit holder to the fax number on file for the permit holder.
E.
A stop work order becomes effective as soon as it is served via one of the methods in Regulation 10.D., regardless of whether delivery is accepted.
F.
Upon the issuance of a stop work order the violator shall
(1)
immediately cease all work as specified in the order and comply with all directives contained in the order to abate the violation, and
(2)
contact the Street-cuts Section to request on on-site inspection for correction of the violation
(a)
by phone 410-396-5889 or
(b)
email <u>streetcuts@baltimorecity.gov</u>.
G.
A stop work order remains in effect until the Department notifies the permit holder in writing of its termination or modification.
H.
Termination of the stop work order does not preclude separate enforcement action by the Department relating to the present or a subsequent violation.
Balt., Md., COBRA § 14.03.01.11 (2026)
Regulation .11 Administrative Hearings.LinkCopy Citation
A.
Any person aggrieved by a decision or action of the Department under <cite data-doc="City of Baltimore, Md., Code" data-path="|26">City Code Article 26</cite>, subtitle 15, may appeal the decision or action to the Director.
B.
A person shall be notified in writing of an appealable decision or action taken by the Department, and the notice shall
(1)
be sent
(a)
via first class mail, and
(b)
by email or facsimile, to the email address or facsimile number on record for the aggrieved person.
(2)
Email notification is effective as of the date of transmission by the Department.
C.
An appeal of a decision or action shall be filed by requesting a hearing
(1)
within 10 days of the date of notification, or the date of receipt of the notice, whichever occurs first,
(2)
in writing and sent to the DOT Street-cuts Section by
(a)
first class mail to: Baltimore City Department of Transportation, Street Cuts Section, 520 Fallsway, Baltimore, MD 21202; and
(b)
by email to <u>streetcuts@baltimorecity.gov</u>.
(3)
If no timely request for a hearing is filed, the aggrieved person shall be deemed to have waived the right to an administrative hearing.
D.
The hearing shall be scheduled within a reasonable time after a request for a hearing is received, and
(1)
DOT shall send a Hearing Notice to the aggrieved person by
(a)
first class mail and
(b)
electronic mail requesting receipt confirmation;
(2)
the Hearing Notice shall
(a)
set the date, time and location of the hearing,
(b)
designate the Hearing Officer; and
(c)
describe the purpose and nature of the hearing
(d)
set forth any rules or procedures that may be required by the Hearing Officer.
E.
A Hearing Officer
(1)
may be any individual member of the DOT designated as such by the Director of the DOT; but
(2)
shall not be the DOT employee who made the decision or took the action being appealed; and
(3)
shall have discretion to set reasonable limits for
(a)
the time for the aggrieved party to present its case;
(b)
the time for the agency response;
(c)
the time for, and any limits on, cross examination; and (d) the time for closing arguments.
(4)
may shorten or extend any time limits designated in these regulations
(a)
at his discretion, and
(b)
for good cause shown.
F.
Not later than 5 days after the date of the Hearing Notice, the aggrieved party shall advise DOT in writing, via first class mail and electronic mail requesting receipt confirmation,
(1)
if it will be represented by counsel and identify its counsel; or
(2)
if the aggrieved party will not be represented by counsel, designate an individual to present the aggrieved party’s case at the hearing.
G.
Formal evidence rules and trial procedures shall not apply, and the Hearing Officer
(1)
may admit and give effect to evidence which possesses probative value commonly accepted by reasonable and prudent persons in the conduct of their affairs;
(2)
may exclude incompetent, irrelevant, immaterial, and unduly repetitious evidence;
(3)
may take judicial notice of general, technical, and scientific facts; and
(4)
shall give effect to the rules of privilege recognized by law.
H.
All evidence, including records and documents, in the possession of DOT, the involved
City agency or the City of Baltimore which the Hearing Officer desires to utilize may
(1)
be made a part of the record in the case, and
(2)
be received in the form of copies, excerpts, or by incorporation by reference.
I.
The hearing shall
(1)
proceed as follows:
(a)
the Hearing Officer shall begin the hearing with a statement concerning the purpose of the hearing and the procedures that will be followed.
(b)
each party may present its case by narrative or by witnesses.
(c)
cross-examination of any witness shall be permitted; however, the parties will not be permitted to argue or engage in debate. The Hearing Officer may reasonably limit or terminate cross examination at any time.
(d)
the Hearing Officer may question any witness or party at any time.
(e)
each party may present its final arguments and summarize its position.
(f)
each party shall have the right to make any additional statements before the hearing it terminated.
(g)
at the discretion of the Hearing officer, the hearing may be adjourned to another date, continued, and postponed.
(2)
Notwithstanding the procedures in <cite data-path="14.03.01.11|I.">Regulation .11.I</cite>., the Hearing officer may, in his discretion,
(a)
decide the order and manner in which testimony and evidence is to be presented and
(b)
make changes to the hearing procedure.
J.
Following the hearing, the Hearing Officer shall
(1)
make every attempt to render a decision within 30 days from the conclusion of the hearing,
(2)
base the decision on the facts and evidence introduced into the record,
(3)
prepare a decision of each hearing which contains the following information:
(a)
date of the hearing,
(b)
name of the Hearing Officer;
(c)
name of the aggrieved party;
(d)
names, titles and affiliations of persons in attendance;
(e)
the purpose and nature of the hearing;
(f)
brief description of documents, testimony and data presented;
(g)
findings and conclusions of the Hearing Officer regarding the action or decision being appealed; and
(h)
the decision of the Hearing officer.
(4)
send a copy of the decision to the aggrieved party, or his attorney of record; by
(a)
first class mail, or
(b)
when provided, by email.
K.
Upon the direction of the Hearing Officer or the aggrieved party, a record of the proceedings may be made.
(1)
The record is adequate if in the form of a tape recording.
(2)
The aggrieved party shall have access to the tape-recording during City business hours, and may have a transcript made at its expense.
(a)
The City shall designate the transcriber, and
(b)
the cost of the transcript preparation shall be paid before the transcript is prepared.
L.
Within ten 10 days of DOT’s service of the final decision of the Hearing Officer, the aggrieved party may submit a written request for a review of the decision of the Hearing Officer,
(1)
which shall be sent by
(a)
first class mail to: Baltimore City Department of Transportation, Street Cuts Section, 520 Fallsway, Baltimore, MD 21202, and
(b)
email to: streetcuts@baltimorecity.gov;
(2)
if no written request for a review is filed within the time required by these rules, the aggrieved party will be deemed to have waived its rights to any further review of the decision of the Hearing Officer.
M.
If a timely request for review is made, a Review Hearing Officer shall be appointed who
(1)
may be an individual member of the DOT designated by the Director to serve as the Review Hearing Officer, but
(2)
shall not be
(a)
the Hearing Officer or
(b)
the DOT employee who made the decision or took the action being appealed.
N.
The review shall proceed in the following order:
(1)
prior to the review proceeding, any party may submit to the Review Hearing Officer and the other party, a brief containing a statement of facts and arguments;
(2)
the Review Hearing Officer shall begin the review hearing with a statement concerning the purpose of the review;
(3)
any party may present a brief articulation of its arguments and summarize its position;
(4)
any party may answer any questions posed by the Review Hearing Officer;
(5)
the Review Hearing Officer has the discretion to request additional testimony or evidence;
(6)
at the discretion of the Review Hearing Officer, the review hearing may be adjourned to another date, continued, or postponed.
O.
Following the review proceeding, the Review Hearing Officer
(1)
shall make every attempt to render a final decision of the review within 30 days;
(2)
may affirm, reverse, or modify the Hearing Officer’s decision;
(3)
shall consider the entire record;
(4)
shall make his decision in writing; and
(5)
shall send a copy of the decision to the aggrieved party.
P.
The decision of the Review Hearing Officer shall constitute the final decision of the Director.
Q.
Under <cite data-doc="City of Baltimore, Md., Code" data-path="|26">City Code Article 26</cite>, §15-36, a party aggrieved by a final decision of the Director may appeal that decision to the Circuit Court for Baltimore City in accordance with the Maryland Rules of Civil Procedure.
Chapter 04 – Curbside Commercial Permits
Balt., Md., COBRA § 14.03.04.01 (2026)
Regulation .01 Scope.LinkCopy Citation
<cite data-path="14.03.04">This chapter</cite> establishes:
A.
A framework for the temporary private use of public space in order to promote an active, accessible, safe, and vibrant urban environment;
B.
Restrictions on the location, construction, and use of a curbside facility;
C.
Insurance requirements for curbside facility permit holders;
D.
The application process for a curbside facility permit, including obtaining a minor privilege to construct the curbside facility;
E.
Responsibilities for permit holders;
F.
Enforcement of the Curbside Permit Guidelines; and
G.
Rules regarding revocation of a minor privilege.
Balt., Md., COBRA § 14.03.04.02 (2026)
Regulation .02 Definitions.LinkCopy Citation
A.
In <cite data-path="14.03.04">this chapter</cite>, the following terms have the meanings indicated.
B.
Terms Defined.
(1)
“ADA” means the federal Americans with Disabilities Act.
(2)
“Applicant” means the individual or entity pursuing a permit under this policy.
(3)
“BCDOT” means the Baltimore City Department of Transportation.
(4)
“Curbside Facility” means the commercial spaces permitted and regulated by this policy.
(5)
“Dimension” means measurable width, length, depth, and height of a curbside facility using feet and inches.
(6)
“Floodplain” means the same as <cite data-doc="City of Baltimore, Md., Code" data-path="|7|§1-2|(w)">City Code Article 7, § 1-2(w)</cite>.
(7)
“Floodplain district” means the same as <cite data-doc="City of Baltimore, Md., Code" data-path="|7|§1-2|(x)">City Code Article 7, § 1-2(x)</cite>.
(8)
“Forbidden road space” means portions of the public right-of-way including:
(a)
Crosswalks,
(b)
Pedestrian ramps,
(c)
Bike lanes,
(d)
Transit lanes or facilities,
(e)
Driving lanes,
(f)
Intersection space,
(g)
No-parking zones,
(h)
Commercial truck bays,
(i)
Handicapped parking spots,
(j)
Fire lanes,
(k)
Garages or driveways, and
(l)
Restricted parking zones that BCDOT will not consider for a curbside facility.
(9)
“Indoor area” means the interior space of a structure with a ceiling and sides enclosed by:
(a)
A combination of permanent or temporary walls, windows, or doorways, whether open or closed, or
(b)
Other physical barriers extending from floor to the ceiling.
(10)
“Local design standards” means neighborhood-specific aesthetic rules issued by Baltimore City.
(11)
“Membrane structure” means an element erected utilizing fabrics, foils, and other textiles with the support of tension cables.
(12)
“Minor privilege fee schedule” means a list of fees for minor privileges that is approved by the Board of Estimates and posted for public view on the BCDOT website.
(13)
“Minor privilege permit” means an approval of a temporary minor privilege” as defined by Baltimore City Charter, Article VIII, § 9.
(14)
“Modular” means a method of design and build with standardized units allowing for a streamlined process in the construction or dismantling of a curbside facility.
(15)
“Parking lane” means a space abutting the curb that is
(a)
Designated for on-street public vehicle storage, and
(b)
Contiguous to the property to which the curbside facility permit is issued.
(16)
“Partner agency” means the following Baltimore City agencies and entities:
(a)
Fire Department,
(b)
Police Department,
(c)
Health Department,
(d)
Parking Authority of Baltimore City,
(e)
Planning Department,
(f)
Department of Housing and Community Development,
(g)
Baltimore Development Corporation,
(h)
Liquor Board, and
(i)
Environmental Control Board.
(17)
“Permanently attached” means a curbside facility which is nailed or bolted to the rightof-way or an existing building.
(18)
“Permit holder” means a person or entity who has been issued a permit to operate a curbside facility.
(19)
“Protective vertical element” means a barrier designed to deflect a vehicular impact while protecting facility occupants, including:
(a)
Water-filled Jersey barriers;
(b)
Weighed barrels;
(c)
Concrete barriers; or
(d)
Other portable barriers.
(20)
“Stop work order” means a formal demand issued by the City requiring the permit holder to remove their facility from the right-of-way.
(21)
“Temporary” means something that lasts for period of time and is not permanent.
Balt., Md., COBRA § 14.03.04.03 (2026)
Regulation .03 Restrictions.LinkCopy Citation
A.
A Minor Privilege Permit for a curbside facility shall be restricted to a parking lane.
B.
BCDOT may consider installations within the following restricted parking zones:
(1)
Loading zones,
(2)
Metered parking,
(3)
Valet zones, and
(4)
Street sweeping corridors.
C.
A curbside facility may not be permanently attached to sidewalks, roads or buildings, and doing so may result in automatic permit revocation.
D.
A curbside facility may not use:
(1)
Amplified music,
(2)
Live entertainment, or
(3)
Open flames.
Balt., Md., COBRA § 14.03.04.04 (2026)
Regulation .04 Applicant Responsibilities.LinkCopy Citation
A.
An applicant shall obtain all permits relevant to their curbside facility including:
(1)
A minor privilege permit,
(2)
Other permits as required by law.
B.
An applicant shall obtain commercial general liability insurance which:
(1)
Provides coverage of one million dollars per occurrence,
(2)
Provides a minimum total aggregate of two million dollars, and
(3)
Designates the Mayor & City Council of Baltimore as an additional named insured.
C.
An applicant shall obtain the following insurance policies to cover a curbside facility:
(1)
Commercial general liability,
(2)
Umbrella insurance,
(3)
Worker’s compensation, and
(4)
Liquor liability if applicable.
Balt., Md., COBRA § 14.03.04.05 (2026)
Regulation .05 Design Standards.LinkCopy Citation
A.
A permit holder shall adhere to the following fire safety guidelines:
(1)
A curbside facility built primarily out of untreated wood or other flammable material shall be built a minimum distance of ten feet from a building; and
(2)
A curbside facility built primarily out of fire-resistant material such as treated wood shall be built a minimum distance of five feet from a building.
B.
BCDOT may not approve a curbside facility that:
(1)
Functions as an indoor area;
(2)
Is within 15 feet of a fire hydrant;
(3)
Is within 15 feet of a pull-in bus stop;
(4)
Is within 15 feet of dumpster;
(5)
Is on a street with a running slope of five percent or more;
(6)
Is on a street with a posted speed limit above 30 miles per hour;
(7)
Is located in or interferes with the functions of forbidden road space;
(8)
Intrudes on the sidewalk;
(9)
Is not ADA compliant;
(10)
Is more than one level;
(11)
Obstructs visibility of a traffic control sign or street sign;
(12)
Blocks stormwater drainage; or
(13)
Permanently restricts access to utilities.
C.
A curbside facility shall:
(1)
Fit within the width of the parking lane;
(2)
Use a protective railing or barrier which does not obstruct visibility above three feet, as determined by BCDOT;
(3)
Provide for a minimum seven feet of clearance between the ground plane and overhead elements;
(4)
Have an entrance which:
(a)
Is accessible via the abutting sidewalk,
(b)
Is at least 48 inches wide,
(c)
Is flush with the curb, and
(d)
Meets ADA compliance standards;
(5)
Feature protective vertical elements within the parking lane which separate the curbside facility from forbidden road space;
(6)
Be free of any tripping or slipping hazards; and
(7)
Incorporate lighting and reflective elements.
D.
A permit holder may incorporate the following weather mitigating elements:
(1)
Canopies;
(2)
Umbrellas;
(3)
Transparent igloos or bubbles; and
(4)
Other protective elements approved by BCDOT.
E.
An elevated curbside facility built flush with the curb shall be designed to support a minimum of 100 pounds per square foot.
F.
A curbside facility may be constructed using modular design practices.
G.
A curbside facility shall adhere to local design standards and adherence shall be reviewed on an annual basis.
H.
A curbside facility located within a floodplain district may be required to implement additional safety measures.
Balt., Md., COBRA § 14.03.04.06 (2026)
Regulation .06 Application Process.LinkCopy Citation
A.
An applicant is required to submit a site plan during the application submission process.
B.
A site plan shall be drawn to scale, clearly labeled and include the following:
(1)
Dimensions,
(2)
Property limits,
(3)
Existing objects,
(4)
Location of a heating device to be used in the curbside facility, if applicable,
(5)
Site features including:
(a)
Posted speed limit,
(b)
Grade of the roadway,
(c)
Pavement type,
(d)
Parking restrictions, and
(e)
Access to utilities.
C.
A permit application shall be reviewed by BCDOT within 60 days.
D.
BCDOT shall submit the application to partner agencies for review and comment during the 60-day review period.
E.
Following the review period, BCDOT may:
(1)
Approve the permit application,
(2)
Request that the applicant revise the application, or
(3)
Reject the application.
F.
Upon BCDOT approval, the applicant shall:
(1)
Send a copy of the application via certified mail return receipt requested to abutting property owners to notify them of the proposed curbside facility; and
(2)
Provide the return receipt to BCDOT as proof of notification.
G.
BCDOT shall submit the application to the Board of Estimates for final review and approval of the minor privilege permit application.
H.
An applicant shall pay a minor privilege fee assessed by the Board of Estimates upon the issuance of a minor privilege permit.
I.
Payment of the minor privilege fee shall be:
(1)
By check or money order in the required amount, and
(2)
Payable to the Director of Finance.
J.
The minor privilege fee is calculated by the method in the curbside commercial section of the minor privilege fee schedule approved by the Board of Estimates.
K.
A final site plan and payment shall be submitted to BCDOT Special Events section by:
(1)
Mail addressed to BCDOT Special Events at the Harry S. Cummings Building at 401 East Fayette Street, Baltimore, MD 21202; or
(2)
In person at the lobby of the Harry S. Cummings Building on 401 East Fayette Street, Baltimore, MD 21202.
Balt., Md., COBRA § 14.03.04.07 (2026)
Regulation .07 Permit Holder Responsibilities.LinkCopy Citation
A.
A permit holder is responsible for the following maintenance tasks required to keep the curbside facility safe for consumption of food and beverage:
(1)
Cleaning the curbside facility daily, including:
(a)
Removing all trash and food waste, and
(b)
Implementing non-toxic preventative pest control measures;
(2)
Securing tables and chairs so that they may not be used outside business hours; and
(3)
Repairing any structural failures or defects immediately upon discovery.
B.
A permit holder may not serve patrons in a curbside facility with known structural or sanitation deficiencies.
C.
A permit holder who desires to make a structural alteration to an existing curbside facility shall
(1)
Submit a new application for the alteration, including a site plan, and,
(2)
Be subject to review by BCDOT and its partner agencies.
Balt., Md., COBRA § 14.03.04.08 (2026)
Regulation .08 Enforcement of Regulation Guidelines.LinkCopy Citation
A.
A curbside facility is a temporary installation and BCDOT may require removal of the curbside facility:
(1)
On a permanent basis if site conditions no longer permit the curbside facility to operate safely, or
(2)
On a temporary basis if removal of the curbside facility is necessary for reasons including:
(a)
Maintenance or repairs within the public right-of-way,
(b)
Extreme weather event preparation,
(c)
Flooding, and
(d)
Other emergencies.
B.
A permit holder who fails to remove a curbside facility upon request may be liable for costs incurred by BCDOT in removing the curbside facility.
C.
A permit holder shall be subject to random inspections by BCDOT and partner agencies.
D.
BCDOT and partner agencies may enforce these regulations by:
(1)
Investigating complaints,
(2)
Issuing warnings,
(3)
Issuing stop work orders,
(4)
Confirming the validity of permits, and
(5)
Recommending the revocation of permits.
E.
The City and its agencies shall not be liable for costs associated with the removal, restoration, or replacement of a curbside facility.
Balt., Md., COBRA § 14.03.04.09 (2026)
Regulation .09 Revocation of Minor Privilege.LinkCopy Citation
A.
The City may revoke or refuse to renew a minor privilege.
B.
BCDOT may issue a stop work order for a curbside facility that is noncompliant with the rules in the curbside commercial regulations.
C.
A permit holder whose curbside facility is noncompliant with these regulations may have their minor privilege permit revoked without a hearing.
Chapter 05 – Parking – Persons With Disabilities and Helpers
Balt., Md., COBRA § 14.03.05.01 (2026)
Regulation .01 Scope.LinkCopy Citation
<cite data-path="14.03.05">This chapter</cite> establishes rules and regulations that govern reserved parking for persons with disabilities and their helpers, including:
A.
The application process for a reserved parking space; and
B.
The renewal process for a reserved parking space.
Balt., Md., COBRA § 14.03.05.02 (2026)
Regulation .02 Definitions.LinkCopy Citation
A.
In <cite data-path="14.03.05">this chapter</cite>, the following terms have the meanings indicated.
B.
Terms Defined.
(1)
Applicant.
(a)
“Applicant” means a person applying for a disabled parking space.
(b)
“Applicant” includes:
(i)
A person with disabilities; and
(ii)
A helper.
(2)
“Department” means the Baltimore City Department of Transportation.
(3)
“Director” means the Director of the Baltimore City Department of Transportation.
(4)
“Disability space” means a reserved parking space for a person with disabilities.
(5)
“Helper” means a person who:
(a)
Renders assistance to a person with disabilities; and
(b)
Resides with the person with disabilities for whom a disability space is assigned.
(6)
“PABC” means the Parking Authority of Baltimore City.
(7)
“Person with disabilities” means an individual that meets the criteria of City Code Article 31, §9-1(a)(1-3).
(8)
“Renewal application” means the form that is provided for a space-holder to complete annually to maintain a disability space.
(9)
“Space-holder” means a person that has received a disability space through an approved application.
Balt., Md., COBRA § 14.03.05.03 (2026)
Regulation .03 Initial Application Process.LinkCopy Citation
A.
An applicant applying for a disability space for the first time shall:
(1)
Complete an application in the form that the Director requires; and
(2)
Acquire the application form by:
(a)
Obtaining a copy from the PABC office; or
(b)
Downloading a copy from the PABC website.
B.
An applicant shall ensure a submitted application contains:
(1)
The required medical documentation; and
(2)
The noted requirements as specified in the application.
Balt., Md., COBRA § 14.03.05.04 (2026)
Regulation .04 Renewal Applications.LinkCopy Citation
A.
To maintain an assigned disability space, a space-holder shall complete a renewal application in accordance with these regulations.
B.
Distribution of Renewal Application.
The PABC shall:
(1)
Ensure a renewal application is issued to a space-holder each year following the initial date that the disability space was awarded; and
(2)
Issue the renewal application to the address listed in the space-holder’s initial application.
C.
A space-holder shall return a renewal application to the PABC within 90 calendar days of receipt.
Subtitle 09 – Traffic
Chapter 01 – Public Traffic Calming Requests
Balt., Md., COBRA § 14.09.01.01 (2026)
Regulation .01 Scope.LinkCopy Citation
These regulations:
(1)
Implement a plan for fulfilling public service requests for traffic calming through the 311-system in Baltimore City;
(2)
Create a prioritization system for traffic calming that accounts for equity; and
(3)
Expand the toolkit of traffic calming options to promote safety and livability on City streets.
Balt., Md., COBRA § 14.09.01.02 (2026)
Regulation .02 Definitions.LinkCopy Citation
A.
In <cite data-path="14.09.01">this chapter</cite>, the following terms have the meanings indicated.
B.
Terms Defined.
(1)
“Arterial street” means freeways, multilane highways, and other important roadways that supplement the United States Interstate System.
(2)
“BCDOT” refers to the Baltimore City Department of Transportation.
(3)
“Collector street” means major and minor roads that connect local roads and streets with arterials.
(4)
“Complete Streets” means a program in Baltimore City that enables access, mobility, economic development, attractive public spaces, health, and well-being for all people.
(5)
“Corridor” means the roadway and adjacent affected roadways where traffic calming is requested.
(6)
“Equity Priority Zones” means equity zones defined by the Complete Streets Manual.
(7)
“Local or neighborhood street” means roads that service limited vehicular traffic and are the primary access to residential areas, neighborhoods, and other local areas.
(8)
“Neighborhood” means community identified by the Baltimore City Planning Department’s official “Neighborhood Statistical Area Map”.
(9)
“Prioritization process” means procedure by which streets or corridors are selected and ranked for traffic calming projects.
(10)
“Service Request (SR)” or “311 Service Request” means a request made via phone or online to the Baltimore City 311 System.
(11)
“Stakeholder” means individuals or entities that are affected by <cite data-path="14.09.01.02">this regulation</cite>.
(12)
“Traffic Calming” means devices or methods used to slow the speed of traffic or reduce volume of traffic.
Balt., Md., COBRA § 14.09.01.03 (2026)
Regulation .03 Initiation of the Traffic Calming Process.LinkCopy Citation
A.
Arterial streets are:
(1)
not subject to the requirements for local or collector streets; and
(2)
subject to a separate investigation process for alternative traffic calming measures.
B.
A stakeholder requesting traffic calming in a neighborhood on a local or collector street shall:
(1)
live within the neighborhood;
(2)
own or operate a business within the neighborhood;
(3)
represent a school or daycare facility within the neighborhood;
(4)
represent a Community Organization within the neighborhood; or
(5)
be a public, elected official, or his or her designee, whose district’s boundaries are within or include a portion of the City of Baltimore.
C.
To initiate the traffic calming process, the Stakeholder must complete a 311 Service Request by:
(1)
calling 311; or
(2)
filling out an online survey
(a)
through the mobile phone application for 311 Service Requests; or
(b)
on City of Baltimore’s 311 website.
D.
A Stakeholder shall provide the following information to be considered for a traffic calming request:
(1)
legal first and last name;
(2)
email address or phone number;
(3)
street address;
(4)
start and end points of the roadway segments where the need for traffic calming should be investigated;
(5)
a specific address or location where speed or cut-through traffic are of concern;
(6)
any relevant and necessary information regarding the traffic calming service request.
E.
For BCDOT to consider a Service Request, the Stakeholder must provide the information found in <cite data-path="14.09.01.03|D.">Regulation .03D</cite> in full.
F.
After submission, the stakeholder will be given:
(1)
a time period for receiving an update for the service request;
(2)
the service request number; and
(3)
if using online or mobile application, a confirmation email with:
(a)
A copy of the completed service request form; and
(b)
The information listed above in <cite data-path="14.09.01.03|D.">Regulation .03.D</cite>.
Balt., Md., COBRA § 14.09.01.04 (2026)
Regulation .04 Investigation of Traffic Calming Request.LinkCopy Citation
A.
The BCDOT shall
(1)
evaluate the need and feasibility of traffic calming, and
(2)
simultaneously provide the Service Request to the Baltimore City Fire Department for notification and feedback.
B.
Data collection and analysis shall proceed immediately following the BCDOT determination of a valid request for traffic calming.
Balt., Md., COBRA § 14.09.01.05 (2026)
Regulation .05 Data Collection and Analysis.LinkCopy Citation
A.
BCDOT Traffic Division shall collect data within the study corridor.
B.
The information collected will be analyzed by BCDOT to determine if traffic calming is
(1)
warranted, and
(2)
feasible.
C.
Data collection units may be deployed on site to collect data related to speed.
D.
Data collection units shall be deployed based on engineering judgement.
E.
A site visit may be conducted to document conditions including:
(1)
roadway grade;
(2)
roadway width and cross-section;
(3)
roadway horizontal geometry;
(4)
lane configurations;
(5)
adjacent land-use;
(6)
multimodal traffic operations; and
(7)
other related geometric and operational roadway features.
F.
The following elements may be reviewed:
(1)
crash data over the previous 6 years;
(2)
street type and target speed in accordance with the Baltimore Complete Streets Manual; and
(3)
Equity Priority Zones.
G.
Local and collector roadways with longitudinal grades of 8 percent or lower that meet the traffic calming criteria for need and feasibility can proceed to the prioritization process.
H.
Local or collector roadways with longitudinal grades greater than 8 percent require further engineering review to determine the applicability and feasibility of
(1)
traffic calming, or
(2)
other mitigation measures:
Balt., Md., COBRA § 14.09.01.06 (2026)
Regulation .06 Prioritization Process.LinkCopy Citation
A.
Following data collection, and approval, BCDOT shall:
(1)
Move the traffic calming Service Request forward to the prioritization process; and
(2)
Submit the Service Request for further engineering or review by Baltimore City Fire Department.
B.
If the application does not meet the criteria threshold of the data collection and analysis, BCDOT shall issue a statement to the Stakeholder denying the Service Request.
C.
BCDOT shall prioritize traffic calming requests based on:
(1)
Severity and prevalence of speeding based on initial data investigation and historical data;
(2)
Severity and prevalence of crashes based on historical data;
(3)
The presence of school zones; and
(4)
Equity Zones as identified on BCDOT’s Equity Map.
D.
Prior to the beginning of construction season, the prioritization process will determine the construction program on an annual basis.
Balt., Md., COBRA § 14.09.01.07 (2026)
Regulation .07 Community Involvement.LinkCopy Citation
A.
Prior to implementation of traffic calming measures, BCDOT shall notify stakeholders of the following information:
(1)
A summary of the traffic calming plan;
(2)
The timeframe of the project comment period; and
(3)
Contact information pertaining to comments or an opt-out request.
B.
BCDOT shall notify stakeholders by:
(1)
Postcard or letter;
(2)
Electronic communication;
(3)
Social media; or
(4)
Other community outreach methods.
C.
BCDOT may post signs on the street in question with the information above.
D.
The following conditions apply to opt-out requests:
(1)
Only opt-out requests from stakeholders abutting the immediate project block(s) shall be considered;
(2)
Stakeholders may be required to provide proof of residency when opting out;
(3)
Comments must be submitted within the specified response period.
Balt., Md., COBRA § 14.09.01.08 (2026)
Regulation .08 Construction SchedulingLinkCopy Citation
A.
Upon conclusion of the public comment period and pending funding availability, BCDOT will schedule the traffic calming devices or measures for installation using the location’s score from the prioritization process.
B.
Local and collector streets that are approved for the installation of traffic calming measures will be scheduled for construction on an annual basis.
C.
Arterial streets may be scheduled for construction separately from local and collector streets to allow for additional analysis, more comprehensive treatments, or other factors.
Balt., Md., COBRA § 14.09.01.09 (2026)
Regulation .09 ReviewLinkCopy Citation
After installation of traffic calming devices, BCDOT may review traffic calming devices for effectiveness.
Balt., Md., COBRA § 14.09.01.10 (2026)
Regulation .10 Traffic Calming DevicesLinkCopy Citation
A.
Types and descriptions of traffic calming devices are available for review within the Design Guidance section of the Baltimore Complete Streets Manual.
B.
Options for traffic calming devices include:
(1)
speed humps, speed tables, and speed cushions;
(2)
curb extensions, also known as bump-outs or bulb-outs;
(3)
rumble strips;
(4)
hardened centerline treatments;
(5)
raised crosswalks;
(6)
raised intersections;
(7)
chicanes;
(8)
mini-roundabouts, also known as neighborhood traffic circles;
(9)
traffic signal timing and operations;
(10)
vehicle access restrictions, such as median diverters;
(11)
traffic signal timing and operations;
(12)
reduction in travelway width;
(13)
reduction in number of through or travel lanes;
(14)
Slow Streets treatments;
(15)
any combination of these devices;
(16)
other available treatments or devices.