Chapter 19: Government Grants — Scoring to the Rubric Under Public Rules

The NIH and the NSF (Chapters 16–17) are government funders, but they are a special, science-focused corner of a vast landscape. Beyond them lies the much broader world of government grants — the program and project funding distributed by federal departments (Education; Health and Human Services and its agencies; Labor; Justice; Agriculture; Housing and Urban Development; and many more), by the fifty state governments and their agencies, and by counties and cities. This is the funding that builds workforce programs, after-school initiatives, health clinics, reentry services, housing projects, and the thousands of other public-purpose efforts that governments fund but do not run themselves. For nonprofits, public agencies, schools, and local governments, these grants are often the largest single source of program money — and they come with the most rules.

Government grants sit at the opposite end of a spectrum from the foundation world of Chapter 18. Where a foundation grant is an instrument of a relationship, a government grant is closer to a contract: you are competing to deliver specified public priorities, under specified public rules, for specified public money, and you will be scored against a published rubric and held to a detailed compliance regime. The relationship skills of Chapter 18 don't vanish — knowing the program and its people still helps — but they are no longer the system. The system is the announcement, the rubric, the eligibility gate, and the compliance regime, and mastering government grants means mastering those.

That gives us the threshold concept of this chapter: government competitive grants are won by scoring to the published rubric and cleared by binary gates. You write to the points the funder actually assigned — not to what you personally think matters — and you clear every eligibility and compliance requirement perfectly, because an ineligible or noncompliant application is never scored at all. In this chapter we map the government-grant landscape (federal, state, and pass-through), distinguish the major grant types, learn to read a Notice of Funding Opportunity and write to its rubric, clear the eligibility and compliance gates, assemble the federal forms, and prepare for the heavy reporting that follows a public award. Our anchors are Lighthouse Community Services (whose reentry workforce program is a natural fit for federal justice and labor grants) and RYCC (whose after-school program fits federal education funding that flows through the states). As always: government programs, forms, and rules change with statute and administration, so verify current specifics at the source — Grants.gov and the specific agency.

19.1 The Government-Grant Landscape

Government grants come from many levels and flow through several channels, and knowing the channel tells you where to look and whom you're dealing with.

Federal department and agency grants. Beyond the science agencies, most federal departments run grant programs tied to their missions: the Department of Education funds educational programs; Health and Human Services agencies fund health and human-services programs; the Department of Labor funds workforce development; the Department of Justice funds public-safety and reentry programs; and so on. These are announced as competitive funding opportunities and are searchable in one central place — Grants.gov — which lists federal grant opportunities across agencies (Chapter 15).

