Grant Budget Narrative Examples: Personnel, Fringe, Travel & More

If you're building a federal grant budget and staring at the SF-424A wondering what a reviewer actually wants to read in the justification boxes, here's the short answer: every line item needs a narrative that ties a dollar amount to a specific, reasonable, allowable activity — not just a number pulled from a spreadsheet. Below are sample narratives for each standard budget category (personnel, fringe, travel, equipment, supplies, contractual, other, and indirect), plus what program officers and grants management specialists are actually scanning for when they review your budget.

This post covers the grant-side budget narrative (SF-424A and the categories federal agencies use for grants and cooperative agreements). It does not cover DCAA-compliant cost proposals for federal contracts — that's a different animal with different rules, and plenty of existing guidance already covers it.

Why the Narrative Matters More Than the Numbers

The SF-424A spreadsheet tells a reviewer what you're spending. The budget narrative tells them why — and it's the single most common place proposals lose points. Grants.gov and most federal agencies require a narrative justification for every line, and reviewers are trained to flag anything that looks unsupported, rounded suspiciously (every number ending in "000"), or inconsistent with the scope of work. A mismatch between your narrative and your project description is one of the fastest ways to get dinged on "budget reasonableness," which shows up on nearly every federal and foundation scoring rubric.

A good rule of thumb: if someone with no context on your organization read only the narrative, they should understand exactly what you're buying, how much of it, and how you arrived at the cost.

Personnel

Reviewers expect to see each role, the percentage of effort (FTE), and the basis for the salary figure.

Sample: "Project Director (0.25 FTE, $95,000 base annual salary): will oversee all project activities, manage subrecipient compliance, and serve as the primary liaison to the program officer. Salary is based on the organization's FY2026 approved salary schedule. Total requested: $23,750."

Avoid listing "TBD" for key personnel — reviewers read that as a sign the project isn't fully planned.

Fringe Benefits

Fringe is almost always expressed as a rate applied to salary, not a flat number.

Sample: "Fringe benefits are calculated at the organization's federally negotiated rate of 28% of salary, covering FICA, health insurance, retirement match, and unemployment insurance, consistent with the rate applied to all staff. Total requested: $6,650."

If you don't have a negotiated indirect/fringe rate agreement (a NICRA), say so and show your de minimis or calculated rate instead — reviewers will look for that disclosure.

Travel

This is where applicants lose the most credibility through vagueness. Break travel into trips, not totals — origin/destination, number of travelers, purpose, and cost basis (GSA per diem and mileage rates).

Sample: "Two staff will travel from Denver, CO to the annual grantee meeting in Washington, DC (1 trip, 3 days). Airfare estimated at $450/person based on recent fares; lodging at the GSA per diem rate for DC ($258/night); meals at the GSA M&IE rate ($79/day). Total requested: $3,166."

Using GSA rates (updated annually at gsa.gov/travel) instead of made-up figures is one of the easiest credibility wins in the whole budget.

Equipment

Federal definitions matter here: under 2 CFR 200.1, equipment is tangible property with a useful life over one year and a per-unit cost of $5,000 or more (many applicants still cite the older $10,000 figure — check your specific NOFO, since agencies can set a higher threshold but not lower). Anything under that line goes in supplies instead.

Sample: "One mobile dental x-ray unit ($18,500): required to provide on-site screenings at rural school sites identified in the needs assessment (Section B). Quote attached from vendor [X]; cost reflects the lowest of three competitive quotes obtained per organizational procurement policy."

Always show you shopped around — a single quote with no comparison invites a reviewer question.

Supplies

Supplies are consumable, under the equipment threshold, and should be grouped logically, not itemized down to staplers.

Sample: "Program supplies ($4,200): includes curriculum materials, printing, and participant workbooks for 150 enrollees at an estimated $28/participant, based on costs from the prior program year."

If this is a renewal or continuation, anchoring the estimate to prior actual costs is one of the strongest justifications you can give.

Contractual

This category gets the most scrutiny because it often represents subawards or consultants, and reviewers want to know how you selected the vendor — not just what they'll do.

Sample: "An external evaluator will be competitively selected through a request for proposals to conduct the required process and outcome evaluation, consistent with 2 CFR 200.318 procurement standards. Estimated cost of $35,000 is based on comparable evaluation contracts of similar scope and duration within the sector."

If you already have a specific subrecipient in mind (common with collaborative or consortium grants), name them and explain the sole-source justification — silence here reads as noncompliance.

This is also the category where small businesses applying as grantees most often stumble, because managing a compliant selection process on top of everything else is a part-time job in itself. It's the kind of thing we built InstaGovOps to help with — the platform flags missing procurement justifications and generates draft narrative language before you submit, which is worth a look if you're assembling more than one or two of these budgets a year (book a 15-minute walkthrough).

Other and Indirect Costs

"Other" is the catch-all — software licenses, communications, participant incentives — and should still be itemized, not lumped.

Sample: "Participant incentive gift cards ($2,500): $25/card for 100 survey respondents, used to improve response rates for the required outcome evaluation, consistent with IRB-approved protocol."

Indirect costs are either your federally negotiated indirect cost rate (NICRA) or, if you've never had one, the 10% de minimis rate every nonfederal entity is entitled to under 2 CFR 200.414 — note that in your narrative explicitly.

Sample: "Indirect costs are calculated at the organization's de minimis rate of 10% of modified total direct costs (MTDC), as the organization has not previously negotiated a rate with a federal agency. Total requested: $8,340."

Getting the Narrative Right the First Time

Every category above gets flagged for the same three reasons: numbers that don't match the scope of work, missing methodology (how did you calculate this?), and language that sounds copy-pasted from a template. Reviewers read hundreds of these; the ones that get funded sound specific, grounded, and internally consistent line by line.

Writing a tight, defensible budget narrative for every category — especially if you're applying to multiple NOFOs a year across different agencies with different formats — is genuinely time-consuming, and it's a big part of why organizations end up hiring a grant writer, in the $70k-$110k salary range according to Glassdoor, or a consultant charging by the proposal. If you'd rather not carry that overhead, it's worth comparing the cost of doing it yourself against a platform built to generate compliant, agency-specific budget narratives automatically (see what InstaGovOps costs vs hiring this in-house).

Either way, treat the narrative as the part of the application doing the real persuading. The spreadsheet just does the math.