# Post-Passage Compliance Guide — California **Version:** v1.1 — 2026-10-01 **Jurisdiction:** California **Status:** General information, not legal advice. Always confirm against the enrolled/chaptered text on [leginfo](https://leginfo.legislature.ca.gov) before advising a client. *(v1.1 adds §8: the loss/veto path — autopsy, override math, and the reintroduction roadmap methodology, powering the Outcome Playbook's paths 2 and 3.)* --- ## 1. The bill is signed — what happens next When the Governor signs a bill, the **Secretary of State chapters it** and assigns a **chapter number** (e.g. "Statutes of 2026, Chapter 123"). The chapter number is the bill's permanent citation — a signed bill that has not yet been chaptered is law, but its chapter number may not be published yet. **Never guess a chapter number; verify on leginfo.** ## 2. Effective dates (Cal. Const. art. IV, § 8(c)) Most new statutes do **not** take effect the day they're signed. The default rules: - **Default:** takes effect **January 1 of the following year** (e.g. bills signed in 2026 take effect January 1, 2027) — unless the bill says otherwise. - **Urgency statutes:** effective **immediately upon signature**, but require a 2/3 vote in each house and a statement of the facts constituting the urgency. - **Appropriation / tax-levy statutes:** effective immediately (or on the date the bill specifies). Budget Acts and budget trailer bills are effective upon signature. - **Bill-specified dates:** many bills set their own operative date (e.g. "operative January 1, 2028") or tie operation to a triggering event. The chaptered text controls — always read the operative-date language. ⚠️ **Lobbyist rule of thumb:** never tell a client "this takes effect immediately" or "January 1" from memory. Pull the chaptered text, find the operative-date language (often the last section), and cite the section. ## 3. From statute to regulation: who writes the rules Most significant bills don't self-execute. They **delegate rulemaking** to a state agency, board, or commission, which must adopt regulations fleshing out the statute before it is fully operable. A compliance roadmap therefore has three tracks: 1. **Statutory obligations** — what the chaptered text requires directly (dates, prohibitions, reporting duties), effective per the bill's operative date. 2. **Agency rulemaking** — the delegated regulations: definitions, forms, fees, safe harbors, enforcement detail. 3. **Operational change** — what the client must actually change in systems, contracts, training, and reporting. Identify the implementing agency from the chaptered text (the bill names the agency, board, or commission it delegates to). SiLobbyist's agency atlas (`/directory.html`, data in `data/agencies-exec.json` / `data/agencies-boards.json`) carries contact details where verified — **never invent an agency contact; link the agency's own rulemaking page where the contact is unknown.** ## 4. APA basics (Government Code § 11340 et seq.) California agency rulemaking follows the **Administrative Procedure Act (APA)**: 1. **Notice published in the California Regulatory Notice Register** (OAL's weekly register) — this starts the clock. 2. **45-day public comment period** (minimum). The agency must consider all comments and respond to relevant ones in the Final Statement of Reasons. 3. **Public hearing** (if requested in writing by interested persons within the comment window, or scheduled by the agency). 4. **15-day comment period** on any substantial revisions ("modified text"). 5. **OAL review** (Office of Administrative Law): OAL has 30 working days to approve or disapprove, checking the six standards — authority, reference, consistency, clarity, nonduplication, necessity. OAL does **not** judge policy wisdom. 6. **Filing with the Secretary of State** → regulation takes effect (usually quarterly effective dates, or the date the agency specifies if permitted). Emergency regulations (Gov. Code § 11346.1) skip the comment periods but expire (typically 180 days, re-adoptable) — they buy time, not permanence. ## 5. Where the lobbyist adds value post-passage - **Comment letters:** the APA comment period is the last structured chance to shape the rule. Drafts via the Drafting Studio (`/studio.html`). - **Workshops/pre-notice discussions:** agencies often hold pre-rulemaking workshops — softer, but where definitions get settled. - **Track the register:** OAL's notice register (`/regs.html` on SiLobbyist) shows open comment periods and deadlines. - **Client briefings:** translate "the bill passed" into an operational to-do list with owners, dates, and cost ranges. That's the Compliance Tracker (`/compliance-tracker.html`). ## 6. Compliance cost estimates — methodology rule Estimates on a client roadmap must be labeled as estimates with the methodology stated (e.g. "staff time @ loaded hourly rate × estimated hours; vendor quotes obtained [date]; assumes N sites"). Ranges beat point estimates. Never present an internal back-of-envelope number as a client commitment or an agency's official figure. ## 8. When the bill dies or is vetoed — the loss-path methodology The Outcome Playbook (`/compliance-tracker.html`, nav label "Outcome Playbook") covers all three fates. Path 1 (passed) is the compliance roadmap above. Paths 2 and 3 turn a loss into the client deliverable that keeps the retainer: the client sees the path to winning next time, not just the loss. ### 8a. Autopsy — from the record, never invented - **Where it died:** the chokepoint (policy committee, Appropriations/suspense, floor, second house, missed deadline, Governor's desk). The Scenario Lab's "Backup paths" tab carries the per-chokepoint playbook (motion to reconsider, gut-and-amend, the suspense fiscal fix, vehicle bill) for losses that are still recoverable in-session. - **Vote analysis:** floor tallies come from the official record (leginfo floor analyses) or the lobbyist's confirmed whip read — entered by the lobbyist, blank means unknown. **Never invent a vote tally.** Whip counts are private working notes: never distributed, never screenshotted, never quoted to a reporter. - **Opposition moves that worked:** documented per claim from the lobbyist's own record of the fight or the opposition's public actions (ad filings, testimony, press). Note: `kb/opposition-playbooks` does not exist — there is no curated archetype file to draw on, so every opposition claim must carry its own source rather than riding a playbook template. ### 8b. Vetoed — the Governor's message is the diagnosis A veto message is the most useful document a losing lobbyist ever gets: the Governor tells you exactly why. Veto rationales in the playbook come from `data/vetoes-2026.json` — 67 vetoes verified against the Governor's official legislative updates, with press-reported veto-message summaries for 9 bills (the rest carry the official bill subject only). Where the message hasn't been reviewed, the rationale shows as **"veto message summary pending review"** with a link to the Governor's update — the lobbyist reads it and enters it. **Never paraphrase or invent a veto rationale.** - **Override math:** overriding requires **2/3 of each house — 54 Assembly + 27 Senate** votes. The playbook computes the shortfall from the lobbyist's confirmed counts and gives an honest viability readout. Overrides are extraordinarily rare in California (the Scenario Lab caps override scenarios at ~8% by construction) — an override fight you can't win burns capital with the members you need next year, so the readout says plainly when next-session strategy is the honest recommendation. - **Next-session strategy:** built from the veto message's objections: what to change in the language (answer the message, don't re-litigate it), which votes to flip, which coalition gaps to close. Most vetoed bills that return are amended to the veto message — the historical analogs (AB 3129→SB 351, SB 1047→SB 53 in `data/recycled-bills.json`) show veto→cured-rerun→signed as the realistic pattern, and the cautionary veto→rerun→vetoed chain (AB 2286→AB 33) shows what happens when the message is ignored. ### 8c. Failed/died — the comeback plan - **Forward plan fields:** interim strategy (interim study, informational hearing, pre-negotiation with the chair's consultant), reintroduction language changes, votes to flip, coalition gaps to close. - **Scenario Lab tie-in:** the forward plan deep-links to `/scenarios.html` and to Goldie with a prefilled reintroduction scenario (bill, veto rationale or autopsy, proposed changes, flip targets) so the next-session math is modeled with stated assumptions and a confidence level — never as a prediction. See `kb/scenario-methodology.md`. - **The outcome memo** (Generate bar → .docx, same pipeline as the compliance one-pager) is the client deliverable for all three paths: outcome & verdict, autopsy, override math (vetoed) or forward plan, and a "what to verify" section that repeats the honesty rules. Nothing in the memo is presented as a prediction. ### 8d. Honesty rules carried over (repeat, because losses tempt fudging) Chapter numbers, effective dates, agency deadlines, and contacts: from official sources or labeled pending — unchanged from §1–§7. Added for loss paths: never invent votes, never invent a veto rationale, never present an unverified count as a floor tally, and never present a comeback plan as a prediction of next-session success. ## 9. Key official links - Chaptered texts & operative dates: https://leginfo.legislature.ca.gov - OAL notice register: https://oal.ca.gov (California Regulatory Notice Register) - Governor's legislative updates (signing/veto news): https://www.gov.ca.gov - SiLobbyist regulatory tracker: `/regs.html` --- **Data honesty (site-wide rule, repeated):** chapter numbers, effective dates, agency deadlines, and contact points come from official sources or are explicitly marked "pending / confirm." Nothing is inferred into a client deliverable.