Checklist · About 30 minutes
Municipal Software Evaluation Checklist
A printable checklist for comparing public records request management software on workflow fit, deadlines, redaction, security, AI, data exit and cost.
How to use this
Use this checklist during and after vendor demos to compare public records request management tools on the same terms. It works best when filled in by a small group: the clerk or records officer, a department representative, counsel, and IT.
- Before any demo, mark the items that are must-haves for your municipality with an asterisk (*).
- Ask each vendor to show, not just tell. Where possible, use one of your own anonymized requests.
- Check an item only if you saw it working or received a clear written answer.
- For anything the vendor describes as "planned" or "on the roadmap," leave it unchecked and note it.
- Use a separate copy for each vendor.
Software can help a municipality apply its own rules consistently. It cannot guarantee compliance with public records law, which varies by state and locality. Treat any such claim with caution and involve your municipal counsel.
Vendor: ______________________ Product: ______________________ Date: ____________
Evaluated by: ________________________________________________
1. Workflow fit
- The tool can represent our actual stages without forcing a different process
- Different request categories can follow different paths (for example, legal review only for some)
- Each request has an owner, status, due date and single history
- Department assignments are tracked individually, with their own status
- Department contributors can respond easily, including "no responsive records"
- Internal notes are clearly separated from requester messages
- Message templates can be edited to match counsel-reviewed wording
Notes: ____________________________________________________________
2. Intake and requester experience
- Residents can submit requests through a public portal
- The portal is clear and usable on a phone
- Staff can log requests received by phone, mail or in person
- Requesters receive a reference number and can check status
- Requesters can track requests without creating an account (if that matters to us)
- The portal can point requesters to records already published online
- The vendor explained what accessibility testing has been done, and whether any formal audit exists
Notes: ____________________________________________________________
3. Deadlines
- We configure our own deadline rules, rather than relying on vendor-encoded rules
- Business and calendar days are both supported
- Start event, after-hours handling and due time are configurable
- Holidays and closures can be maintained in a calendar
- Pauses and extensions are supported and recorded with reasons
- Each deadline shows how it was calculated, in plain language
- Rule changes do not silently alter deadlines for requests already in progress
- Manual overrides require a reason and are logged
- Reminders are sent before deadlines, and overdue requests are escalated
Notes: ____________________________________________________________
4. Documents
- Supported file types meet our needs (list gaps in notes)
- Uploads are validated and scanned for malware
- Text is extracted for search, including OCR for scanned documents
- Duplicate uploads of the same file are detected
- Originals are preserved and access to them can be restricted
Notes: ____________________________________________________________
5. Redaction
- Redactions permanently remove underlying content (we tested by trying to select or search redacted text)
- Metadata is scrubbed from released copies
- The system verifies that redacted content is gone before release
- Each redaction requires an exemption reason
- The vendor was clear about file types that cannot be redacted in the tool
- Release is blocked for unverified or outdated redacted copies
Notes: ____________________________________________________________
6. Review, release and audit
- Legal review can be required, and decisions are recorded
- Release approval by a separate person can be required
- Records are delivered to requesters securely
- The audit trail records who did what and when
- The audit trail is protected against editing
- Audit history can be exported
Notes: ____________________________________________________________
7. AI features (if any)
- AI features are off by default
- Turning them on is an administrative decision that is recorded
- AI never applies redactions, decides exemptions, sends messages or releases records
- Every suggestion requires a person to accept it
- The vendor explained clearly whether any record content goes to an external provider
- Data-use, retention and location terms for any external provider are available for counsel's review
- Prompts and document content are not stored in logs
- All workflows work fully with AI turned off
Notes: ____________________________________________________________
8. Security and access
- The vendor separated implemented controls from planned ones in writing
- Roles and permissions are granular
- Department contributors can be limited to their own requests
- Access to requester personal information can be restricted
- Two-step verification is available
- Single sign-on is available, if we require it (or its status is stated honestly)
- Hosting location and backup practices are documented
- Certifications, independent assessments and penetration testing status are stated plainly, including "none yet"
- Our IT staff have reviewed the vendor's security documentation
Notes: ____________________________________________________________
9. Integrations and reporting
- Integrations we need are available today (list which are only planned)
- An API and webhooks are available for our IT staff
- Standard reports cover open, overdue and closed requests
- Data can be exported to CSV
Notes: ____________________________________________________________
10. Implementation and support
- Responsibilities for configuration are clear (ours versus the vendor's)
- Open requests can be imported with original received dates preserved
- Training is offered for each role
- Support channels and response times are stated in the contract
- A pilot option is available, with agreed success criteria
Notes: ____________________________________________________________
11. Data ownership and exit
- The contract states that we own our data
- We can export all requests, documents and audit history in usable formats
- The export timeline on termination is defined
- The contract addresses what happens to our data if the vendor closes
Notes: ____________________________________________________________
12. Cost and contract
- Base price and included features are clear
- Add-on costs are listed
- Pricing model (per user, per department, flat) is understood
- Renewal increases are capped or defined
- Termination terms are acceptable
Notes: ____________________________________________________________
Summary
| Area | Must-haves met? (Y / N / Partly) | Concerns |
|---|---|---|
| Workflow fit | ||
| Intake and requester experience | ||
| Deadlines | ||
| Documents | ||
| Redaction | ||
| Review, release and audit | ||
| AI features | ||
| Security and access | ||
| Integrations and reporting | ||
| Implementation and support | ||
| Data ownership and exit | ||
| Cost and contract |
Items the vendor described as planned rather than built:
For more context on each area, see What to Consider When Evaluating Public Records Request Management Software. To see how CivicRecords answers these questions, visit the security page.
From Civicade · General guidance, not legal advice. More resources