Are You Grant-Ready? What to Put in Place Before Applying

Grant readiness is the work you do before an opportunity is posted. It is unglamorous, it never feels urgent, and it is the single biggest differentiator between organizations that win competitive funding and organizations that keep narrowly missing.

The pattern is familiar. A strong organization doing genuinely good work sees a well-matched solicitation with a three-week deadline. Two of those weeks get spent locating financial statements, reconstructing program numbers, and writing a logic model from scratch. The narrative gets drafted in the final days. It reads like it was written in the final days, because it was.

Readiness moves that work earlier, so that the weeks before a deadline can be spent on the actual case for support.

Governance and organizational documents

These are the items reviewers use to establish that you are a functioning organization. Have current versions in one place, and know where that place is.

• IRS determination letter, and current state charitable registration in every state where you solicit
• Articles of incorporation and current bylaws, with the date they were last reviewed
• Board roster with affiliations, terms, and officer roles
• Conflict of interest policy, with signed annual disclosures
• Financial policies and procedures, including approval thresholds and separation of duties
• Most recent audit or financial review, and the current-year operating budget approved by the board
• W-9, DUNS or UEI number, and SAM.gov registration if you pursue federal funding

A word on SAM.gov registration in particular: it expires annually, and renewal can take longer than expected. An expired registration has cost organizations opportunities they were otherwise well positioned to win.

Program design that can be described precisely

Reviewers are evaluating whether your program is likely to work. That judgment rests on how specifically you can describe it.

For each program you intend to seek funding for, you should be able to state the following without improvising.

• The problem, with evidence. Who is affected, where, how many, and what it costs them and the community. Data, not assertion.
• The intended outcome. One primary outcome, plus no more than three supporting ones. Outcomes describe change in people or conditions, not services delivered.
• The theory of change. Why these activities should produce that change, including the assumptions the logic depends on.
• The program model. Dosage, sequence, staffing, setting, eligibility, and intake. How much of what, delivered by whom, to whom, over what period.
• The evidence base. What this design is built on, whether that is published research, a recognized model, or your own documented results.

Outcome data you can actually produce

This is where most organizations are least prepared, and it is the area funders have grown most serious about.

Before applying, you want a baseline. Not a perfect one. A real one. You should know what you currently achieve so that the target you propose is credible and so that you can report against it later without inventing a measurement system mid-grant.

• Indicators for outputs and outcomes. Outputs count what you did. Outcomes capture what changed. You need both, and you need to know which is which.
• An owner for each measure. A named person who collects it, using a specific instrument, on a specific schedule.
• A place the data lives. One place. Not four spreadsheets maintained by three people with different definitions of the same field.
• At least one period of history. A year of imperfect data beats a perfect plan to start collecting data next quarter.

If you are not there yet, start now with a small set of measures. The organization that has tracked five indicators consistently for a year is in a far stronger position than the one proposing to track twenty starting at award.

A budget that holds up to scrutiny

The budget is read as evidence of organizational competence. A budget that does not match the narrative undermines both.

Build program budgets on fully loaded cost. That means salaries plus benefits and payroll taxes, the supervision time the program actually consumes, the share of facilities and technology it uses, and the cost of the evaluation and reporting the grant will require. Organizations routinely omit the last one and then discover that compliance reporting is consuming staff time that was never funded.

Know your indirect cost rate, or know how you allocate shared costs and be able to explain the method. Be able to show which other sources support the program, and what happens to it when this grant ends.

Fit, before effort

Readiness also means being ready to decline. A high-volume approach to every open solicitation produces low win rates and, more damagingly, pulls programs toward whatever is fundable rather than toward what the community needs.

Before you commit staff time to an application, ask four questions. Does this fit our strategic priorities? Can we deliver what it requires with the capacity we have? Can we meet the reporting obligations? And if we win it, what happens to this work when the funding period ends?

A disciplined pipeline of well-matched opportunities will outperform a large pipeline of loosely matched ones, and it will cost your staff far less.

Plan the post-award work before the award

Winning is the beginning of an obligation. Decide in advance who owns compliance, who tracks deliverables, who assembles reports, and when. Organizations that sort this out after the award tend to spend the first quarter of the grant period building the tracking they should have designed during the application.

Readiness is a standing capability, not a project. Built once and maintained, it turns every future opportunity from a scramble into a decision.