Public Records Request Routing
A practical employee procedure for recognizing possible public records requests, sending them to official intake, and alerting a preservation contact when relevant—without deciding disclosure or retention.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Local government · County and municipal services · Public education · Public utilities
Overview
Public Records Request Routing is a procedure page for employees who may receive a request for organizational records or information. Its four-step path asks the receiving employee to recognize a possible request, send it with its original message or attachments to official intake, alert the designated preservation contact when relevant, and leave review and response with the authorized role. The worked example follows a resident asking a fictional Harbor County Services counter employee for last month's inspection notes.
Use this template to explain the first handoff across service counters, email, and other employee-facing channels. It makes the operational boundaries explicit: record the date and channel, preserve the original request context, use the approved intake route, and do not promise disclosure or a response date. The roles section distinguishes official intake, preservation contact, and response owner, and identifies a route for correcting outdated guidance.
This page is not a legal interpretation, disclosure decision tree, retention schedule, or records search procedure. It does not establish statutory deadlines, exemptions, local applicability, or an intake-system integration. Before publishing, replace the fictional ownership and route with verified organizational details and point employees to the authoritative retention procedure. If employees need detailed instructions for logging, searching, reviewing, or responding, publish those as separate authoritative procedures and link them from the relevant step rather than expanding this routing guide into competing policy.
Standards & compliance context
- Treat this template as routing guidance only; confirm applicable public-records requirements, scope, and deadlines with the organization's authorized legal or records-management roles.
- The page distinguishes request routing from disclosure and retention decisions, which must remain with roles authorized by the organization's approved procedures.
- Use the organization's approved preservation handoff when relevant; this template does not define retention requirements or authorize deletion.
- Check the published page for WCAG 2.1 AA accessibility, including descriptive links, meaningful headings, keyboard navigation, and readable contrast.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Route possible records requests to authorized intake
Use this notice to keep the receiving employee's role focused on routing, not deciding what must be disclosed.
-
Fictional example: Harbor County Services uses this guide to show the handoff. Follow your organization's approved procedure and scope; the receiving employee does not decide whether records must be disclosed.
Recognize, route, and hand off
Follow the ordered steps to send the original request context to official intake and alert the preservation contact when appropriate.
-
If someone asks for records or information, use this path rather than deciding the request yourself. Keep the original message and attachments with the request as you use the official intake route. Do not promise a response date or decide what may be disclosed. Recognize the request Treat a request for organizational records or information as a possible public records request, even if it arrives in a conversation, email, or at a service counter. If unsure, route it to official intake. Use official intake Send the request and its original message or attachments through your organization's authorized intake route. Include the date received and the channel through which it arrived. Alert the preservation contact when relevant If the request may involve records that need preservation, notify the designated preservation contact through the approved handoff. Do not make independent retention or deletion decisions. Leave response ownership with the authorized role The authorized response owner coordinates next handling and any response. Do not promise disclosure, interpret exemptions, or send records directly unless your approved procedure authorizes that action.
Worked example: inspection notes at a service counter
See how an employee can handle an in-person request while leaving records review and response ownership with authorized roles.
-
A resident asks a Harbor County Services counter employee for last month's inspection notes. The employee records the date and channel, forwards the request and any original written message through official intake, and alerts the preservation contact because the request may relate to records that need preservation. The employee does not search personal files, decide which notes can be released, or promise when the resident will receive them. Official intake logs and routes the request; the authorized response owner coordinates the response under approved procedures.
Image
Request types and approved handling
Consult the organization's approved guidance for request handling rather than treating this page as a disclosure or retention decision tool.
Roles, ownership, and upkeep
Use the role definitions, ownership, and correction path to keep the routing instructions accurate and within scope.
-
Official intake receives, logs, and routes possible requests. Preservation contact receives concerns about preserving potentially relevant records; this handoff does not decide retention requirements. Response owner coordinates authorized review and response. The receiving employee routes the request and avoids making disclosure decisions. Public Service Operations owns this fictional example guide. Ask the official intake role for help identifying the approved routing procedure. Send an outdated-route or guidance correction through that role to Public Service Operations; do not include sensitive request material outside its authorized intake process. This page covers disclosure-request routing, not internal records-retention decisions. Use the organization's authoritative retention procedure for those decisions.
How to use this template
- Replace the fictional organization and owner details with confirmed names for official intake, the preservation contact, the response owner, and the guide's accountable team.
- Add the organization's approved intake route and authoritative retention-procedure destination using supported site links, and verify that employees can access them.
- Publish the page where employees who receive requests can find it, such as a public-service or records-handling knowledge area, with a clear navigation label.
- When a request arrives, send it and its original message or attachments through official intake and include the date received and channel.
- If the request may involve records needing preservation, notify the designated preservation contact through the approved handoff without making retention or deletion decisions.
- Ask the content owner to review the page when a route or role changes, and send corrections through the approved route without attaching sensitive request material.
Best practices
- Keep the official intake route visible beside the recognition and handoff steps so employees do not have to infer where to send a request.
- Preserve the original message and attachments with the handoff, and record the date and channel through which the request arrived.
- Use verified role names and destinations rather than generic labels that leave employees guessing about the authorized recipient.
- State plainly that the receiving employee does not decide disclosure, interpret exemptions, or promise a response date.
- Describe preservation as a notification to the designated contact, not as permission for employees to alter retention or delete records.
- Keep the retention procedure as the authoritative home for retention decisions and link to it rather than reproducing its rules here.
- Review the route and role details after any intake-process change, and provide a correction path that does not expose sensitive request material.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Which requests should employees route through this procedure?
Route a request for organizational records or information as a possible public records request, whether it arrives in conversation, by email, or at a service counter. If the request is unclear, send it to official intake for assessment. The guide does not determine whether a request falls within a particular law or organizational policy.
Who should receive and handle a request?
The employee who receives the request sends it and its original message or attachments through the organization's authorized intake route. Official intake logs and routes the request, while the authorized response owner coordinates review and any response. A preservation contact is notified through the approved handoff when preservation may be relevant.
When should an employee notify the preservation contact?
Notify the designated preservation contact when the request may involve records that need preservation. Use the approved handoff rather than making an independent retention, deletion, or preservation decision. The contact's role and escalation route should be specified in the organization's procedure.
Does this guide determine disclosure requirements or response deadlines?
No. It is a routing procedure, not a legal determination or response schedule. Employees should not promise a response date, interpret exemptions, or promise disclosure. The authorized response owner handles review and response under approved organizational procedures and applicable requirements.
What information should accompany the handoff?
Send the request through official intake with the original message or attachments, the date received, and the channel through which it arrived. Preserve the context of an in-person or conversational request according to the approved procedure. Do not send sensitive request material through channels that are not authorized for intake.
Can the receiving employee search for records or send them directly?
This example does not authorize employees to search personal files, decide what can be released, or send records directly. Leave those actions to the roles and steps defined by your organization's approved procedure. Follow a different authorized workflow only when the organization explicitly provides one.
How should an organization customize this page?
Replace the fictional Harbor County Services example with confirmed local role names and the actual official intake route. Add the approved preservation handoff and link to the authoritative retention procedure if the site provides one. Confirm the scope and correction route with the content owner before publishing.
How often should this routing guide be reviewed?
Review it whenever the intake route, preservation contact, response ownership, or authoritative retention procedure changes. Public Service Operations owns the fictional example and receives corrections through official intake. In a real organization, name the accountable owner and establish a review cadence under the site's content governance process.
Does this template connect to an intake or records-management system?
The page describes a handoff but does not include a configured intake integration, form, or workflow. Add a destination only after confirming the organization's authorized route and the page's supported link options. Until then, publishing the procedure requires providing employees with the real approved intake instructions.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Public Records Request Routing ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
