Federal Grant Compliance Checklist: 2 CFR 200

What is federal grant management?

Federal grant management turns an award agreement into controlled work: authorized spending, documented purchases, measurable performance, accurate reports, and an orderly closeout. For a nonprofit recipient, that means connecting each obligation to a person and a record before a report or review is due.

This checklist covers core recipient responsibilities. It is not a complete assessment of every federal program. Read your notice of award, amendments, agency implementation, pass-through conditions, and applicable version of the Uniform Guidance together. Section 200.101 explains applicability, including situations that receive different treatment. Section 200.110 addresses implementation timing. Older awards should not automatically be treated as though every current revision applies to them.

Sources were checked September 22, 2026; the official eCFR API reported Title 2 as current through September 18, 2026. This is educational information, not legal, accounting, or audit advice. Resolve award-specific questions with the awarding agency or pass-through entity and, where appropriate, your grants attorney or auditor.

Start one requirement register with the award identifier, source section, responsible person, due date, required evidence, reviewer, and completion record. Keep the original instruction beside your interpretation. The post-award grant management guide explains recipient responsibilities; the post-award checklist covers award setup. For coordinating several awards, use the multi-grant tracking workflow.

What does grant compliance training cover?

Useful grant compliance training teaches staff to recognize a requirement, carry out the control, retain support, and escalate an exception. It should connect program work with finance rather than leave each team to interpret the same award independently.

Use the following checklist in an award kickoff, periodic review, and staff handover. The quoted fragments are from the linked regulation; the suggested records and common failures are practical examples, not an exhaustive legal evidence standard.

200.302 Financial management

• Identify each federal award in your financial records and reconcile its budget, spending, and source support.

Rule: Financial systems must support required reports and show the use of award funds. Section 200.302(b) requires award identification, supported financial records, expenditure-to-budget comparisons, and written procedures for payment and cost allowability. The rule specifically requires “source documentation.” Read 2 CFR 200.302.

Produce: An award register connected to the accounting records, a current approved budget, reconciled financial reports, invoices or other transaction support, and the applicable written procedures.

Common failure: A spreadsheet balance agrees with last month's export but excludes a later payroll adjustment. Record the accounting cut-off date and who reviewed the reconciliation. A current-looking dashboard is not a substitute for a reconciled ledger.

200.303 Internal controls

• Document who prepares, reviews, approves, and monitors grant transactions and reports.

Rule: Recipients and subrecipients must establish, document, and maintain effective internal controls, monitor compliance, and take “prompt action” when noncompliance is identified. The section also addresses safeguarding sensitive information. Read 2 CFR 200.303.

Produce: Approval responsibilities, written procedures, access decisions, evidence of review, and an exception log showing corrective action and follow-up.

Common failure: A policy exists but nobody can show it was used. A small team should identify where duties overlap and document an appropriate independent review or other control. The control's design and operation need assessment; naming a backup alone does not establish effectiveness.

200.403 Factors affecting allowability of costs

• Review a cost against its purpose, timing, restrictions, accounting treatment, and support before charging it.

Rule: An allowable cost must meet the section's combined criteria, including necessity, reasonableness, allocability, consistent treatment, and documentation. The regulatory phrase is “adequately documented.” Budget availability alone does not establish allowability. Read 2 CFR 200.403.

Produce: The purchase or expense record, the connection to the award, approval evidence where required, the relevant budget category, and support for the date and accounting treatment.

Common failure: Staff assume an approved budget allows every charge in that category. Review the specific cost and any required prior approval. Section 200.403(h) also distinguishes administrative closeout costs from other costs: do not turn the closeout window into general permission to continue program spending.

200.405 Allocable costs

• Use a documented method to assign shared costs to the activities that benefit.

Rule: Allocation follows “relative benefits received.” A cost assigned to one federal award cannot simply be moved to another to cover a funding shortage or avoid restrictions. Read 2 CFR 200.405.

