Politics · Oct 13

I want one public record, not a paperwork war with city hall

Politics

A city project near my block has changed schedule twice, and the public explanations do not match what contractors told residents at the site. I want the document that shows when the latest schedule was approved and what work it covers. I do not want every email anyone has ever sent about the project.

A neighbor gave me a public-records request template that is six paragraphs long and asks for communications, notes, calendars, drafts, attachments, messages, and metadata over three years. He says agencies only respond when people sound serious. To me, it sounds like a request designed to create delay and fees while burying the answer in thousands of pages.

I am not asking this forum for legal advice or a prediction about what my city must release. Rules and exemptions differ, and the official records office should explain its process. My question is about scope and civic usefulness.

The record I think I need is the most recent approved project schedule or change order, including its approval date and the public office responsible. If no single document exists, I would ask the records officer to suggest the narrowest description that captures the decision. I can provide the project name, location, and approximate month. I would also ask for an estimate before any chargeable work proceeds.

Part of me worries that being cooperative will make the request easy to brush aside. Another part thinks the aggressive template treats staff as adversaries before anyone has refused anything. If the narrow request fails, I can document the response and refine it. Starting broad leaves no obvious next step except a fight.

How narrow is too narrow? What information helps a records office locate a decision without forcing the requester to know the agency's internal filing system?

Discussion

5 community replies

@JulesAfterDark

Describe the decision, date range, project, and likely record type, then state the information goal in plain language. You are not required to guess the exact folder name; the request should be specific enough that staff can recognize what would answer it.

@northstar88

A single final document may omit how the decision changed. If the public explanation conflicts with site information, a narrow set of approval emails or revision logs could be relevant. Start focused, but do not assume the final schedule tells the whole story.

@maren17

A staged request could handle that: obtain the latest approved schedule first, identify its revision date and approver, then request the bounded records for that change only if the conflict remains.

@TheoInTransit

Have you checked whether the project page, contract register, or meeting packet already contains the change order? Publicly posted records may answer the question faster and reveal the agency's naming convention.

@softfocus

What makes a public-records request both accountable and proportionate when the requester cannot know how the agency stores information?