Here's the thing to remember about this form: it's a public document. 👀 Anyone can read it — your filing officer, reporters, your opponent. The goal isn't perfection for its own sake; it's meeting the requirements without raising red flags. A clean, consistent filing signals a campaign that knows what it's doing. With that in mind, here are the ten small things that trip up almost everyone: 👇 1️⃣ "Self-Employed" is an occupation situation, not an employer. 💼 The FPPC wants the name of the business. If there isn't a separate business name, there are magic words for that: "No Separate Business Name." Yes, that's really what you write — it's straight from the FPPC's own manual. ✨ 2️⃣ Skip the acronyms. 🔤 Your donor knows what "VP of BD at GTM Labs" means. The public doesn't, and disclosure is for them. The FPPC specifically lists acronyms as incomplete information (their manual's example: "ABBA — no acronyms" 🎶), so spell everything out — occupation and employer both. 3️⃣ Occupation means job title, not industry. 👷 "Real Estate" tells us the field; "Broker" or "Property Manager" tells us the job. The occupation box wants the job. 4️⃣ Physical addresses only — P.O. Boxes don't count. 🏠 Itemized contributors need a street address. Donors sometimes push back on this, so it helps to know: contributor addresses are redacted from the publicly posted version, so their home address isn't going up on the internet — but the filed form still has to have it. ⏰ Keep an eye on the calendar too: if you don't have name, street address, occupation, and employer within 60 days of a $100+ contribution, it has to be returned. A quick follow-up email to the donor usually solves it. 5️⃣ Lawn signs are CMP, not LIT. 🪧 Easy mix-up — signs feel like literature, but LIT is for mailers and flyers. Signs fall under campaign paraphernalia. This might be the most common miscode in local politics, so you're in good company if you've done it. 6️⃣ Know when a code alone is enough — and when it isn't. 🎯 For most expenditures (WEB, LIT, CMP, POS...), the code fully satisfies the requirement, and adding descriptions on some lines but not others just makes the schedule look uneven — a good example of "more detail isn't better." But a few codes DO need a description alongside them: ✈️ TRC — candidate travel 🤝 MTG — meetings (include how many people attended) 🎪 FND — fundraising events (include the date and number of people present) Rule of thumb: code alone where it fits, code plus the required details for travel, meetings, and events, and consistency down the page either way.