Produce: The allocation method, underlying records, calculation, reviewer approval, and explanations for changes. For employee compensation, also assess the records against 2 CFR 200.430, rather than assuming a budget estimate is sufficient support.

Common failure: Shared staff time is split according to available grant balances. In a hypothetical shared service, an allocation based on documented usage may support a decision; a convenient equal split needs its own rationale. Do not backfill a method merely to reproduce the desired expenditure total.

200.318–200.327 Procurement standards

• Select and document the appropriate procurement method before committing to a purchase.

Rule: Section 200.318 requires documented procedures, conflict-of-interest standards, contractor oversight, and “procurement records.” The history must explain the procurement method, contract type selection, contractor selection or rejection, and price basis. Read 2 CFR 200.318.

Produce: The requirement, procurement-method decision, applicable threshold basis, quotations or proposals where required, evaluation, conflict review, contract, price support, and evidence that the goods or services were received.

Common failure: A preferred supplier is selected first and the competition record is assembled afterward. Section 200.320 distinguishes informal, formal, and noncompetitive methods. Do not assume one universal dollar threshold applies to every organization, date, and transaction; check the current definitions, permitted exceptions, and your documented procedures. Contracts also need the applicable Appendix II provisions required by section 200.327.

200.331–200.332 Subrecipient determination and monitoring

• Determine whether each funded relationship is a subaward or procurement contract, then apply the corresponding controls.

Rule: Classification follows the substance of the relationship under section 200.331. If your nonprofit acts as a pass-through entity by making a subaward, section 200.332 requires assessment of fraud and noncompliance risk and monitoring, including review of “financial and performance reports.” It also addresses required subaward information, exclusion checks, audit verification, and follow-up. Read 2 CFR 200.332.

Produce: A documented classification decision, subaward agreement, risk assessment, monitoring plan, reports reviewed, issues raised, and records of resolution. Maintain the basis for any monitoring changes.

Common failure: Calling an organization a vendor in the accounting system is treated as a sufficient determination. Another failure is receiving a subrecipient report without reviewing its content. If documented classification confirms that you make no subawards, record why the pass-through monitoring duties in section 200.332 do not apply. Do not skip the classification decision under section 200.331.

200.328–200.329 Financial and performance reporting

• Build the reporting calendar from the award and verify the report against financial and program support before submission.

Rule: Section 200.328 governs financial reporting; section 200.329 governs performance reporting. For ordinary quarterly or semiannual reports, the current provisions specify due dates no later than “30 calendar days” after the reporting period. Annual reports generally have a 90-calendar-day outside limit; the performance section also permits annual reports before an award anniversary. Read 2 CFR 200.328 and 200.329.

Produce: The actual award deadline, required form or portal, reconciled financial support, performance definitions and calculations, narrative, approval, and submission confirmation. Record an authorized extension if one is granted.

Common failure: Staff enter the regulatory outside limit as their deadline without reading the award, or mistake a saved draft for a submitted report. Financial and performance reports must tell a coherent story, but they remain separate deliverables when the award requires both.

200.334 Record retention requirements

• Assign a retention trigger to each record category and check for holds before disposal.

Rule: The general retention period is “three years” from submission of the final financial report. Quarterly or annually renewed awards and certain categories have different triggers. If litigation, a claim, or an audit starts before that period expires, retain the affected records until resolution and final action. Written retention extensions can also require longer preservation. Property records generally run from final disposition. Read 2 CFR 200.334.

Produce: A record inventory, final-report submission date, category-specific retention schedule, hold register, and accessible files with appropriate permissions.

Common failure: The team deletes records three years after the award end date. Another is retaining a spreadsheet of links after the linked documents or former employee's account have disappeared. Test retrieval with someone who did not create the file. The grant file guide provides a practical organization structure.

200.501 Audit requirements and 200.512 report submission

• Calculate federal awards expended for the entity's fiscal year and plan any required audit submission.