🎓 Going Deeper — knowing the departments and finding the state agencies: Effective government-grant seekers learn the map of who funds their kind of work, because opportunities recur from the same agencies year after year. On the federal side, it pays to know which department and sub-agency funds your field: education programs from the Department of Education; health and human-services work from HHS agencies (for example, the Administration for Children and Families, the Health Resources and Services Administration, or the Substance Abuse and Mental Health Services Administration); workforce programs from the Department of Labor's Employment and Training Administration; public-safety and reentry programs from the Department of Justice's Office of Justice Programs; rural and nutrition programs from the Department of Agriculture; housing and community development from HUD. Each posts recurring competitions, often on a predictable annual cycle you can anticipate and prepare for. On the state side — where so much pass-through money lives — the equivalent agencies (your state's education department, health department, workforce board, criminal-justice or corrections agency, housing finance agency) post their own competitions, frequently on their own websites and procurement portals rather than on Grants.gov. Building a simple map of "which agencies, federal and state, fund work like mine, and when do they post" turns government-grant seeking from reactive scrambling into a planned, anticipatory pipeline (Chapter 3) — and it's the single highest-leverage research investment a government-focused organization can make.

State and local government grants. States run their own grant programs funded by state dollars, and counties and cities fund local priorities. State agencies often mirror the federal structure (a state education department, a state health department, a state workforce board) and announce their own competitive opportunities through state systems.

Pass-through funding (the crucial channel). A great deal of "federal" money is never granted directly to local organizations. Instead, the federal government grants it to states (or other intermediaries), which then subgrant it to local organizations. This is pass-through funding, and the local organization is a subrecipient. RYCC's most realistic federal opportunity, for example, is a program where federal education dollars for after-school programming flow to the state education agency, which competitively subgrants them to local providers. The practical lesson: much federal money reaches you through your state, so you must watch state agencies, not only Grants.gov, and you must understand that as a subrecipient you inherit federal rules administered through state processes.

🧩 Productive Struggle: Before reading on, consider: Lighthouse wants federal money for its reentry program. Should it watch Grants.gov for a direct federal grant, watch its state agencies for pass-through subgrants, or both — and why might the same federal dollars be available through more than one channel with very different competition and rules? Jot your thinking. The answer, developed below, is both: some federal reentry money is granted directly by a federal agency (national competition, federal rules, larger awards), while other federal money passes through the state (state competition, state-administered, often more accessible to local organizations). Knowing which channel a given pot of money flows through tells you where to apply, whom you're competing against, and whose rules govern.

📜 How We Got Here: The pass-through structure exists because of how American federalism distributes power and administration. The federal government raises money and sets priorities, but much program delivery happens at the state and local level, so federal grant dollars are frequently routed through states that adapt and administer them within federal parameters. This is why a single federal program can look different in each state, why "the rules" for a pass-through grant are a layered mix of federal law (e.g., 2 CFR 200) and state administration, and why building a relationship with your state agency matters even for "federal" money. Understanding the structure prevents a common rookie error — looking only at Grants.gov and missing the larger, more accessible pool of federal money flowing through your own state government.

19.2 Types of Government Grants

A few distinctions determine whether and how you can compete.

Discretionary (competitive) grants are awarded competitively, at the agency's discretion, to applicants who apply and are scored against published criteria. These are the grants this chapter is mostly about — you write a proposal, it's scored, and the highest-scoring eligible applications are funded. This is where proposal craft matters.

Formula grants are distributed by a formula (often to states or other governmental units) based on factors like population or need, not through a competitive proposal. You generally don't "win" a formula grant by writing a great proposal; the money is allocated by law. But formula money often becomes the source of pass-through subgrants you can compete for at the state level.

Block grants are broad federal grants to states for general purpose areas (such as community development or social services), giving states flexibility in how they use the funds — again, often becoming the source of state-administered subgrants.

The strategic upshot: as a local organization, you mostly compete for discretionary grants (federal or state) and for the subgrants that flow from formula and block grants through your state. Knowing which kind a given opportunity is tells you whether there's a proposal to write and where the competition happens.

📊 From the Field: Trace Lighthouse's reentry money to see why the channel matters so much. Federal support for reentry exists in more than one form. Some is direct discretionary money — a federal justice agency runs a national competition for reentry programs, and Lighthouse could apply directly (against national competition, under full federal rules, for a potentially larger award). Some federal money instead passes through the state — federal workforce or justice dollars granted to a state agency, which subgrants them to local reentry providers (against state-level competition, administered by people in Lighthouse's own state, often more accessible to a mid-sized local nonprofit). And the state may run programs with its own dollars too. The same broad purpose — funding reentry — is thus reachable through several channels with very different competition, award sizes, rules, and odds. The veteran move is to map all of them, then choose where Lighthouse actually competes best: perhaps the state pass-through first (winnable, capacity-building, a track record to build on), then the national direct competition once Lighthouse has the scale and administrative history to be competitive and to manage a larger award. "Is there federal money for reentry?" is the wrong question. "Through which channels, and where do I compete best right now?" is the right one.

