Public records
How Municipal Teams Can Improve Request Visibility and Deadline Tracking
Practical ways for municipal records teams to see every open request, calculate deadlines consistently, and catch problems before they become overdue.
· 7 min read · Civicade
Missed deadlines rarely come from carelessness. More often they come from not being able to see the whole picture: which requests are open, who has them, and how much time is really left. This article covers how municipal teams can improve visibility into open requests and track response deadlines consistently, with practical examples and common pitfalls.
Two problems that feed each other
Visibility and deadline tracking are closely linked. If you cannot see every open request in one place, you cannot reliably know what is due. And if due dates are calculated inconsistently, even a complete list does not tell you where to focus.
In a hypothetical mid-sized city, a records officer might keep a spreadsheet of open requests while department contributors track their part in their own email. The spreadsheet shows a due date, but it was calculated by hand on the day the request arrived — before the city added an unexpected closure day and before the requester took a week to respond to a clarification question. The date on the sheet is no longer right, and nobody knows it.
Improving this means tackling both problems: a single, current view of the work, and a deadline calculation that is consistent, explainable, and updated when circumstances change.
Part 1: Improving visibility
Put every open request in one view
The foundation is a single list of every open request, regardless of how it arrived. For each one, the team should be able to see at a glance:
- Reference number and short title
- Current status
- Owner
- Departments involved and whether their part is complete
- Due date, and how many days remain
- Whether the clock is currently paused, and why
If your team uses a spreadsheet today, this can be a well-maintained sheet with these columns. If you use a dedicated tool, look for an inbox or board view with filters and saved views.
Make the next action obvious
A list of requests is more useful when each one shows what needs to happen next. "Collecting records — Police, due Thursday" is more actionable than "In progress." Statuses that describe the next step help people pick up work without asking.
Track department work separately
Department collection is often where time disappears. When a request needs records from several departments, track each department's part as its own assignment with an owner and a target date. That way, the records officer can see that Public Works has responded but Finance has not, without sending another round of emails.
Use saved views for different roles
Different people need different slices of the same work:
| Role | Useful view |
|---|---|
| Records officer | All open requests, sorted by due date |
| Records specialist | Requests assigned to me |
| Department contributor | Open tasks for my department |
| Legal reviewer | Requests awaiting legal review |
| Manager | Requests past their internal targets, and requests nearing their due dates |
Report regularly
A short monthly review helps the team spot patterns: categories that routinely take longer, departments that need more support, or periods when volume spikes. Keep reports simple and use them to improve the process, not to assign blame.
Part 2: Consistent deadline tracking
Write the rule down — with counsel
Public records laws differ by state, and some localities add their own requirements. Response periods, how days are counted, when the clock starts, whether it can pause, and whether extensions are allowed all vary. This article does not describe any jurisdiction's rules. Work with your municipal counsel and consult your state's official guidance to define the rules that apply to you.
Once defined, write the rule down in a form that can be applied the same way every time. A useful written rule answers these questions:
- Is the response period counted in business days or calendar days?
- How many days is the period?
- When does the clock start — when the request is received, or when it is acknowledged?
- How are requests received after business hours, on weekends, or on holidays treated?
- Does the day of receipt count as day one?
- Is the deadline at the close of business or at the end of the day?
- If a calendar-day deadline lands on a closed day, does it move to the next business day?
- Can the clock pause, for example while awaiting clarification, and under what conditions?
- Are extensions allowed, how long can they be, and what must be recorded?
- Are there other milestones, such as an acknowledgment deadline?
Your municipality may have different rules for different request categories. Record those as separate rules.
Keep the business calendar current
Deadline calculations depend on knowing which days your offices are open. Maintain a calendar of workdays, business hours, holidays, and closures, and update it each year — and whenever an unplanned closure occurs. Record the calendar in one place so that everyone works from the same version.
Record how each deadline was calculated
When a due date is set, record the inputs: which rule applied, when the clock started, which days were skipped, and any pauses or extensions. This makes it possible to explain the deadline to a colleague, a requester, or a reviewer later, and to recalculate correctly if something changes.
A plain-language explanation might read like this hypothetical example:
Received Friday after closing time, so the clock starts Monday. Ten business days counted, skipping the Wednesday holiday. Paused three days while awaiting the requester's clarification. Due at close of business on the resulting date.
Handle pauses and extensions explicitly
Pauses and extensions are where manual tracking most often goes wrong. A clerk sends a clarification request, the requester answers a week later, and the spreadsheet due date is never updated. Treat pauses and extensions as recorded events with a start, an end, a reason, and the name of the person who recorded them — and only use them where your counsel has confirmed the law permits it.
Don't change the rules under existing requests
When a rule changes — for example, after counsel's review or a change in law — decide how it applies to requests already in progress. A common, defensible practice is to keep the rule version that applied when the request was received and apply the new version to new requests from an effective date. Document whatever approach your counsel recommends.
Set reminders before the deadline, not on it
Reminders are most useful a few days before a deadline, when there is still time to act. Decide which thresholds make sense for your team — for example, a reminder several business days out and another the day before — and who should receive them. Decide also who is notified when a request becomes overdue, so it gets attention from someone who can help.
Common pitfalls
Calculating once and never again. A due date set on day one becomes wrong when the calendar changes, a pause occurs, or an extension is granted. Recalculate when inputs change.
Unrecorded overrides. Sometimes a deadline must be adjusted manually. That is fine, but record the reason and who made the change.
Different people, different methods. If two staff members would calculate the same deadline differently, the rule is not written down clearly enough.
Assuming a vendor's default rule is correct. Some products ship with example rules. Treat them as starting points to review with counsel, never as legal determinations.
Visibility that depends on one person. If the only complete view of open requests is in one person's head or personal files, coverage during absences is at risk.
How software can help — and where it can't
Software is good at applying a written rule consistently, counting business days across holidays and daylight-saving changes, recalculating when pauses or extensions occur, and sending reminders on schedule. It cannot decide what the rule should be. That is a legal question for your counsel.
CivicRecords handles deadlines this way. Each municipality configures its own deadline rules — business or calendar days, start event, after-hours rollover, due time, pause and extension settings, and reminder thresholds — along with a holiday and closure calendar. Rules are versioned with effective dates, so existing requests keep the version they started with. Each request shows a step-by-step plain-language explanation of its deadline, and requesters can see a plain-language explanation through their tracking link. Manual extensions and overrides require a reason and are recorded in the audit trail. Reminders and overdue escalation run automatically. CivicRecords does not encode any state statute; the example rule included at setup is marked as needing configuration and counsel validation.
You can read more about how this fits into the broader workflow on the CivicRecords product page, or see our guide to moving from shared inboxes to a trackable workflow.
A visibility and deadline checklist
- One list of every open request, from every intake channel
- Each request has an owner, a status, and a recorded due date
- Department assignments are tracked individually
- Deadline rules are written down and reviewed by counsel
- The business calendar includes this year's holidays and closures
- Each due date records how it was calculated
- Pauses and extensions are recorded with reasons
- Rule changes have effective dates and do not silently alter existing requests
- Reminders go out before deadlines, and overdue requests are escalated
- A short monthly review looks at what is overdue and why
To see where your team stands today, work through our Public Records Workflow Assessment Checklist. If you'd like to see configurable deadline rules in action, you can request a demo.
This article is general information, not legal advice. Public records requirements vary by state and locality. Confirm your obligations with your municipal counsel and official state guidance.