Grant Proposal Writing FAQ: 13 Questions Grant Writers Ask Before Every Submission
Published: Last updated:
Reviewed:
TLDR
This FAQ prevents three specific failures: submitting a 15-page narrative to a funder whose RFP specifies 5 pages, which signals the applicant cannot follow instructions and eliminates the application before review; writing a sustainability section that says 'we will seek additional grants,' which reviewers score as non-responsive because it restates the problem the funder is trying to solve; and receiving an award and then managing compliance in a spreadsheet disconnected from the proposal budget, creating a reconciliation gap that produces audit findings.
Three specific failures that grant proposal writers repeat: submitting a 15-page narrative to a funder whose RFP specifies 5 pages, which signals the applicant cannot follow instructions; writing a sustainability section that says “we will seek additional grants,” which reviewers score as non-responsive; and receiving an award and then managing compliance in a spreadsheet disconnected from the proposal budget, creating a reconciliation gap that produces audit findings at closeout. These 13 questions address each of those failure points.
How long should a grant proposal be?
Follow the funder’s stated page or word limit exactly. If the RFP specifies five pages, submit five pages — not four and not six. A submission that exceeds the stated limit signals the applicant cannot follow instructions, and many funders disqualify over-length submissions before review.
If no length is specified, federal grants typically run 15–25 pages for the narrative section, foundation grants typically run 5–10 pages, and community foundation grants typically run 3–5 pages. Headers, short paragraphs, and numbered lists help reviewers find the criteria they are scoring against. Length is constrained by the RFP; clarity is your variable.
What is the difference between an LOI and a full proposal?
A Letter of Intent (LOI) is a brief document — typically one to three pages — that introduces your organization and proposed project to determine whether the funder wants to invite a full proposal. LOIs are common among private foundations as a screening mechanism. An LOI is not a formal application and carries no compliance obligations.
A full proposal is the complete application package — narrative, budget, budget narrative, attachments, and required certifications. When an LOI receives a “please submit a full proposal” response, that is an invitation, not a commitment. Invitations to submit do not guarantee funding.
Should I contact the program officer before submitting?
Yes, when the funder’s website or RFP indicates program officers are available for pre-submission conversations. Most federal agency program officers and many large foundation program officers welcome brief calls to clarify eligibility, confirm your project fits the program’s priorities, and get informal feedback on your approach.
The call should be brief and specific: what is the program’s current priority focus, does your proposed project fit, are there any technical requirements to know about. Do not call to ask whether you should apply — that signals you have not read the RFP. Funders that prohibit contact with program officers will state it in the RFP; follow that instruction.
What is a logic model and do I need one?
A logic model is a one-page visual diagram that shows the relationship between your inputs (staff, budget, partners), activities, outputs (the things you will produce or deliver), and outcomes (the changes in knowledge, behavior, or conditions that result). Many federal grants and large foundation grants require a logic model as a separate attachment.
Even when not required, building one forces you to test the internal logic of your project: if your inputs produce these activities, will those activities plausibly produce those outputs, and will those outputs plausibly produce those outcomes? Logic models that jump from activities directly to long-term impact without intermediate outcomes are common and reviewers notice them.
How detailed should the budget narrative be?
Every line in the budget should have a corresponding narrative justification that explains what the item is, why it is necessary for the project, and how the cost was calculated. “Personnel: $45,000” is not a budget narrative — it is a line item.
A proper narrative reads: “Project Director (0.5 FTE x $90,000 annual salary = $45,000). The Project Director will oversee daily program implementation, manage community partner relationships, and prepare all required reports.” Reviewers use the budget narrative to verify that costs are reasonable and allocable. A budget without a narrative is a common reason proposals are scored poorly on the budget section.
What financial documents do foundations typically require?
Most private foundations require: the most recent audited financial statements (or reviewed financials if below the audit threshold), the most recent IRS Form 990, a current operating budget, and a project budget. Some also require a list of other funders and pending grant applications.
The 990 is public information and foundations will look it up regardless of whether you submit it — include it proactively. Audited financials older than two years are a red flag. If your audit is in process, note that in the application and provide the draft if available.
What is a good success rate for grant proposals?
The sector-wide average success rate for competitive grant proposals is 20–30%. For organizations with strong funder relationships and track records with specific program officers, success rates of 40–60% are achievable for renewal grants. For unsolicited proposals to funders with no prior relationship, success rates can be 5–10%.
A more useful metric: what is your success rate by funder category (federal, state, foundation, corporate)? Federal grants have lower success rates but larger award sizes; community foundation grants have higher success rates but smaller awards. Track success rates by category to allocate writing time toward the best return on investment.
How do I write about sustainability in a grant proposal?
The sustainability section should answer one specific question: what will continue after this grant ends, and how will it be funded? “We will seek additional grants” is not a sustainability plan — it restates the problem the funder is trying to solve.
A credible sustainability section names the specific funding sources you will pursue (earned revenue, government contracts, a specific individual donor campaign), provides evidence that those sources are viable, and is honest about what will not continue if alternative funding is not secured. Funders know some projects are grant-dependent; they want to see that you have thought clearly about what you are actually promising.
Can I submit the same proposal to multiple funders?
You can, with modifications. A proposal submitted verbatim to multiple funders signals that it was not written for any of them — reviewers notice when mission statements and priority language do not match their program’s stated interests.
The approach that works: write a base narrative covering the core project description and evaluation plan, then customize sections that reference funder priorities, geographic focus, and RFP alignment. The budget must be individualized because award amounts vary. Disclose concurrent submissions when funders ask — most federal applications require disclosure of pending applications.
What should I do if my proposal is rejected?
Request reviewer feedback if the funder provides it — many federal agencies and some large foundations offer written reviewer comments or program officer debriefs. Read the feedback before your next submission to that funder, not as validation of why they were wrong but as data about how your proposal was read.
Common rejection reasons: project does not fit the program’s current priority focus, budget is inconsistent with the narrative, evaluation plan is not credible, or the organization lacks a track record in the proposed area. Rejection from one funder does not mean the project is unfundable — it may mean misaligned priorities. Move the proposal to the next appropriate funder.
How do I write an evaluation plan without a research background?
An evaluation plan needs to answer four questions: what will you measure, how will you measure it, when will you collect data, and who is responsible? You do not need a research background to answer those questions clearly.
Start with your outcomes. For each outcome, identify an indicator, a data source, a collection method, and a timeline. If the grant requires an independent evaluator, name a local university program or evaluation firm in the proposal. Staff-administered pre/post surveys with clear instruments are sufficient for most foundation grants.
What makes a budget raise red flags for reviewers?
Six items that trigger reviewer scrutiny: indirect costs that exceed the funder’s cap without explanation; personnel costs inconsistent with the narrative (the proposal says one program director manages the project; the budget funds three); equipment purchases over $5,000 on grants that do not explicitly allow capital expenditures; no fringe benefit rate applied to personnel; consultant fees above $150/hour without justification; and a budget total inconsistent with the project scope.
How do I connect the proposal to our grant management system after award?
After an award letter arrives, four things should happen before any spending begins: set up a restricted fund code in your accounting system using the grant’s official award number, enter the approved budget into your grant management system line by line, enter every reporting deadline from the award agreement into a compliance calendar, and assign a responsible staff member for each deadline.
The proposal budget is the compliance baseline — every expenditure will be measured against it. If your grant management system and accounting system are separate, the approved budget needs to exist in both with matching line items. Discrepancies between the grant management record and the general ledger are the most common source of reconciliation errors at closeout.
Free resource
Get the Nonprofit Grant Compliance Checklist
A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.
Frequently asked
Frequently Asked Questions
How long should a grant proposal be?
Follow the funder's stated page or word limit exactly. If the RFP specifies five pages, submit five pages — not four and not six. A submission that exceeds the stated limit signals the applicant cannot follow instructions, and many funders disqualify over-length submissions before review. If no length is specified, federal grants typically run 15–25 pages for the narrative section, foundation grants typically run 5–10 pages, and community foundation grants typically run 3–5 pages. Use white space intentionally — dense, unbroken text is harder to score. Headers, short paragraphs, and numbered lists help reviewers find the criteria they are scoring against. Length is constrained by the RFP; clarity is your variable.
What is the difference between an LOI and a full proposal?
A Letter of Intent (LOI) is a brief document — typically one to three pages — that introduces your organization and proposed project to determine whether the funder wants to invite a full proposal. LOIs are common among private foundations as a screening mechanism. They typically cover: who you are, what problem you are addressing, what you propose to do, what outcomes you expect, and a rough budget total. An LOI is not a formal application and carries no compliance obligations. A full proposal is the complete application package — narrative, budget, budget narrative, attachments, and required certifications. When an LOI receives a 'please submit a full proposal' response, that is an invitation, not a commitment. Invitations to submit do not guarantee funding.
Should I contact the program officer before submitting?
Yes, when the funder's website or RFP indicates program officers are available for pre-submission conversations. Most federal agency program officers and many large foundation program officers welcome brief calls or emails before submission to clarify eligibility, confirm your project fits the program's priorities, and get informal feedback on your approach. The call should be brief and specific: what is the program's current priority focus, does your proposed project fit within this year's priorities, and are there any technical requirements you should know about. Do not call to ask whether you should apply — that question signals you have not read the RFP. Funders that explicitly prohibit contact with program officers will state it in the RFP; follow that instruction.
What is a logic model and do I need one?
A logic model is a one-page visual diagram that shows the relationship between your inputs (staff, budget, partners), activities, outputs (the things you will produce or deliver), and outcomes (the changes in knowledge, behavior, or conditions that result). Many federal grants and large foundation grants require a logic model as a separate attachment. Even when not required, building one forces you to test the internal logic of your proposed project: if your inputs produce these activities, will those activities plausibly produce those outputs, and will those outputs plausibly produce those outcomes? Logic models that skip links — jumping from activities directly to long-term impact without intermediate outcomes — are common and reviewers notice them. The logic model also becomes the foundation for your evaluation plan.
How detailed should the budget narrative be?
Every line in the budget should have a corresponding narrative justification that explains what the item is, why it is necessary for the project, and how the cost was calculated. 'Personnel: $45,000' is not a budget narrative — it is a line item. A proper narrative reads: 'Project Director (0.5 FTE x $90,000 annual salary x 12 months = $45,000). The Project Director will oversee daily program implementation, manage community partner relationships, and prepare all required reports.' Reviewers use the budget narrative to verify that costs are reasonable and allocable to the project. A budget without a narrative — or with a narrative that just restates the dollar amounts — is a common reason proposals are marked incomplete or scored poorly on the budget section.
What financial documents do foundations typically require?
Most private foundations require: the most recent audited financial statements (or reviewed financials if the organization is below the audit threshold — typically $1,000,000 in federal expenditures, raised from $750,000 for fiscal years ending September 30, 2025 or later), the most recent IRS Form 990, a current operating budget, and a project budget. Some also require a list of other funders and pending grant applications. The 990 is public information and foundations will look it up regardless of whether you submit it; include it proactively. Audited financials older than two years are a red flag that the organization may not be current on its filings. If your audit is in process, note that in the application and provide the draft if available. Never submit unaudited management financials as a substitute for audited statements without noting the difference.
What is a good success rate for grant proposals?
The sector-wide average success rate for competitive grant proposals is 20–30%, meaning roughly one in four to five proposals receives funding. For organizations with strong funder relationships and track records with specific program officers, success rates of 40–60% are achievable for renewal grants. For unsolicited proposals to funders with no prior relationship, success rates can be 5–10%. A more useful metric than overall success rate: what is your success rate by funder category (federal, state, foundation, corporate)? Federal grants have lower success rates but larger award sizes; community foundation grants have higher success rates but smaller awards. Track success rates by category so you can allocate grant writing time toward the funders with the best return on investment.
How do I write about sustainability in a grant proposal?
The sustainability section should answer one specific question: what will continue after this grant ends, and how will it be funded? 'We will seek additional grants' is not a sustainability plan — it restates the problem the funder is trying to solve. A credible sustainability section names the specific funding sources you will pursue (earned revenue, government contracts, a specific individual donor campaign, an endowment draw), provides evidence that those sources are viable (a current contract you are expanding, a donor who has indicated interest, a fee structure that covers program costs), and is honest about what will not continue if alternative funding is not secured. Funders know that some projects are grant-dependent; they want to see that you have thought clearly about what you are actually promising will continue.
Can I submit the same proposal to multiple funders?
You can, with modifications. A proposal submitted verbatim to multiple funders signals that it was not written for any of them specifically — reviewers notice when mission statements, priority language, and geographic focus do not match their program's stated interests. The approach that works: write a base narrative that covers your core project description and evaluation plan, then customize the sections that reference funder priorities, geographic focus, and alignment with the RFP. The budget must be individualized for each submission because award amounts vary. Disclose concurrent submissions when funders ask (most federal applications require disclosure of pending applications), and update all active applications immediately if an award is made that would change the project scope.
What should I do if my proposal is rejected?
Request reviewer feedback if the funder provides it — many federal agencies and some large foundations offer written reviewer comments or debriefs with program officers. Read the feedback before your next submission to that funder, not as validation of why they were wrong but as data about how your proposal was read. Common rejection reasons: project does not fit the program's current priority focus (a strategy problem, not a writing problem), budget is inconsistent with the narrative, evaluation plan is not credible, or the organization lacks a track record in the proposed area. Rejection from one funder does not mean the project is unfundable — it may mean the funder's priorities, award sizes, or geographic focus do not align with your project. Move the proposal to the next appropriate funder.
How do I write an evaluation plan without a research background?
An evaluation plan needs to answer four questions: what will you measure, how will you measure it, when will you collect data, and who is responsible? You do not need a research background to answer those questions clearly. Start with your outcomes — the changes in knowledge, behavior, or conditions you expect the project to produce. For each outcome, identify an indicator (the observable sign that the outcome occurred), a data source (surveys, attendance records, test scores, client case notes), a collection method (pre/post survey, observation, administrative data pull), and a timeline. If the grant requires an independent evaluator, name a local university program or evaluation firm in the proposal. If it does not require independence, staff-administered pre/post surveys with clear instruments are sufficient for most foundation grants.
What makes a budget raise red flags for reviewers?
Six budget items that trigger reviewer scrutiny: indirect costs that exceed the funder's cap without explanation (federal programs often cap indirect at 26% modified total direct costs; foundation grants may cap at 10–15%); personnel costs that are inconsistent with the narrative (the proposal says one program director will manage the project; the budget funds three); equipment purchases over $5,000 on grants that do not explicitly allow capital expenditures; no fringe benefit rate applied to personnel (signals the applicant did not account for actual employment costs); consultant fees above $150/hour without justification; and a budget total that is inconsistent with the project scope (a $30,000 budget to 'transform citywide mental health outcomes' signals unrealistic expectations or scope creep in the narrative).
How do I connect the proposal to our grant management system after award?
After an award letter arrives, four things should happen before any spending begins: set up a restricted fund code in your accounting system using the grant's official award number, enter the approved budget into your grant management system line by line (not as a total), enter every reporting deadline and compliance milestone from the award agreement into a compliance calendar, and assign a responsible staff member for each deadline. The proposal budget is the compliance baseline — every subsequent expenditure will be measured against it. If your grant management system and accounting system are separate, the approved budget needs to exist in both places with matching line items. Discrepancies between the grant management record and the general ledger are the most common source of reconciliation errors at closeout.
