How to Read a NOFO: A Practical Guide

1. Why the NOFO Is the Only Document That Matters

Federal grant applicants spend enormous effort on proposal writing, budget development, and organizational documentation — but the highest-leverage activity in the entire process is often the least practiced: reading the funding announcement carefully.

The Notice of Funding Opportunity is the source of truth for every federal grant. Everything a reviewer will look for, every requirement, every scoring criterion, every submission rule — it's all in the NOFO. Applicants who read the document explicitly, extract what matters, and align their applications to what's actually asked consistently outperform applicants who skim, assume, or write from prior proposals.

This guide walks through how to read a NOFO strategically. For broader federal application context, see how to apply for federal grants. For the lifecycle frame in which the NOFO sits, see the federal grant lifecycle.

2. The Standard NOFO Structure

Federal NOFOs follow a standardized structure defined by federal grant policy. Understanding the structure means knowing where to find what you need without hunting through the entire document.

3. Section I: Funding Opportunity Description

Section I describes what the program is, why it exists, and what work it funds. This is the section most applicants read first — and it's usually the wrong place to start.

What Section I contains

• Program purpose — the underlying goal the funder is trying to accomplish
• Statutory authority — the law or executive action that created the program
• Background — context on why the program exists and what problem it addresses
• Priorities — specific areas of emphasis for the current funding cycle
• Definitions — terms used with specific meaning throughout the NOFO

How to read Section I strategically

The strategic value of Section I is understanding what the funder wants to accomplish, not confirming that your work fits generally. Read for:

Explicit priorities. Federal programs often specify priorities that receive special consideration. Applications aligned with stated priorities typically score higher; applications ignoring the priorities are functionally competing at a disadvantage.

Operative definitions. Terms like "rural," "underserved," "low-income," "minority-serving," and "evidence-based" often carry specific regulatory definitions in Section I that differ from plain-English usage. An organization proposing to serve "rural communities" that don't meet the NOFO's rural definition faces automatic problems.

Statutory constraints. The underlying statute shapes what the program can and cannot fund. Section I typically references statutory language that constrains later decisions.

4. Section II: Federal Award Information

Section II tells you the money. Total available funding, expected number of awards, size ranges, and period of performance. It also often reveals strategic information about the funder's approach.

What Section II contains

• Total available funding for the current cycle
• Estimated number of awards the funder anticipates making
• Range of award amounts — minimum, maximum, and typical
• Period of performance — how long grants run
• Type of funding instrument — grant, cooperative agreement, or contract

What Section II reveals strategically

The math in Section II tells you the applicant profile the funder is targeting. If total funding is $10 million and the funder expects 4 awards, they're targeting large-scale applicants with substantial capacity. If they expect 40 awards, they're targeting smaller organizations pursuing focused projects. Applications significantly outside the expected range face uphill scoring.

Award size ranges also signal proposal scope. A program with awards from $50,000 to $500,000 will receive proposals across that range, and reviewers calibrate expectations to award size. A proposal requesting $450,000 needs to demonstrate work that justifies large investment; a proposal requesting $75,000 doesn't need the same complexity.

Cooperative agreements versus grants matter significantly. Cooperative agreements involve substantial federal involvement during execution — the federal agency will be a working partner, not just a funder. Some organizations welcome that partnership; others find it constraining.

5. Section III: Eligibility Information

Section III is where most applications are lost before they're written. Read this section first, ruthlessly, before investing any drafting time.

What Section III contains

• Eligible applicants — organizational types that may apply
• Cost sharing or matching requirements — required applicant contributions
• Other eligibility requirements — certifications, registrations, specific characteristics

How to read Section III

Treat every eligibility statement as binary. Either your organization meets the condition or it doesn't. Don't rationalize partial fits — federal reviewers apply eligibility tests strictly during compliance screening, and partial eligibility is treated as ineligibility.

Build an explicit checklist from Section III:

• List every eligibility statement
• Note the exact requirement for each
• Identify what evidence you'll need to demonstrate compliance
• Verify each condition against your organization's documented status

For systematic eligibility verification, see how grant eligibility works.

Where Section III gets misread

