Casework and correspondence tracking for elected offices

Reference article · 6 min read

An elected office runs two overlapping operations. One is casework: a resident calls about a water bill, a missed inspection, a delayed benefit determination, or a permit stuck in review, and a staff member tries to get a real answer out of the department that owns the problem. The other is correspondence: letters, emails, form campaigns, and petitions asking the officeholder to take a position. Both arrive on the same phone line and in the same inbox, both are judged by how quickly and personally the office responds, and both create records that outlive the staff member who made them.

Most offices begin with a shared mailbox and a spreadsheet. That holds until the caseload passes the point where anyone can say what is open, who owns it, or what a department actually promised. The purpose of a casework and correspondence system is not to answer mail faster. It is to make the office's commitments visible, to keep department responses moving, and to leave a record that is complete, retrievable, and correctly bounded.

Separate the case from the letter

These are different record types with different lifecycles, and conflating them is the most common design mistake.

• Casework concerns one person or household, names a third party agency, often requires authorization to proceed, and closes only when there is an outcome.
• Position correspondence expresses a view on an issue. It closes when a response goes out. Volume is the challenge, not investigation.
• Service requests such as potholes or streetlights usually belong in the jurisdiction's 311 or work order system. The elected office should be able to open a ticket there and see its status without becoming a parallel queue.

Decide early which system is authoritative for each type, and make sure a case can be reclassified without being retyped.

Build the referral loop, not just the log

The work that distinguishes an elected office is the handoff to a department and the follow-through. A system that only records the original contact captures the least useful half.

• One constituent record. Deduplicate by name, address, phone, and email, and show prior contacts at intake. A repeat caller with three open matters should not look like three strangers.
• A short controlled taxonomy. Issue, department, and district, chosen from a list rather than typed. Free text cannot be reported on.
• Referrals with due dates. Record who received the referral, what was asked, when a response is expected, and what came back. Aging reports and automatic reminders do more for response times than any template.
• Outcome coding at closure. Resolved, partially resolved, referred elsewhere, outside jurisdiction, constituent withdrew, no response from agency. Without this, the office cannot tell the difference between a department that helps and one that stalls.
• District and issue reporting. Counts by district, issue, department, and open age, exportable for briefing the officeholder and for budget conversations.

Handle release authorizations and sensitive casework carefully

Casework involving public benefits, health care, immigration status, taxes, education records, or child welfare frequently requires written constituent consent before an agency will discuss the matter. Federal privacy law, health privacy rules, student records law, and state confidentiality statutes all constrain disclosure in different ways, and many agencies publish their own privacy release form that they will accept in place of yours. Requirements and forms change, so confirm current practice with the agency and with your counsel rather than relying on a form a predecessor drafted.

In the system itself, that means release forms are attached to the case, scoped to the named agency and subject, dated, and flagged when they expire. It also means role-based access so that sensitive case notes and attachments are not visible office wide, restraint about copying identifiers such as Social Security numbers into note fields or unencrypted email, and an access log the office can review.

Manage volume without losing the personal reply

Form campaigns and petitions arrive in bursts. The system should identify duplicate or near duplicate text, group it into a single campaign, and let staff approve one response for the group while still allowing individual replies. Petitions are best stored as one record with an attached signer list rather than thousands of separate contacts. Templates need version control and a clear approval path, because a position letter sent in the officeholder's name is a public statement. Out of district contacts should be identifiable at intake and routed or acknowledged according to office policy.

Retention, disclosure, and the campaign line

Constituent correspondence is usually a government record subject to a retention schedule set by the state archives or the local records officer, and retention periods vary by record type and jurisdiction. Confirm the applicable schedule rather than letting each staff member decide when to delete mail.

Disclosure is more nuanced. Many states limit or exempt constituent identifying information in casework, and some legislative bodies are covered by different rules than executive agencies. Ask counsel how your office's records are treated before promising a constituent confidentiality.

Keep official casework strictly separate from campaign activity. Most jurisdictions prohibit using public resources for campaign purposes, and some restrict mass mailings in the period before an election. The practical rules are simple: no exporting constituent lists into campaign tools, no campaign staff accounts in the official system, and no solicitation language in official correspondence.

Plan for the transition before you need to

When an officeholder leaves, open cases, release authorizations, and files do not manage themselves. Decide in advance who inherits casework, typically the successor office or the agency that would normally handle the matter, and note that consent given to one office does not automatically transfer. Before the handover, close what can be closed, send closure letters, hand off live matters to the responsible department, apply any records hold, and deprovision accounts on a schedule. Whether the files belong to the office or to the individual varies by jurisdiction and body, so settle that question with your records officer and counsel in a quiet period, not during a transition.

What to ask and how to start

Ask vendors to demonstrate, with realistic data: intake and duplicate detection, a referral with a due date and an escalation, restricted access to a sensitive case, a form mail campaign grouped and answered, and an aging report by district and issue. Then ask how records are exported in bulk, in an open format, including attachments and audit history.

In the contract, require full data export on demand and at termination, hosting and support locations, breach notification timelines, configurable retention and legal hold, field level access control with audit logging, and written confirmation that constituent data will not be used for any purpose other than serving your office. Start small: agree on the issue taxonomy and the referral due date policy first, since those decisions shape everything the system can later tell you.

HQT builds and integrates case management, correspondence, and reporting systems for state and local government offices.

Frequently asked questions