💡 Key Insight: "There's federal money for that" is not the same as "I can apply for federal money for that." Much federal funding is formula or block money that you cannot apply for directly — but that reaches you as competitive subgrants through your state. So when you hear that the federal government funds your kind of work, the right next questions are: Is there a direct discretionary competition (on Grants.gov), a state-administered subgrant competition (through a state agency), or both? Which am I eligible for? And where is the actual proposal I can write? Tracing the money from its federal source through any pass-through to the competition you can actually enter is a core government-grants skill — and it's why Chapter 3's prospecting work, applied to government, often means studying your state agencies as much as federal sites — and asking, every time, not merely "who funds this?" but "which specific competition, open to an organization like mine, can I actually enter, and when does it post?"

19.3 Reading the NOFO and Writing to the Rubric

A federal competitive grant is announced in a Notice of Funding Opportunity (NOFO) — also historically called a Funding Opportunity Announcement (FOA), and at other agencies an RFP, RFA, or solicitation. Whatever it's called, it is the single most important document for the grant: it is, in effect, the law governing this competition, and Chapter 3's lesson to read the announcement twice (once for compliance, once for subtext) and Chapter 15's lesson to follow it exactly both apply with full force. A government NOFO is long, dense, and absolutely binding.

Two features of the NOFO dominate everything: the eligibility section and the review criteria (the scoring rubric).

The review criteria are usually published as explicit, point-weighted sections: a rubric stating exactly how many points reviewers assign to each part of your application. This is the chapter's threshold concept made concrete. You met it first in Chapter 3, in RYCC's local RFP, where program design and evidence were worth 30%, community need 25%, and budget only 10% — so that is where the length and effort belonged. Government competitive grants almost always work this way, and the discipline is the same: write to the points the funder assigned. Find the rubric, see where the points are, and allocate your effort, length, and care in proportion. If "project design" is worth 40 points and "organizational capacity" 10, your project-design section should be your most developed, not your organizational boilerplate. Writing to your own sense of what matters, instead of to the published rubric, is the single most common way strong applicants lose winnable government grants.

🚪 Threshold Concept: Government competitive grants are won by scoring to the published rubric. The reviewer is not forming a holistic impression of your brilliance (the NIH) or weighing two grand criteria (the NSF) or deciding whether they trust you (a foundation). The reviewer is, quite literally, assigning points against a published rubric, section by section. So your job is to make it easy for them to give you full points on every criterion: address each scored criterion explicitly, in the order and language of the rubric, with a heading that matches it, leaving the reviewer no work to find where you earned the points. Crossing this threshold transforms how you draft — you stop writing the proposal you want to write and start writing the proposal the rubric rewards, which are not the same document. The applicants who internalize this build their proposals as a direct response to the scoring criteria; the ones who don't write eloquent proposals that score poorly because the points aren't where their eloquence went.

📋 Template — Reverse-engineer the rubric before you write: From the NOFO, (1) copy the review criteria and their point values into a table. (2) Under each criterion, list exactly what the NOFO says reviewers look for. (3) Plan your proposal's sections to mirror the rubric — same order, same language, a heading per criterion. (4) Allocate your page budget by points (the 40-point criterion gets the most space; the 10-point one gets proportionate space). (5) For each criterion, note the evidence you'll provide to earn full points. Write from this table. If a sentence doesn't help you earn points on a scored criterion, question whether it belongs.

⚠️ Common Pitfall: Burying the answer to a scored criterion where the reviewer has to dig for it. Government reviewers often score dozens of applications against a rubric, criterion by criterion, frequently using a scoring sheet that follows the NOFO's order. If your "needs" evidence is scattered across the narrative instead of sitting under a clear "Statement of Need" heading that matches the rubric, a hurried reviewer may not find it — and unfound evidence earns zero points, however well you wrote it. The fix is structural: mirror the rubric's organization and language exactly, label each section to match a scored criterion, and put the evidence for each criterion squarely under its heading. Make scoring you well effortless.

To see the discipline in action, watch Lighthouse reverse-engineer a (composite) reentry-program NOFO whose rubric reads: Statement of Need (15 points), Project Design and Implementation (35), Outcomes and Evaluation (20), Organizational Capacity and Management (20), Budget and Budget Narrative (10). Lighthouse builds the table and immediately sees the shape of the proposal the funder is actually buying:

Criterion	Points	Lighthouse's plan
Statement of Need	15	A focused, evidenced case for local reentry need — substantial, but not the centerpiece.
Project Design & Implementation	35	The centerpiece. The largest, most detailed section: the reentry-to-employment model, activities, timeline, partners, staffing — written to earn all 35.
Outcomes & Evaluation	20	Specific employment/recidivism outcomes, measures, and an evaluation plan (Chapter 10).
Org Capacity & Management	20	Track record and the capacity to manage the award (compliance, reporting) — not just run the program.
Budget & Budget Narrative	10	Correct, 2 CFR 200-compliant, clearly justified — but proportionate; not where the bulk of effort goes.

Notice what the table prevents. An applicant following instinct might write a passionate, ten-page needs section (worth only 15 points) and a thin project-design section (worth 35) — pouring effort exactly backwards. Lighthouse's table forces the opposite: Project Design, at 35 points, becomes the longest and most carefully built section, with a heading that matches the rubric so the reviewer scoring "Project Design and Implementation" finds Lighthouse's design right where they expect it. The same logic governs RYCC's pass-through education subgrant, whose rubric will likewise tell Denise where the points — and therefore the effort — belong. The rubric is not a hoop; it is the funder telling you, in points, exactly what proposal to write.

19.4 The Eligibility and Compliance Gates

Before merit is ever scored, a government application must pass through binary gates — and "binary" is the key word. Unlike a rubric criterion, where a weak section costs you some points, an eligibility or compliance failure is pass/fail: miss it, and your application is rejected without being scored at all, no matter how excellent.

Eligibility is the first gate. NOFOs specify exactly who may apply — types of organizations (nonprofits, units of government, institutions of higher education, tribes), sometimes geographic or population restrictions, sometimes requirements like a minimum operating history. Eligibility is strict and literal: if the NOFO says applicants must be a unit of local government and you are a nonprofit, no partnership workaround you invent on your own will change that (though the NOFO may itself permit nonprofits to apply in partnership with a government, which is different — read it exactly). The first thing to do with any government NOFO is confirm, beyond doubt, that you are eligible. Effort spent writing an ineligible application is wholly wasted.

Registration and submission are the next gates, and Chapter 15 covered them: federal applicants must have an active SAM.gov registration and a Unique Entity ID (UEI), and submit through Grants.gov (or an agency/state system), exactly on time and in the required format. These registrations take weeks, expire, and must be current — the classic avoidable disaster is missing a deadline because SAM.gov registration lapsed. State systems add their own registration steps.

📊 From the Field: Ask any experienced federal grant seeker for a horror story and you'll hear some version of this: a strong application, weeks of work, a capable team — undone by a lapsed SAM.gov registration discovered the day before the deadline. SAM.gov registration must be renewed annually, and renewal is not instant; a registration that expired quietly months ago can take days or longer to reactivate, and Grants.gov will not accept a submission from an organization whose registration isn't active. The application that cannot be submitted is scored zero — the most painful possible outcome, because the work was good and the failure was purely administrative. The defense is simple and unglamorous: know your organization's SAM.gov renewal date, renew well ahead of it, verify your registration is active the week you decide to pursue an opportunity (not the week it's due), and never assume it's fine because it was fine last year. This is the binary gate at its most merciless — and its most preventable. Treat registration status as a standing organizational responsibility, not a per-application afterthought.

🔄 Check Your Understanding: Why is a single eligibility or registration failure more catastrophic than a weak section of your project narrative?

Answer

Because eligibility and registration are binary, pass/fail gates that come before scoring: an ineligible, unregistered, or late application is rejected and never scored at all, so even a 100-point narrative is worth nothing. A weak narrative section, by contrast, costs only some of that section's points and can be offset by strong scores elsewhere. The lesson: confirm eligibility and complete registration first and perfectly (weeks early), because they are the gates that decide whether your merit is ever read — and unlike a rubric criterion, there's no partial credit.