Rule: For a non-Federal entity subject to Subpart F, the current threshold is “$1,000,000 or more” in federal awards expended during its fiscal year. This is an entity-wide expenditure test, not a per-award ceiling or cash-receipt test. Subpart F does not apply to for-profit organizations; their applicable award and oversight requirements need separate review. A Single Audit or an eligible program-specific audit is required under the applicable provisions. Read 2 CFR 200.501.

The Federal Audit Clearinghouse identifies the higher threshold for fiscal years beginning on or after October 1, 2024, and the earlier $750,000 threshold for fiscal years beginning before that date. For example, a calendar fiscal year beginning January 1, 2025 uses the $1,000,000 threshold. Do not apply it retrospectively to a late audit of an earlier period.

Produce: The expenditure calculation and supporting award schedule, the threshold determination, auditor engagement when required, reporting package, corrective-action records where applicable, and FAC submission evidence.

Common failure: The organization counts only direct federal grants and overlooks federal subawards. Being below the threshold does not remove award duties or record-access requirements. Consult the applicable rules for unusual funding and entity types. Under section 200.512, submission is generally due by the earlier of 30 calendar days after receipt of the auditor's reports or nine months after the audit period ends, subject to the section's extension and nonbusiness-day provisions.

200.344 Closeout

• Reconcile final reporting, outstanding obligations, funds, and property before marking the award closed.

Rule: A direct recipient must submit required final reports “no later than 120 calendar days” after the period of performance ends. A subrecipient generally has 90 calendar days after its subaward period ends, or an earlier agreed date. The section separately addresses liquidation of financial obligations and authorized extensions. Read 2 CFR 200.344.

Produce: Final financial and performance reports, submission confirmations, reconciliation of obligations, required refunds, property accounting, unresolved-issue records, and the relevant closeout correspondence.

Common failure: The award is marked complete when program delivery ends, although invoices, reports, or property questions remain open. Another is treating a request for an extension as approval. Keep the submitted request and the authorized decision separate. Use the closeout checklist to organize the remaining actions.

What evidence should a federal grant compliance checklist track?

Track evidence of the decision and review, as well as the underlying transaction. The table below compares a weak completion signal with records that can help a reviewer examine what happened. No document listed here automatically establishes compliance; its accuracy, relevance, and applicable requirements still matter.

At each review, select one completed item and follow it backward to the instruction and forward to the evidence. This small operational check can reveal missing links, inaccessible files, or a status that was updated before the underlying work finished. Set the review frequency according to the award and your controls; this article does not prescribe a universal interval.

What can federal grants management software support?

Software can organize obligations, ownership, supporting files, and review queues. It cannot determine which regulation applies simply because a grant is labeled federal. The team must enter and maintain the correct award-specific requirements and continue using the agency's required reporting channels.

GrantConsole attaches evidence to deliverables and displays explainable warnings about entered deadlines and records. Those mechanics can support the work involved in financial and performance reporting, but a stored file still needs review. GrantConsole's public product description documents the capabilities summarized below.

The 30-day product warning uses the grant's end date and open deliverables; it is not the legal closeout or final-report deadline. Spending-versus-time warnings likewise identify a pattern, not whether a cost is allowable. These thresholds are product choices, not federal standards.

This is an operational mapping, not a regulatory endorsement or a claim that the rules implement all of 2 CFR 200. GrantConsole tracks the obligations you enter; it does not interpret the award for you. Review its product scope and live demo against an award register you have already checked.

How should you organize federal grant management training?

Train from the award outward. Give grants, finance, and program staff one fictional transaction and report to work through together. Have them identify the rule, choose the supporting records, assign the review, and explain what would cause escalation.

Include exception handling. Staff should know what to do when a purchase lacks support, a reporting definition is unclear, a subrecipient misses a deliverable, or a requested budget change has no approval. Capture the answer in the procedure and award record rather than relying on a verbal handoff.

A useful training result is that a second person can retrieve the instruction, explain the decision, and locate the submission evidence. Where the interpretation remains uncertain, record the question, responsible person, and authoritative response before treating it as resolved.