From the Citizen Engagement & Services edition of November 1, 2026
St. Paul projects 24,400 data requests in 2026, up from 668 in 2017; Wilder Research finds requests growing more complex as residents use AI
City of St. Paul, Minnesota (City Attorney's Office); Wilder Research · Public records and data practices requests · St. Paul, Minnesota, United States
- Publisher
- KSTP 5 Eyewitness News
- Original publication
- 2026-10-28
- Source retrieved
- 2026-11-02
- Event date
- 2026-10-28
What happened
At a 2027 budget committee meeting, St. Paul City Attorney Irene Kao said the city is on track for 24,400 data requests in 2026, up from 668 in 2017, 22,678 in 2024 and 21,915 in 2025. The article says the office seeks two staff at $226,406; 14 department designees review requests, and a data practices supervisor was hired in August. Council President Rebecca Noecker asked for a long-term strategy beyond hiring. Kao said technology could help but legal review would still be needed. Wilder Research, which evaluated the process, said an easier portal and more engaged residents drive volume, and that requests are growing more complex as people use AI to write them.
Why it matters
Adds a large-city data point to the AI-driven records surge already seen in smaller jurisdictions: an outside evaluation links rising request complexity to residents using AI, and officials say technology alone won't remove legal review.
Evidence and measured results
TV news report of a budget presentation, with quotes from the city attorney and Wilder Research. The Wilder evaluation was not opened, and the AI link is a qualitative observation without counts.
Limitations and uncertainty
Published Oct. 28, before the stream's last completed run, but not captured then; included because it adds an independent evaluation. The article names the 'County Attorney's Office' for the staffing request in an apparent error. AI's share of volume is not quantified.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Data request volume and complexity are outgrowing staff, partly because residents use AI to write broad requests.
- Stakeholders
- City attorney
- Data practices supervisor
- Department records designees
- City council budget committee
- Discovery questions
- How many staff hours go to redaction and email retrieval?
- Can you identify AI-written or bulk requests?
- What does your tracking system automate today?
- Value hypothesis
- Better triage, search and redaction tools may slow staffing growth, but legal review remains; no savings are shown.
- Potential engagement
- A records workflow and tooling assessment with a redaction pilot on complex requests.
- Unsupported claims
- How much of the volume AI drives
- That tools can replace legal review
- Specific cost savings
Pre-sales engineering
Role takeaway
- Fit
- Fits cities with high-volume records programs and fragmented tracking tools.
- Architecture and integration
- Records tracking linked to email and document search plus redaction tooling.
- Prerequisites
- Request data with time tracking
- Access to email archives
- Defined redaction rules
- Constraints
- Minnesota data practices law
- Human legal review required
- Security
- Control access to sensitive records during search and log redaction decisions.
- Proof of value
- Measure hours per complex request before and after tooling
- Audit redaction accuracy on a sample
Delivery
Role takeaway
- Work
- Implement triage, scoping and redaction support for data requests.
- Dependencies
- Tool procurement
- Designee training
- Request data baseline
- Ownership
- City attorney's data practices supervisor.
- Skills and adoption
- Designees learn new triage and redaction tools and scoping conversations.
- Governance checkpoints
- Baseline volume and time report
- Policy on bulk or AI-written requests
- Quarterly backlog review
- Acceptance criteria
- Proposed: median time to close falls against baseline
- Proposed: backlog stops growing
- Risks
- Volume outpaces gains
- Redaction errors
- Policy seen as limiting public access
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Tracking systems that don't support redaction and email retrieval leave manual work; intake, search and redaction tooling are the likely technology targets.
Governance
Who approves, reviews and stays accountable for outcomes?
Council is asking for a long-term strategy, so policy on AI-written or bulk requests and scoping practices are in play alongside staffing.
Security and privacy
What data, permissions and controls need testing?
Rising volume increases redaction workload and the risk of releasing protected data under Minnesota data practices law.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Request handling is spread across 14 designees and depends on human legal review; hiring alone was called unsustainable.
Procurement
What should contracts, pricing and exit terms secure?
Candidate purchases include redaction, e-discovery-style search and portal triage, but the article names no tool.
Operating model
Which teams own the service once it runs?
Volume grew about 36-fold since 2017; triage, scoping conversations with requesters and centralized coordination are operating levers.
Publication history
Read preserved resource versions (JSON)Stable resource ID: st-paul-mn-data-requests-24400-projected-2026-ai-complexity-20261028