The compliance regime. Federal grants operate under the Uniform Guidance — 2 CFR Part 200 — the body of federal rules governing allowable costs, procurement, financial management, audit, and reporting for federal awards. You met its principles in the budget chapters (Chapters 11–12): costs must be allowable, allocable, and reasonable; some costs are restricted or unallowable; indirect costs follow negotiated or de minimis rates. A government budget must be built to these rules, and a budget that requests unallowable costs or misapplies the indirect rate signals to reviewers that you don't understand the compliance regime you'd be accountable to — a credibility problem beyond the budget points themselves.

🎓 Going Deeper — what 2 CFR 200 actually governs: The Uniform Guidance is worth knowing in outline, because it shapes both your budget and your post-award life. It sets cost principles (what's allowable: costs must be necessary, reasonable, allocable to the award, and not specifically disallowed — some categories, like certain entertainment or lobbying costs, are flatly unallowable); administrative requirements (financial management standards, internal controls, and procurement rules requiring competition when you buy goods and services with federal funds); indirect cost rules (you may use a federally negotiated rate, or, if you've never had one, often a de minimis indirect rate the guidance permits, so you are not forced to forgo indirect recovery — Chapter 12); and audit requirements (the Single Audit). For the proposal stage, the practical takeaways are: build the budget only from allowable costs, apply the correct indirect rate, document your basis of estimate, and reflect procurement and match rules where they apply. For the post-award stage, the same rules govern how you spend, document, and report. You don't need to memorize the regulation, but you do need to build to it — and to know it exists, where to find it, and when to ask your finance office or a grants specialist. Demonstrating fluency with these rules, even lightly, signals to reviewers that you can be trusted with public money.

19.5 The Forms, the Budget, and the Application Package

A federal application is a package of specified components, not just a narrative, and assembling it correctly is part of the work.

Most federal applications use the SF-424 family of forms — the SF-424 (the cover application), the SF-424A (the budget information form for non-construction projects), and others depending on the program. Beyond the forms, a typical package includes the project narrative (written to the rubric, within strict page limits), a budget and budget narrative/justification (Chapters 11–12, built to 2 CFR 200), a logic model or required framework (Chapter 10), and a set of required attachments the NOFO specifies (which may include letters of commitment, organizational documents, indirect-rate agreements, résumés, and more).

A package also includes assurances and certifications — standard forms by which your organization legally promises to comply with applicable federal laws and requirements (nondiscrimination, lobbying restrictions, drug-free workplace, and so on). These are not optional and not negotiable; by signing, your authorized representative binds the organization. They're usually routine, but they are legally serious.

✅ Best Practice: Involve your organization's grants/finance office — and start the package early — because the federal package is where avoidable failures cluster. If you're at an institution with a sponsored programs office (Chapter 4), it must review and submit federal applications, and it has its own internal deadline days before the funder's. If you're a small nonprofit without one, identify now who owns the budget, the registrations, and the authorized representative's signature, because someone must. Build a package checklist straight from the NOFO's list of required components — every form, every attachment, every certification — and treat it like the pre-submission checklist of Chapter 15. Assemble it days early, not hours: federal portals are unforgiving near deadlines, registrations can lapse at the worst moment, and a single missing required attachment is a binary failure. The applicants who lose winnable federal grants on technicalities are almost always the ones who treated the package as a last-minute formality rather than as half the work. Make the package a project in its own right, owned by someone, finished early.

🗣️ From the Review Panel: (A federal grant reviewer reflects.) I review against the scoring sheet, criterion by criterion, and I have a stack of applications to get through. The ones that score well make my job easy: their sections match the criteria, their headings tell me where I am, and the evidence for each criterion is right where I expect it. The ones that score poorly aren't usually bad programs — they're applications where I had to hunt for the answer to a criterion, or where the applicant clearly wrote what they wanted to say instead of answering what the NOFO asked. When I can't find your response to a criterion, I can't award the points; I'm not allowed to give credit for what I assume you meant. And the package matters: a missing required attachment or a budget with unallowable costs tells me you may struggle with the compliance this award demands. Make it effortless to score you well, and answer exactly what was asked.

