Your executive director forwards a funding notice at 4:50 on a Thursday. "This looks perfect for us. Can we get it in by Friday?" The notice has a narrative, a budget, four attachments and a registration you haven't checked.
You can say yes and absorb the cost, or say no and look uncooperative. There is a third option: give your leader the information they need to make a good decision. This article covers why these requests happen, how to make the work visible, how to say "not yet" with options and one document to share this week.
Why the request lands this way
Leaders usually see an opportunity and a dollar figure. The hours, the dependencies and the rules sit out of sight. A leader who has never assembled an application can't tell a two-day task from a two-week one.
That's a gap in information, not bad intent. A request like this often comes from enthusiasm for the mission and a real need for money. Closing the gap is part of your job, and it usually works better than resisting.
Make the work visible
Put the work on one page before you respond. A leader can weigh something they can see.
Start with the facts of the notice
Read the notice for the real due date, the required parts and any registration step. Federal rules set expectations for notice windows: under 2 CFR 200.204, an agency should make a funding opportunity available for at least 60 calendar days, and none should be open for less than 30 unless the agency determines that exigent circumstances justify it. A leader who thinks the deadline is tight may be reading it wrong, or may be right. Either way, the notice sets the schedule.
Check registrations first, because they can't be rushed. Grants.gov says SAM.gov registration can take an average of 7 to 10 business days after all information is entered, and weeks or months if information isn't available or verified. If your organization isn't registered, that alone can decide the question. Registrations before you need them covers what to check.
Build a standard timeline
Keep a template that shows what a typical application takes, in working days. Here is a hypothetical example for a mid-sized application with 20 working days available:
| Phase | Working days | What happens |
|---|---|---|
| Decide | 2 | Read the notice, check eligibility, run a go/no-go |
| Plan | 2 | Agree on the concept and outline, request inputs from partners and finance |
| Draft | 7 | Write the narrative and budget |
| Internal review | 3 | Program, finance and leadership read the draft |
| Revise | 3 | Fold in comments |
| Final checks and upload | 2 | Compare against the notice, build the package, submit early |
| Buffer | 1 | Portal trouble and surprises |
| Total | 20 |
Share the template once, in calm conditions, before the next urgent request. When a notice arrives, you can lay it over the actual dates and show where the squeeze falls.
Name the dependencies
Many of the delays belong to other people: a partner letter, a signature, audited financials, board approval. List who owns each one and the date you need it. A leader who sees "waiting on the board chair's signature" will make the call that moves it.
Say "not yet" with options
A flat "that's impossible" ends the conversation. A set of choices continues it. Lay out two or three:
- Meet the date by cutting scope. "We can submit by Friday if we skip the optional attachments and use last year's logic model, but the application will be thinner."
- Meet the date with help. "We can do it with a program lead for two days and finance for one. Who can we borrow?"
- Aim for the next deadline. "We'd have a stronger application in the next cycle. We can use the time to line up partners and data."
- Pass on this one. "It's a modest award for a heavy lift. Here's what else we could spend that time on."
Say what each option costs: other work that slips, risk of an error and the hours involved. Then ask the leader to choose. The decision stays with them, and you've made sure they're making it with the facts. A go/no-go check gives you a neutral way to compare.
Tone matters here. Open with what you can do, not what you can't: "I want to pursue this. Here are the ways to make it work." Bring the one-page timeline, point to the dates, and keep the conversation on the application, not on workload complaints.
If the leader pushes back, ask what is driving the date. Sometimes the real deadline is a board meeting or a budget gap, and that opens options the notice's due date doesn't.
When the timeline really is short
Sometimes the answer is yes, and the work has to move fast. A few steps make a compressed schedule safer:
- Decide who has final say on content and stick to it.
- Freeze the draft at an internal deadline a day or two before the real one.
- Submit early. Portal problems are easier to fix with time left. Portal panic covers what to do when a submission fails.
- Plan the recovery. Tell leadership that the people who sprinted will need lighter days afterward.
A short timeline is a reasonable request when it's chosen with open eyes. It becomes a problem when it's a habit that nobody has examined.
Your next step
Draft a standard timeline for your typical application, using the table above as a starting point and your own phases and days. Share it with your executive director in a short meeting, and ask for one thing: that future requests come with the notice, so you can lay the timeline over the real dates.
When a short timeline can't be avoided, SoliContraX can give you a draft to review. Upload the notice, approve a concept and start from your own materials. The decisions about what's worth pursuing still belong to you and your leaders. See how to get started.