Ambiguous terms interpreted favorably. Applicants routinely read ambiguous eligibility language in ways that favor their organization. If Section III says "small businesses may apply" without defining small, verify the operative definition — often referenced in Section I or in cited federal regulations — before assuming you qualify.

Missed operational requirements. Eligibility often extends beyond entity type to include registrations (SAM.gov active, UEI current), plans (Comprehensive Plan for HUD funds, Hazard Mitigation Plan for FEMA funds), and certifications. These operational requirements catch applicants who focus only on organizational category.

Cost sharing dismissed as flexible. When Section III specifies a cost share, it's not a suggestion. Applicants who submit without the required match are usually eliminated at compliance screening.

6. Section IV: Application and Submission Information

Section IV is the operational instruction manual. Everything about what you submit, how you submit it, and when you submit it lives here.

What Section IV contains

• Address to request application package — where to find forms
• Content and form of application submission — required narrative components with page limits and formatting rules
• Dun and Bradstreet universal identifier / UEI requirement
• Submission dates and times — the firm deadline
• Intergovernmental review — Executive Order 12372 requirements for some programs
• Funding restrictions — what specifically cannot be funded
• Other submission requirements — attachments, letters, certifications

How to read Section IV

Build the application checklist directly from Section IV. Every requirement gets a checklist item, and you verify each item is satisfied before submitting.

Specific patterns to watch for:

Page limits. Federal NOFOs specify page limits for narrative sections. A 25-page narrative submitted at 26 pages may have excess pages stripped before review or the application rejected outright. Page limits are firm.

Format requirements. Font size, line spacing, and margins are typically specified explicitly. Submissions violating format requirements can be rejected at compliance screening. Following the format requirements literally, even when they seem arbitrary, is essential.

Attachment requirements. Section IV lists every attachment the application must include. Build a document by document checklist. Common attachments: organizational chart, letters of support with specific content, resumes of key personnel, financial statements, indirect cost rate agreement, evaluation plan.

Submission mechanism. Federal grants are typically submitted through Grants.gov, but specific programs may use other systems (research.gov for NSF, agency-specific portals). Verify the correct submission mechanism and test access before deadline day.

Deadline specifics. Submission deadlines specify both date and time, and time zone. A deadline of 5:00 PM Eastern is not 5:00 PM Pacific. Late submissions are rejected without exception.

Funding restrictions

Section IV typically includes an explicit list of what cannot be funded. Common restrictions:

• Alcohol
• Entertainment
• Fundraising
• Lobbying
• Political activity
• Construction (in programs not intended for capital)
• Pre-award costs
• Contingency reserves
• Foreign travel (unless justified)

Building a budget that includes restricted costs creates immediate compliance problems even if the application is otherwise strong.

7. Section V: Application Review Information

Section V tells you exactly how you'll be scored. Applications that score well align with Section V explicitly; applications that ignore Section V often produce strong work that doesn't earn points.

What Section V contains

• Evaluation criteria with specific factors and weights
• Review and selection process description
• Anticipated announcement and award dates
• Any additional information on review

How to read Section V

Section V should shape the narrative structure in Section IV. If Section V lists five evaluation criteria with weights, the narrative should address all five with proportional depth. If Section V weights "organizational capacity" at 25%, the capacity discussion should occupy roughly 25% of the narrative — not two sentences at the end.

Common evaluation criteria across federal programs:

Some programs weight criteria unusually — a research program might weight methodology at 50% and organizational capacity at 5%. A demonstration program might weight innovation at 30% and evaluation plan at 20%. Reading Section V explicitly reveals what the specific program actually values.

8. Section VI: Federal Award Administration

Section VI describes what happens if you win. Most applicants skip this section during application development, but reading it early informs several strategic decisions.

What Section VI contains

• Federal award notices — how you'll be notified
• Administrative and national policy requirements — applicable federal regulations
• Reporting requirements — what you'll report and how often
• Terms and conditions — general grant obligations

Why to read Section VI early

Section VI reveals the post-award workload. A program requiring monthly financial reports, quarterly programmatic reports, and annual site visits carries substantial post-award burden. A program with annual reporting carries less. Understanding the burden before applying helps evaluate whether the funding-to-effort ratio actually makes sense for your organization.