🔄 Check Your Understanding: A federal application package is missing one required attachment that the NOFO listed, but the project narrative is excellent. The proposal isn't a forms-only program. What is the likely consequence, and what does it tell you about how to treat the package?

Answer

A missing required component is typically a binary failure — the application may be deemed nonresponsive and rejected without being scored, or it loses the points/responsiveness tied to that component, regardless of how strong the narrative is. The lesson: the package is half the work, not an afterthought to the narrative. Build a package checklist straight from the NOFO, assign someone to own every form, attachment, and certification, and finish assembling days early. Government grants are cleared by binary gates as much as won by the rubric — and an unforced package error can sink an otherwise-fundable application.

📐 Project Checkpoint — If government-bound, build your rubric table and compliance plan: If your project targets a government grant, (1) find a real NOFO (on Grants.gov or a state agency site) for a program you're eligible for — confirm eligibility first. (2) Build the rubric table from Section 19.3: criteria, point values, what reviewers look for, your evidence, and your page budget by points. (3) Outline your project narrative to mirror the rubric exactly. (4) List the package components (forms, budget, attachments, assurances) and your registration status (SAM.gov/UEI active? state systems?). (5) Note the reporting and match obligations (Section 19.6) so you build them in from the start. Save it in your "My Proposal" document. If your project isn't government-bound, do step 2 against any scored RFP — writing to a rubric is a transferable skill that sharpens every proposal.

19.6 After the Award: Public Money, Public Accountability

With a foundation, the post-award relationship is stewardship (Chapter 18). With a government grant, the post-award reality is compliance and reporting — and it is heavy, because you are accountable for public money. Understanding this before you apply is part of deciding whether to apply at all, since the administrative burden is real. A government grant is not free money that arrives and is yours to use; it is a conditional, monitored, reportable obligation to deliver specified results with specified funds and to prove, on a schedule, that you did — and the organization that grasps this before applying makes far wiser decisions about which awards to pursue than the one dazzled by the dollar figure alone.

A government award comes with a period of performance (the defined window in which funds must be used), programmatic reporting (regular reports on what you did and the outcomes you achieved, against the objectives in your proposal), and financial reporting (regular reports on how you spent the money, against your approved budget). Many federal awards also trigger the Single Audit requirement: organizations expending above a federal threshold of federal funds in a year must undergo a specific, rigorous audit of their federal awards. Awards may require matching or cost-sharing (Chapter 11), drawing funds through specific systems, prior approval for budget changes, and retention of records for years.

🔍 Why Does This Work?: Why is the government's post-award compliance so much heavier than a foundation's? Because the money is public, and public money carries public accountability: every federal dollar is ultimately taxpayer money, appropriated by Congress for a specified purpose, and the government is legally obligated to ensure it was spent lawfully and as intended. The reporting, the Single Audit, the allowable-cost rules, the records retention — all of it exists so that the use of public funds can be verified and defended to Congress, auditors, and the public. This reframes the burden: it's not bureaucratic cruelty but the price of stewarding public money, and an organization that handles it well becomes a trusted grantee that agencies fund again. The compliance capacity is itself an asset — which is why Chapter 13's organizational-capacity case, for government grants, must convincingly include the capacity to manage the award, not just do the program.

This is also why government grants reward organizations with genuine administrative infrastructure, and why a small organization should weigh the compliance burden honestly before pursuing large federal awards. The money is substantial, but so is the accountability — and taking public money you cannot properly administer is a serious risk, not a windfall. (Chapter 26, on managing the grant after you win, develops the post-award world in full.)

