Learn
What does “full catchment” mean?
Updated 2026-08-04
Full catchment means tracking every public body that regularly decides outcomes for people who live in one place — not only the city council agenda page. In practice that includes councils, planning and other commissions, community services districts, water and fire agencies, school boards when they are part of the local map, and similar special districts. CivicCatch uses “catchment” for that whole map: one place, many governments, one week view with links back to official packets.
Residents do not experience life as a single .gov silo. A rate change, a land-use hearing, or a fire-safe vegetation rule may land on a district calendar that never appears on the city’s homepage. Early warning that stops at council alone is incomplete early warning.
Why isn’t city council enough?
City council is often the most visible body, and many transparency tools stop there because the city’s calendar is easiest to scrape. But water infrastructure votes, school bond calendars, and special-district assessments frequently matter as much to a household as a council ordinance. Those bodies publish on separate sites, with separate RSS feeds or PDF packets, on different posting schedules. A resident who only follows council news can still be surprised by a decision that never appeared on the city site.
| Approach | What residents see | Typical gap |
|---|---|---|
| Council-only calendar | City council (and maybe planning) | Water, fire, CSD, school boards on other sites |
| Full catchment | One place week across confirmed bodies | Still verify on each agency packet |
Full catchment does not mean inventing a new government. It means admitting the map residents already live under and making that map readable in one place before meetings happen.
Which kinds of bodies are usually in scope?
Scope varies by place. A mountain valley may have a community services district, a municipal water district, a fire authority, a city council, and planning or tourism commissions. A suburban city may add a school district, a park district, and a transportation commission. The rule of thumb: if the body posts public agendas and its votes change daily life for people in that place, it belongs in the catchment unless the city or publisher explicitly excludes it during setup.
CivicCatch proposes bodies from public sources; a human confirms what to watch. That confirmation step is deliberate. Catchment coverage without local confirmation risks watching the wrong ZIP’s agencies or missing a district that residents care about most.
How does full catchment show up for a resident?
On a place site, “this week” opens with a short factual lead naming which bodies meet, then lists meetings with links to official agendas. The lead is not a news story and not a press release. It is an answer capsule: what is posted, which bodies are on the calendar, and where to verify. Email digests, when enabled, carry the same cited shape so the inbox and the web do not disagree.
Always treat the agency packet as the system of record. CivicCatch is unofficial early warning. If a highlight and a PDF disagree, the PDF wins. If a vote outcome is not yet in minutes or another confirmed source, it should not be invented from agenda language alone.
How is this different from a single-body calendar widget?
A widget glued to one agenda feed can be useful and still leave residents blind to the rest of the map. Full catchment is a product choice: one place name, many bodies, shared week view, official links. Cities buy that when they want transparency people can finish without standing up a newsroom. Publishers buy that when they want republish-safe capsules under the town’s name rather than masthead chrome.
For a concrete example, open the Big Bear Valley demo and scan which bodies appear in a single week. Then compare that to visiting each agency site separately. The time difference is the practical meaning of catchment.
What should cities and publishers confirm during setup?
Confirm display name and place branding, which bodies to include or exclude, how residents receive the week (email, subdomain, or both), and that every watched source has a known official agenda URL pattern. Confirm that preview tenants stay noindex until the catchment list is trustworthy. Confirm that staff understand CivicCatch will not auto-write “what passed” narratives from agendas alone.
How does catchment coverage change over time?
Catchments are not static. Agencies merge, new commissions form, and posting URLs change when a city migrates its website. A useful early-warning product treats the body list as an owned configuration: review it when a clerk reports a broken agenda link, when a district starts meeting monthly instead of quarterly, or when residents ask why a familiar board is missing. Cities should assign a named owner for that review — often the clerk, PIO, or city manager’s office — so the map does not silently rot.
Publishers covering multiple towns should keep per-place catchments separate even when the same reporter works all of them. Place-first delivery means the Big Bear Valley week and a neighboring city’s week do not share chrome or confuse which packet is authoritative. Full catchment is a discipline of scope and citation, not a single national feed of every government meeting in California.
If you are evaluating CivicCatch for your city, start with the demo week view, list the bodies your residents actually live under, and ask whether your current transparency stack would have shown each of those meetings with an official link before the gavel. That gap — or the lack of one — is the business case for catchment coverage.