Proposed Name
Exact spelling and punctuation of the requested street name, including suffix (Road, Avenue, Lane) and any intended capitalization or diacritical marks.
A well-prepared Street Naming Request shortens review, reduces public objections, and meets municipal procedural requirements for adoption.
Multiple municipal and private stakeholders prepare, submit, or review these requests depending on local procedure.
Knowing who to involve early improves completeness and speeds processing.
The City Clerk receives the petition, confirms submission completeness, posts required public notices, and prepares the ordinance for council action. The clerk ensures legal posting timelines are met and maintains the official record of the ordinance once adopted.
Public Works reviews technical effects on signage, maintenance, and addressing. The director coordinates GIS updates and confirms whether the proposed name conflicts with existing naming conventions or emergency responder locators.
Exact spelling and punctuation of the requested street name, including suffix (Road, Avenue, Lane) and any intended capitalization or diacritical marks.
Clear description of the affected right-of-way with start/end points, adjacent addresses, and block or parcel identifiers to avoid confusion.
A scaled map or plat showing the location, property lines, centerline, and existing street names; include a PDF or print-quality image for record.
Signed statements from abutting property owners or proof of municipal authority when the roadway is publicly owned; specify who granted consent and when.
Short narrative explaining the reason for the name (historical, memorial, safety, directional) and any community support or objections.
Name, mailing address, email, and daytime phone for the proposer and a designated municipal contact for follow-up and hearings.
| Field | Configuration |
|---|---|
| Document Upload | Allow PDF/DOCX attachments; require map file |
| Signature Fields | Add signer fields for owner consents and proposer signature |
| Conditional Fields | Show additional questions when 'private road' selected |
| Routing | Auto-send to clerk, planning, and public works |
Use a secure eSubmission platform that accepts PDF and DOCX and supports signer authentication for owner consents.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no credit card | Varies | Varies | Varies | Varies |
| Bulk Send | Yes — available on Premium | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Clerk logs petition and confirms materials
Planning and public works evaluate impacts
Council hears testimony and public comment
Ordinance passed and records updated
Often published 14–30 days before hearing
Deadlines vary; submit per clerk's schedule
Scheduled per council calendar and agenda timing
Local code defines the period to contest adoption
Ordinance states when the new name takes effect
A neighborhood group proposes honoring a local figure with a street renaming
A developer submits proposed roadway names for a subdivision