📊 From the Field: There's a smart on-ramp for an organization not yet ready to manage a large direct federal award: become a subrecipient first. When Lighthouse partners as a subrecipient under a larger organization's federal grant — say, a bigger workforce intermediary that holds the prime award — Lighthouse delivers a defined piece of the work and learns the federal compliance world (reporting, allowable costs, documentation, monitoring) with the prime recipient's support and oversight, at a scale it can handle. The prime carries ultimate accountability and helps Lighthouse build the systems and track record that later make it credible as a direct applicant. This is the government-grants version of matching ambition to capacity (the threshold lesson of Chapter 16's mechanism arc): you don't have to leap straight to a large direct award. You can ascend — subrecipient, then small direct award, then larger — building administrative muscle at each step. Agencies and prime recipients alike prefer a grantee who has demonstrably managed federal money before, so the subrecipient path is both a learning route and a credibility-building one.

🪞 Learning Check-In: Notice your reaction to this compliance regime. If it feels daunting, that's an honest response — government grants are demanding, and that's information, not a reason for shame. The right question isn't "am I intimidated?" but "does my organization have, or can it build, the capacity to administer this award responsibly?" For some organizations the answer is yes, and government grants become a major, sustaining source of support. For others, especially small or young ones, the honest answer is "not yet" — and the wise move is to build capacity (sometimes by first being a subrecipient under a larger organization's grant, learning the compliance ropes with support) before pursuing large direct awards. Matching your ambition to your administrative capacity is, here as with NIH mechanisms (Chapter 16), a mark of strategic maturity.

19.7 Strategy: Compete on the Rubric, Win on Compliance

Pull the threads together. Succeeding with government grants means: find opportunities you are genuinely eligible for (federal on Grants.gov, plus state-administered pass-through subgrants — trace the money to the competition you can actually enter); read the NOFO as binding law; build your proposal to score on the published rubric, allocating effort by points and mirroring the rubric's structure; clear every binary gate (eligibility, registration, format, deadline) perfectly and early; assemble the full package (forms, budget to 2 CFR 200, attachments, assurances) correctly; and go in with eyes open about the post-award compliance and reporting you're taking on. The relationship skills of Chapter 18 still help — knowing the program officer and the agency's priorities sharpens your proposal — but they sit on top of a system run by rubrics and rules.

Set the government world beside the others we've seen:

The Part III lesson holds once more: the universal proposal is your engine, and each funder is a different chassis. The government chassis is built from rubrics, eligibility gates, and compliance rules. Master writing to the rubric and clearing the gates, and you can compete for the largest pool of program funding in the country — and steward it well enough to be funded again. And there is a compounding reward for getting good at this: agencies and pass-through funders prefer grantees who have managed public money cleanly before, so each well-run government grant makes the next one easier to win and easier to administer. The organization that builds genuine rubric-writing skill and genuine compliance capacity doesn't just win one grant; it becomes a trusted government grantee, which is among the most durable funding positions in the entire landscape — public money is vast, recurring, and disproportionately renewed to those who have proven they can be trusted with it.

🔄 Check Your Understanding: A capable organization writes a genuinely excellent, eloquent government proposal but scores poorly and isn't funded. Give two distinct reasons rooted in this chapter — not "the program was weak."

Answer

Several are valid. Two clear ones: (1) They wrote to their own sense of what mattered, not to the published rubric — pouring effort into sections worth few points while under-developing the high-point criteria, or scattering evidence so reviewers couldn't find it under the matching headings, so the eloquence didn't land where the points were. (2) A binary gate or package failure — a missed required attachment, an unallowable-cost budget, a formatting/page-limit violation, or (worst) an eligibility or registration problem that kept it from being scored at all. Both reflect the chapter's threshold: government grants are won by scoring to the rubric and cleared by binary gates, not by general excellence.

Spaced Review

Retrieve these from earlier chapters without looking back.

1. (From Chapter 18) Contrast the core logic of a foundation grant with that of a government grant, and say what each implies about where your effort goes.
2. (From Chapter 15) What registrations and systems must a federal applicant have in place, why must you start them weeks early, and how does that connect to this chapter's "binary gate"?
3. (From Chapter 3) How does the scorecard/weighting idea you used to read RYCC's local RFP reappear as this chapter's central discipline?

Answers

