Appendix D: FAQ and Troubleshooting

The questions grant writers actually ask — and the things that go wrong — with short answers and a pointer to the chapter that treats each fully. Use this as a quick-diagnosis reference: find your situation, get oriented, then go to the chapter for the real guidance.

How to use this appendix. The FAQ (D.1) answers common questions; the troubleshooting guide (D.2) maps symptoms to likely causes and fixes. Both are starting points — the depth is in the chapters they cite.

D.1 Frequently Asked Questions

Getting started

I've never written a grant. Where do I start? Start by understanding what a grant is — a mission transaction, an exchange in which a funder advances its goals through your work (Chapter 1) — and what funders want (Chapter 2). Then find a funder that fits your work (Chapter 3) before you write a word. Fit first; writing second.

How do I find funders for my project? Use the finding tools in Appendix B: Grants.gov for federal, Candid/990-PF for foundations, agency sites for specifics. Then run each candidate through the fit check (Chapter 3, Appendix C Card 2). Don't apply widely and hope — apply where you genuinely fit.

How long does it take to write a proposal? Longer than you think — weeks to months for a substantial one. The most preventable failure is starting too late. Plan backward from the deadline (Chapter 4, Appendix A.8), and register early (SAM.gov can take weeks, Chapter 15).

Do I need to be a nonprofit / have a PhD / have grant experience? It depends entirely on the funder and program — eligibility is the first thing to verify (Chapter 3). Some funding requires nonprofit status, academic appointment, or small-business status; some doesn't. Check the announcement's eligibility section first.

Writing

What's the single most important part of a proposal? The part the funder reads first and weights most — usually the specific aims page or executive summary (Chapters 6–7). If that doesn't land, the rest may not be read closely. But a proposal is only as strong as its coherence — every part must point the same way (Chapter 5).

My proposal feels generic. How do I make it specific? Specificity comes from real numbers, named methods, concrete activities, and evidence — not adjectives. Replace every vague claim with a concrete one (Chapters 8–9). "We will significantly improve outcomes" is weak; "We will increase the screening rate from 40% to 65% over 18 months, measured by [method]" is strong.

How honest should I be about risks and weaknesses? Honest. Disclosed weakness beats discovered weakness. Name your real risks and your contingencies (Chapter 9) — it builds credibility, and reviewers will find the risks anyway. The same applies to the budget and capacity: don't hide gaps; address them.

How do I write about a community without sounding deficit-focused? Use asset-based framing: name the community's strengths alongside the real, often externally-imposed barriers (Chapters 25, 31). Never reduce people to their problems. Authentic, respectful framing is both more ethical and more persuasive.

Budget and compliance

How do I set the budget number? Build it from real costs, bottom-up — don't pick a number and reverse-engineer it. Every line must be necessary, reasonable, and allocable (Chapters 11–12). Then check it matches the funder's typical grant size (Chapter 3) and format (Appendix A.6).

What are indirect costs / F&A, and can I include them? Indirect (facilities & administrative) costs are real costs of doing the work that aren't tied to one project — administration, facilities, utilities. Most funders allow them at a negotiated or specified rate; some foundations cap or disallow them. Check the funder's policy and your organization's rate (Chapters 11–12, 26).

What's a UEI / SAM.gov / eRA Commons, and do I need it? For federal funding, your organization registers in SAM.gov and receives a UEI (Unique Entity Identifier); NIH uses eRA Commons, NSF uses Research.gov (Chapters 15, 19, Appendix B). These take time — register weeks ahead. Missing registration is a preventable disqualifier.

After submission

How long until I hear back, and what are my odds? It varies widely — months for many federal programs. Success rates vary by funder and program (for example, NIH R01 success rates have often been roughly one in five; verify current figures). Hold realistic expectations (Chapter 35) and keep a pipeline so one decision doesn't make or break you (Chapter 33).

