Public Records — All Jurisdictions

PRR portals, passive-monitoring opportunities, adapter consolidation, build sequence.
Today: Mon, May 11, 2026 Last scoped: May 11, 2026 (Phase 4 sub-agent recon) Jurisdictions: 7 Backend status: Greenfield · scoped
Leverage insight: The 7 jurisdictions collapse into 5 distinct adapter code paths, not 7. Two NextRequest tenants (Miami + Hialeah) share a code path and both expose publicly-browseable /requests indexes — this is the single highest-leverage passive monitoring target in the whole system: every completed PRR plus its responsive documents, scrapeable daily, zero requests filed. Two JustFOIA tenants (Miami Beach + Coral Gables) share a code path (status-only publicly). Miami-Dade GovQA is its own (session-stateful, rate-limited, no public completed-request browser). Pinecrest and South Miami are email-only and need SMTP submission + inbox-watching adapters. Florida Chapter 119, F.S. imposes no fixed shot clock — only "reasonable time" per AG opinions and case law. Practical norms: GovQA ack 1–3 business days / fulfillment 10–45 days; follow-up nudges at +14 and +25, escalate at +30 with the "reasonable time" cite.

Side-by-side: PRR portal · platform · public log

Jurisdiction Platform Public completed-request log? Adapter
Coral Gables JustFOIA Partial — status/title only JustFOIA adapter (shared w/ MB)
Miami-Dade County GovQA (+ separate Police tenant) No GovQA adapter (own)
City of Miami NextRequest Yes — full index + docs NextRequest adapter (shared w/ Hialeah)
Miami Beach JustFOIA Partial — status/title only JustFOIA adapter (shared w/ CG)
Pinecrest Email/in-person No SMTP + inbox-watch
South Miami Email/PDF form No SMTP + inbox-watch (shared w/ Pinecrest)
Hialeah NextRequest Yes — full index + docs NextRequest adapter (shared w/ Miami)

Coral Gables

JustFOIA · status/title publicly visible · files private
PRR portalcoralgablesfl.justfoia.com/publicportal
CustodianCity Clerk's Office · 305-569-5210
Passive targetsLegistar (coralgables.legistar.com), JustFOIA recent-requests list, lobbyist registrations via Lobbyist Dashboard
Adapter notes: JustFOIA renders client-side — likely needs headless browser, not raw HTTP. Watch the recent-requests list for title patterns matching your topics (container stacking, specific RFPs) and trigger follow-up PRRs when relevant.

Miami-Dade County

GovQA · session-stateful · no public completed-request browser
PRR portal (main)miamidadecounty.govqa.us
Police tenantmiamidadecountyfl.govqa.us
Records pagemiamidade.gov — public records
Passive targetsLORIS lobbyist registrations (LORIS) — overlaps with existing lobbyist-watch.yml; Clerk Lobbyist View; Legislative Information Center; Commission on Ethics opinions and Form 1/6 references
Adapter notes: GovQA URLs carry embedded S(...) session IDs and rate-limit aggressively — use a real session, low concurrency, polite headers. No public browse-completed feature, so passive monitoring is limited to the proactively-posted surfaces.

City of Miami

NextRequest · publicly-browseable /requests index — HIGHEST passive yield
PRR portalmiami.nextrequest.com
Public logmiami.nextrequest.com/requests — all completed requests + responsive docs
Records pagemiami.gov — request public records
Passive targetsNextRequest closed-request feed (the prize); Legistar (Granicus) for agendas; lobbyist registrations via City Clerk
Adapter notes: NextRequest exposes clean URLs and is the easiest to scrape — start here for Stage A. Each closed request page includes title, date, agency, requester (when public), and responsive document URLs.

Miami Beach

JustFOIA · status/title publicly visible · files private
PRR portalmiamibeachfl.justfoia.com/publicportal
Email fallbackresearchrequest@miamibeachfl.gov
Records pagemiamibeachfl.gov — public records request
Document storeLaserfiche WebLink (CityClerk) — incidental PRR material gets archived here; see Miami Beach single-pane artifact for taxonomy
Passive targetsJustFOIA recent-requests list; lobbyist Fee Expenditure & Compensation Statements (filed Feb 28 annually); P-card/expense disclosures; OIG reports (in Laserfiche)
Adapter notes: Miami Beach is unusually transparent — proactive posting includes OIG reports, compensation statements, expense disclosures. The JustFOIA portal itself reveals less than Laserfiche does. For PRR-fulfilled records, expect to follow up directly with City Clerk.