1. A foundation grant runs on relationship and trust, so effort goes into cultivation, story, outcomes, and stewardship; a government grant runs on a contract logic, scored against a published rubric under binary eligibility/compliance gates, so effort goes into writing to the points and clearing the gates perfectly. 2. A federal applicant needs an active SAM.gov registration and a UEI, and must submit via Grants.gov (or an agency/state system) on time and in format; these take weeks and expire, so starting early prevents the classic avoidable disaster — and they are binary gates: lapse or lateness means the application isn't scored at all. 3. In Chapter 3, RYCC's RFP weighted program design 30%, community need 25%, budget 10%, telling Denise where length and effort belonged. Government competitive grants almost always publish such a point-weighted rubric, and this chapter's threshold concept — write to the points the funder assigned — is exactly that scorecard discipline made central.

Chapter Summary

Key Takeaways

• Government grants beyond NIH/NSF span federal departments, state agencies, and pass-through (subrecipient) funding — often the largest source of program money for nonprofits, schools, and local governments, and the most rule-bound.
• Know the type: discretionary (competitive — you write a scored proposal), formula and block (allocated by law, but often the source of state-administered subgrants you can compete for). Trace the money to the competition you can actually enter.
• Threshold concept: government competitive grants are won by scoring to the published rubric and cleared by binary gates. Write to the points the funder assigned; clear every eligibility/compliance gate perfectly, because an ineligible or noncompliant application is never scored.
• Read the NOFO as binding law; build your proposal to mirror the rubric (order, language, headings) and allocate effort by points; make it effortless for a reviewer to award full points.
• Clear the binary gates: confirm eligibility first; keep SAM.gov/UEI and any state registrations current; submit on time and in format; meet 2 CFR 200 in the budget.
• A government award brings heavy post-award accountability — period of performance, programmatic and financial reporting, possible Single Audit, match, records retention. Weigh the compliance burden against your administrative capacity before applying.

Action Items

1. Search Grants.gov and your relevant state agencies for opportunities you're genuinely eligible for; trace pass-through money to the real competition.
2. For a target NOFO, build the rubric table (criteria, points, evidence, page budget) and outline your narrative to mirror it.
3. Confirm and renew SAM.gov/UEI and state registrations now — weeks before any deadline.
4. Build the budget to 2 CFR 200 (allowable, allocable, reasonable; correct indirect rate; any required match).
5. Assemble the full package (SF-424 forms, budget narrative, attachments, assurances) and plan for reporting from the start.

Common Mistakes

• Writing to your own priorities instead of the rubric — under-developing high-point criteria, or hiding evidence where reviewers can't find it.
• Treating eligibility or registration as a formality — a binary failure that wastes the entire effort.
• Looking only at Grants.gov and missing the larger pool of pass-through money through your state.
• Requesting unallowable costs or misapplying indirect rates, signaling you don't grasp the compliance regime.
• Pursuing large awards beyond your administrative capacity to manage — taking on public-money accountability you can't meet.

Decision Framework — "Should I pursue this government grant, and how?"

1. Am I eligible? → Confirm beyond doubt first; if not, stop (no workaround for a binary gate).
2. What channel is the money? → Direct discretionary (Grants.gov), state pass-through subgrant, or both? Find the competition I can actually enter.
3. What does the rubric reward? → Build the rubric table; plan to write to the points.
4. Are my registrations current and my package complete? → SAM.gov/UEI, state systems, forms, attachments, assurances — clear every gate early.
5. Can I administer the award? → Honestly weigh the 2 CFR 200 compliance, reporting, and audit burden against my capacity; consider being a subrecipient first if not yet ready.

🔁 Carry this forward: You've now seen the rule-bound government world and the relationship-driven foundation world — the two poles of the funding landscape. Next, SBIR/STTR (Chapter 20) occupies a fascinating hybrid: government money for commercializing innovation, where the proposal must satisfy both rigorous federal review and a hard-nosed market logic. Watch the rubric-and-compliance discipline you built here meet a new demand — proving not just merit and feasibility, but commercial potential, where the federal government acts less like a grantor and more like an early investor betting on your innovation reaching the market.