I got rejected. Now what? Rejection is information, not a verdict — most funded grants were rejected at least once. Read the critique after the sting fades, find the real concerns, and resubmit substantially strengthened (Chapter 22). Resubmission wins most grants that get funded.

I got funded! Now what? Celebrate — then steward it. You now have obligations: reporting, compliance, financial management, and the relationship (Chapter 26). Doing this well funds your next grant (Chapters 33, 35). A grant is the start of a relationship, not the end of a transaction.

Tools and career

Can I use AI to write my proposal? As an assistant, yes; as the author, no. You remain accountable for every word, must verify everything (AI fabricates citations and facts), must protect confidential data, and must follow the funder's disclosure rules (Chapter 24). AI speeds parts of the work; it can't supply the judgment, relationships, truth, or strategy.

Can I get paid a percentage of grants I win? No — contingency pay (a percentage of grants won) is considered unethical by the profession (Chapter 35). Grant writers are paid for their work — salary, hourly, or project fee — not for outcomes they can't control.

Is grant writing a real career? Yes — a durable, transferable one, in lasting demand across every sector that runs on grants (Chapter 35). It can be a whole career (in-house, research administration, freelance, the funder's side) or the sustaining skill of another one.

D.2 Troubleshooting Guide (symptom → likely cause → fix)

"My proposals keep getting rejected and I don't know why." - Likely cause: poor funder fit, or not writing to the criteria. Fix: verify fit before writing (Chapter 3, Card 2); request and read the reviewer feedback (Chapter 22); write explicitly to each scored criterion (Chapter 19).

"Reviewers say my proposal is 'not significant' / 'incremental.'" - Likely cause: the so-what chain is weak or unevidenced. Fix: rebuild significance — magnitude, consequence, who's affected, why now — every link evidenced (Chapter 8, Card 5).

"Reviewers say the approach is 'vague' or they 'can't tell what you'll do.'" - Likely cause: not enough strategic detail where it matters. Fix: go deep on the critical/risky methods; show who does what, how, when; add a timeline and contingencies (Chapter 9).

"My budget got questioned / cut / flagged." - Likely cause: budget doesn't match the narrative, or lines lack justification. Fix: reconcile budget = justification = narrative; give every line a basis of estimate (Chapter 12, Card 7).

"My proposal was rejected without review / returned." - Likely cause: a compliance failure — eligibility, format, missing component, late, or registration lapsed. Fix: run the full compliance checklist before submitting; register weeks ahead; submit early (Chapter 15, Card 8).

"My proposal reads like it was written by five different people." - Likely cause: a multi-author proposal not integrated. Fix: one person owns voice and coherence; revise the whole for one argument in one voice (Chapters 5, 23, Card 6).

"I'm always scrambling at the deadline." - Likely cause: starting too late; no backward timeline. Fix: plan backward from the deadline with internal milestones; start the registration and the aims page early (Chapter 4, Appendix A.8).

"I keep applying but rarely win, and I'm burning out." - Likely cause: applying without fit, no pipeline, no sustainable practice. Fix: apply only where you fit; build a diversified pipeline so wins come over time; build a reusable toolkit; protect your resilience (Chapters 32, 33, 35).

"The funder's announcement contradicts itself / I'm not sure what they want." - Likely cause: dense or ambiguous guidelines. Fix: read it twice (compliance, then subtext); when still unclear, ask the program officer — that's what they're for (Chapters 2, 3, 19).

"I cited a statistic / source the AI gave me and it turned out to be wrong." - Likely cause: trusting AI output without verification. Fix: verify every fact, citation, and statistic against the primary source — always; AI fabricates plausibly (Chapter 24, Card 11).

When the guide doesn't cover it. Two reliable moves solve most problems not listed here: return to the chapter that treats your component or funder (the table of contents and the cross-references throughout will point you), and ask a human — the program officer (about the funder), your sponsored-programs/grants office (about compliance and process), or a peer/mentor/mock panel (about the proposal itself). Grant writing rewards the writer who asks the right question of the right person at the right time.