330.13
EFFECTIVE DATE OF APPROVED PROJECTS
San Francisco Planning Code · SF Planning Code § 330.13
Corpus is an independent public-information project, not the official City of San Francisco website. Stable reference URL
SEC. 330.13. EFFECTIVE DATE OF APPROVED PROJECTS. (a) A final decision on an application for an appealable project shall become effective after a 10 working day appeal period to the California Coastal Commission has expired, unless either of the following occur: (1) a valid appeal is filed in accordance with City and State regulations, or (2) local government requirements are not met per Section 330.6(b). When either of
the above occur, the California Coastal Commission shall, within five calendar days of receiving notice of that circumstance, notify the local government and the applicant that the local government action has been suspended. The applicant shall cease construction immediately if that occurs. (b) Coastal Zone Permits for projects not appealable to the California Coastal Commission shall become effective only after other required planning or building permit applications have been issued. (Ord. 509-85, App. 11/22/85, 1985) SEC. 330.14. EXPIRATION DATE AND EXTENSIONS. A Coastal Zone Permit shall expire one year from the date of issuance unless otherwise explicitly modified by approval conditions for the project. The Zoning Administrator may extend a Coastal Zone Permit prior to its expiration for up to 12 months from its original date of expiration. Coastal Zone Permit extensions may be granted upon findings that the project continues to be in conformance with the Local Coastal Program. (Amended by Ord. 509-85, App. 11/22/85) SEC. 330.15. COASTAL ZONE PERMIT FEES. Before accepting any Coastal Zone Permit Application for filing, the Planning Department shall charge and collect a fee as set forth in Section 351(d) for processing a Coastal Zone Permit Application. No fees shall be established for appealing any Coastal Zone Permit. (Amended by Ord. 509-85, App. 11/22/85; Ord. 188-15 , File No. 150871, App. 11/4/2015, Eff. 12/4/2015) AMENDMENT HISTORY Nonsubstantive changes; Ord. 188-15 , Eff. 12/4/2015. SEC. 330.16. PROCEDURAL PERMIT REVIEW CHANGES. Any proposed changes in the Coastal Zone Permit procedures specified in Sections 330 through 330.16, or any subsequent action by the Board of Supervisors, Planning Commission or Zoning Administrator pertaining to the permit review process of Coastal Zone Permits shall be submitted to the California Coastal Commission for its review prior to final approval. The California Coastal Commission shall take action on any such amendments within a reasonable time period after the submittal of any such proposals. (Amended by Ord. 509-85, App. 11/22/85) SEC. 331. [REDESIGNATED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; redesignated as Sec. 422 by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 331.1. [REDESIGNATED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; redesignated as Sec. 422.1 by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 331.2. [REDESIGNATED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; redesignated as Sec. 422.2 by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 331.3. [REDESIGNATED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; redesignated as Sec. 422.3 by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 331.4. [REPEALED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; repealed by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 331.5. [REPEALED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; repealed by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 331.6. [REDESIGNATED.] (Added by Ord. 61-09, File No. 090181, App. 4/17/2009; redesignated as Sec. 422.5 by Ord. 108-10, File No. 091275, App. 5/25/2010) SEC. 333. PUBLIC NOTIFICATION PROCEDURES. (a) Purpose. The purpose of this Section 333 is to establish procedures for all public notifications required by this Code, except for those requirements set forth in Section 311. (b) Applicability. The requirements of this Section 333 shall apply to any hearing before the Planning Commission, Historic Preservation Commission, and/or the Zoning Administrator for which public notice is required in this Code, except that the requirements set forth in Section 311 shall be applicable to certain applications as set forth in Section 311. The Zoning Administrator shall determine the means of delivering all forms of public notice, in a manner consistent with the Planning Commission’s policy on notification, provided that the requirements of this Section 333 are satisfied. (c) Notification Period. For the purposes of this Section 333, the Notification Period shall mean no fewer than 20 calendar days prior to the date of the hearing, or in the case of a Building Permit Application a period of no fewer than 20 calendar days prior to any Planning Department approval of the application. (d) Content of Notice. (1) All notices provided pursuant to this Section 333 shall have a format and content determined by the Zoning Administrator, and shall at a minimum include the following: (B) the Planning Department case number or Building Permit Application number, as applicable, for the subject project; and (C) the basic details of the project, including whether the project is a demolition, new construction, alteration, or change of use; and basic details comparing the existing and proposed conditions at the property including building height, number of stories, dwelling unit count, number of parking spaces, and the use of the building; (D) instructions on how to access the online notice and plan sets for the project, including how to obtain paper copies of the plan sets, and additional information for any public hearings required by the Planning Code and for which public notification is required for a development application: the date, time and location of the hearing; instructions for how to submit comments on the proposed project to the hearing body; and an explanation as to why the hearing is required; and