You need an outcome number from the program team, a salary figure from finance and a bio from a partner. You send an email asking for "any information you have on the project." A week later you have two attachments nobody can use and one reply that says "will get to this."
Grant writers depend on people who are not grant writers and who have other deadlines. This article shows how to ask in a way that gets answers: interview instead of emailing, request the specific sentence, number or document, set a deadline inside your deadline and store every answer so you never have to ask again.
Why "send me information" fails
A broad request makes your colleague do two jobs: guess what you need, then find it. Both are slow, and neither feels urgent. The reply arrives late and incomplete, and you end up chasing it.
A specific request is the opposite. It can be answered in a few minutes from memory or a quick lookup. "What was the total number of unduplicated clients served in the most recent full fiscal year, and which report did it come from?" is a request someone can actually act on.
Before you contact anyone, work out what you need from the funding notice. Mark each place where the application needs a fact you do not have, such as a number, a name, a date or a document, and list them by person. Reading the notice first means you ask once, not four times.
Interview, don't email
For anything complex, a 20-minute call with prepared questions can get you more than a long email thread. You hear the reasoning behind the number, you can ask a follow-up straight away and the colleague does not have to write anything.
How to run it:
- Send the questions in advance. A short list, three to six items, so they can think or look things up.
- Book 20 minutes, not an hour. Short meetings are easier to say yes to.
- Record the answers in their words. Write notes during the call, then read the key points back at the end: "So the figure is 412, from the third-quarter report?"
- Send a written summary the same day. It confirms what was said, and it gives them a chance to correct you.
Questions that work for a program lead
- What problem does a participant come in with, and what changes for them?
- What numbers do we track, where do they live and who pulls them?
- What did we change in the past twelve months, and why?
- Is there a story from a participant, with identifying details removed, that shows the difference?
Notice the pattern: each question can be answered in a sentence or two, and each one maps to a section of the application.
Ask for the exact thing
When email is the right tool, make each request complete. A good request has five parts: the exact item, the format, the deadline, why it matters and what to do if it does not exist.
Here is a hypothetical before and after. Say a grant writer is preparing a budget for a youth program.
Before: "Hi Marcus, can you send me the staffing and budget info for the after-school program? Thanks!"
After: "Hi Marcus, I'm building the budget for the county youth grant, due September 30. By Friday, could you send (1) the current salary and fringe percentage for the two site coordinators and (2) the monthly cost of the van lease? A reply in the body of the email is fine. The funder asks for staff cost by position, so these two items let me fill in two budget lines. If you do not have the van figure, tell me who does."
The second version can be answered in five minutes, and it tells Marcus why the question matters. It also gives him a way out if he does not hold the information.
Finance is a special case. For federal awards, salary charges must rest on records of the work actually performed, and under 2 CFR 200.430, budget estimates alone do not qualify as support for charges to a federal award, though they may be used for interim accounting purposes under conditions the rule lists. If your budget includes staff time on a federal grant, ask the finance lead how the organization documents effort now, so the narrative describes a system that exists. The budget justification, line by line explains how those numbers appear in the application.
Build a deadline inside the deadline
Colleagues respond to dates. If your application is due on the 30th, the information that feeds it cannot arrive on the 29th. Work backward:
- Internal deadline for information: at least a week before you start drafting that section.
- Reminder: one friendly nudge two days before.
- Escalation path: if it still has not arrived, ask your proposal owner to help. Deciding who owns the proposal makes this simple, because one person has the standing to ask a supervisor for a few minutes of a colleague's time.
Say it plainly in your first request: "I need this by Friday so there's time for follow-up questions." Knowing a second round is coming also tells people the date is real.
Be kind about it. Thank people when they answer, show them where the material landed in the application and tell them how it did. People who see their work used are more likely to see the next request as worth their time.
Keep every answer you get
The best way to reduce requests is to stop asking for the same thing twice. Every time a colleague answers a question, store the answer where you can find it later.
- A fact sheet. Client counts, staff numbers, budget totals, program descriptions and dates, each with a source and a date.
- Bios and job descriptions for key staff, kept current.
- Reports and evaluations you can quote from.
- Participant stories, with consent noted.
Review it once or twice a year and ask owners to confirm that their entries are current. The boilerplate library covers building and maintaining text you reuse, and key personnel shows what to keep for each person named in an application.
Your next step
Take your next information request and turn it into a list of specific questions, each with a named person and an internal deadline. Send them together, or book the 20-minute call. After you receive the answers, save each one in a shared document with its source.
SoliContraX works the same way at the application level: it keeps a knowledge base of your organization's own materials and reuses it across applications, and it lists what is still missing from a draft, which makes a clearer request than "any information you have." See how to get started.