🏛️ About & Methodology

How Austin Council Monitor works, where the data comes from, and its limitations

⚙️ How It Works

Austin Council Monitor is an automated pipeline that runs twice daily and publishes plain-language summaries of Austin City Council meetings.

austintexas.gov/council/meetings
    │
    ▼
Scrape meeting links (pattern: /YYYYMMDD-type)
    │
    ▼
Download agenda PDF → Extract text
    │
    ▼
Google Gemini AI → Generate 3–5 bullet summary
    │
    ▼
Save to database → Email subscribers → Publish site

Update Schedule

The pipeline runs automatically at 8:00 AM and 6:00 PM Central Time daily via GitHub Actions. New meetings are typically published within minutes of being posted to the city website.

📡 Data Sources

Primary Source

All meeting data originates from the City of Austin Meeting Info Center, the official public record maintained by the City of Austin. No data is altered, inferred, or supplemented from other sources.

What Is Captured

FieldDescription
Meeting dateParsed from the meeting URL (YYYYMMDD format)
Meeting typeRegular, Work Session, Committee, etc.
Meeting URLDirect link to the official city meeting page
Agenda PDFDownloaded temporarily for text extraction, then deleted
AI summaryGenerated from agenda text; not stored with original PDF

Meeting Types Monitored

Regular Meeting Work Session Special Called Meeting Austin Housing Finance Corp Audit & Finance Committee Mobility Committee Public Health Committee Housing & Planning Committee Climate, Water, Energy & Public Enterprises Public Safety Committee Economic Opportunity Committee

🤖 AI Summarization

Model

Summaries are generated using Google Gemini 2.5 Flash, a large language model optimized for speed and factual accuracy on structured document content.

Prompt

Each agenda is summarized with the following instruction:

"Summarize this Austin City Council agenda in 3–5 bullet points. Focus on the most important items, public hearings, and policy decisions. Keep it concise and accessible to the general public."

⚠️ Limitations

AI summaries are not a substitute for official records. They are intended as a first-pass orientation tool, not a definitive account of meeting content.

📰 For Journalists & Researchers

Austin Council Monitor is designed with journalists, civic technologists, and engaged citizens in mind. All underlying data is publicly accessible.

Direct Data Access

Database Schema

The austin_meetings.db SQLite database is committed to the repository and updated with each pipeline run.

ColumnTypeDescription
meeting_idTEXTUnique ID (e.g. 20260409-reg)
dateTEXTMeeting date (YYYY-MM-DD)
meeting_typeTEXTHuman-readable meeting type
meeting_urlTEXTOfficial city meeting page URL
agenda_urlTEXTAgenda PDF URL (if available)
gemini_summaryTEXTAI-generated summary
created_atTEXTTimestamp when first discovered
notified_atTEXTTimestamp when email alerts sent

Update Cadence

The pipeline runs at 8:00 AM and 6:00 PM CT daily. The RSS feed and website are updated within each run. There is no manual editorial step — publication is fully automated.

Attribution

If citing an AI-generated summary from this site, please use: "Austin Council Monitor (austincouncil.app), summarized using Google Gemini AI." Always link to the original official meeting page for reference.

Contact

Questions, corrections, or collaboration inquiries: open a GitHub issue.

💡 About This Project

Austin Council Monitor is an open-source civic media project built to demonstrate how lightweight AI tooling can make local government more accessible. It is not affiliated with or endorsed by the City of Austin.

The full source code is available on GitHub under the MIT license. Contributions and adaptations for other cities are welcome.

For official City of Austin information, always refer to austintexas.gov.