# The Midnight-Amendment Playbook **SILobbyist Rapid Response · v1.0 — 2026-10-01** Companion to [/rapid.html](/rapid.html). General practice guidance, not legal advice. The scenario: a hostile amendment drops late at night. The vote is hours or a day away. You need a statement draft, a whip update, and a client alert — before your client hears it from someone else. --- ## 1. Triage — the first 15 minutes 1. **Read the actual amended print first.** Pull the amended bill on [leginfo](https://leginfo.legislature.ca.gov) and read the change yourself before reacting. Standard practice in rapid-response work: verify the facts before shaping the message — inaccurate first statements are the fastest way to lose credibility (Institute for Public Relations, crisis-response best practices: "be quick… be accurate"). 2. **Classify the change**: hostile / neutral / friendly. Check whether the threshold moved (did the amendment add an urgency clause or an appropriation? Prop 54's 72-hour-in-print rule constrains floor votes on amended bills — know your window). 3. **Set the deadline on the clock** — floor vote time, next committee gate — and write it down where the team sees it. 4. **Open the Rapid Response Console** and log the intake. Everything you do next flows from one fact sheet. ## 2. Who to call first (in this order) 1. **The author's office / allied staff.** Call — don't text, don't email. Ask: what changed, why, and what comes next. You want the read from the office driving the bill before you read it from the press. 2. **Your coalition partners.** One quick call to the lead partner: shared position check, agree on message discipline. In crisis communication, one consistent message across spokespeople beats three fast ones (Institute for Public Relations; PR News crisis checklist: "define the terms… form a rapid response team"). 3. **Key committee/floor staff** if the amendment changes jurisdiction, thresholds, or analysis. 4. **Your client — only after 1–3.** The client should hear the amendment from you, with a plan attached, not as a rumor. Standard crisis practice: call the most affected stakeholders personally rather than relying on email; a live conversation demonstrates control, then follow with the written alert (Crisis PR Playbook, Bluesky PR). **After the calls:** draft the three comms on /rapid.html — statement, whip update, client alert. ## 3. Comms sequencing Order matters — never reverse it: 1. **Internal first.** Whip update and team message stay inside the room. Whip counts are private, never distributed, never screenshotted to a reporter. 2. **Client alert second.** Email from your own address. Facts → what it means for them → what you're doing → what they should do → when they hear from you next. Keep it shorter than you want to. 3. **Press statement third** — only if the situation warrants one. Not every amendment deserves a statement; reacting to everything trains the press to ignore you (Goff Public: "don't rush to respond — not every situation warrants a statement"). 4. **Then update the bill tracker** (your /bills.html watchlist, position letter, and any testimony drafts that quoted the old text). ## 4. What never goes in writing hastily - **No whip counts in email or text** — ever. They become exhibits. - **No predictions about outcomes** ("we'll kill this 54–26"). Write your intel, not your conclusions. - **No admissions or blame in writing.** Apology-adjacent language belongs on a call, not in a paper trail. Crisis guidance is consistent: stick to verified facts, don't speculate, keep one spokesperson (Institute for Public Relations; media-public-relations.com rapid-response checklist: two approvals before publication for substantive statements). - **No message to a legislator's office you haven't run past the client when the client is paying for the position.** Discipline is the product. - **No speculating about the other side's motives.** Describe what the amendment *does*, not what you think the author *meant*. ## 5. The overnight checklist (keep on the console) - [ ] Amended print read — threshold and 72-hour window checked - [ ] Author/ally office called (voice) - [ ] Coalition partner position synced - [ ] Statement drafted — principal quote approved by principal - [ ] Whip count current — target math confirmed - [ ] Client alert sent from your own email before the news cycle - [ ] Tracker, position letter, testimony drafts updated to the new print - [ ] Next-update time promised and calendared ## Sources - Institute for Public Relations, *Crisis Management and Communications* — initial-response best practices: be quick (within the first hour), be accurate, be consistent, use all channels — https://instituteforpr.org/crisis-management-and-communications/ - PR News, *A Checklist for an Effective Crisis Communication Plan* — pre-draft templates, right is better than fast, rapid-response team — https://www.prnewsonline.com/checklist-crisis-plan/ - Bluesky PR, *Crisis PR Playbook* — call key stakeholders personally before emailing the wider base; one spokesperson; agreed talking points — https://5157867.fs1.hubspotusercontent-na1.net/hubfs/5157867/Crisis%20PR%20Playbook.pdf - Goff Public, *Communicating in times of rapid change* — don't rush; be transparent about what you do and don't know — https://goffpublic.com/blog/communicating-in-times-of-rapid-change-lessons-from-the-crisis-communications-playbook - Media-public-relations.com, rapid-content checklist — timestamp, verified facts, actions taken, contact, next-update line, two approvals before publication — https://media-public-relations.com/download/1471/?tmstv=1789695787 - CA specifics: Prop 54 (2016) 72-hour in-print rule (Cal. Const. art. IV, §8); official amended prints at https://leginfo.legislature.ca.gov **Standing rule of this console:** the tool drafts, you customize, you send. Nothing here ever sends itself.