Flagged sections

Administrative Code — Sunshine Ordinance (Ch. 67)

• The definition of 'Meeting' spans three main categories plus four detailed exclusions with multiple sub-conditions, creating a labyrinthine structure that requires careful reading to understand when public-access rules apply.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Section (b) introduces a conditional requirement for third-party contracts with multiple nested conditions (ownership interest types, government functions, meeting scope) that may be difficult for non-specialists to apply in practice.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section references the Ralph M. Brown Act by citation to Government Code sections without reproducing relevant terms, requiring readers to look elsewhere to understand the full scope of requirements.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (f) is lengthy and contains multiple overlapping conditions, exceptions, and provisions about notice requirements, waivers, and alternate locations that could be difficult for a non-lawyer to parse.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subdivision (e) contains nested conditions and cross-references that make the exceptions to the no-off-agenda-action rule intricate and hard to follow for lay readers.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section is lengthy with multiple nested categories (54956.7 through 54957.6), each with different disclosure templates and conditional requirements that cross-reference state government code sections.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section contains multiple conditional release provisions for litigation recordings with overlapping time-based and event-based triggers that may interact unpredictably in practice.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subdivisions (b), (c), and (d) create overlapping timing requirements for document availability (before the meeting, during discussion, or immediately during discussion) that could be clarified or consolidated.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section contains multiple subsections with cross-references, exceptions, and detailed conditions (especially subsection (d) on litigation and (e) on collective bargaining) that make it lengthy and require careful reading to understand all the limitations.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section involves cross-references to Section 67.8, conditional logic for different meeting types (regular, special, adjourned, continued, urgent), and interconnected disclosure requirements that require understanding multiple regulatory layers.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section contains multiple detailed subsections with varying reporting timelines, conditions, and exceptions (especially subsection (b)(3) on settlements) that interact in ways requiring careful reading.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (e) contains nested conditional procedures (volunteer sourcing, then non-profit, then professional) and multiple deadline variations (48 hours generally, but noon for Monday/Tuesday meetings) that create potential confusion in implementation.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (c) contains multiple cross-references and conditional clauses about when recording applies, equipment availability, and retention periods that may confuse readers about which meetings must be recorded.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subdivision (a) contains a lengthy exception for Board of Supervisors committees that makes the rule harder to follow and creates potential ambiguity about when the exception applies.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section uses multiple legal references and conditional clauses that make it harder to parse, particularly the exception regarding confidential information and the multiple remedies available (injunctive relief, declaratory relief, misconduct complaints).

Administrative Code — Sunshine Ordinance (Ch. 67)

