Escalate on a schedule rather than on frustration, anddocument every attempt. The statutory clock runs against the agency as a whole,not the department sitting on the material, so the records officer carries adeadline for work they cannot compel. A written escalation trail is the onlyreal protection.
Almost every records officer has had this month. The requestis scoped, the custodians are identified, the task went out ten days ago, andone department has not replied to anything. The deadline does not care.
It is worth being precise about the shape of it, because theframing determines what you do next.
The records office holds a legal obligation with a fixeddate attached. It does not hold authority over the departments that possess therecords. Those two facts sit in different parts of the organization chart, andthe gap between them is where these requests stall.
That is not a failure of anyone's character. The departmentthat has gone quiet is usually not obstructing. They are short-staffed, therequest landed with someone who has never handled one, it looks like a largeamount of unfamiliar work, and nothing in their week makes it urgent. Meanwhilethe clock runs against your name.
Treating it as a motivation problem produces reminder emailsthat get read and deprioritized. Treating it as a structural problem producesan escalation path, which is the thing that actually moves it.
The word that matters is schedule. Escalation triggered byfrustration arrives at unpredictable times, reads as personal, and is easy todismiss. Escalation triggered by a date is routine, impersonal, and hard toargue with.
Set the schedule when the task goes out, not when it isalready late. A workable ladder looks like this.
First contact, at assignment. The task, the specificrecords sought, the date you need them by, and the statutory deadline it feeds.Naming the statutory date early is the single most useful thing in the wholesequence, because it converts your internal request into a legal one in thereader's mind.
Second contact, at the halfway point. Same content,copied to the department head. Not as a threat, as a status update to someonewho needs to know their team has an open obligation.
Third contact, when the remaining time is less than thework will take. This one goes to whoever carries the agency's legalexposure, usually counsel or a deputy administrator, and it states plainly thatthe response will be late, which department the material sits with, and whathas been asked and when.
Each step is written, each is dated, and none of themrequires the records office to have authority it does not have.
The escalation trail is not administrative overhead. It isthe record that determines who owns the failure.
Without it, a late response is a records office problem.With it, a late response is a documented dependency that three written requestsfailed to move. Those are very different conversations with an oversight body,and the only thing separating them is whether somebody kept the dates.
Keep the trail inside the case file rather than in your sentitems. Escalation that lives in one person's mailbox disappears the moment thatperson is on leave or leaves the agency, which is reliably the moment itbecomes relevant.
A records officer saying responses are slow gets sympathyand nothing else. A records officer showing that one department accounts formost of the elapsed time across forty requests gets a meeting with someone whocan change it.
That is the argument for tracking time by department ratherthan only by request. Per-request delay looks like bad luck. The same delayaggregated across a quarter looks like a resourcing decision somebody needs tomake, and it points at the specific place to make it.
Govflo models thestages that run in parallel separately from the ones that gate everythingbehind them, so several departments searching at once are visible as their owntracks rather than as a single status that says open. It is built to measurehow long a request sits in each stage, which is what turns a run of individualdelays into the aggregate number that changes a resourcing conversation.
It does not compel a department to answer. Nothing does,short of authority the records office generally does not hold, which is why thewritten trail matters as much as the reminder.
Sometimes it will, and the request is still incomplete. Twothings help.
Release what you have. Rolling production gets records tothe requester sooner, keeps the file visibly moving, and stops one slowdepartment from holding up everything else. Most disputes begin with silencerather than with a decision the requester disliked, and a requester who hasreceived two batches and been told what remains rarely escalates.
Tell the requester the truth about the delay. Not theinternal politics, but the fact of it: material is outstanding from adepartment, you have requested it on these dates, and here is when you expectit. Statutes vary on what notice is required, but candor at this point costsnothing and prevents most appeals.
