Establishing secure connection…Loading editor…Preparing document…

Ordinance No. An Ordinance of the City of San Jose

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Final Telecommunications Ordinance

CITY OF ,

ORDINANCE NO.

AN ORDINANCE AMENDING CERTAIN SECTIONS OF CHAPTER ; CREATING A NEW SECTION ; AND CREATING A NEW CHAPTER RELATING TO TELECOMMUNICATIONS.

BE IT ORDAINED BY THE GOVERNING BODY OF THE CITY OF :

Section 1. Section is amended to read:

14-1.2 Definitions. As used in this Chapter.

Height means the vertical distance above grade to the highest point of a structure or of a building. For telecommunication facilities refer to Section .

Public right-of-way means the total area of the land deeded, reserved by plat, or otherwise acquired by the city, the county or the state of primarily for the use of the public for the movement of people, goods and vehicles and for the installation and maintenance of public utilities, telecommunication facilities or drainage ways.

Public utility means any plant, property or facility for the generation, transmission, distribution, sale, or furnishing to, or for, the general public, of electricity, light, heat, power, natural gas, water, steam, sanitary sewer, refuse collection, and street maintenance, in accordance with and pursuant to state laws, including , et seq., and , et seq.

Right-of-way means the total area of land deeded, reserved by plat or otherwise acquired by a governmental unit or private organization primarily for the use of the public for the movement of people, goods and vehicles or by a public or private organization primarily for the installation and maintenance of utilities and telecommunication facilities or by a railroad primarily for the laying of its tracks.

Section 2. Section is amended to read:

14-17.4 Special Exceptions.

A. After public notice as set forth in subsection and subject to appropriate conditions and safeguards, the board of adjustment may permit as special exceptions:

(1) private day-care nurseries and kindergartens as provided in subsections and ;

(2) hospitals and extended care facilities, provided:

(a) that facilities with fewer than fifty (50) beds or equivalent shall have a lot area of at least two (2) acres, and that all structures in connection with such facilities shall be at least twenty-five feet (25') from any lot line;

(b) that facilities with over fifty (50) beds or equivalent shall have a lot area of at least five (5) acres, and that all structures in connection with such facilities shall be at least fifty feet (50') from any lot line;

Section 3. Section is amended to read:

Permitted Principal Uses and Structures.

A. The principal uses and structures permitted in the district are:

Section 4. Section is amended to read:

Permitted Accessory Uses and Structures.

Telecommunication facilities as set forth in Section .

Section 5. Section is amended to read:

Definitions. As used in this section:

Building height means the vertical distance above grade to the highest point on the roof plane of a structure or building.

Section 11. A new Section is enacted to read:

Special Exceptions, Telecommunication facilities are permitted as special exceptions as per section .

Section 15. A new Section is ordained to read:

TELECOMMUNICATIONS FACILITIES

Purpose. The purposes of this Chapter are to:

Section 16. A new Section is ordained to read:

Definitions. As used in this section the following terms shall have the meanings set forth below:

Section 17. A new Section is ordained to read:

Applicability. All towers or antennas located within the city limits whether upon private or public lands shall be subject to this ordinance.

Exceptions:

Amateur Radio Station Operators/Receive Only Antennas

Preexisting Towers or Antennas

AM Array

Emergency Services

Section 18. A new Section is ordained to read:

General Requirements. All towers and antennas whether administratively approved or requiring a special exception shall comply with the existing city codes.

Section 19. A new Section is ordained to read:

Uses not Requiring a Permit.

Section 20. A new Section is ordained to read:

Administrative Approval of Certain Uses.

Section 21. A new Section is ordained to read:

Special Exceptions.

Section 22. A new Section is ordained to read:

Equipment Storage Facilities.

Section 23. A new Section is ordained to read:

Removal of Abandoned Antennas and Towers.

Section 25. A new Section is ordained to read:

Waivers.

Section 26. A new Section is ordained to read:

Penalties and Proceedings for Antennas and Towers in violation of this section.

Section 27. A new Section is ordained to read:

Severability.

Section 32. A new Section is ordained to read:

TELECOMMUNICATIONS GENERALLY

Purpose.

Section 33. A new Section is ordained to read:

Definitions:

Section 34. A new Section is ordained to read:

REGISTRATION REQUIREMENT

Registration. Except as otherwise provided herein, all telecommunications owners having telecommunications facilities located within the city shall register annually with the city as telecommunications owners.

Registration required:

Section 36. A new Section is ordained to read:

Registration Information.

Section 38. A new Section is ordained to read:

USES OF PUBLIC PROPERTY

Section 40. A new Section is ordained to read:

Lease Application.

Section 47. A new Section is ordained to read:

Fees and Compensation.

Section 52. A new Section is ordained to read:

Construction Standards for Linear Telecommunications Facilities

Section 67. A new Section is ordained to read:

PENALTIES AND PROCEEDINGS FOR ENFORCEMENT OF THIS CHAPTER

_____________________________________

MAYOR

________________________________________

CITY CLERK

___________________________________

CITY ATTORNEY

PASSED, APPROVED and ADOPTED this day of , .

_____________________________________

MAYOR

________________________________________

CITY CLERK

___________________________________

CITY ATTORNEY

Effective Date

Approved As To Form

City Attorney

Enter text✕

What an Ordinance No. for the City of San Jose Represents

An ordinance for the City of San Jose is a local law enacted by the San Jose City Council that creates, amends, or repeals municipal regulations. It is identified by an ordinance number, a descriptive title, and an adoption date, and once signed and filed it becomes part of the municipal code or public record. Ordinances set binding rules for residents, businesses, and enforcement agencies, and they typically include findings, enacting language, effective dates, and directions for codification and publication.

Why the Ordinance Number and Proper Form Matter

A correctly prepared ordinance entry ensures legal enforceability, clear public notice, and accurate codification. It reduces disputes about scope, timing, and authority while providing a durable public record that departments and the public can rely on.

Why the Ordinance Number and Proper Form Matter

Who interacts with an Ordinance No. in practice

Several groups create, review, or rely on municipal ordinances at different stages.

  • City officials and legislative staff draft and shepherd the ordinance through readings and votes.
  • City attorney and outside counsel review legal form, preemption, and enforceability issues.
  • Residents, businesses, and regulated parties consult the ordinance for compliance and public comment.

Clear role separation during drafting, adoption, and filing reduces procedural mistakes and legal risk.

Primary signatories and officials

Mayor

The mayor (or presiding officer per charter) often signs adopted ordinances to signify executive approval. In some charters a mayoral signature is ceremonial; consult the city charter for finality rules.

City Clerk

The city clerk typically attests to adoption, assigns the ordinance number, and files or publishes the document for the public record, which is essential for codification and effective-date determinations.

Essential ordinance metadata to include

Ordinance Number: Unique identifier
Title: Short descriptive title
Adoption Date: MM/DD/YYYY
Effective Date: MM/DD/YYYY
Attestation: City Clerk signature
Signatures: Mayor and officials

Step-by-step overview: how an ordinance reaches final form

This condensed sequence shows the typical lifecycle from draft to codification; procedures vary by charter and state law.

  • 01
    Drafting: Prepare findings, sections, and enacting clause for council consideration.
  • 02
    Public Notice: Publish hearing notices and make the draft available for public review.
  • 03
    Council Vote: Council holds readings/hearings and votes to adopt or reject the ordinance.
  • 04
    Filing and Publication: City clerk attests, assigns number, files and publishes per city rules.

Customizing and completing an ordinance workflow online

Set up an electronic workflow that mirrors municipal review steps and retains an audit trail for adoption and publication.

Field Configuration
Template Create reusable ordinance template with standard headings and enacting clause.
Signer Roles Define mayor, clerk, and department approvers with signing order.
Authentication Select email, SMS, or stronger methods for signer verification.
Notifications Enable automatic reminders and delivery of signed copies to archive.

Where to file, send, and submit an adopted ordinance

Adoption is followed by formal filing and publication; different recipients require specific copies or formats.

  • City Clerk Office: Official repository for ordinance attestation and numbering.
  • Municipal Code Division: Submit for codification into the city code or municipal code supplement.
  • Affected Departments: Provide finalized ordinance to impacted city departments for implementation.
  • Public Posting: Publish notices or post the ordinance online per local rules.

Distribution options and technical considerations

Municipal documents may be shared by email, portal, or physical copy; choose formats that preserve records and signatures.

  • Email Delivery: Send signed PDF copies to stakeholders.
  • Public Portal: Host adopted ordinance PDFs for transparent access.
  • Physical Records: Retain signed originals per archival rules.

Typical timing milestones for ordinance adoption

Municipal timelines differ by charter; the list below shows common milestones to track during the adoption process.

First Reading Published:

Notice and first reading scheduled in advance of public hearing.

Public Hearing Date:

Opportunity for public comment and final deliberation.

Adoption Vote:

Council votes to pass or fail the ordinance.

Mayor Review Period:

Executive may sign or veto within the chartered timeframe.

Effective Date:

Specified in ordinance or set by charter (often immediate or after 30 days).

Common mistakes to avoid when preparing an ordinance

  • Using inconsistent or duplicate ordinance numbers across drafts leading to codification confusion.
  • Leaving the effective date blank or conflicting with the mayoral signature and publication schedule.
  • Omitting required findings or statutory authority that justify the municipal regulation.
  • Failing to maintain an auditable chain of custody for signed and published ordinance documents.

Consequences of an incorrectly prepared or filed ordinance

Unenforceable Provision: Courts may refuse enforcement
Legal Challenge: Litigation risk and costs
Administrative Delay: Implementation postponed
Public Confusion: Compliance ambiguity arises
Financial Exposure: Potential fines or damages
Codification Errors: Incorrect municipal code entries

eSignature platform pricing and feature snapshot relevant to municipal workflows

Common vendor pricing models and key features that matter for ordinance workflows, including audit trails and HIPAA/BAA support where applicable.

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 by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Practical examples of ordinance-related document flows

Two typical scenarios show how municipal teams handle ordinance drafting, adoption, and publication while preserving legal records.

City Council Adoption Workflow

A staff attorney prepares the draft and findings for council

  • Clerk posts hearing notice and agenda online
  • After a two-reading process the clerk attests the signed ordinance, files the number, and publishes the final text for public access, ensuring codification.

Interdepartmental Implementation

A regulatory ordinance assigns duties to multiple departments

  • Each department receives the codified ordinance and implementation memo
  • Departments update procedures and publish guidance documents, with the clerk retaining the executed record for the archive.

Frequently asked questions about Ordinance No. preparation and filing

Answers address common legal, procedural, and technical questions encountered during ordinance drafting, signature, and publication.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users