Public-sector voting and agenda management on OnBase
Inside the City of Tampa workflow: how council agendas, attachments, and votes flow through OnBase with the audit trail an open-records request expects.
Public meetings look like a procedural exercise. Inside the workflow that produces them, they're a content-management problem with a hard deadline and an open-records expectation hanging over every record. Here's how the City of Tampa runs theirs on OnBase.
Agenda assembly
Departments submit items into OnBase against a council meeting record. Each item carries supporting documents, staff reports, contracts, exhibits, and a sponsoring department. Agenda compilation is a query, not a copy-paste exercise, and it produces a packet that's identical to the one council members read.
Council member view
Members read the packet in OnBase before the meeting. Annotations, questions, and follow-ups are recorded against the item, useful for both the next session and the public record.
The vote itself
- Roll call recorded against the meeting record.
- Per-item vote captured at the moment it's taken, aye / nay / abstain / absent, with timestamp.
- Approved items route automatically to the responsible department's queue.
Open records, working backward
The reason this matters: when an open-records request comes in three years later for everything that touched a particular contract, the request resolves in minutes instead of weeks. The agenda item, the vote, the contract, and every downstream amendment are all linked in OnBase to the same record. Public-records readiness is a byproduct of running the workflow correctly the first time.