• The definition of 'Public Information' requires cross-reference to the California Public Records Act and its specific Government Code sections, which may be unfamiliar to ordinary residents without access to state law.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (d) contains a lengthy multi-part test with nested conditions and cross-references to First Amendment law that may be difficult for lay readers to parse.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section involves multiple filing procedures (current vs. older documents), cross-references to the California Public Records Act and Section 67.24, and conditional language about what must or may be filed, making it harder to follow than needed.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section is lengthy with multiple subsections and cross-references to state law that may require readers to understand California Public Records Act provisions to fully grasp the local rules being imposed.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Section (c) contains a nuanced exception permitting inquiries about requester purpose in certain mixed-exempt/non-exempt records scenarios, which may be unclear in application.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section chains to Section 67.27 for justification requirements and references the California Public Records Act without restating its scope, making full understanding require consultation of external documents.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section uses nested conditional language (subsections a–d with cross-references to the California Public Records Act and 'this Article') that requires readers to track multiple legal concepts and external authorities.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section contains overlapping and repetitive requirements about index content, organization, and maintenance spread across multiple sentences, making the core obligations somewhat difficult to extract.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section contains multiple overlapping requirements with different timelines (six months, concurrent with public distribution, within 48 hours, weekly updates) that could be clearer if reorganized by compliance deadline.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section mixes multiple obligations (contractual requirements, notice procedures, advertiser rights, and public-record rules) in a single paragraph, making it harder to parse what applies to whom and when.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (b) contains intricate definitions with multiple threshold triggers (monthly compensation OR contacts), compensation aggregation rules, and separate thresholds for individuals versus organizations, making it difficult to determine coverage.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section contains multiple nested exceptions, carve-outs, and cross-references (e.g., to Ethics Commission articles and Government Code sections) that make it difficult to follow, particularly subsections (b) and (c).

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section uses layered conditions ('accept, allow to be collected, or direct or influence') and cross-references an ordinance without spelling out all enforcement or exemption details.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (c) is a long, dense paragraph combining multiple obligations (record-keeping, public access, enforcement mechanisms, and specific applications) that could be clearer if broken into separate sentences or subsections.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The membership composition rules in subsection (a) are intricate with multiple overlapping categories and specific qualifications for journalists; the ethical wall requirement and legal advisor assignment also add procedural complexity.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section conflates multiple distinct policies (open meetings, communication records, subsidy conditions) in a single provision, with overlapping conditions like 'to the extent not expressly prohibited by law' that create interpretive questions.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section references multiple entities (Ethics Commission, City Attorney's Office, Sunshine Ordinance Task Force) and prerequisites (financial-interest affidavit requirement) that may not be immediately clear to readers unfamiliar with the city's governance structure.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The section cross-references three different state and local laws (Sunshine Ordinance, Brown Act, Public Records Act) without defining them, making full understanding require knowledge of external legal sources.

Administrative Code — Sunshine Ordinance (Ch. 67)

• Subsection (d) introduces a procedural trigger ('40 days after a complaint is filed') that depends on undefined prior steps and cross-references to other enforcement mechanisms not explained in this section.

Administrative Code — Sunshine Ordinance (Ch. 67)

• The phrase 'greater or more expedited' creates ambiguity when one law provides broader access but slower disclosure, while another provides narrower access but faster disclosure—it is unclear which takes precedence in such cases.

Campaign and Governmental Conduct Code

• The section relies on understanding the relationship between state and local law, incorporation by reference, and what 'inconsistent with' means in legal hierarchy—concepts that may confuse non-lawyers about which rules actually apply.

Campaign and Governmental Conduct Code

• The section cross-references California Government Code Section 82013 and the definition of 'committee' requires understanding of campaign finance law outside this Code.

Campaign and Governmental Conduct Code

• The section references external California regulations and requires understanding of multiple document types and retention timelines across different statutory sources.

Campaign and Governmental Conduct Code

• The section cross-references state law (California Government Code Section 81009 and the Political Reform Act) without defining the specific requirements those statutes impose, making full compliance depend on understanding external documents.

Campaign and Governmental Conduct Code

• The section contains multiple nested subsections with cross-references to state law and conditional requirements (e.g., 'provided that' clauses) that may confuse readers unfamiliar with campaign finance rules.

Campaign and Governmental Conduct Code

• The section involves overlapping reporting requirements (Chapter requirements, State law, and this Section), multiple filing dates, and conditional timing ("if necessary") that requires readers to understand when circulation ends.

Campaign and Governmental Conduct Code

• Subsection (e) on aggregation of affiliated entity contributions involves multiple overlapping rules and cross-references that require careful reading to understand when contributions must be combined.

Campaign and Governmental Conduct Code

• Subsection (b) contains multiple nested conditions (the $5,000 threshold, 'at the behest of' language, exceptions for public appeals and contributions to the requesting official themselves) that interact in ways requiring careful parsing.

Campaign and Governmental Conduct Code

• The section contains multiple layers of rules (direct coordination, rebuttable presumptions, and exceptions) with overlapping criteria and detailed subconditions that cross-reference each other, making it difficult for a non-lawyer to quickly grasp the full scope.

Campaign and Governmental Conduct Code

• The section contains overlapping time periods (receipt of bill vs. last day of delivery month), a presumption framework with two conditions, and an exception for credit cards that creates interpretive nuance around what counts as 'accrued expense.'

Campaign and Governmental Conduct Code

• Subsection (b) contains multiple interrelated rules about fund use, committee control, withdrawal scenarios, and surplus disposition with cross-references to other regulations and Ethics Commission authority.

Campaign and Governmental Conduct Code

• The section contains multiple cross-references, nested definitions (particularly 'Affiliate' and 'City Contractor'), and layered notification requirements across different parties that make it difficult to follow.

Campaign and Governmental Conduct Code

• The section contains multiple defined terms with specific dollar thresholds, lists of eight different boards/commissions, and interrelated prohibitions and exceptions that require careful cross-referencing to apply correctly.

Campaign and Governmental Conduct Code

• The section involves multiple triggering conditions (three separate subsections in (a)), cross-references to state law and other city code sections, and a distinction between different types of campaign expenditures and communications that may be difficult for lay readers to parse.

Campaign and Governmental Conduct Code

• The section has multiple subsections with cross-references, different thresholds for different offices, and numerous conditions that interact, making it hard to track all eligibility requirements at once.

Campaign and Governmental Conduct Code

• The section contains multiple conditional formulas, time-dependent thresholds, and separate rules for two different offices with slightly different matching percentages and caps, making it dense and cross-referential.

Campaign and Governmental Conduct Code

• The section references Section 1.140 and the Political Reform Act without defining what those conditions or reporting requirements actually are, requiring readers to look elsewhere to understand what conduct triggers termination.

Campaign and Governmental Conduct Code

• The section contains multiple overlapping restrictions and exceptions (especially in subsection (a)) that require careful reading to understand what is and is not permitted.

Campaign and Governmental Conduct Code

• The repayment section contains multiple penalties and conditions (excess payments, improper expenditures, spending-ceiling violations) that operate under different triggers and with potentially overlapping consequences, making the full scope of liability unclear without careful reading.

Campaign and Governmental Conduct Code

• The provision has multiple nested thresholds, different rules for two offices, and a conditional activation clause that requires understanding the interplay between supplemental reporting and public financing certification.

Campaign and Governmental Conduct Code

• The section involves calculations (per-resident amounts, percentage deductions, timing), cross-references to other Charter sections, and parallel structures for two different election types that require careful parsing.

Campaign and Governmental Conduct Code

• The section relies heavily on cross-references to state law (California Government Code section 82047.5) and undefined parallel obligations ('as required by either state or local law'), which requires readers to consult multiple sources to understand full compliance duties.

Campaign and Governmental Conduct Code

• The section contains numerous cross-references, nested exceptions, and varying requirements by ad type (print, audio, video, digital, mail) that make it difficult to determine what applies in a specific situation.

Campaign and Governmental Conduct Code

• The section contains multiple cross-references to the Political Reform Act, detailed apportionment rules for multi-candidate communications, and granular reporting requirements spread across several subsections that require careful reading to understand all obligations.

Campaign and Governmental Conduct Code

• The apportionment rules for multi-candidate communications in subsection (a) and the detailed documentation requirements in subsection (b)(4) with sub-categories (A) and (B) create multiple moving parts that require careful tracking.

Campaign and Governmental Conduct Code

• The section lists eight separate duties with cross-references to the Charter and State law, making it harder for lay readers to understand the full scope and interplay of the Commission's responsibilities.

Campaign and Governmental Conduct Code

• The section's nested structure and reliance on undefined cross-references ('this Chapter,' 'enforcement authority,' 'Ethics Commission') may confuse readers unfamiliar with the broader San Francisco campaign finance framework.

Campaign and Governmental Conduct Code

• The phrase 'in furtherance of its duties under the Charter' is somewhat vague and could be interpreted broadly, potentially giving the Commission power beyond the specific examples listed.

Campaign and Governmental Conduct Code

• The phrase 'does not directly affect the jurisdiction of the Board of Supervisors or the City and County to control campaign contributions' is a double negative nested in legal language that ordinary residents may struggle to parse.

Campaign and Governmental Conduct Code

• The definitions are numerous and often cross-reference other code sections and state law; the 'officer of the City and County' definition in particular lists many boards and commissions with nested parenthetical clauses that make it dense and difficult to parse.

Campaign and Governmental Conduct Code

• Subsections (d), (e), and (f) contain multiple cross-referenced conditions and overlapping rules about contributions and bundling that could be simplified.

Campaign and Governmental Conduct Code

• The Executive Director's open-ended discretion to require 'additional training sessions' without defined criteria, frequency, or standards could be unclear in application.

Campaign and Governmental Conduct Code

• Subsection (a) contains a lengthy conditional clause ('If any lobbyist employs or requests, recommends or causes a client...') that makes the rule's scope somewhat difficult to parse on first reading.

Campaign and Governmental Conduct Code

• The section's enforceability depends on understanding the cross-referenced lobbyist registration requirements, deadlines, and exemptions elsewhere in the Chapter—a reader cannot fully understand this rule in isolation.

Campaign and Governmental Conduct Code

• Subsection (b) contains a long, nested definition of what fundraising solicitations must be retained, with multiple clauses describing different types of committees and ballot measures.

Campaign and Governmental Conduct Code

• Subsection (a) contains multiple embedded procedural requirements (notice periods, calendar requests, Executive Director notifications) that interact in ways requiring careful reading to fully understand the reduction/waiver process.

Campaign and Governmental Conduct Code

• Subsection (c) contains multiple nested conditions about when penalties are considered 'imposed' and when final determinations occur, making it lengthy and difficult to parse.

Campaign and Governmental Conduct Code

• The section references compliance with Section 1.515 without defining what those reporting requirements are, requiring readers to consult another section to understand the full obligation.

Campaign and Governmental Conduct Code

• The section cross-references multiple Charter sections and involves layered enforcement mechanisms (administrative, civil, and criminal) with varying penalty amounts based on different conditions, making it difficult for a lay reader to grasp the full enforcement landscape.

Campaign and Governmental Conduct Code

• The section uses multiple layers of nested clauses and repetitive phrasing ('Section, subsection, subdivision, sentence, clause, phrase or portion') that could be simplified without changing meaning.

Campaign and Governmental Conduct Code

• The provision's reference to the state law 'as said Act reads on the date this ordinance is adopted and as said Act may be amended from time to time' creates a potentially evolving standard that requires readers to track both the current state law and any future amendments to understand what this ordinance means at any given time.

Campaign and Governmental Conduct Code

• The section incorporates an external state regulation by reference and specifies that amendments to that regulation automatically become part of San Francisco's code, which can make it hard for residents to know what the actual current rules are without consulting the state regulation.

Campaign and Governmental Conduct Code

• The section references three other sections (3.1-101, 3.1-102, 3.1-103) and requires understanding what Form 700 statements, Sunshine Ordinance declarations, and ethics training certificates are in order to fully grasp what's being tracked.

Campaign and Governmental Conduct Code

• Subsection (c) contains multiple overlapping notice requirements with different timelines (30 days for department heads to file, 15 days to notify Ethics Commission) and unclear role divisions between appointing officials and commission secretaries.

Campaign and Governmental Conduct Code

• The section relies on undefined external references (Section 3.1-107 and unspecified 'other Sections') that readers cannot evaluate without consulting multiple parts of the code.

Campaign and Governmental Conduct Code

• The definition uses multiple overlapping categories (director, officer, partner, trustee, employee, position of management) to capture business positions, which could benefit from clearer organization or examples.

Campaign and Governmental Conduct Code

• The section contains nested conditionals (unless/provided, however) and cross-references to undefined terms ('Disclosure Category 1' and scope determinations) that require reading other parts of the Chapter to fully understand.

Campaign and Governmental Conduct Code

• The rule relies heavily on external reference to Proposition Q (from 1993) and undefined departmental designation processes, making it difficult for a reader to fully understand without additional context.

Campaign and Governmental Conduct Code

• The section consists of a dense table with over 250 designated positions and their corresponding disclosure categories, which makes it difficult for a typical reader to quickly understand whether their role is covered and what they must disclose.

Campaign and Governmental Conduct Code

• The section is presented as a bare table without explanation of what 'Disclosure Categories' means or what Category 1 requires, making it hard for a non-specialist to understand the actual obligations.

Campaign and Governmental Conduct Code

• The disclosure rule spans multiple business categories (art buying/selling, security systems) and extends to past activity (two years) and future possibility (foreseeably), creating ambiguity in what exactly must be reported.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 2' without defining it in this excerpt, requiring readers to cross-reference other sections to understand what must actually be disclosed.

Campaign and Governmental Conduct Code

• The section references an external standard (Sec. 3.1-500) for Board members and uses a cross-referenced disclosure category system that requires readers to understand what 'Category 1' and 'Category 2' mean, neither of which is defined in this excerpt.

Campaign and Governmental Conduct Code

• The section consists entirely of a long repetitive table with 79 positions, making it difficult to scan or understand the underlying policy without additional context about what Category 1 disclosure actually requires.

Campaign and Governmental Conduct Code

• The disclosure requirement is stated in abstract terms ('services, supplies, materials, machinery or equipment of the type used') that require readers to understand what kinds of goods the department actually buys, making it hard to know exactly what must be disclosed without additional context.

Campaign and Governmental Conduct Code

• This section's meaning depends entirely on understanding what 'Disclosure Category 1' requires, which is defined elsewhere in the Code and not explained here.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 2' without defining it in the text itself, requiring readers to look elsewhere in the Code to understand what disclosures are actually required.

Campaign and Governmental Conduct Code

• The section consists mostly of a long table of job titles with assigned disclosure categories; it lacks explanation of what Category 1 and Category 2 actually require, forcing readers to cross-reference elsewhere in the code.

Campaign and Governmental Conduct Code

• The disclosure requirements are presented as a single run-on sentence with multiple nested categories (business entities, income sources, employee income, real property) that could be clearer if separated into a bulleted or numbered list.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 2' and 'Category 1' without defining what those categories require, making it hard to understand the full scope of obligations without consulting other parts of the code.

Campaign and Governmental Conduct Code

• The section requires cross-reference to other parts of the code to understand what 'Disclosure Category 1' and 'Disclosure Category 2' actually entail; the full scope of obligations is not self-contained in this text.

Campaign and Governmental Conduct Code

• The section mixes the substantive disclosure rule with a detailed table of positions and categories, and references an external Proposition Q that is not defined here, making it difficult to understand the full scope without additional context.

Campaign and Governmental Conduct Code

• The section is largely a table of positions and disclosure categories with minimal explanatory text; readers unfamiliar with Category 1 disclosure requirements or the department's role may need to consult related sections to understand the full context and obligations.

Campaign and Governmental Conduct Code

• The section references another section (Sec. 3.1-500) for the District Attorney position itself and requires readers to understand the relationship between different disclosure categories defined elsewhere in the code.

Campaign and Governmental Conduct Code

• The section is a bare table with no explanatory text about what 'Disclosure Categories' or 'Category 1' means, leaving readers needing to consult other code sections to understand the actual requirements.

Campaign and Governmental Conduct Code

• The section relies on the definition of 'Disclosure Category 2' stated above it, making it hard to understand in isolation what must actually be disclosed without reading the category definition.

Campaign and Governmental Conduct Code

• The section consists entirely of a long table with 51 positions and offers no explanation of what 'Disclosure Categories' means, what 'Category 1' entails, or why certain positions are designated—readers must cross-reference other Code sections to understand the substance.

Campaign and Governmental Conduct Code

• The section is presented as a table without explanatory text, making it unclear what 'Category 1' actually requires or how it connects to the broader disclosure framework.

Campaign and Governmental Conduct Code

• The section is a bare table with no explanation of what 'Disclosure Categories' or category '1' means, leaving readers without context for why these positions are listed or what obligations follow.

Campaign and Governmental Conduct Code

• The section mixes a general disclosure rule (Category 2 definition) with a lengthy position-by-position table without clear organization, making it hard to scan and understand which jobs fall under which category.

Campaign and Governmental Conduct Code

• The table-format rule references an undefined 'Disclosure Category 1' without explaining what information must be disclosed or the process for filing.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 2' without defining it in this text, requiring readers to consult other sections of the Code to understand what specific items must be disclosed.

Campaign and Governmental Conduct Code

• The section references undefined disclosure categories (1-4) whose substantive requirements are stated in subsections (a)-(c), making it difficult to understand what each position must actually disclose without cross-referencing multiple provisions.

Campaign and Governmental Conduct Code

• The section contains three overlapping disclosure categories with different scopes, cross-references to Proposition Q, and an extensive multi-department position table, making it difficult to determine quickly which disclosure rules apply to a specific job.

Campaign and Governmental Conduct Code

• The definition of what must be disclosed is broad and somewhat circular ('provide services of the type utilized by the Health Authority'), leaving room for interpretation about which organizations qualify.

Campaign and Governmental Conduct Code

• The section is presented as a bare table without explanatory text about what 'disclosure categories' mean or why these positions warrant category 1 classification, requiring readers to consult other code sections to understand the full requirement.

Campaign and Governmental Conduct Code

• This section's meaning depends entirely on consulting a separate section (3.1-510), making it difficult to understand independently what disclosure obligations actually apply.

Campaign and Governmental Conduct Code

• This section is part of a larger conflict-of-interest disclosure scheme that requires cross-reference to the full definitions of Disclosure Categories 1 and 2 elsewhere in the Code to understand what must actually be reported.

Campaign and Governmental Conduct Code

• The section is a bare table with no explanatory text, making it unclear to a non-specialist what 'Disclosure Category 1' actually requires or why these specific positions were chosen.

Campaign and Governmental Conduct Code

• The section cross-references 'Prop Q' (Proposition Q from 1993) and 'Delegated Departmental Purchasing' without defining them in this text, making it hard for readers unfamiliar with those terms to fully understand the scope of disclosure for Category 3 positions.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 2' and 'Disclosure Category 1' without defining what those categories require beyond a single sentence, forcing readers to consult other parts of the Code to understand the full scope of disclosure obligations.

Campaign and Governmental Conduct Code

• The section is a bare list of positions with minimal explanation of what disclosure duties actually attach or what 'Category 1' entails, requiring readers to cross-reference other parts of the Code to understand the legal obligation.

Campaign and Governmental Conduct Code

• The disclosure rule references a separate 'Disclosure Category 1' (implied but not defined in this section), making it difficult to understand what the Commissioner must disclose compared to other positions without consulting related Code sections.

Campaign and Governmental Conduct Code

• The section is extremely sparse and uses a table format that separates positions from disclosure categories; the relationship between 'Disclosure Category 2' and the designated positions is implicit rather than clearly stated in narrative form.

Campaign and Governmental Conduct Code

• The section combines a general disclosure rule with a detailed two-part table listing positions and categories, making it harder to parse the actual requirements without cross-referencing the disclosure categories defined elsewhere in the Code.

Campaign and Governmental Conduct Code

• The section appears incomplete or excerpted, making it unclear whether these are the only positions, what the full disclosure requirements are, or what authority establishes them.

Campaign and Governmental Conduct Code

• The section is organized as a two-column table that cross-references another section (Sec. 3.1-500) for the Mayor's specific requirements, making it necessary to consult multiple sources to understand the full disclosure obligation.

Campaign and Governmental Conduct Code

• The section consists primarily of a lengthy table with dozens of job titles and category assignments, making it hard to discern the underlying principles without examining many entries.

Campaign and Governmental Conduct Code

• The section mixes a definition of Category 2 with a lengthy table of positions and their assigned categories, making the overall structure harder to parse and the relationship between the text and table unclear.

Campaign and Governmental Conduct Code

• The section references an undefined 'Disclosure Category 1' and 'Disclosure Category 2' without explaining what information must actually be disclosed under each category, making it incomplete as written.

Campaign and Governmental Conduct Code

• The section consists entirely of a disclosure category definition followed by a long table of positions with assigned categories; the logic connecting category level to position is not explained in the text itself.

Campaign and Governmental Conduct Code

• The section contains 95+ designated positions scattered across two disclosure categories with inconsistent assignment patterns (many similar job titles assigned to different categories), making it difficult to determine which disclosure requirement applies to a specific role.

Campaign and Governmental Conduct Code

• The section consists almost entirely of a long table of 57 job titles with category assignments; readers need to cross-reference their position in the table to understand their obligations, and the substance of what 'Disclosure Category 2' actually requires is stated only in the opening sentence.

Campaign and Governmental Conduct Code

• The section is a long tabular list with 100+ position titles organized by department and bureau, making it difficult to navigate or understand the full scope of coverage without careful review.

Campaign and Governmental Conduct Code

• The definition of Disclosure Category 2 is a single long sentence with multiple nested clauses and conditions, making it difficult to parse what financial interests must be disclosed.

Campaign and Governmental Conduct Code

• The section is extremely sparse and appears to be a stub referring to a disclosure table; the full substance likely depends on understanding what 'Category 1' disclosure actually requires, which is defined elsewhere in the Code.

Campaign and Governmental Conduct Code

• The section references a broader disclosure framework (Disclosure Category 2) without fully defining what Category 1 requires, making it hard to understand the actual scope of obligations for different positions without consulting other code sections.

Campaign and Governmental Conduct Code

• The section mixes a definition of Disclosure Category 2 with a long, repetitive two-column table of job titles and categories, making it hard to parse the overall rule and locate specific positions.

Campaign and Governmental Conduct Code

• The section references external disclosure categories without defining them in the text, requiring readers to consult cross-referenced conflict-of-interest rules to understand what must actually be disclosed.

Campaign and Governmental Conduct Code

• The section is a bare table with minimal explanation of what these positions do, their powers, appointment process, or what Category 1 disclosure actually requires—readers must cross-reference other Code sections to understand the full context.

Campaign and Governmental Conduct Code

• The section cross-references two disclosure categories with different scopes, requires understanding of geographic and temporal qualifiers ("within two miles," "within the past two years"), and includes a detailed position table that may not capture all role variations.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 2' without defining it in this excerpt, and references a broader disclosure framework that requires cross-reference to understand the full scope of disclosure obligations.

Campaign and Governmental Conduct Code

• The section mixes substantive disclosure rules in subsection (a) with an extensive table of 60+ designated positions and categories, making it lengthy and requiring cross-reference to understand which jobs have which disclosure obligations.

Campaign and Governmental Conduct Code

• The section references 'Category 1' and 'Disclosure Categories' without defining what information must actually be disclosed in this section; readers must cross-reference other parts of the Code to understand specific requirements.

Campaign and Governmental Conduct Code

• The section references Disclosure Category 1 without defining what that category requires; readers must cross-reference another part of the Code to understand the actual disclosure obligations.

Campaign and Governmental Conduct Code

• The section is presented as a bare table without explaining what Category 1 disclosure actually requires, leaving readers unclear about what information must be disclosed and why.

Campaign and Governmental Conduct Code

• The section consists almost entirely of an unannotated table with many job titles and category numbers, making it difficult to understand without cross-referencing other sections (Sec. 3.1-500, Sec. 3.1-510) that define what Category 1 actually requires.

Campaign and Governmental Conduct Code

• The section uses multiple nested disclosure categories with varying scopes across six different job titles, requiring readers to cross-reference tables and regulatory language to understand their obligations.

Campaign and Governmental Conduct Code

• The section references 'Disclosure Category 1' and 'Category 2' without defining what those categories require, making it impossible to understand the actual scope of disclosure obligations from this section alone.

Campaign and Governmental Conduct Code

• The section uses nested conditional language ('which has submitted a proposal to enter into or which has entered into') that could be clearer about the temporal scope and whether past, present, or prospective contracts all trigger disclosure.

Campaign and Governmental Conduct Code

• The section's meaning depends entirely on understanding what ordinance it refers to and the Political Reform Act's requirements, neither of which are explained here, making it difficult for a lay reader to understand the practical significance.

Campaign and Governmental Conduct Code

• The section uses a table format with asterisks and cross-references to state law (Government Code sections 87200 and 87314) that may confuse readers unfamiliar with how disclosure categories and state requirements work together.

Campaign and Governmental Conduct Code

• The section combines a broad construction rule, a carve-out for protected labor activities, and an exception for procedural errors, requiring readers to hold multiple concepts in mind.

Campaign and Governmental Conduct Code

• Subsection (c) is lengthy and establishes a detailed governance structure with multiple interlocking deadlines (initial appointments by day 60, first review by June 30, 2024, ongoing reviews every other year, sunset in 2030), roles, and data-reporting requirements that require careful tracking.

Campaign and Governmental Conduct Code

• The definitions cross-reference other departments and regulations (Building Code, tax code), and the 'permit consultant' definition has multiple exclusions that require careful parsing.

Campaign and Governmental Conduct Code

• This section cross-references multiple California Government Code sections (87100 et seq. and 1090 et seq.) without defining what those mean, requiring readers to consult state law to understand the full scope of prohibited interests.

Campaign and Governmental Conduct Code

• The interaction between the broad prohibition and the two enumerated exceptions—particularly exception (ii) which allows participation in selecting oneself as chair—creates potential ambiguity about what conduct is actually permitted.

Campaign and Governmental Conduct Code

• The standard for voiding a decision requires proving both willfulness and a failure to act with 'disinterested skill, zeal, and diligence primarily for the benefit of the City'—a multi-part legal test that may be difficult to apply consistently.

Campaign and Governmental Conduct Code

• The section contains multiple subsections with cross-references to state law, definitions of 'restricted source' that rely on other Code sections, and nuanced rules about intermediaries and indirect gift arrangements that create overlapping prohibitions.

Campaign and Governmental Conduct Code

• Section (a)(1) contains multiple interlocking prohibitions, carve-outs, and examples that make it difficult to follow the full scope of what is and is not allowed.

Campaign and Governmental Conduct Code

• The section uses crossed negatives ('does not include') and multiple jurisdictional references that require careful parsing, and the $2,500 threshold is now obsolete given inflation since the rule was written.

Campaign and Governmental Conduct Code

• The exceptions in subsection (b) are numerous and somewhat overlapping, particularly the distinction between acting as a member/employee versus merely acting as an agent of an officer, which may be difficult to apply in borderline cases.

Campaign and Governmental Conduct Code

• The definition of 'confidential or privileged information' relies on two external legal frameworks (Sunshine Ordinance and Public Records Act), making its scope dependent on understanding those separate rules.

Campaign and Governmental Conduct Code

• The section contains multiple overlapping restrictions with different timeframes, definitions, and carve-outs that require careful cross-referencing (e.g., subsection (b)(1) redefines 'department' for certain former officials).

Campaign and Governmental Conduct Code

• The phrase 'provide assistance to or otherwise aid or abet' uses overlapping legal language that means roughly the same thing, making the rule longer and potentially more confusing than necessary.

Campaign and Governmental Conduct Code

• The section refers to 'this Chapter' without specifying which Chapter, requiring readers to trace back to understand the full scope of what violations it protects against.

Campaign and Governmental Conduct Code

• The section is entirely a cross-reference to multiple Charter sections; someone trying to understand the Commission's actual powers must consult external documents, making direct understanding difficult without those sources.

Campaign and Governmental Conduct Code

• The definition of 'Developer' is lengthy and contains nested examples (LLCs, partnerships) that may confuse readers about which individuals or entities bear responsibilities under the chapter.

Campaign and Governmental Conduct Code

• The section contains multiple nested subsections with different timing, definition cross-references, and overlapping requirements that create room for interpretation—particularly around what constitutes a 'contact' and which nonprofits must be reported.

Campaign and Governmental Conduct Code

• The section contains multiple cross-referencing conditions with overlapping timeframes and exceptions that require careful reading to understand when the prohibition applies and when it does not.

Campaign and Governmental Conduct Code

• The section's effectiveness and meaning depend entirely on the regulations the Ethics Commission adopts, which are not provided in the Code text itself, making it difficult for the public to know what the actual obligations are.

Campaign and Governmental Conduct Code

• The provision relies entirely on cross-reference to Section 3.242(d), making it impossible to understand the actual penalties without consulting another section of the Code.

Campaign and Governmental Conduct Code

• The section references multiple external documents (Charter Section C3.699-13 and accompanying regulations) whose content is necessary to fully understand investigation procedures, making it difficult for a citizen to grasp the complete process from this text alone.

Campaign and Governmental Conduct Code

• The section contains multiple cross-referenced procedures (subsections a–g) with conditional pathways for different complaint types, 60-day response timelines, and escalation procedures that require careful reading to understand the full workflow.

Campaign and Governmental Conduct Code

• Multiple definitions contain overlapping or similar concepts (improper government activity vs. unlawful activity), and some definitions are themselves multi-clause with internal exceptions, which may create confusion about precise application.

Campaign and Governmental Conduct Code

• The section contains multiple cross-references to other code sections and the Charter, and subsection (d) creates several overlapping exceptions that may be unclear in interaction.

Campaign and Governmental Conduct Code

• Subsection (c) contains four separate exceptions with multiple conditions and sub-clauses that require careful reading to understand what the Controller can disclose and when.

Charter

• The section includes multiple procedural layers (Civil Service Commission setting, Controller implementation, coordination with budget cycles, initial setup period rules) that could be clearer about the actual decision-making flow.

Charter

• The section contains multiple overlapping rules about special meetings in different locations with varying notice periods (24 hours for general special meetings, 15 days for out-of-City Hall meetings, plus committee referral), making it easy to misapply.

Charter

• The section contains multiple conditional provisions, cross-references to Government Code and the Charter, and layered requirements about when teleconferencing is allowed that require careful reading to parse fully.

Charter

• The section mixes procedural rules (readings, voting) with substantive restrictions (one subject per ordinance, effective dates, franchise timelines) across multiple paragraphs, making it dense and cross-referenced.

Charter

• The section contains multiple conditional clauses and cross-references (Sections 3.103 and 9.104) that require readers to consult other parts of the Charter to understand the full scope and exceptions.

Charter

• The section contains multiple overlapping requirements about notice timing (5 days, 18 hours, 36 hours) and different publication thresholds for ordinances versus resolutions that could be consolidated or clarified.

Charter

• The exception clause references an external ordinance from 1932 by name and date, requiring readers to consult other documents to understand the full scope.

Charter

• The section involves multiple procedural steps, cross-references, and conditional requirements (e.g., what happens if the hearing requirement is missed) that make it somewhat difficult for a layperson to follow the full process.

Charter

• The section uses multiple nested negatives and exceptions that require careful reading: prohibited interference, except for inquiry, except for testimony, except for legislation on non-specific matters.

Charter

• The section contains 20 distinct powers and responsibilities with multiple sub-conditions and cross-references (particularly Section 3.103 and 3.104), making it dense and difficult to navigate at a glance.

Charter

• The section references an external ordinance for disaster succession without specifying which one, requiring readers to consult additional documents to understand the complete chain of command.

Charter

• The section has multiple conditional paths (approval, disapproval with veto override, inaction) and cross-references to other Charter sections that affect interpretation.

Charter

• The section lists nine distinct responsibilities and powers spread across multiple numbered items with cross-references to other city commissions and exceptions, making it dense and somewhat difficult to parse the full scope of authority.

Charter

• This appendix is a table of contents listing 13 separate sections (F1.100 through F1.113) without providing the actual text of those sections, making it impossible to assess the full scope of duties or identify specific obligations.

Charter

• The phrase 'to the extent law permits' and cross-reference to 'this Article IV' require readers to consult other parts of the Charter to understand which rules actually apply to which bodies.

Charter

• The section contains multiple cross-references to state law and the Charter, conditional pathways for different types of boards, different timelines for various steps, and nuanced rules about voter-approved versus ordinance-created bodies that create procedural complexity.

Charter

• The section spans six subsections with overlapping concepts (requirements in (a) and (b), policy statements in (c), enforcement in (d), and procedural matters in (e)–(f)), making it harder to isolate what actually binds appointing officers versus what is aspirational.

Charter

• The section has cross-references to other Charter sections (A8.409-4 and A8.590-5), a conditional clause about 45-day extensions that depends on rejection, and overlapping procedural steps that require careful reading to distinguish between proposal, approval, and ordinance enactment.

Charter

• The section references external state law (Government Code Title I, Division 4, Chapter 10) and a separate Charter section without defining them, making full understanding require consultation of those outside documents.

Charter

• The section involves multiple timelines (30 days for rehearing petition, 30 days after denial or new decision), cross-referenced legal standards (abuse of power, fraud, evidentiary justification), and the interplay between the hearing officer, applicant, Retirement System, and Board—requiring careful reading to understand the procedural flow.

Charter

• The section references the Charter, the Board of Supervisors' budget process, and Internal Revenue Code Section 401(a), creating cross-dependencies that may be unclear to lay readers without additional context.

Charter

• The section contains overlapping provisions about appointment procedures, term lengths with multiple exceptions, and succession rules that create a convoluted governance structure requiring careful cross-reference to Charter sections.

Charter

• The section references membership criteria set 'by ordinance' elsewhere, making the full scope of coverage non-obvious from this text alone.

Charter

• The section references 'this Charter' and the Health Service Board's role without defining these terms or explaining the relationship between the fund, the board, and the contribution requirements in detail.

Charter

• Subsection (a) contains a convoluted sentence about Board authorization and payment enumeration that is difficult to parse grammatically.

Charter

• The section cross-references 'this Article' and 'this Charter' without defining the full scope of those documents, making it unclear to a reader what specific budgetary and fiscal rules apply.

Charter

• The section contains multiple cross-references (Section 4.101(2), Section 15.105) and a detailed carve-out for insurance and indemnification authority that requires parsing several conditional clauses to understand the museums' powers.

Charter

• The section contains four nested numbered duties with multiple clauses and cross-references (e.g., 'Section 3.100'), making it dense and somewhat hard to parse for a general reader.

Charter

• The section involves cross-references to external conditions (the Brundage Collection's conditions and 'other gifts') that are not defined here, requiring readers to consult other documents to understand the full scope of the commission's duties.

Charter

• The section requires cross-reference to Sections 3.100 and 15.105 to fully understand appointment procedures and removal authority, which may confuse readers unfamiliar with the full Municipal Code.

Charter

• The section lists nine duties and two additional powers across multiple paragraphs with cross-references to other Charter sections, and the final paragraph adds a constraint with qualifications that requires careful reading to understand the limits on board member conduct.

Charter

• Subsection (b) is a long, complex sentence with multiple conditions and cross-references (Government Code Section 54953(b), Charter Section 10.101) that makes it difficult to parse the eligibility rules for remote participation.

Charter

• The section contains six distinct subsections (GENERAL, GENERAL PLAN, REFERRAL OF CERTAIN MATTERS, PERMITS AND LICENSES, ENFORCEMENT, ZONING AMENDMENTS, ZONING ADMINISTRATOR, and CONDITIONAL USE) covering different Commission powers, with detailed procedural rules, timelines, and approval thresholds that require careful reading to understand the full scope.

Charter

• Section (a) contains intricate appointment procedures, Charter cross-references, automatic approval triggers, and a historical staggering mechanism (lots determination on July 1, 2002) that may confuse readers unfamiliar with municipal governance structures.

Charter

• The section lists seven distinct duties across multiple paragraphs with cross-references to other code sections, making the full scope of the Commission's authority somewhat hard to grasp quickly.

Charter

• The section references Charter sections (3.100, civil service, and ethics provisions) that are external to this section, requiring readers to consult other parts of the Code to fully understand the scope of the Commission's authority and limitations.

Charter

• The section contains intricate conditional rules about when appointments become operative depending on whether the Board acts, fails to act, or acts differently for anticipated versus immediate vacancies, requiring careful parsing of multiple time-dependent scenarios.

Charter

• The section references two external code sections (3.100 and 15.105) and uses the phrase 'except where the Charter grants such authority to another officer or department,' creating potential ambiguity about the Commission's actual powers without consulting those other sources.

Charter

• Subsection (c) contains outdated transition language from a 2008 Charter amendment with specific staggered-term provisions that are no longer operative but remain in the Code.

Charter

• Subsection 2 contains a long, nested conditional sentence about underground parking that combines multiple approvals, conditions, and revenue-sharing provisions in a single clause.

Charter

• The section's actual meaning depends heavily on external documents (the Burton Act and 1969 Transfer Agreement) that are not reproduced here, making it difficult for a reader to understand the Commission's full scope of authority without consulting those sources.

Charter

• The section references external sections (3.100 and 15.105) for appointment and removal procedures, making the complete rule distributed across the Code.

Charter

• The section involves multiple cross-references (Section 15.105), overlapping appointment and approval procedures, and staggered term mechanics that require careful parsing to understand the full governance structure.

Charter

• The section mixes current operational rules (subsection a), future qualification requirements (subsection b), and a one-time transition rule tied to a specific date (subsection c), requiring readers to track which rules apply when.

Charter

• The section combines multiple governance roles (appointment process, oversight duties, appeals jurisdiction, and rule-making authority) with cross-references to other Charter sections and Building Code provisions, making it lengthy and multi-layered.

Charter

• The section mixes appointment procedures, eligibility criteria, term length, removal rules, and operational requirements across multiple subsections, requiring readers to track multiple interconnected rules about the same body.

Charter

• The section contains multiple nested duties (subsections a–g), cross-references to the referral process, and conditional language about timing and exceptions that require careful reading to fully understand.

Charter

• The section mixes multiple unrelated provisions: general department management authority, the appointment and reorganization powers, and a specific restriction on dual employment—making the overall structure somewhat disjointed and potentially confusing on first read.

Charter

• The staffing provisions involve multiple interlocking deadlines, reports, and procedures spanning different calendar years and fiscal years, with conditional language that requires careful tracking of when actions must occur.

Charter

• The phrase 'during a conflagration' and the broad grant of demolition authority in the third paragraph may be unclear to residents about what triggers and limits this emergency power.

Charter

• The section contains multiple cross-references to the Charter, the Administrative Code, and other sections (e.g., Section 4.132), making it difficult for a non-expert to understand the full scope of authority without consulting other documents.

Charter

• The section's meaning depends on understanding Section 6.101 and the planned merger, making it difficult to understand in isolation.

Charter

• The section contains multiple cross-references (Sections 4.101-4.104), a staggered term structure with different expiration dates, and nuanced appointment and confirmation procedures that make the full governance structure difficult to follow.

Charter

• Subsection (b) includes boilerplate language about Government Code Section 87103 and conflict-of-interest law that, while legally important, may confuse readers about the practical composition requirements.

Charter

• The section contains multiple detailed subsections covering appointment procedures, qualifications, landmark and district designations, certificates of appropriateness, Mills Act contracts, and other duties, with intricate appeal procedures and cross-references to the Planning Code that make it lengthy and difficult to navigate as a whole.

Charter

• Subsection (e) contains intricate conditions and cross-references (Government Code 3304, the 60-day limitation, exigent circumstances) that determine when DPA can bypass the Chief of Police and file charges directly.

Charter

• The section contains overlapping provisions about term limits, staggered initial appointments, and vacancy filling that span multiple paragraphs and require careful reading to understand fully.

Charter

• The section cross-references Section 15.100 for conflict-of-interest rules without restating them, and uses the phrase 'civil service provisions of this Charter' which requires knowledge of other parts of the Charter to fully understand.

Charter

• The section covers multiple distinct powers (rulemaking authority, veto procedure, attorney relationship, and ballot-submission authority) in a single provision, which could be clearer if organized separately.

Charter

• The section delegates rule-making authority to the City without specifying what conflict of interest laws actually exist or what they prohibit, making it difficult for a reader to know what specific conduct is prohibited.

Charter

• The section contains multiple overlapping removal processes (subsections a, b, c) with different procedures for different officials, cross-references between subsections, and conditional rules that require careful reading to apply correctly.

Charter

• Subsection (b)(1) contains multiple overlapping approval processes (nomination, public hearing, 60-day clock, deemed approval, and effective date rules) that interact in ways requiring careful reading.

Charter

• Subsection (c) contains overlapping and somewhat redundant language about transition procedures, director continuity, and Charter cross-references that could be streamlined for clarity.

Charter

• The appointment process involves multiple appointors and a 60-day approval timeline with automatic approval conditions, making the mechanism somewhat intricate for a casual reader.

Charter

• The first subsection contains an elaborate multi-step process with conditional branches, time limits, and procedural rules for resolving conflicts of interest, making it significantly longer and more convoluted than other subsections.

Charter

• The section interweaves governance structure, funding sources (direct City appropriation and court-collected fees), personnel authority, and access rights across six dense paragraphs with multiple cross-references to state law and the Charter.

Charter

• The section references the Charter, uses nested numbering with both numbers and letters, and interweaves interim and final appropriations timelines in a way that requires careful parsing.

Charter

• Subsections (g) and (h) contain nested conditions, cross-references to other sections, and a multi-step amendment process with deemed-approved language that makes the fixed budgetary cycle rules difficult to follow.

Charter

• The section's role in the broader budget process and what happens with the Controller's opinion are not explained, making it hard for readers to understand the practical significance or consequence of this step.

Charter

• The section uses nested conditional language and cross-references to 'the Mayor's proposed' amounts, making it easy to misunderstand the constraints on the Board's amendment authority.

Charter

• The section contains multiple conditional clauses, cross-references to different fund types, and overlapping time limits that require careful reading to fully understand the veto and override process.

Charter

• The section mixes three distinct rules (internal transfers, budget amendments, and emergency ordinances) that operate under different approval processes and conditions, requiring careful parsing of which rule applies when.

Charter

• The section references external legal frameworks (California Constitution and state law) without explaining them, making it difficult for ordinary readers to understand what "in accordance with" means in practice.

Charter

• The section lists eight separate exemptions to voter approval, each with different conditions and cross-references, making it difficult to quickly understand which bonds require voter consent and which do not.

Charter

• The section contains multiple conditional exemptions with specific dates, dollar amounts, and cross-references to other ordinances that make it difficult for a non-specialist to understand the full scope of when voter approval is required.

Charter

• The single sentence structure is long and heavily nested, making it difficult to parse the sequence of steps and conditions required.

Charter

• The section contains multiple cross-references (Sections 3.105 and 9.113) and uses technical financial terminology (unencumbered balances, financing leases, exchange of payments) that may be unclear to non-specialists.

Charter

• The section's full meaning depends on understanding the referenced Charter section B7.305, which is not provided here and may contain material conditions or limitations.

Charter

• Section (a) is a single 100+ word sentence with multiple embedded clauses and exceptions that make it difficult to parse; section (b) involves cross-references to bond terms and legal availability concepts that require specialized knowledge.

Charter

• The section contains multiple conditional formulas, cross-references between subsections, and layered triggers that interact with inflation and prior-year calculations, making it difficult to follow the full mechanics.

Charter

• The section relies heavily on cross-reference to Section 9.114 for the actual requirements and 'budget description' details, making it difficult to understand the full scope of obligations without consulting another section.

Charter

• The sentence structure is long and nested, making it hard to identify the actual obligation (the word 'should' rather than 'shall' also creates ambiguity about whether this is mandatory).

Charter

• The section contains multiple overlapping thresholds (revenue, expenditure, term length, modification impacts) across three subsections with varied conditions, making it dense and cross-referential.

Charter

• The section involves multiple deadlines, moving targets (different departments included at different times), and cross-references to mayoral and board procedures that may be detailed elsewhere in the code.

Charter

• The section involves multiple actors (Controller, Mayor, Board of Supervisors), procedural deadlines, voting thresholds, and cross-references to other administrative requirements that require careful reading to understand the full process.

Charter

• The 'Discrimination' definition lists many overlapping or interrelated categories in a single definition, making it dense; the 'Initiative' definition has two numbered sub-parts with multiple conditions that require careful parsing.

Charter

• The section combines multiple distinct departmental responsibilities (merit system, health/safety, workers' compensation, labor relations) with cross-references to other Charter sections, making it dense and requiring understanding of related governance structures.

Charter

• The section contains 19 separate categories with varying conditions, cross-references to other Charter provisions, and nuanced caps on certain exemptions that require careful parsing to understand fully.

Charter

• The section mixes procedural requirements (Board approval, Director certification) with conditional language (reasons beyond control) that could benefit from clearer organization of the two conditions for renewal.

Charter

• The section is a brief delegation that gains meaning only through cross-reference to the Charter, ordinances, and state law—a reader cannot fully understand the actual election rules from this section alone.

Charter

• The section coordinates multiple election cycles, exempts Board of Supervisors to another section, and includes a non-standard five-year term exception that requires cross-reference to Section 3.101 term limits to fully understand.

Charter

• Subsection (c) contains nested conditional clauses about election timing (120 days, one year, scheduled elections) that could confuse readers about when exactly the appointment ends.

Charter

• Subsections (c) through (e) contain overlapping and somewhat repetitive logic about candidate elimination and vote transfer that could be streamlined for clarity.

Charter

• The term-limit and succession rules are intricate, with multiple conditional provisions about what counts as a full term and when people become eligible again after serving.

Charter

• The section contains multiple nested procedural rules about appointment, removal, appeals, and conflict-of-interest waivers that require careful reading to understand the full process and interplay between the Elections Commission, Civil Service Commission, and Board of Supervisors.

Charter

• The section contains multiple distinct rules about different roles (City employees generally, City Attorney, Sheriff) and conditional provisions (waivers, alternative plans based on elections and ballot measures), making it lengthy and somewhat hard to follow as a unified rule.

Charter

• The section contains eleven extremely long, repetitive boundary descriptions with numerous street-by-street sequences, compass directions, and cross-references to census tracts, making it difficult for most readers to visualize or verify district boundaries without mapping tools.

Charter

• The phrase 'except as otherwise provided in this Article' signals that this general rule has multiple exceptions defined elsewhere in the same Article, making the full legal effect difficult to assess without cross-referencing those sections.

Charter

• The section contains multiple conditional pathways for when and how initiatives appear on ballots, with different timing rules and signature thresholds that require careful reading to understand.

Charter

• The section relies heavily on cross-references to other Charter sections (9.106, 9.107, 9.108, 9.110, 14.101) whose content is not provided, making it difficult to understand the full procedural requirements without consulting those sections.

Charter

• The section contains multiple subsections with cross-references, conditions, and carve-outs (e.g., bond indenture exceptions, hydropower asset calculations, specific percentage thresholds) that make it dense and difficult to parse.

Charter

• The section contains eight distinct priority categories for fund use, cross-references to revenue bonds and general obligation bonds, and a specialized definition of 'non-airline revenues' that requires careful reading to understand the mechanism.

Charter

• The section involves multiple overlapping ownership, management, and employment relationships that require careful parsing to understand the division of authority.

Charter

• The section lists eight separate appropriations with varying funding mechanisms (some tax-based with specific rates, others discretionary), making it lengthy and requiring careful parsing to understand each entity's funding source.

Charter

• The section is lengthy and contains multiple nested subsections with cross-references, intricate funding formulas, and several interconnected planning requirements that make it difficult to follow holistically.

Charter

• The section contains multiple cross-referenced subsections with intricate timelines, baseline calculations tied to Controller computations, and interconnected planning cycles (Years 1–4 repeating every five years) that are difficult to parse without multiple readings.

Charter

• The section extensively cross-references Charter Section 16.108 and requires further ordinance implementation by the Board of Supervisors, making the full scope of the committee's powers dependent on documents outside this section.

Charter

• The section contains intricate cross-references to the Charter, Business and Tax Regulations Code, Planning Code, and California law, along with multiple conditional appropriation formulas, revenue-calculation methodology, and a complex interim inclusionary housing framework that spans subsections (c) through (g).

Charter

• The section uses nested legal terms ('renewal, extension, transfer or amendment') and assumes familiarity with what a 'franchise' means in municipal law, which differs from common usage.

Charter

• The section combines multiple requirements (document access, notice timing, and eight distinct triggering events in two separate lists) with cross-references to confidentiality rules and the Board's discretionary authority to lower thresholds, making it difficult to parse all obligations at once.

Charter

• The section uses multiple overlapping phrases ("relative solely to," "for that purpose") and parallel structure across two sentences that could be streamlined for clarity.

Charter

• This is a table of contents listing over 250 subsections covering multiple overlapping retirement systems with different rules for different cohorts of employees hired in different years, making it difficult to navigate without understanding the underlying organizational logic.

Charter

• This is a bare appendix listing section numbers without substantive rules; readers must cross-reference multiple sections elsewhere in the code to understand actual obligations and procedures.

Charter

• This is an appendix consisting entirely of section headings with no substantive text provided, making it impossible to assess the actual requirements, obligations, or rules it contains.

Charter

• The section contains multiple cross-references (Charter, Elections Code), procedural timelines, and definitions that interact in ways requiring careful coordination between election officials and project approvers.

Charter

• The section involves multiple cross-references to other code sections, intricate revenue-calculation rules, a phased implementation timeline (base year 2002-03, contributions from 2010-11 onward, spending proposals from 2028 onward), and conditional approval procedures that interact in layered ways.

Charter

• The section references an external fund (the Public Education Enrichment Fund) without defining it here, which requires readers to look elsewhere in the code to understand the funding source and mechanism.

Charter

• The section contains multiple cross-referenced studies, agencies, and components (equity analysis, professional development guidelines, neighborhood-specific metrics) that together create a dense procedural and substantive framework.

Charter

• The section involves multiple overlapping reporting deadlines (April 1 and January 31), cross-references to other sections (16.127-9, 16.127-5), and numerous required components spread across subsections (a)–(g), making it difficult to track all obligations at once.

Charter

• The section contains multiple conditional scenarios (audit failures, reserve policy failures, new revenues from voters, state LCFF funding changes, state preschool funding) with cross-references and nested subsections that make it hard to track all the circumstances under which reductions apply.

Charter

• The conditional 'in the event' clause in subsection (b) creates a complex trigger mechanism involving potential state actions, and the cross-reference to Charter Section 16.108 requires external knowledge to fully understand the remedy.

Charter

• The section refers to other sections (16.123-1 through 16.123-10) but does not appear in context, making it unclear what rules are actually subject to this sunset provision.

Charter

• The section uses defined terms ('watch law') and cross-references constitutional protections in a way that requires understanding both the statutory scheme and the underlying constitutional constraints.

Charter

• The section is lengthy with many subsections (a through l) that mix preamble/background (a–j) with operative definition and governance structure (l), making the core obligation somewhat diffuse.

Charter

• The section uses nested clauses and multiple goals (coordination, accessibility, effectiveness) that could be stated more directly.

Charter

• The section uses "shall invite" for some members but appears to mandate inclusion of department heads, creating ambiguity about whether participation is optional or required.

Charter

• The section contains multiple interrelated responsibilities, timelines, and cross-references (to the CCNA, DCYF, SFUSD, and Article IX) that create dependencies and layers of accountability across different agencies.

Charter

• The section involves cross-references to the Charter, multiple funding sources, and several interrelated staff responsibilities that could be clearer about which department has final authority.

Charter

• The section references multiple entities (Council, City departments, SFUSD, Board of Supervisors, Children and Youth Fund) and roles across subsections, and cross-references Article IX budget procedures, making the full scope of obligations difficult to track without reading the broader Code.

Charter

• The section contains multiple cross-references to other code sections (16.108(i)(1) and 16.127-5) that are necessary to understand the full scope of the CCNA and Plan requirements.

Charter

• The section involves multiple cross-referenced funds (Children and Youth Fund Baseline, PEEF, PEEF Baseline), overlapping review timelines, and conditional approval language ('on balance') that may be difficult for non-experts to parse.

Charter

• The section contains multiple cross-references (Children and Youth Fund Baseline, PEEF, PEEF Baseline, Plan and Outcomes Framework) that are not defined here, making it difficult for a reader unfamiliar with related ordinances to fully understand its scope and requirements.

Charter

• The section hinges on conditional events (Council ceasing to exist, voters removing Charter sections) and cross-references four other sections that readers would need to consult to understand the full scope of transferred duties.

Charter

• Section (m) and its five subsections create a nested structure that could be clearer; the relationship between the overarching goals (a–l) and the prioritized program areas (m)(1)–(5) is somewhat ambiguous.

Charter

• The section involves multiple phases of contributions across 20 years (2016 baseline through 2036-2037), with different escalation rules and technical definitions of 'discretionary revenues' that exclude specific tax increases, requiring careful attention to dates and conditions.

Charter

• The section contains ten subsections with overlapping categories and numerous examples, some with cross-references to other code sections, making it dense and somewhat difficult to parse comprehensively.

Charter

• The section contains eight detailed subsections with cross-references and conditional language (e.g., 'to the extent of' in (c), 'other than' in (e) and (g)) that require careful parsing to understand what is and is not excluded.

Charter

• The section is lengthy and contains multiple nested requirements, timelines, and cross-references (e.g., to Sections 16.128-3, 16.128-4, 16.128-7, 16.128-11, and Charter Section 16.108) that make it difficult to follow for a lay reader.

Charter

• The section references Sections 16.128-1 through 16.128-12 without providing details about what those sections cover, making it hard to understand the full scope of what can be implemented.

Charter

• The double negative structure ('No...shall be held invalid...unless') and the compound causation test ('substantial injury' AND 'different result probable') may be difficult for lay readers to parse.

Charter

• Without seeing the full regulatory framework (Sections 16.128-1 through 16.128-11), it is unclear what obligations or programs will lapse, making it difficult for residents to assess the practical impact of this sunset.

Charter

• The section contains dense cross-references to tax codes, charter provisions, and budget procedures, plus intricate rules about revenue adjustments, fund carryover, and budget deficit conditions that may be hard for ordinary residents to follow.

Charter

• The section contains eleven nested principles, multiple cross-references to the Charter and other ordinances, and layered authority provisions that require careful reading to understand implementation responsibilities.

Charter

• The section contains intricate fiscal provisions with conditional appropriation rules, reserve account mechanics, and multiple override scenarios (subsections d–1 through d–7) that make the funding mechanism difficult to follow.

Charter

• The rent-affordability calculations in subsection (e) are layered (e.g., 'rent restricted at 30% of 60% of Median Income' with household payment at 'not to exceed 30% of 15% of Median Income') and require cross-referencing multiple income definitions, making the operative rent levels hard to parse without detailed calculations.
• Subsection (d)(2)–(d)(3) contains intricate conditions for annual appropriation adjustments tied to discretionary revenue calculations and deficit thresholds, with multiple carve-outs and year-specific minimums that create overlapping rules.

Charter

• The section involves cross-references to other agencies, conditional effective dates, and interplay between discretionary spending and contractual obligations, making it somewhat difficult to parse.

Charter

• The section contains multiple operative dates, cross-references to prior versions of the Charter, provisions about amendment incorporation, and carve-outs for specific initiative ordinances, making it dense and difficult to follow without close reading.

Charter

• The sentence structure is densely packed with legal terms and multiple categories of legal instruments (rights, claims, actions, orders, obligations, proceedings, bond authorizations, contracts) that could be clearer if enumerated or explained with examples.

Charter

• The section consists largely of an unstructured list of 80+ Charter section references with varying formats (single sections, ranges, and partial sections), making it difficult to parse without the original 1932 Charter document.

Charter

• The section contains nested conditional provisions (offices 'for which this Charter does not provide') that require readers to understand both what the Charter creates and what it omits.

Charter

• The section contains multiple transitions with different effective dates and conditional language (particularly the Recorder-County Clerk consolidation with its two phases), making it difficult to track what happens when.

Charter

• The section references "this Charter" and "operative date" without defining them in the excerpt, making it difficult for readers unfamiliar with the Charter's context to understand the timeline and scope.

Charter

• The section's operative date is tied to a Charter's 'effective date,' which is not defined in this excerpt and creates ambiguity for someone reading this section in isolation.

Charter

• The section uses nested conditional clauses and cross-references the 1932 Charter, making it somewhat difficult to parse the precise conditions under which protections apply and transfer.

Charter

• The section references multiple other sections (Charter of 1932, Section 10.105, civil service rules) and uses dated operative-date language that makes it difficult to apply without understanding the full historical and regulatory context.

Charter

• The section refers to three other code sections (9.114, 9.115, 9.116) that define the actual requirements, making full understanding depend on consulting those sections elsewhere in the Code.

Charter

• The section contains extensive cross-references and a lengthy mapping of old Charter sections to new ordinance section numbers, making it difficult to follow without consulting multiple code documents.

Charter

• The preamble lists seven distinct purposes connected by semicolons, which can be hard to parse as a unified statement of intent.

Charter

• The preamble is lengthy with nine subsections covering multiple distinct policy goals, legislative findings, and interpretive directions that could be streamlined for clarity.

Charter

• Section (b) is lengthy and convoluted, with nested conditions and cross-references that make the taxi-transfer authority difficult to parse on first reading.

Charter

• The section contains multiple cross-referenced subsections with layered obligations (minimum standards, milestones, additional standards, reporting, climate planning) that may be difficult for a general reader to track holistically.

Charter

• The section contains multiple nested conditions, cross-references to other code sections, specific fiscal years, and intricate formulas for calculating adjustments that make it difficult for non-lawyers to understand how the fund actually works year to year.

Charter

• The section cross-references other sections (8A.103 and Section 4 of an unspecified measure) that are necessary to understand what performance standards are being evaluated.

Charter

• The interaction between subsection (a)'s two different rejection procedures (one for general changes, one for strategic route evaluations) and subsection (c)'s separate process for mid-year route abandonments creates multiple pathways that may be unclear to readers.

Charter

• Subsection (b) is a long, heavily parenthetical sentence with multiple conditional clauses and exclusions that obscures the core grant of authority to the Agency.

Charter

• The section references multiple external documents (Charter, Planning Code) and depends on understanding Section 8A.102(b)(5), making it hard to grasp in isolation.

Charter

• The section contains multiple nested membership requirements (at least 10 riders, at least 2 paratransit users, at least 3 seniors) that collectively may be difficult to track during actual appointments and could create overlapping quota categories.

Charter

• The section cross-references state law (Streets and Highways Code § 32657) and involves overlapping board memberships and ex officio roles that may be unfamiliar to typical readers.

Charter

• Subsection (b) contains multiple nested conditions (acquisition restrictions, funding floors, inflation adjustments, and Transit First Policy consistency) that interact in ways requiring careful cross-reference to Section 16.110 and other policy frameworks.

Charter

• The street-by-street route descriptions are long and require careful reading to visualize; clearer would be a map reference or simplified directional language.

Charter

• Section (a) contains ten numbered principles that are aspirational and somewhat overlapping in scope, making the core directive less sharply defined than a direct mandate.

Charter

• The preamble is lengthy and contains seven numbered policy goals with cross-cutting references to rates, bonds, labor, and environmental equity that may be difficult for readers to parse without seeing the operative sections that follow.

Charter

• Subsection (e) contains multiple nested conditions about voter approval, timing requirements, and exceptions that may be difficult for readers to parse on first reading.

Charter

• The section lists nine interrelated goals with some containing multiple embedded objectives (e.g., goal 4 combines land management, natural resources, hydroelectric operations, and habitat protection), making it dense and requiring careful parsing to understand the full scope.

Charter

• The section requires coordination across multiple entities (Public Utilities Commission, Board of Supervisors, General Manager) and three separate long-range planning documents with different time horizons and purposes, making implementation interdependent and potentially confusing.

Charter

• The section interweaves authorization authority, charter references, negative restrictions (what cannot be financed), procedural requirements (engineer and planning certifications), and state law incorporation, making it dense and cross-referential.

Charter

• The section contains multiple numbered requirements, cross-references to charter sections, bond resolutions, and state/federal law, plus delayed effective dates contingent on a 2002 election outcome, making it dense and multi-layered.

Subdivision Code

• This is a division heading introducing an entire code section with multiple parts; the full scope and specific requirements are in the subsections that follow this heading.

Subdivision Code

• Subsection (b) creates a hierarchy where state amendments can override local law, which may confuse readers about what rules actually apply to them.

Subdivision Code

• Subsection (c) layers multiple objectives together, and item (7) introduces alternative compliance pathways (on-site units, off-site construction, or in-lieu payments) that require cross-reference to other sections to understand fully.

Subdivision Code

• The section relies entirely on cross-reference to Chapter 87 without restating the core prohibitions or defining 'protected class' here, making it hard for a reader to understand what is actually prohibited without consulting another part of the code.

Subdivision Code

• The section is highly cross-referential to State Subdivision Map Act sections (66412, 66426, 66428) and multiple other Code sections, making it difficult to understand without consulting multiple sources.

Subdivision Code

• The section contains multiple cross-references to external documents (SMA, Plans, Plan Documents, Development Agreement) and layered priority rules that require understanding three different legal sources and their interactions.

Subdivision Code

• The section contains 12 numbered subsections with overlapping purposes, some of which restate similar concepts (e.g., (1) and (2) both address compliance with City standards and the General Plan), making it dense and somewhat repetitive for a purposes clause.

Subdivision Code

• The section is heavily cross-referenced to state law (SMA sections) and other city code sections, making it difficult for a non-lawyer to understand applicability without consulting multiple sources.

Subdivision Code

• Subsection (d) cross-references the State Subdivision Map Act multiple times and incorporates enforcement procedures by reference, making the full scope of the rule difficult to understand without consulting external law.

Subdivision Code

• Subsection (d) is a long, nested sentence with multiple conditional clauses and cross-references that make it hard to parse the actual obligations and Director discretion.

Subdivision Code

• The section uses extensive nested phrasing ("Article, Section, subsection, paragraph, sentence, clause or phrase") repeated multiple times, which makes it harder to follow than necessary despite expressing a straightforward legal concept.

Subdivision Code

• The section contains many cross-references (e.g., to Sections 1309, 1344, Planning Code 207.4) and relies on external definitions; readers need to consult other sections to fully understand income thresholds and household-size conversions.

Subdivision Code

• The section references external 'Subdivision Regulations' that are not defined or excerpted here, making it difficult for a reader to understand what specific requirements actually apply.

Subdivision Code

• The section involves multiple cross-references (Article 6, Section 1322(c), the Subdivision Regulations) and several conditional exceptions that require careful parsing of what is and is not required.

Subdivision Code

• The section uses confusing cross-references (e.g., 'Section 1312'), jumps between subsections (a, b, d, e, f with no (c) defined here), and mixes rules for different application types (Tentative Maps, Parcel Maps, Conversions) without clear internal organization.

Subdivision Code

• The section references multiple cross-sections (1315(b), 1313(a)(1), 1314(b)) and involves overlapping notice requirements to different categories of people, making it difficult to follow who gets notified when and for what purpose.

Subdivision Code

• The section contains 17 different fee categories with specific dollar amounts, multiple subsections with conditions, cross-references to other codes, and procedural rules for adjustments and refunds that together make it dense and hard to parse.

Subdivision Code

• The section contains multiple cross-references to other Code sections and California law (Davis-Stirling Act, Subdivision Map Act), detailed technical requirements for condominium formation, and a lengthy notice with sub-provisions that make the overall rule structure difficult to follow.

Subdivision Code

• The section involves multiple cross-references to map types (Final Map vs. Parcel Map), environmental review frameworks (CEQA), and the certification language in subsection (a)(6) is dense and negatively constructed, making it harder for non-lawyers to parse.

Subdivision Code

• The section involves cross-references (Section 1313(b)), appeal procedures, and overlapping authority between the Director, Planning Department, and Board of Supervisors that may be hard for lay readers to parse.

Subdivision Code

• The section references Sections 1333.2-1333.5 without explaining what those exceptions are, making it difficult for a reader to know the full scope of vesting tentative maps without consulting multiple sections.

Subdivision Code

• Subsection (a)(5) contains seven subcategories of approvals and the cross-references to other City Planning Code sections and Building Code provisions make it difficult for a non-expert to determine exactly which approvals apply to a particular project.

Subdivision Code

• The section contains multiple cross-references to California Government Code, layered conditions (approval contingent on state law limitations), and overlapping time periods that interact in ways requiring careful reading.

Subdivision Code

• Subsection (b) uses double negatives and cross-references ('notwithstanding,' 'to the extent permitted by otherwise applicable law') that may obscure its practical effect for non-lawyers.

Subdivision Code

• The section references an external state law (California Government Code Section 66499) without explaining what security types are acceptable, making it difficult for non-lawyers to understand what security satisfies the requirement.

Subdivision Code

• The section cross-references multiple other regulations (Subdivision Regulations, Better Streets Plan, Section 1339) and glosses over specific technical requirements that are defined elsewhere, making it hard for a reader to understand what exactly is required.

Subdivision Code

• Subsection (c) contains extensive cross-references to California Public Utilities Code sections and repeats definitions multiple times, making it dense and hard to follow for a general reader.

Subdivision Code

• The section relies heavily on external documents (Article 18 of Public Works Code, Article 16 of Public Works Code, Master Plan, Better Streets Plan) that a typical resident would need to consult separately to understand full requirements.

Subdivision Code

• The section relies heavily on cross-reference to Section 1337(c) without summarizing what those covenants should contain, making full understanding difficult without consulting another part of the Code.

Subdivision Code

• The section relies on external standards (Subdivision Regulations) and assumes familiarity with coordinate systems, bonds, and the subdivision filing process, making it difficult for non-specialists to fully understand.

Subdivision Code

• The section references an external funding source (Administrative Code Section 10.100-50) without defining what those monies are or how they are collected, making it hard for a reader to understand the full context.

Subdivision Code

• The section contains multiple subsections with cross-references to other sections (1309, 1344, 1385), nested conditions, and several alternative compliance paths that make it difficult to follow without consulting other parts of the Code.

Subdivision Code

• The section's effect depends on understanding Section 1341 (not provided) and the continued existence of a limit in Section 1396, making it difficult to grasp in isolation.

Subdivision Code

• The definition of 'eligible household' in subsection (2)(b) involves a formula combining gross income plus asset value that may be unclear to lay readers without explanation of how the 10% calculation applies in practice.

Subdivision Code

• The section is lengthy and cross-references multiple prior ordinances, with different rules for units purchased at different times (before/after January 18, 2009, before/after October 1, 2025), making it difficult to determine which rules apply to any specific unit.

Subdivision Code

• Subsection (d) is a dense, multi-clause sentence covering multiple requirements (timing of underground facility installation, exclusion of survey monuments, and length of service connections) that could be clearer if separated.

Subdivision Code

• This section's meaning depends entirely on understanding Public Works Code Section 206(b), which is not quoted here, making independent interpretation difficult.

Subdivision Code

• This section references Section 1347(b) without explaining what improvements or obligations it contains, making it difficult to understand the full scope of what fees apply.

Subdivision Code

• The section references 'Final Map' and 'prorated share' without defining them, and cross-references other code sections implicitly, making it harder for residents to understand the full scope of what fees apply and how they're calculated.

Subdivision Code

• This section references external requirements (Chapter 2 Article 2 of SMA and the Subdivision Regulations) without specifying what those detailed format and content rules are, making it difficult for a reader to know the full scope of what a Final Map must contain.

Subdivision Code

• The section references "SMA" (Subdivided Lands Map Act) and "Application Packet" and "Advisory Agency" without defining them, requiring knowledge of other code sections and procedures to fully understand the context.

Subdivision Code

• The section references technical concepts (critically expansive soils, embankments, excavation slopes, faults) and relies on definitions of professional qualifications (soils engineer, registered engineering geologist) that are not defined within this section itself.

Subdivision Code

• The section references an external Planning Code provision (Section 207.3) that readers would need to consult separately to fully understand what units qualify for legalization in the first place.

Subdivision Code

• Section 1381(a)(4)(C) contains a lengthy, nested provision about price-increase limitations with multiple conditions and cross-references that requires careful parsing to understand when and by how much prices may be adjusted.

Subdivision Code

• The section contains multiple cross-references, nested conditional rules, and technical formulas (income multiples, cost-of-living adjustments, priority criteria) that require careful reading to fully understand all pathways and obligations.

Subdivision Code

• The section relies on understanding what Section 1385 contains and depends on a separate rule (Section 1396) remaining in effect, making it difficult to evaluate the actual impact without reading multiple sections.

Subdivision Code

• The section contains multiple conditions, cross-references to external indices (Bay Area Cost of Living Index), carve-outs (Code-required improvements), and overlapping evaluation criteria (vacancy rates, displacement history, rent history) that interact in ways requiring careful interpretation.

Subdivision Code

• The section involves multiple conditions and timelines (filing date, issuance of Public Report, recordation of Final Map, 60-day offer period, six-month conveyance window) that interact in ways a typical reader may find difficult to track.

Subdivision Code

• The section references undefined terms ('equivalent substitute housing,' 'additional cost,' and rights 'as provided in this Code') that require cross-reference to other Code sections to be fully understood.

Subdivision Code

• The section contains multiple conditional scenarios, cross-references to an external index (Bay Area Cost of Living Index), and intertwined provisions about freeze periods, subsequent increases, and relief procedures that require careful parsing.

Subdivision Code

• The section weaves together multiple overlapping timelines (120-day notice, existing leases, lease extension option, statutory eviction notice) and cross-references California law, making the interplay of notice periods and tenant rights non-obvious without careful parsing.

Subdivision Code

• The section involves cross-references to Section 1391 (lease extensions and tenant protections), the role of the Central Relocation Services agency, and special rules for subtenants and elderly/disabled tenants that require understanding multiple conditions.

Subdivision Code

• The rule depends on understanding what 'issuance of the State Department of Real Estate's Final Subdivision Public Report' means, which is a technical regulatory milestone not defined in this section.

Subdivision Code

• The section involves multiple interconnected pools, eligibility criteria spanning 1990–2004 with different rules for different periods, and intricate ticket-counting rules that are difficult to follow without careful re-reading.

Subdivision Code

• The suspension trigger in subsection (c) depends on a complex calculation in subsection (d) that starts counting from 2014 and subtracts a fixed number, and the maximum period in subsection (e) involves a formula that is hard to verify without access to the underlying conversion data.

Subdivision Code

• The section contains multiple cross-references to other Code sections, specific Administrative Code subsections defining prohibited eviction types, and layered conditional requirements that make it difficult to follow the complete eligibility picture without consulting external provisions.

Subdivision Code

• The section contains multiple cross-references to other Code sections (Planning Code 249.94, 415.1, Administrative Code 37.9 and 37.9E, Subdivision Code Article 9 and various numbered sections), nested conditions, and technical procedural requirements that make it difficult to parse without consulting other documents.

Subdivision Code

• The section is lengthy and cross-references multiple state law provisions (SMA sections, Business and Professions Code, Civil Code, Government Code); the interplay between tenant rights, timing requirements, and procedural steps is intricate and would benefit from clearer organization.