A practical framework for scoping a foundation grant in three weeks, not three months.

Grant timelines rarely slip during writing. They slip during scoping, because scoping produces no artifacts and therefore no visible progress. A week spent deciding whether a funder is actually a fit looks, from the outside and often from the inside, like a week where nothing happened.

So it gets skipped, and the team starts drafting. Three weeks later somebody asks what the ask amount is, and the answer changes the entire argument.

The fix is to give scoping four named deliverables, each small enough to finish in a sitting and concrete enough that someone else can review it.

Origin. Why this funder, in two sentences, with evidence from their last three grant cycles. Not 'they fund education in the Southeast' — that is their website. Something closer to: 'their last nine education awards clustered between $75K and $150K, all multi-year, all to organizations with existing outcome data, and two of them went to peers of ours.' If you cannot write those two sentences, you are not ready to write anything else.

Alignment. The specific overlap between their stated priorities and a program you already run. The phrase 'already run' is load-bearing. Designing a new program to fit a funder is the single most reliable way to end up two years into work your team resents.

Ask. The number, and the shape of the number. Shape means duration, restriction, whether indirect is included, and what the money is buying in terms of capacity rather than activities.

Plan. Who writes what, by when, and who reviews it. Named people, real dates. A plan with a role instead of a name is a plan with a gap in it.

Week one produces origin and alignment. This is research work, mostly reading — prior awards, 990s, the funder's own reports, and any conversation history you have. Ending week one with a documented no is a successful week one, and teams need to hear that explicitly or they will never do it.

Week two produces the ask and the budget skeleton. Skeleton means the line items and their relative sizes, not the final arithmetic. The point is to fix the shape of the request before any narrative depends on it.

Week three is drafting against a settled frame. Writing is fast when the argument is already decided. Most teams believe drafting is the slow part because they have only ever drafted while still arguing.

The common failure mode is starting the narrative before the ask is fixed. Every change to the number cascades: the outcomes change, the staffing changes, the timeline changes, the evaluation plan changes. Teams end up rewriting the same three paragraphs five times and reasonably conclude that grant writing is miserable.

The second failure mode is scoping without a decision point. If there is no moment where someone is authorized to say 'no, this is not a fit,' the scoping phase has no exit condition and simply blends into drafting. Put the go/no-go on the calendar at the end of week one and give it to a named person.

A few practical notes from teams running this. Keep all four artifacts in one place the whole team can see, not in the lead writer's notes. Timebox origin research to four hours — the return drops sharply after that. And write the two-sentence origin statement even when the funder is obvious, because the discipline of writing it is what surfaces the cases where it is obvious and wrong.

Three weeks is not a magic number. Larger federal applications need six to eight, and the same four deliverables scale to fit. What does not scale is skipping them.

Fix the number early. Defend it in the budget narrative. Then write.