Section VI also reveals compliance frameworks. Federal programs are typically governed by Uniform Guidance (2 CFR Part 200), but specific programs add program-specific requirements. Reading these before application prevents surprises after award.

For deeper coverage of post-award reporting, see federal grant reporting requirements. For compliance patterns, see common grant compliance mistakes.

9. Section VII: Federal Awarding Agency Contacts

Section VII is short but often underused. It contains contact information for the program officer and grants management specialist administering the opportunity.

Why to contact program officers

Program officers can answer specific questions that would take hours to research otherwise:

• Whether your organization type qualifies for edge cases
• What "responsive to priorities" means in practice for this cycle
• How reviewers typically interpret ambiguous criteria
• Whether specific costs would be allowable
• What kinds of proposals have historically succeeded

Most program officers welcome pre-application questions. They would rather clarify ambiguity before you invest 100 hours than have to reject an otherwise-strong application later. Cold-calling a program officer with a well-formed specific question is often the highest-leverage 15 minutes you'll spend on the application.

What not to do

Program officers can't:

• Preview your application or provide detailed pre-application feedback
• Advocate for your specific application during review
• Provide inside information that other applicants don't have
• Confirm that you'll win

Respect the boundary. Program officers who feel gamed will remember at reporting time.

10. A Practical Reading Strategy

The temptation with any NOFO is to start at page 1 and read through. That approach wastes time. A more efficient practice:

First pass: Eligibility triage (15 minutes)

Read Section III explicitly. Verify your organization meets every stated requirement. If any requirement is unmet, stop reading and either fix the issue or move to a different opportunity.

Second pass: Fit assessment (30 minutes)

Read Section I (program purpose), Section II (award scale), and Section V (evaluation criteria). Decide whether this program actually fits your organization's work at the scale the funder is expecting.

Third pass: Application planning (60 minutes)

Read Section IV thoroughly. Build the application checklist. Identify what you already have, what you need to create, and what will require external input (letters of support, partner agreements, etc.).

Fourth pass: Post-award consideration (15 minutes)

Read Section VI. Confirm you can operate under the specified reporting and compliance requirements.

Fifth pass: Full read (2 hours)

Now read the entire NOFO carefully, top to bottom. By this point you know what to look for, and specific language will register that would have washed over you on a cold read.

Total: roughly 4 hours to a NOFO analysis that positions the rest of the application work strategically. Applicants who skip these passes and start drafting from a superficial read often lose the first 40 hours of application work to fundamental misreadings.

11. Common NOFO Misreadings

Certain misreading patterns recur across grant programs and applicant types.

12. Building NOFO Fluency

Reading NOFOs efficiently is a skill that develops with practice. The first NOFO in an unfamiliar program area is difficult; the tenth NOFO in the same program area is much faster.

Practices that build fluency

Read many NOFOs, not few. Even NOFOs you won't pursue teach the vocabulary and structure of federal grantmaking. Reading a NOFO per week builds fluency faster than intensive study of one.

Compare NOFOs across cycles. Reading last year's NOFO alongside this year's reveals what changed. Federal programs adjust priorities, weights, and requirements between cycles — noticing what changed is often high-value.

Reference successful applications. Some federal programs publish redacted successful applications. When available, reading successful applications alongside the NOFO shows how winners aligned to the rubric.

Track your own analysis. Building your own NOFO analysis template — with fields for each strategic question — accelerates future analyses and produces a knowledge base over time.

13. Frequently Asked Questions

14. Conclusion

Reading a NOFO well is the highest-leverage skill in federal grant work. The document contains every answer to every question about the opportunity — but only for applicants who read strategically, extract what matters, and build applications aligned to what the funder actually asked for.

The organizations that win federal grants consistently don't necessarily write better proposals than the organizations that lose. They read the NOFO better, build applications that align to the rubric explicitly, and avoid the misreadings that eliminate strong applications before review even starts.

For the broader federal application context, see how to apply for federal grants. For the lifecycle in which the NOFO sits, see the federal grant lifecycle. For eligibility verification specifically, see how grant eligibility works.