Questions for the people responsible for public funding

Establish the record first

Ask funding officials questions a document can check: what a line item funds, who approved an expenditure and when, what reporting rule applies, and what record would show whether the money was spent as budgeted. Before you request an interview with anyone who oversees public animal funding, find out what already exists on paper. Budgets, grant awards, board minutes and contract files often answer basic questions faster than any conversation will, and they carry a paper trail an interview can’t replace.

Check the agency’s own website first. That is also where the federal guidance starts: before making a request, look to see whether what you want is already publicly available, and FOIA.gov carries a search tool for material agencies have already posted online. If the material isn’t posted, record that absence as part of your preparation and skip the guessing.

When the records you need sit with a federal agency, the federal government’s guidance on making a FOIA request lays out the actual mechanics: requests must be in writing and reasonably describe the records sought, most agencies take requests electronically, and there’s no required form.

That guidance also draws a boundary worth keeping in mind before you interview anyone: the law “does not require agencies to create new records or to conduct research, analyze data, or answer questions when responding to requests.” An interview and a records request serve different purposes for that reason alone.

That guidance covers federal agency records specifically. A city animal control department or a county-funded shelter follows a different process, and locating that process belongs in your preparation from the start.

Confirm which body actually holds the record before you draft a single question. A funding board, an oversight commission and a contracted nonprofit may each hold different pieces of the same story, and knowing who holds what shapes every question that follows.

Build a written record log before you request time with anyone, with columns for the document found, its date, what it shows, what is missing, and what only a person can explain. Note what you found, what’s missing, and what a source can add that a document cannot.

What questions should you ask a funding official?

Write questions that ask for facts a person can actually verify, and keep opinions about intent or character out of the list. A funding official can tell you what a line item covers, when a contract was signed, or how a disbursement was reported.

They cannot reliably tell you what “most” taxpayers think or predict outcomes with certainty, so don’t frame questions that invite that kind of guess.

Anchor every question to a document, date or dollar figure you’ve already found in the record. “This report shows a transfer of funds in this line item. Walk me through what that covers” gets a more useful answer than “Is this program working?”

Separate factual questions from accountability questions, and ask them in that order:

• What does this line item fund, specifically?
• Who approved this expenditure, and on what date?
• What reporting requirement, if any, applies to this fund?
• What record would show whether the funds were spent as budgeted?

Avoid questions that ask an official to characterize animal welfare outcomes, medical results or behavioral claims. Those require the kind of clinical or scientific evidence a funding interview cannot produce and a records desk cannot certify.

If a source volunteers a welfare or health claim, treat it as their statement awaiting documentation, and follow up by asking what document supports it.

Keep your list short enough to get through in the time you’re given. A focused set of answerable questions produces a usable record; a long list of open-ended ones produces a transcript full of hedged non-answers.

Separate an interview from a records request

An interview and a records request are two different tools, and confusing them wastes both. A records request compels an agency to search for and produce existing documents.

An interview asks a person to explain, in their own words, what those documents mean or why a decision was made.

The federal guidance on this point is direct: agencies aren’t obligated “to conduct research, analyze data, or answer questions” simply because you’ve filed a request. That limit matters when you’re timing your reporting.

If you need an agency’s reasoning explained, that’s an interview question. If you need the underlying disbursement record itself, that’s a request, and the federal request process outlines how such requests move through an agency’s FOIA office once filed in writing.

Don’t ask an official to “confirm” something during an interview that a document should already show. That wastes the conversation and gives the source room to reframe a fact as opinion.

Instead, request the document, read it, then ask what it means.

Sequence matters here. File any records requests early. Agencies typically process requests in order of receipt, and the guidance says the time it takes will vary with the complexity of the request and any backlog already pending, with simple, targeted requests seeking fewer pages moving faster than ones needing searches in multiple locations. You can narrow your request before filing and ask the agency about its current backlog; the response time isn’t guaranteed. Schedule interviews once you have documents in hand, so your questions can point to a specific page, date or figure rather than asking someone to summarize from memory.

Keep a written log of which questions were answered by documents and which required a person to explain. That log becomes part of your own record of how the story was built, and it protects you if a source later disputes what was said.

Give the response its proper place

Treat an official’s answer as their statement awaiting verification until a document backs it up. If someone tells you a program met its goals or that spending followed the budget as written, attribute that claim to them by name and title, and hold it there until a document confirms it.

Note where the answer came from and how it compares to what the record shows. If an answer matches the paper trail, say so plainly. If it doesn’t, or if no document exists to check it against, that gap belongs in your reporting too.

Some questions won’t get answered at all. An official may decline to comment, defer to a spokesperson, or say the information isn’t available.

Record that outcome exactly as it happened. A non-answer is itself part of the record, and noting it accurately is more useful than smoothing it over.

Keep a clear line between what a document establishes and what a person asserts. A budget line is a fact. A characterization of that line’s success is a statement someone made, on a given date, that a future document could confirm or contradict.

When you publish, attribute claims to their source consistently: the agency, the official, the document. Readers should be able to tell, sentence by sentence, whether they’re looking at a verified record or a stated position waiting on verification.

Then go back to the log. The questions a document answered and the questions a person answered are two different columns, and the rows still empty after the interview are your next records request.