Village of Pinecrest

Email/in-person only · no portal
Records pagepinecrest-fl.gov — public records
CustodianVillage Clerk · clerk@pinecrest-fl.gov · 305-234-2121 · 12645 Pinecrest Pkwy
Fees$0.15/page
Passive targetsCouncil agendas/minutes on village site; lobbyist registrations via Village Clerk
Adapter notes: No FOIA log to scrape. Phase 4 here means standing PRR templates filed via SMTP + an inbox-watcher to pull responsive records.

South Miami

Email/PDF form · no portal
Records pagesouthmiamifl.gov — public records requests
CustodianCity Clerk Nkenga A. Payne · npayne@southmiamifl.gov
Request formPDF form
Passive targetsAgendas via CivicEngage; Lobbyist Information
Adapter notes: Same SMTP + inbox-watch pattern as Pinecrest. Two cities share a code path.

Hialeah

NextRequest · publicly-browseable /requests index — HIGHEST passive yield
PRR portalcityofhialeahfl.nextrequest.com
Public logcityofhialeahfl.nextrequest.com/requests
Email fallbackcityclerk@hialeahfl.gov
Records pagehialeahfl.gov — public records request
Passive targetsNextRequest closed-request feed; Council agendas via Agenda Center; lobbyist filings via City Clerk
Adapter notes: Same code path as City of Miami NextRequest. Historically Hialeah is the least proactive publisher of the seven — treat as PRR-driven beyond what NextRequest reveals. New Calvo administration (sworn Jan 12, 2026) issued transparency executive orders; cadence/disclosure norms may shift.

3-stage build plan

Stage A · Week 1 — Passive catalog (zero requests filed)

Two NextRequest scrapers (Miami, Hialeah) hitting /requests daily — parse request ID, title, status, agency, responsive doc URLs. Two JustFOIA scrapers (Miami Beach, Coral Gables) for status + title; flag matches against a watchlist of topics for Stage B follow-up. Legistar/agenda pulls for Miami-Dade and Coral Gables. LORIS lobbyist diff job gated against existing lobbyist-watch.yml to avoid duplicate work. Per-jurisdiction "proactive doc" link table (calendars, expense reports, OIG, ethics filings). No requests submitted — build the catalog first.

Stage B · Weeks 2–3 — Standing PRR templates

5–8 parameterized request bodies for high-value categories: lobbyist-to-official emails (sliding 30-day window per named official), Mayor/Manager/Commissioner calendar exports, vendor contract files post-award above $250k (scoring sheets, evaluation committee notes, debrief letters), code enforcement records by parcel/folio (directly applicable to JD's container stacking matter), P-card and travel reimbursement for target officials (quarterly), settled litigation / claims register (quarterly), OIG / Auditor reports issued in window (Miami-Dade OIG, Miami Beach OIG), capital project change orders. Submission adapters for GovQA, NextRequest, JustFOIA, SMTP fallback. Cadence configurable. Follow-up logic at +14 / +25 / +30 days.

Stage C · Week 4+ — Integration

Full-text indexing of responsive documents. Entity extraction tied to client roster + topic taxonomy already in the system. Alert routing into the same channel agenda-watch uses. Cross-reference of FOIA-log titles against lobbyist-watch.yml activity (e.g., flag when another lobbyist files a PRR on a matter Eric is tracking — particularly valuable on NextRequest where requester names are often public).

Open questions before Stage B can ship:
  1. Which active client matters (beyond JD's container stacking in unincorporated Miami-Dade) should seed the initial PRR template list?
  2. Priority ranking on the 5 adapters. Gut: Miami-Dade GovQA, City of Miami NextRequest, Miami Beach JustFOIA tier 1; Coral Gables and Hialeah tier 2; Pinecrest and South Miami tier 3. Confirm or reorder.
  3. Filer identity — PRRs submitted under "P3 Miami" (visible to opposing lobbyists watching the same logs, particularly on NextRequest where requester is published) or under a neutral name (cleaner intel, raises disclosure questions if discovered)?
  4. Ethics posture — as a registered lobbyist yourself, monitoring other lobbyists' communications with officials is lawful but reputationally sensitive. Confirm whether Phase 4 outputs are internal-only, shared with clients, or surfaced in any public deliverable; that decision drives whether we log requester identity in metadata.