SF-424B: Assurances for Non-Construction Programs

The SF-424B is the Assurances for Non-Construction Programs form, and it is the least-read consequential document in a federal grant package. Applicants scan it, sign it, and move on. What they have actually done is commit the organization to seventeen standing obligations, several of which continue for years after the money is spent.

What kind of document this is

The SF-424B is a certification, not a questionnaire. There are no boxes to tick and nothing to tailor. One signature accepts every assurance on the list, and that signature carries the same legal weight as any other contractual commitment the organization makes.

That matters because the assurances are written in the compressed language of federal statute, referencing acts and executive orders by number rather than describing what they require. It is entirely possible to sign the form in good faith without knowing what you have agreed to. The obligations apply regardless.

Construction programs use the SF-424D instead. It carries comparable assurances plus items specific to real property: flood insurance, historic preservation, and restrictions on how a federally assisted facility can be used or disposed of.

The assurances with real operational cost

Most of the seventeen are commitments any competent organization already meets. A handful create ongoing work, and these are the ones worth reading before you sign.

Legal authority and financial capability. You certify that your organization has the legal authority to apply and the institutional, managerial, and financial capability to plan, manage, and complete the project. This is not aspirational. If your accounting system cannot track costs by budget category and separate federal from non-federal funds, you have certified to something untrue.

Access to records. You grant the awarding agency, the Comptroller General, and their representatives access to your books, documents, and records for audit or examination. In practice this means an auditor can ask for anything and you must produce it.

Record retention. Records must be kept for the period the agency specifies, ordinarily three years from submission of the final expenditure report. Deleting a project mailbox during a routine IT cleanup can put you in breach of an assurance you signed years earlier.

Conflict of interest. You certify you will establish safeguards prohibiting employees from using their positions for purposes that constitute or present a conflict of interest. A written policy is the expected evidence.

Nondiscrimination. A stack of civil rights statutes applies: Title VI of the Civil Rights Act, Section 504 of the Rehabilitation Act, the Age Discrimination Act, Title IX, and others. These apply to the whole program, not only to the federally funded slice of it.

Standards for merit systems and political activity. Where applicable, you agree to comply with merit system standards for personnel administration and with the Hatch Act's restrictions on political activity by employees whose principal employment is federally funded.

Who is allowed to sign

Only the Authorized Organization Representative may sign the SF-424B, the same official who signs the SF-424 cover form and submits the package through Grants.gov.

The word that matters is authorized. An AOR role in the Grants.gov system is a technical permission; authority to bind the organization is a governance question answered by your bylaws, board resolutions, or delegation of authority policy. A grants manager with system access but no delegated signing authority who signs the form has created a live compliance problem rather than a completed application.

Confirm two things before deadline week: that your AOR designation in Grants.gov is current, and that the person holding it actually has authority to commit the organization. Both take time to fix and neither can be fixed at 11pm.

Sign it after the readiness conversation, not before

The productive way to use the SF-424B is as a checklist run before you decide to apply. Read the seventeen assurances against how your organization actually operates and ask, item by item, whether you could produce evidence if an auditor asked tomorrow. Do you have a written conflict of interest policy? Can your accounting system segregate federal funds? Do you have a records retention schedule that someone follows? Is your nondiscrimination policy current and posted?

Where the answer is no, you have found a real gap, and the gap exists whether or not you sign the form. Signing simply converts an operational weakness into a certification you cannot support. Our grant readiness checklist covers most of the same ground in plainer language and is a faster way to run the exercise.

How the assurances connect to what comes after

The SF-424B is the bridge between applying and being accountable. Nearly every obligation it names reappears later as a post-award requirement: the record retention assurance shows up during the single audit, the financial capability assurance shows up in post-award grant management, and the access-to-records assurance is what makes both possible.

Reading it that way makes the form less of a formality and more of a preview. It tells you, before you have spent a dollar, exactly what the government expects to be able to verify. For the rest of the package it sits inside, see the SF-424 cover form, the SF-424A budget form, and the full Grants.gov registration path.