The Compliance Backbone for Grant-Funded Energy Projects

Foreword

Foreword

Three decades inside the regulatory and operational side of the energy sector taught me a habit I cannot shake. I read post-award failures backward from the finding. The finding is rarely where the failure happened. The finding is where the documentation ran out. The actual failure occurred earlier, in the months when the team was building the project and not building the administrative spine that the project would later need to lean on. By the time the single audit notice lands, or the program officer schedules a site visit, or the OIG sends a letter, the recipient is in a documentation reconstruction posture rather than a documentation defense posture. Those are not the same thing. One produces clean findings. The other produces eighteen to twenty-four months of corrective action work.

This is the fifth reference in the Energy Compliance, Inc. Grant Funding Series and the first of the long-form authority whitepapers in the series. The four references that preceded this one are tactical. They sit on a desk next to a working application or a working award and they help the team find gaps. This one is different. This one is a textbook for the compliance discipline that holds a federally funded energy project together through the entire period of performance and into closeout. The audience is the people who actually operate that discipline: the controller and grants administrator at a public power utility, the development lead carrying a DOE grant alongside an IRA project, the project manager at an electric cooperative that took its first federal award in a decade, the finance director at an industrial energy user whose efficiency project came in under a competitive federal program.

The pattern I have watched on federal energy awards is consistent enough to plan around. The award lands. The team builds the project. The team does not build the administrative spine at the same pace. Reporting goes in on time, more or less, for the first few quarters. The sub-recipients get monitored, sort of, when there is time. Procurement files get assembled the way the entity has always assembled procurement files. Then a federal review touches the file and the gap between what was done and what the file documents is wide enough to produce findings. The findings are not the failure. The failure was the gap between the work and the file, and the gap was built in over years.

The compliance backbone is the structure that closes that gap. It is not exotic. The Uniform Guidance at 2 CFR 200 already specifies most of what is required. Program-specific terms and conditions specify the rest. Agency policy directives fill in the texture. What entities lack is not the regulatory text. What entities lack is a working translation of the regulatory text into a documentation lifecycle that runs concurrently with project execution rather than catching up to it later. This reference is that translation. It is the same backbone I work through with clients when they engage Energy Compliance, Inc. for a Post-Award Compliance

Administration scope. The substance is identical. The engagement carries the workload. Either way, the structure below is the right structure.

This reference is not marketing material disguised as content. It is what a senior practitioner in this work would build for an entity that wanted to do post-award correctly the first time. Read it that way. Build it that way. The federal energy money is moving at a pace and scale that most recipient entities were not built to administer. The administrative spine has to be built either way. Better to build it on purpose than to assemble it under audit pressure.

Rob Smith, Founder, Energy Compliance, Inc.

Closing Note

About Energy Compliance, Inc.

About Energy Compliance, Inc.

Why Post-Award Is Where Federal Energy Projects Actually Fail

Why Post-Award Is Where Federal Energy Projects Actually Fail

The energy industry has spent the last several years celebrating award announcements as if the announcement itself were the achievement. The announcement is the easy part. The hard part runs for three to seven years after the announcement, through the period of performance, through reporting cycles, through audits, through closeout. That period is where federal money becomes either a clean executed project or a corrective action plan with a name and a docket number. The difference between the two outcomes is almost always traceable to whether the recipient built a compliance backbone or assumed the project's technical merit would carry the administrative weight.

The Pattern Across Three Decades I have watched the same arc on federally funded energy projects since the original DOE State Energy Program awards of the 1990s. The application phase runs intensely. The award letter lands. The team that won the award rotates back to its prior responsibilities. The construction phase begins, often with new personnel who did not write the application and do not carry the same intuitive understanding of the obligations the application accepted on behalf of the recipient. The first quarterly Federal Financial Report goes in. The team is proud of submitting on time. The numbers are close enough that the program officer does not flag them.

Eighteen months later, a single audit firm walks through the recipient's general ledger and asks for the procurement file that supports a major equipment purchase. The procurement file exists in the form the entity has always maintained it for state and local procurements. It does not exist in the form the Uniform Guidance specifies at 2 CFR 200.318-327. The auditor flags a procurement deficiency. The deficiency surfaces as a finding in the Schedule of Findings and Questioned Costs. The questioned cost is the entire purchase. The entity now has six months to demonstrate, retroactively, that the procurement satisfied the federal standards it never explicitly tracked against.

The pattern is not exotic and it is not new. What is new is the scale. The Infrastructure Investment and Jobs Act and the Inflation Reduction Act together moved federal funding into energy at a level the recipient population was not staffed to administer. Entities that had managed one or two federal awards across a decade now hold five or seven simultaneously. The administrative discipline that worked for one award fails at five. The backbone has to be built on purpose, with structure, before the volume overwhelms the team that is trying to administer it on intuition.

The Failure Surfaces Are Predictable If the failure surfaces are predictable, then the prevention surfaces are also predictable. I keep a running tally of the categories of finding I have personally watched produce material questioned costs on federally funded energy projects. The categories are stable across program lines. Procurement documentation insufficient to evidence competition or sole-source justification. Sub-recipient monitoring conducted in name only, with risk assessments missing or not refreshed annually. Cost principles applied unevenly, with allocability questions surfacing on shared costs and indirect cost rates. Time and effort certifications for personnel costs absent or signed retroactively. Property and equipment inventories that do not reconcile to general ledger asset registers. Quarterly reports that do not tie to the underlying ledger when traced backward. Single audit Schedule of Expenditures of Federal Awards that omits awards, mistranslates CFDA numbers, or fails to capture pass-through arrangements.

Each of those categories has a counterpart in the Uniform Guidance. None of the failures are caused by silent regulatory ambiguity. The recipients did not read 2 CFR 200 and find it unclear. The recipients did not read 2 CFR 200 at all, or read it once at the kickoff meeting and never returned to it as the operative reference during execution. The compliance backbone is the artifact that makes 2 CFR 200 a continuous reference rather than a one-time read.

What Auditors Actually Look At A single audit under the Uniform Guidance at 2 CFR 200 Subpart F is structured around major program selection, internal controls testing, and compliance requirement testing across the fourteen compliance requirements applicable to the program. The auditor is not improvising. The auditor is working a Compliance Supplement that the Office of Management and Budget publishes annually and that names, by CFDA number, the specific compliance requirements that apply to the program and the specific testing the auditor must conduct. The entity that has read the applicable Compliance Supplement section before the audit walks in has already won most of the audit defensibility battle. The entity that has not read it is reacting to questions whose pattern the auditor knew in advance.

The Compliance Supplement is publicly available. The applicable sections for major energy programs run thirty to sixty pages per program. Reading them is not optional for entities that intend to pass a clean single audit. Reading them after the audit notice lands is too late.

The Cost of Getting It Wrong The financial exposure on a failed post-award engagement is rarely a single line item. The exposure compounds. Questioned costs at the audit level become disallowed costs at the agency level if the recipient cannot defend them. Disallowed costs become repayment obligations. Repayment obligations can include interest under the Debt Collection Improvement Act. Sub-recipient findings flow back to the pass-through entity under 2 CFR 200.332. A recipient with a material finding on one award goes onto a different

competitive footing for the next award the agency considers. Some agencies impose high-risk recipient designations under 2 CFR 200.208 that carry additional reporting, more frequent monitoring, restricted advance payment, and prior approval requirements on routine actions.

None of those consequences attaches to the project's technical merit. All of them attach to the administrative spine.

Bridge to Chapter 2 The compliance backbone has a name when it is built deliberately. The name is the Compliance Obligation Matrix. The matrix is the working document that translates the Notice of Award, the terms and conditions, the program guidance, and the applicable Uniform Guidance into a live register of obligations, owners, evidence, and review dates. The next chapter walks through what that matrix actually contains and how it operates as the spine of the post-award discipline.

The Compliance Obligation Matrix: Anatomy and Lifecycle

The Compliance Obligation Matrix: Anatomy and Lifecycle

The Compliance Obligation Matrix is the working artifact that distinguishes a recipient operating a federal award on purpose from a recipient operating one on intuition. It is not a binder. It is not a spreadsheet that gets opened at the kickoff meeting and then forgotten. It is a live register that the grants administrator updates weekly during active periods and that every personnel change carries forward without information loss. Properly built, it answers four questions on demand for every obligation the award carries. What is the obligation. Who owns it. What evidence demonstrates compliance. When was the obligation last reviewed and by whom.

The Source Material the Matrix Translates A federal energy award carries obligations from at least four overlapping sources. The Notice of Award itself, including any special terms and conditions specific to the recipient or the project. The general terms and conditions that the awarding agency publishes and incorporates by reference, often the DOE Special Terms and Conditions, the EPA General Terms and Conditions, or the agency-specific equivalent. The program specific guidance documents the agency publishes for the funding opportunity, including any program specific cost guidance, environmental review requirements, or community benefits expectations. The Uniform Guidance at 2 CFR 200, which applies to virtually all federal awards as the cross-cutting administrative framework.

In addition to those four, certain awards trigger statutory and regulatory obligations that exist outside the award documents themselves. Davis-Bacon prevailing wage applies under the Davis-Bacon Act and Related Acts to construction work performed on awards that incorporate the requirement. The Build America, Buy America Act applies to infrastructure projects under most federal financial assistance programs since the IIJA expansion. NEPA environmental review applies under the National Environmental Policy Act and the implementing agency procedures. Section 106 historic preservation review applies under the National Historic Preservation Act when the project affects historic resources. Title VI civil rights compliance applies under the Civil Rights Act of 1964 to all federally assisted programs. Each of those statutory frameworks generates obligations that may or may not be enumerated in the Notice of Award itself but that always apply to projects that meet the triggering criteria.

The Compliance Obligation Matrix collects every obligation from every source into a single working register. The act of building the matrix is itself the first compliance discipline. Recipients that have built one have read everything they signed. Recipients that have not built one have signed documents they did not read with the attention the documents required.

The Anatomy of the Matrix Every row in the matrix represents one obligation. The columns enumerate what the recipient knows about that obligation. At a minimum the matrix carries the obligation description, the source citation, the responsible owner, the evidence type, the evidence location, the review frequency, the most recent review date, the most recent review outcome, and the next review date. Matrices that have been built well also carry a risk rating per obligation that reflects the financial exposure and historical failure pattern, and a status field that flags any obligation currently in remediation.

The obligation description is written in operational language, not in regulatory language. "Submit Federal Financial Report SF-425 quarterly within thirty days of each calendar quarter close" is an operational obligation. "Comply with 2 CFR 200.328" is a citation. The matrix translates citations into actions. The owner field names a person, not a department. Departments do not file reports. People file reports. The evidence type field specifies what artifact demonstrates compliance: a signed certification, a submitted form with confirmation receipt, a procurement file with named contents, a sub-recipient monitoring report with a date and signature, a property inventory reconciled to the asset register. The evidence location field specifies where that artifact is filed so that any subsequent reviewer can retrieve it without asking the owner.

The review frequency field reflects the natural cadence of the obligation. Reporting obligations carry quarterly or annual frequencies. Procurement obligations carry transaction-driven frequencies. Sub-recipient monitoring obligations carry risk-adjusted frequencies that range from quarterly desk reviews to annual on site visits. The review date and outcome fields carry the audit trail that demonstrates the matrix has been operated, not merely populated.

Building the Matrix at Award Acceptance The matrix should be built before the period of performance begins, not after the first reporting cycle has already run. The grants administrator reads every document the award package contains, including incorporated-by-reference documents the recipient may not have downloaded. The administrator works through the Uniform Guidance with the program-specific compliance requirements identified in the relevant section of the OMB Compliance Supplement open alongside it. Each obligation that surfaces enters the matrix.

The initial population of the matrix typically takes thirty to sixty hours of administrator time for a single federal energy award of moderate complexity. The hours are concentrated and uncomfortable. They are also the cheapest hours the recipient will spend on the entire award. The same administrator working under audit pressure two years later will spend three to five times those hours reconstructing what the matrix would have captured in real time. I have watched that arithmetic play out on every recipient I have advised through a post-award engagement. The matrix is not optional discipline. It is purchased discipline. The recipient either purchases it at the front end with administrator time or purchases it at the back end with audit firm time and disallowance arithmetic.

Operating the Matrix During the Period of Performance The matrix is opened weekly during active periods and at minimum monthly during quieter phases. The grants administrator works the obligations whose review dates fall in the upcoming two-week window. Where an obligation has been satisfied, the review date and outcome update. Where an obligation is at risk, the matrix flags it for management attention. Where a new sub-award is issued or a contract modification lands, new obligations enter the matrix.

The matrix becomes the artifact that supports management certifications, board reports, internal audit reviews, and external audit responses. When the single audit firm asks for evidence of post-award internal controls, the matrix is the evidence. The auditor does not need to be told the recipient operates a matrix. The auditor needs to see the matrix, see the dated review entries across the period of performance, and trace specific obligations through specific evidence artifacts. The matrix that has been operated, not merely populated, satisfies that test in a single document review.

Personnel Transitions Without Information Loss Federal awards run three to seven years. Most recipient organizations turn personnel within that horizon. A matrix that depends on the institutional memory of one grants administrator fails the first time that administrator leaves the role. A matrix that captures evidence locations, review history, owner assignments, and source citations transfers cleanly to a successor. The successor reads the matrix and is operational within days. The successor whose predecessor left no matrix spends months reconstructing the obligation set from primary documents and produces, in the meantime, the kinds of gaps that surface as findings.

The discipline of writing the matrix down rather than carrying it in one administrator's head is itself a control. The control survives the administrator.

Bridge to Chapter 3 The matrix is only as accurate as the source documents that feed it. The next chapter walks through how to read those documents with the attention they require. The Notice of Award is not a press release. The terms and conditions are not boilerplate. The program guidance is not optional context. Reading them produces the obligations the matrix later operates.

Reading the Award: NOA, Terms and Conditions, Program Guidance, Agency Policy Directives

Reading the Award: NOA, Terms and Conditions, Program Guidance, Agency Policy Directives

The Notice of Award arrives by email. The recipient celebrates. The recipient files the email and the attachments. Six months later, when the program officer references a specific term in passing, the recipient cannot recall having read it. That sequence is the most common entry point to a downstream finding. The award documents are not boilerplate. They are the operational instructions for the next three to seven years of administrative work. Reading them with the attention they require is the first hour of post-award discipline, and it has to happen before the first dollar is drawn down.

The Notice of Award Itself The Notice of Award is a multi-page document, not a one-page announcement. It identifies the awarding agency, the program, the recipient, the federal share, the recipient cost share if any, the period of performance, the project description, the approved budget, and the standard and special terms and conditions that apply. The standard terms and conditions are usually incorporated by reference rather than printed inline. The special terms and conditions are listed explicitly. Special terms are where the agency has added obligations specific to this award that the recipient will not find anywhere else.

Special terms often include reporting frequencies that exceed the default quarterly cadence, prior approval requirements for budget modifications that exceed specified thresholds, milestone-based payment triggers, community benefits plan reporting obligations, Justice40 reporting obligations, environmental review hold points, and program-specific cost share documentation requirements. A recipient that misses a special term because the document was scanned rather than read produces a finding the auditor will treat as a material failure of internal control.

I have watched special terms include obligations as significant as a requirement to consult quarterly with a community advisory board, a requirement to file an annual demographic workforce report, a requirement to provide ninety days notice before any change in key personnel, and a requirement to maintain the funded equipment in service for a period that extends beyond the project's federal period of performance. Each of those obligations carries a remedy if violated, and the remedy is rarely cheap.

Standard Terms and Conditions Each awarding agency publishes its own standard terms and conditions. DOE Office of Energy Efficiency and Renewable Energy uses one set. DOE Loan Programs Office uses another. EPA uses agency-wide terms. USDA Rural Development uses program-specific terms. The standard terms incorporate by reference the Uniform Guidance at 2 CFR 200, the agency's own regulations at the relevant CFR title, and any cross cutting statutory frameworks the agency administers.

The standard terms are where the recipient finds the operational mechanics of how the award works. How drawdowns occur. Whether the recipient uses the Automated Standard Application for Payments system. What approval is required for budget realignment across cost categories. How no-cost extensions are requested. How equipment with a unit acquisition cost above $5,000 is treated under 2 CFR 200.313. How the audit obligation is satisfied. How the closeout package is constructed.

A recipient that has not read the standard terms is operating an award on assumptions. The assumptions are usually wrong in at least two places. The two places are where the audit finding lands.

Program-Specific Guidance Beyond the Notice of Award and the standard terms, most federal energy programs publish program-specific guidance documents that govern how the program operates. DOE EERE programs publish guidance on Davis-Bacon applicability, on community benefits plans, on Justice40 reporting, on diversity equity inclusion accessibility reporting, on energy justice analysis. DOE LPO publishes guidance on Buy America applicability, on prevailing wage compliance, on apprenticeship reporting. EPA Greenhouse Gas Reduction Fund publishes guidance on capital deployment, on private capital leverage reporting, on community benefit calculation. Each program's guidance is binding to the extent the Notice of Award incorporates it, which is essentially always.

Program guidance is updated during the period of performance more often than the standard terms. The recipient is responsible for tracking the updates. Agencies do not always notify recipients individually when program guidance changes. The grants administrator who has subscribed to the program's listserv and the agency's news service has a chance of catching the updates. The administrator who has not subscribed will find the updates by accident, usually after the new requirement has already produced a noncompliance.

Agency Policy Directives Underneath the program guidance sits the agency's policy directive structure. DOE issues policy memoranda from the Office of the General Counsel, from the relevant program office, and from the Office of Acquisition Management. EPA issues policy through Office of Grants and Debarment memoranda. USDA issues through the National Office. These policy directives interpret the regulatory text and clarify how the agency intends

to administer ambiguous provisions. They are binding on the agency's contracting officers and on the recipient when incorporated into the award terms.

Recipients rarely read agency policy directives unless someone tells them to. The recipients that do read them are usually the ones who have been through a finding and want to understand what tripped them. By that point the cost of reading has already been paid. Reading policy directives before the finding is cheaper.

A Reading Protocol That Works I work the following protocol with recipients at award acceptance. Read the Notice of Award start to finish, then read it a second time, marking every obligation. Read the special terms and conditions and add them to the matrix one by one. Pull the standard terms and conditions from the agency's website, read them, and confirm they are the current version effective on the award date. Pull the program-specific guidance documents referenced in the Notice of Award and read them in full. Search the agency's policy directive page for any directives issued in the prior twenty-four months that may apply to the program. Open the OMB Compliance Supplement section for the program's CFDA number and read it to understand what the auditor will look at. Build the matrix from the union of everything read.

That protocol takes four to eight hours for a moderately complex award. It is the cheapest four to eight hours the recipient spends on the award. It is also the protocol most recipients skip.

Bridge to Chapter 4 Reading the award identifies the obligations the recipient carries directly. It also identifies the obligations the recipient flows down to sub-recipients under any sub-award. Sub-recipient monitoring is its own discipline, and it is one of the highest-volume sources of single audit findings on federal energy projects. The next chapter walks through how the pass-through entity discharges that obligation.

Sub-Recipient Monitoring as Pass-Through Discipline (2 CFR 200.331-333)

Sub-Recipient Monitoring as Pass-Through Discipline (2 CFR 200.331-333)

) A pass-through entity that issues a sub-award carries an obligation under 2 CFR 200.331 through 200.333 to monitor the sub-recipient's performance against federal requirements. That obligation does not transfer with the dollars. The dollars flow down. The accountability does not. When the sub-recipient produces a finding, the pass-through entity carries the finding back to the awarding agency. I have watched pass-through entities lose more federal money on sub-recipient findings than on their own direct administrative failures. The category is consistently the most expensive line on the post-award failure ledger.

The Distinction the Regulation Requires The first decision the pass-through entity makes is whether the relationship with the downstream party is a sub-award or a contractor procurement. The distinction matters and it is regulatory, not stylistic. Under 2 CFR 200.331, a sub-recipient is one that carries out a portion of the federal program itself, with responsibility for programmatic decision-making, eligibility determinations, or measurement of program performance. A contractor provides goods or services that support the recipient's project but does not carry out the federal program. The same downstream entity can be a sub-recipient on one award and a contractor on another, depending on what work it is doing.

The regulation lays out specific factors for the determination. Whether the entity determines who is eligible to receive federal assistance. Whether it has performance measured in relation to whether the program's objectives were met. Whether it has responsibility for programmatic decision-making. Whether it is responsible for adherence to program compliance requirements. Whether it uses the federal funds to carry out a program, as compared to providing goods or services for a program. A contractor relationship looks different on each of those factors.

The determination is documented in writing at the time the agreement is structured. Pass-through entities that have skipped the documentation step find themselves arguing the distinction during an audit, with the auditor having already classified the relationship one way and the entity arguing the other way. The argument is usually a loser. The documentation, if done at the structuring step, prevents the argument.

Required Information at the Time of Sub-Award When the pass-through entity issues a sub-award, 2 CFR 200.332(a) requires specific information to be communicated to the sub-recipient. The Federal Award Identification Number. The federal awarding agency. The CFDA number and name. The award name and date. The sub-award period of performance. The total

amount of federal funds obligated to the sub-recipient. The total amount of federal funds awarded to the pass through entity. The federal award project description. The names and contact information of relevant agency officials. The applicable indirect cost rate for the sub-recipient. Any requirements imposed by the pass through entity, including all general terms and conditions and any pass-through-specific terms.

That information block is mandatory. A sub-award that omits any of the elements produces an immediate compliance gap. I have reviewed sub-award files where the pass-through entity issued the sub-award under its own standard professional services template without updating the template to include the federal information block. Every sub-award issued under that template carried the same defect. Multiplying one omission across twenty sub-awards is how findings of high frequency and questioned costs are generated.

Risk Assessment Under 200.332(b) Before issuing the sub-award, the pass-through entity is required under 2 CFR 200.332(b) to evaluate each sub-recipient's risk of noncompliance. The risk assessment considers prior experience with the same or similar sub-awards, the results of previous audits, whether the sub-recipient has new personnel or new systems, and the extent and results of federal awarding agency monitoring. The risk assessment is documented and refreshed annually. The risk rating drives the intensity of monitoring across the period of performance.

Risk assessments in practice often default to a generic low-medium-high rating without underlying analysis. The analysis is what makes the rating defensible. A sub-recipient that has never received federal funding before is not low risk simply because no prior audit findings exist. The absence of prior audits is itself a risk factor. A sub-recipient that has received federal funding through other awards and whose single audit history shows prior findings against the compliance requirements relevant to this sub-award is high risk regardless of how good the relationship feels. The matrix captures the rating and the analysis behind it.

Monitoring Across the Period of Performance The pass-through entity's monitoring obligation under 2 CFR 200.332(d) is ongoing across the period of performance. The forms of monitoring include desk review of financial reports and performance reports, on site visits, sampling-based transaction testing, and review of audit reports. The monitoring intensity is calibrated to the risk rating. High-risk sub-recipients receive frequent and substantive monitoring including on-site reviews. Low-risk sub-recipients receive at least desk review of routine reports and periodic transaction sampling.

Monitoring activities are documented contemporaneously. The documentation includes what was reviewed, who reviewed it, when, what findings or observations resulted, and what corrective actions were taken by the sub-recipient. Verbal feedback to a sub-recipient that does not produce a written record is not monitoring for purposes of the regulation. The single audit looks at the written record. The conversation that did not get written down did not happen as far as the audit is concerned.

Issuing Management Decisions on Sub-Recipient Audit Findings When a sub-recipient's single audit produces findings, the pass-through entity is required under 2 CFR 200.332(d)(3) and 200.521 to issue a written management decision within six months of the audit acceptance date. The management decision states whether the pass-through entity concurs with the finding, what corrective action is required, and what consequences will follow if the action is not taken. Pass-through entities that have not built a workflow for tracking sub-recipient audit completion dates miss this deadline routinely. The miss itself becomes a finding against the pass-through entity at its own next single audit.

The workflow is not complicated. Track when each sub-recipient's fiscal year ends. Calculate the audit submission deadline at nine months from year-end under the Federal Audit Clearinghouse rules. Calendar the management decision deadline at six months from the audit acceptance date. Open each sub-recipient's audit report from the FAC when it is posted. Review the Schedule of Findings and Questioned Costs. Issue the management decisions on the awards that surface findings. File the management decisions in the pass through entity's records and in the matrix.

The Cost of Not Doing It The financial exposure on sub-recipient monitoring failure is not the sub-recipient's questioned cost. It is the pass-through entity's full federal share that flowed through the sub-recipient. When the agency determines that the pass-through entity did not adequately monitor the sub-recipient, the agency can disallow the entire pass-through amount and require repayment from the pass-through entity. The pass-through entity then pursues recovery from the sub-recipient through whatever contractual mechanisms exist. The recovery often does not equal the disallowance. The pass-through entity carries the difference.

I have watched a pass-through entity write off seven figures in this scenario. The sub-recipient was a community-based organization with limited capacity to repay. The pass-through entity was a regional public power authority. The award was a multi-million-dollar DOE program. The monitoring file consisted of two desk reviews and no on-site visits across an eighteen-month period. The auditor concluded the monitoring was inadequate. The agency concurred. The repayment obligation landed on the pass-through entity. The sub recipient absorbed what it could. The difference was a hard write-off that affected the authority's rate base.

Bridge to Chapter 5 Sub-recipient monitoring sits on top of the broader cost principle framework that governs every dollar charged to a federal award, whether the dollar flows directly through the recipient or flows down through a sub-recipient. The next chapter walks through what the cost principles actually require and where recipients most often misapply them.

Cost Principles Under 2 CFR 200 Subpart E: Allowability, Allocability, Reasonableness

Cost Principles Under 2 CFR 200 Subpart E: Allowability, Allocability, Reasonableness

Cost principles are the regulatory architecture under which every dollar charged to a federal award is evaluated. They sit at 2 CFR 200 Subpart E and they apply at the moment the cost is incurred, not at the moment the auditor asks about it. Recipients that approach cost principles as a documentation exercise after the fact will fail the documentation test routinely. Recipients that approach cost principles as an evaluation discipline at the point of incurrence will produce files that withstand any reasonable audit scrutiny.

The Allowability Tests Under 2 CFR 200.403, a cost is allowable when it satisfies a series of tests. The cost must be necessary and reasonable for the performance of the federal award. The cost must be allocable to the federal award. The cost must conform to the cost principles in Subpart E and to the terms and conditions of the federal award. The cost must be treated consistently with other costs incurred for the same purpose in like circumstances. The cost must be determined in accordance with generally accepted accounting principles. The cost must not be included as a cost or used to meet cost sharing or matching requirements of any other federally financed program. The cost must be adequately documented.

Each test stands alone. A cost that satisfies six of the seven tests but fails one is disallowed. I have watched audits surface disallowances on the documentation test alone, where the cost was clearly necessary, reasonable, allocable, and consistent, but the file did not contain enough evidence to prove those facts. The cost was correct. The file was incomplete. The agency disallowed it anyway because the regulation requires adequacy of documentation, not adequacy of intent.

Reasonableness as a Judgment Standard Under 2 CFR 200.404, a cost is reasonable if, in its nature and amount, it does not exceed that which would be incurred by a prudent person under the circumstances prevailing at the time the decision was made to incur the cost. The standard is the prudent person operating in the recipient's circumstances. It is not the cheapest available option. It is the option a careful manager spending the recipient's own money would have selected, considering quality, timeliness, supplier reliability, and total cost of ownership.

Reasonableness is the test most often litigated at audit because the standard is judgmental. The recipient defends reasonableness through documentation of the decision-making process. Why this vendor. Why this price. What alternatives were considered. What evaluation criteria applied. The defense rests on the documentation, not on the recipient's later recollection of why the decision made sense. The auditor reads

what is in the file. The auditor does not interview the project manager about what he remembers about a decision made eighteen months earlier.

Allocability and the Shared Cost Problem Under 2 CFR 200.405, a cost is allocable to a federal award if it is incurred specifically for the award, benefits both the award and other work and can be distributed in proportions that may be approximated using reasonable methods, or is necessary to the overall operation of the entity and is assignable to the award in accordance with the cost principles. The third category is where most allocability disputes surface. Shared costs that touch multiple funding sources require an allocation methodology that is documented, applied consistently, and defensible against scrutiny.

Common allocation methods include direct labor hours, square footage, machine hours, headcount, and unit measures specific to the function. Each method has applicability constraints. Allocating administrative overhead based on direct labor hours produces defensible results for personnel-intensive functions. Allocating the same overhead by headcount produces different and equally defensible results for staff intensive functions. The recipient selects a method, documents the selection rationale, applies the method consistently, and revisits the method periodically as the cost mix shifts.

Recipients that use multiple allocation methods across multiple cost pools without documenting the selection rationale produce allocability findings at audit. The fix is rarely about changing the methods. The fix is about documenting the methodology in a written cost allocation plan that the auditor can reference and that the recipient applies consistently.

Indirect Cost Rates and Negotiated Agreements Indirect costs are recovered through the recipient's negotiated indirect cost rate agreement under 2 CFR 200.414, through the ten percent de minimis rate available to certain entities that have not negotiated a rate, or through a cost allocation plan for certain entity types. The indirect cost recovery framework is one of the most technically complex areas in the Uniform Guidance and one of the most consequential financially. A recipient with a five hundred thousand dollar award and a thirty percent indirect cost rate is recovering one hundred fifty thousand dollars in indirect costs on that award. A recipient operating under the ten percent de minimis recovers fifty thousand. A recipient that has misapplied the indirect cost framework recovers neither and faces a finding for the recovery that was claimed inappropriately.

The cognizant agency for indirect cost negotiation depends on the recipient type and the funding portfolio. For state and local governments, the cognizant agency is determined by the largest dollar value of awards received. For nonprofits and institutions of higher education, similar rules apply. The negotiated rate agreement governs the entity's indirect cost recovery across all federal awards and must be referenced in every applicable cost calculation. Recipients that have a negotiated rate but do not reference it correctly on individual awards generate findings even though the rate itself is valid.

Selected Items of Cost 2 CFR 200 Subpart E contains specific guidance for over fifty enumerated items of cost. The selected items appear at 2 CFR 200.420 through 200.475. They include advertising and public relations, alcoholic beverages, alumni activities, bad debts, bonding costs, commencement and convocation costs, communication costs, compensation for personal services, conferences, contingency provisions, contributions and donations, defense and prosecution of criminal proceedings, depreciation, employee health and welfare costs, entertainment costs, equipment and other capital expenditures, exchange rates, fines penalties damages and other settlements, fundraising and investment management, gains and losses on disposition of assets, general costs of government, goods or services for personal use, idle facilities, insurance and indemnification, intellectual property, interest, lobbying, losses on other awards, maintenance and repair, materials and supplies, memberships subscriptions and professional activity, organization costs, pre-award costs, professional service costs, proposal costs, publication and printing, rearrangements and alterations, recruiting, relocation costs, rental, scholarships and student aid, selling and marketing, specialized service facilities, student activity, taxes, termination costs, training, travel, and trustees.

Each enumerated category carries specific rules. Some categories are allowable with conditions, some are allowable up to specified limits, some are unallowable as a matter of regulation. Recipients that charge costs in the enumerated categories without consulting the relevant section produce findings. The fix is reading the relevant section at the point of incurrence, not after the audit.

Time and Effort Reporting Under 2 CFR 200.430, charges to federal awards for personal services must be supported by records that accurately reflect the work performed. The records must be supported by a system of internal control that provides reasonable assurance the charges are accurate, allowable, and properly allocated. For employees working solely on a single federal award, periodic certifications signed by the employee or supervisor satisfy the requirement. For employees splitting time across multiple awards or between federal and non-federal work, personnel activity reports or equivalent documentation must reflect the after-the-fact distribution of actual activity.

Recipients that bill personnel costs based on budgeted distribution rather than actual time and effort generate findings. The fix is implementing a time and effort process that captures actual work, certifies it on an appropriate cadence, and reconciles it to the labor cost charges in the general ledger.

Bridge to Chapter 6 Cost principles govern the substantive evaluation of every charge. Procurement principles govern how the recipient selects vendors and contractors whose costs will later be charged. The next chapter walks through the procurement framework at 2 CFR 200.317-326 and the documentation discipline that protects every procurement against later scrutiny.

Procurement Under 2 CFR 200.317-326: Documentation as Defense

Procurement Under 2 CFR 200.317-326: Documentation as Defense

Procurement is the area where state and local recipients most frequently produce findings because the federal procurement framework is more prescriptive than most state and local frameworks. Recipients that have run procurement for decades under state law assume their existing process satisfies federal requirements. Often it does. Sometimes it does not. The differences are subtle enough that they survive a casual comparison and surface only when a federal auditor walks the file. The defense against procurement findings is documentation built into the procurement process, not assembled afterward.

The Standards Apply to All Procurements Under 2 CFR 200.317, states must use the same policies and procedures for federal procurements that they use for non-federal procurements, with limited additional federal requirements. Non-state recipients, including local governments, Indian tribes, institutions of higher education, and nonprofits, follow the federal procurement standards at 2 CFR 200.318 through 200.327 directly. The distinction matters because state recipients have more latitude than non-state recipients, but the federal cross-cutting requirements still apply to both.

The general procurement standards at 2 CFR 200.318 require recipients to maintain oversight to ensure contractors perform in accordance with their contracts, maintain written standards of conduct covering conflicts of interest, avoid acquisition of unnecessary or duplicative items, use value engineering clauses where appropriate, conduct procurements in a manner providing full and open competition, and document significant procurement history including the rationale for the method, the selection of contract type, the contractor selection or rejection, and the basis for the contract price.

The documentation requirement is the operational core. Procurements that have been conducted properly but documented inadequately fail at audit. Procurements that have been documented thoroughly but conducted poorly produce different findings about the underlying conduct. The thorough document at minimum allows the recipient to demonstrate what was done. The thin document allows the auditor to assume the worst.

Methods of Procurement Under 2 CFR 200.320, the recipient selects from five methods of procurement. Informal procurement under the micro-purchase threshold applies to acquisitions at or below the federal micro-purchase threshold, currently $10,000 unless the recipient has self-certified to a higher threshold under the conditions in 200.320(a)(1)(iv). Informal procurement under the small purchase threshold applies to acquisitions between

the micro-purchase threshold and the simplified acquisition threshold, currently $250,000. Sealed bid procurement is used for construction work under specified conditions. Competitive proposals procurement is used when sealed bidding is not appropriate, particularly for services. Noncompetitive procurement is permitted only under specified conditions including single source availability, public exigency, awarding agency authorization, and inadequate competition after solicitation.

Each method carries documentation expectations that align with the level of dollar exposure. Micro purchases require equitable distribution among qualified suppliers and reasonable price determinations. Small purchases require price or rate quotations from an adequate number of qualified sources. Sealed bids require formal advertisement, time for bid preparation, public opening, and award to the lowest responsive responsible bidder. Competitive proposals require formal advertisement, evaluation against published criteria, and award to the proposer whose proposal is most advantageous to the recipient. Noncompetitive procurement requires written documentation of the justification.

Recipients that select methods inconsistently with the dollar exposure produce findings. Recipients that select the correct method but document the selection rationale poorly produce different findings. The matrix carries the rationale for the method selected on every procurement above the micro-purchase threshold.

Sole Source and Noncompetitive Justification Noncompetitive procurement under 2 CFR 200.320(c) is permissible under one of four conditions. The acquisition is from a single source. The public exigency or emergency for the requirement will not permit a delay. The federal awarding agency or pass-through entity expressly authorizes a noncompetitive procurement. After solicitation of a number of sources, competition is determined inadequate. The justification under any of the four conditions must be documented in writing.

Recipients commonly invoke sole source for proprietary equipment, for incumbent vendor expertise on existing systems, and for specialized services where qualified providers are limited. Each invocation is defensible only if the documentation supports the claim. The sole source justification file should establish what was sought, what alternatives were investigated, why no alternative satisfied the requirement, and how the price was determined to be reasonable. Files that consist of a one-paragraph sole source memorandum signed by the project manager are not adequate. Files that include a documented market survey, vendor research, technical justification, and price analysis are adequate.

I have watched recipients lose disallowance arguments on sole source procurement at the documentation level. The procurement may have been entirely defensible on the merits. The file did not show the work. The auditor disallowed it.

Conflict of Interest Under 2 CFR 200.318(c), the recipient must maintain written standards of conduct covering conflicts of interest and governing the actions of its employees engaged in the selection, award, and administration of contracts. No employee, officer, or agent may participate in the selection, award, or administration of a contract supported by a federal award if a real or apparent conflict of interest would be involved. The standards must provide for disciplinary actions for violations.

Recipients that have inherited general conflict of interest policies from state or local frameworks should compare them against the federal language. Differences usually surface in disclosure procedures, in covered relationships, and in disciplinary mechanics. The compliance backbone includes a conflict of interest disclosure file maintained per procurement above the micro-purchase threshold, with disclosures from each selection committee member and from any employee with material involvement in the contract.

Cost or Price Analysis Under 2 CFR 200.324, the recipient must perform a cost or price analysis in connection with every procurement action in excess of the simplified acquisition threshold. The level of detail and the method of analysis depend on the facts surrounding the procurement, but at a minimum the recipient must make independent estimates before receiving bids or proposals. The estimate is documented before the bids are opened. The bid prices are compared against the estimate. Significant variances are investigated.

Recipients that document estimates after the fact, by writing down what the bid prices were and calling that the estimate, generate findings that the auditor will treat as evidence of weak internal control. The estimate is contemporaneous or it is not an estimate. The matrix flags every procurement above the simplified acquisition threshold and confirms the estimate documentation is in the file before the bid opening.

Contract Provisions Under 2 CFR 200.327 and Appendix II to Part 200, every contract above specified thresholds must include certain federal provisions. The required provisions vary with the type and value of the contract and include termination for cause and convenience, equal employment opportunity, Davis-Bacon and Copeland Act applicability for construction, Contract Work Hours and Safety Standards Act compliance, rights to inventions, Clean Air Act and Clean Water Act compliance, debarment and suspension, byrd anti-lobbying, and procurement of recovered materials.

Recipients that issue contracts under their standard templates without confirming the federal provisions are included produce findings on every contract issued. The fix is a federal contract addendum that incorporates the Appendix II provisions and is appended to every contract above the relevant thresholds. The addendum lives in the matrix. Every contract files the addendum signature with the contract itself.

Procurement File Construction A procurement file that satisfies audit scrutiny includes the procurement initiation request, the determination of method, the independent estimate, the solicitation document, the proof of advertisement or distribution, the responses received, the evaluation committee composition and conflict disclosures, the scoring or evaluation work papers, the selection memorandum, the award notification, the contract with required federal provisions, the cost or price analysis, the contractor's debarment certification verification through SAM.gov, the documentation of buy-American or BABA applicability and compliance if applicable, the documentation of prevailing wage applicability and compliance if applicable, and any modifications during the contract's life.

The list is long. It is also predictable. A standard procurement file template carrying placeholders for each required element and used on every procurement reduces the documentation burden by an order of magnitude and produces files that survive audit on the first review. The matrix indexes every procurement file by procurement identifier and confirms each element is present before the procurement is closed in the file system.

Bridge to Chapter 7 Cost principles and procurement principles govern what gets spent and how. Reporting principles govern what gets communicated to the awarding agency about that spending and the project progress underneath it. The next chapter walks through the reporting cadence that every federal energy award carries.

The Reporting Cadence: FFR/SF-425, Performance, ASAP, Program-Specific

The Reporting Cadence: FFR/SF-425, Performance, ASAP, Program-Specific

Federal energy awards run on a reporting cadence that begins at the first quarter after award acceptance and runs through closeout. The reports are not optional. They are not negotiable in timing. They are not subject to the recipient's own preferred fiscal calendar. They run on the federal cadence and the recipient adjusts. Recipients that miss reporting deadlines generate findings at audit and erode the credibility of the recipient's overall compliance posture. Recipients that submit reports on time but with numbers that do not tie back to the general ledger generate different and worse findings.

The Federal Financial Report (SF-425) The Federal Financial Report on Standard Form 425 is the primary financial reporting instrument across federal grants. It captures cumulative federal expenditures, federal share of expenditures, recipient share, program income earned, indirect costs claimed, and federal cash received. The form is filed quarterly for most awards, with the period of performance final report due within ninety days of the period of performance end date under 2 CFR 200.344, unless the awarding agency specifies a different deadline.

The numbers on the SF-425 must reconcile to the recipient's general ledger. The auditor will trace the cumulative expenditures from the most recent SF-425 back through the underlying transactions. Recipients that have submitted SF-425s based on estimates or based on operational reporting that does not align with the general ledger fail this reconciliation test. The fix is a formal closing process at the end of each reporting period that reconciles the proposed SF-425 to the general ledger before the form is submitted. The matrix carries the SF-425 submission cadence and links to the reconciliation work papers for every period.

The accrual basis question matters. The Uniform Guidance permits the SF-425 to be filed on either a cash basis or an accrual basis, but the recipient must use the same basis consistently across the period of performance and must report on the basis the agency specifies if the agency specifies one. Inconsistent basis between periods produces reconciliation problems that compound through the period of performance.

Performance Reporting Performance reports are program-specific and capture progress against the milestones, deliverables, and objectives stated in the approved project narrative. The frequency, format, and substantive content vary by program. DOE EERE awards typically require quarterly progress reports against milestones, with annual progress reports that aggregate the four quarterly submissions. EPA awards typically require semiannual or annual reports. USDA Rural Development awards carry their own cadence.

Performance reports are the artifact through which the awarding agency tracks whether the project is delivering what the award purchased. Performance reports that downplay slippage, omit known issues, or report milestones as complete when they are not generate findings when the auditor compares the report to the underlying evidence. Performance reports that report slippage transparently, identify root causes, and document mitigation actions build credibility with the program officer and produce defensible records.

The performance report submission is the moment when the project's institutional candor is tested. Recipients that have built a habit of reporting truthfully through the period of performance carry that habit through to closeout. Recipients that have built a habit of optimistic reporting generate cumulative gaps that surface at the closeout review.

ASAP and Drawdown Discipline Federal awards that draw through the Automated Standard Application for Payments system carry drawdown discipline that the recipient operates daily or weekly during active spending periods. Drawdowns must be supported by immediate cash needs. Under 2 CFR 200.305, advance payments must be limited to the minimum amounts needed and timed to be in accordance with the actual immediate cash requirements in carrying out the program or project. The Cash Management Improvement Act applies to states and provides specific timing requirements.

Recipients that draw federal funds in advance of need and hold them in interest-bearing accounts violate the immediate cash needs principle. The fix is a drawdown protocol that aligns drawdowns to disbursement dates rather than to the recipient's general cash management convenience. The matrix carries the drawdown protocol and the documentation that confirms timing alignment.

The interest earnings issue compounds the timing issue. Under 2 CFR 200.305(b)(9), interest earnings on advance payments must be remitted at least annually to the Department of Health and Human Services Payment Management System if total earnings exceed five hundred dollars per year, with limited exceptions. Recipients that have not built the interest earnings tracking and remittance workflow generate findings at audit.

Program-Specific Reporting Many federal energy awards carry program-specific reporting obligations that exist in addition to the financial and performance reports. DOE community benefits plan implementation reporting. DOE energy justice reporting. DOE diversity equity inclusion accessibility reporting. EPA Greenhouse Gas Reduction Fund private capital leverage reporting. USDA Rural Development project-specific milestones tied to disbursement triggers. Each program-specific obligation is enumerated in the program guidance and incorporated by reference into the award.

Program-specific reports often carry their own templates, their own submission portals, and their own review cycles. The matrix captures every program-specific reporting obligation and assigns owner, frequency, and evidence location. The recipient that has not built the matrix at this granularity will miss obligations that the award documents reference indirectly through program guidance and that the recipient never explicitly cataloged.

Reconciling Reports to the General Ledger The single audit firm walks every reporting submission against the general ledger. The SF-425 cumulative expenditures must match. The drawdowns must reconcile to ASAP records. The cost share contributions must trace through the recipient's books. The program income, if any, must reconcile to revenue records. The performance report milestones must reconcile to the underlying procurement files, contracts, and deliverables.

Recipients that have not built the reconciliation discipline submit reports that look right to the program officer at the time and surface problems at the single audit. The fix is a closing protocol per reporting period that produces the reconciliation work papers contemporaneously and files them with the report submission. The matrix references the work papers per period.

Bridge to Chapter 8 Financial and performance reporting capture the dollar and milestone dimensions of the award. Property and equipment management captures the asset dimension. Federal awards that fund equipment carry obligations that extend beyond the period of performance and that recipients underestimate routinely. The next chapter walks through what 2 CFR 200.310 through 200.316 actually require.

Property and Equipment Management Under 2 CFR 200.310-316

Property and Equipment Management Under 2 CFR 200.310-316

Federal awards that fund equipment, real property, or supplies carry property management obligations that survive the period of performance and that affect the recipient's books, the recipient's insurance posture, and the recipient's eventual disposition decisions. Recipients that treat equipment purchased with federal funds the same way they treat equipment purchased with their own funds will fail the property management requirements at audit and will face disposition disputes years after the award has closed.

Title and Use Conditions Under 2 CFR 200.313, title to equipment acquired under a federal award vests upon acquisition in the non federal entity, subject to the conditions in the regulation. The recipient holds title but the federal interest persists. The conditions include use of the equipment for the purposes of the federal award until that work is completed, use of the equipment on other projects supported by the federal government to the extent the original use is no longer needed, and disposition under specified procedures when the equipment is no longer needed for the original or any federally supported activity.

The federal interest persistence means the recipient cannot sell, transfer, or otherwise dispose of federally funded equipment unilaterally during the period when the federal interest applies. The recipient must follow the disposition procedures in the regulation and obtain awarding agency approval where required. Recipients that have disposed of equipment without following the disposition process generate findings that can convert to disallowed cost obligations equal to the federal share of the equipment's fair market value at disposition.

Property Records and Physical Inventory Under 2 CFR 200.313(d)(1), the recipient must maintain property records that include a description of the property, a serial number or other identification number, the source of funding for the property including the Federal Award Identification Number, who holds title, the acquisition date, the cost, the percentage of federal participation, the location, the use and condition of the property, and any ultimate disposition data including the date of disposal and sale price.

Under 2 CFR 200.313(d)(2), a physical inventory of the property must be taken and the results reconciled with the property records at least once every two years. The reconciliation is documented. Discrepancies are investigated. Lost, damaged, or stolen equipment is reported under 2 CFR 200.313(d)(3).

Recipients that operate property registers in their general fixed asset systems often discover at audit that the federal-specific information required by 200.313(d)(1) is not captured. The fixed asset system tracks acquisition cost, location, and depreciation. It does not necessarily track federal source, FAIN, percentage of federal participation, or federal use conditions. The fix is a federal property module either inside the asset system or as a parallel register, with reconciliation between the two and with biennial physical inventory documented in the matrix.

Equipment Threshold and Capitalization Equipment is defined under 2 CFR 200.1 as tangible personal property having a useful life of more than one year and a per-unit acquisition cost of $5,000 or more. Items below the threshold are treated as supplies under 2 CFR 200.314. Items at or above the threshold are equipment for purposes of the federal property management framework.

Recipients commonly use their own capitalization thresholds, which may be higher or lower than the federal $5,000 threshold. The federal definition controls for purposes of federal property management. An item that the recipient does not capitalize on its own books because it falls below the recipient's local capitalization threshold may still be federal equipment under the federal definition. The matrix tracks federal equipment under the federal definition regardless of the recipient's capitalization treatment.

Real Property Under 2 CFR 200.311, real property acquired or improved with federal funds carries title vested in the recipient subject to use conditions. Real property must be used for the original authorized purpose. When no longer needed for that purpose, disposition procedures apply. The federal share of the property's fair market value may be due to the awarding agency at disposition.

Real property obligations are commonly underestimated because they outlast the period of performance. A recipient that improved a facility with federal funds five years ago and is now considering converting the facility to another use must work the federal disposition framework before the conversion. Recipients that have skipped that step have generated retroactive obligations.

Supplies Under 2 CFR 200.314, supplies are tangible personal property other than equipment, with a unit acquisition cost below the equipment threshold. Supplies acquired with federal funds and not needed at the conclusion of the federal award have specific disposition treatment. If the aggregate fair market value of unused supplies exceeds $5,000, the recipient may retain or sell them but must compensate the federal awarding agency for its share. Smaller balances may be retained without compensation.

The supplies provision is often missed because supplies do not carry the same visibility as equipment. The fix is a closeout supplies inventory that establishes the unused balance, calculates the fair market value, determines whether the disposition threshold applies, and documents the disposition or compensation as part of the closeout package.

Insurance Coverage Under 2 CFR 200.310, the recipient must provide the equivalent insurance coverage for real property and equipment acquired or improved with federal funds that the recipient provides for property the recipient owns. The federal interest is not a separate insured interest in most cases, but the property itself must be insured against the same risks at the same levels. Recipients that have not added federally funded equipment to the insurance schedule generate findings at audit even when no loss has occurred.

Disposition When the Award Closes or Equipment Is No Longer Needed Under 2 CFR 200.313(e), when equipment originally acquired with federal funds is no longer needed for the original project or program or for other activities currently or previously supported by a federal awarding agency, disposition procedures apply based on the current per-unit fair market value. Items with a current per-unit fair market value of $5,000 or less may be retained, sold, or otherwise disposed of with no further obligation to the federal awarding agency. Items above $5,000 require options of retention, sale with compensation to the federal awarding agency, or transfer to the federal awarding agency or to another federally supported project.

The disposition workflow requires advance communication with the awarding agency in many cases. Recipients that have skipped the communication step have generated findings even when the disposition was otherwise defensible. The matrix carries the disposition framework and prompts the workflow at the appropriate triggers.

Bridge to Chapter 9 Property management is one of the substantive compliance requirements that the single audit tests directly. The next chapter walks through the broader single audit posture under 2 CFR 200 Subpart F, from the Schedule of Expenditures of Federal Awards through findings resolution.

Single Audit Posture Under Subpart F: From SEFA Through Findings Resolution

Single Audit Posture Under Subpart F: From SEFA Through Findings Resolution

Recipients of federal awards that expend $1,000,000 or more in federal awards in a fiscal year are subject to the single audit requirements under 2 CFR 200 Subpart F, as updated in 2024. The single audit is not an audit the recipient hires for itself in the way the recipient hires its annual financial statement audit. The single audit is a regulatory audit conducted under specific federal standards that the recipient is required to procure. The framework is unforgiving when the recipient treats it casually.

Threshold and Coverage The single audit threshold sits at $1,000,000 in federal expenditures, expanded from $750,000 effective for fiscal years beginning on or after October 1, 2024 under the 2024 Uniform Guidance revisions. Federal expenditures aggregate across all federal awards the entity received and includes pass-through awards. The expenditure is recognized when the activity giving rise to the expenditure occurs, generally when the cost is incurred or the loan is disbursed.

Recipients that approach the single audit threshold within a fiscal year should evaluate whether the threshold will be crossed early enough to procure the audit firm at appropriate quality. Single audit firms with experience in federal grant audits, particularly in the energy sector, are not always available on short timelines. The recipient that scrambles to procure an audit firm in the last quarter of the audit year often ends up with a firm whose experience is shallow and whose audit work creates as many problems as it surfaces.

The Schedule of Expenditures of Federal Awards The Schedule of Expenditures of Federal Awards, the SEFA, is the recipient's listing of all federal awards expended in the fiscal year. The SEFA is the recipient's responsibility, not the auditor's. The auditor tests the SEFA's completeness and accuracy but does not produce it. SEFAs that omit awards, mistranslate CFDA or Assistance Listing numbers, or fail to distinguish between direct awards and pass-through awards generate findings.

The SEFA requires the Assistance Listing number, the federal award identification number, the federal awarding agency, the pass-through entity if applicable and any identifying number assigned by the pass through entity, and the total amount provided to subrecipients from each federal program. Major programs are determined from the SEFA, and the SEFA accuracy drives the major program determination. A SEFA that misstates the federal expenditures on a program can cause the auditor to test the wrong programs as major.

The recipient builds the SEFA from internal accounting records and from confirmations with awarding agencies and pass-through entities. The build process should be a controlled exercise documented contemporaneously, not a year-end reconstruction. The matrix carries the SEFA build protocol and references the supporting reconciliation work papers.

Major Program Selection Under 2 CFR 200.518, the auditor selects major programs using a risk-based approach. Type A programs, the larger programs by federal expenditures, are subject to a presumption of major program designation unless the auditor concludes the program is low risk under specific criteria. Type B programs, the smaller programs, are tested as major only if the auditor identifies risk that warrants major designation.

The recipient does not select major programs. The auditor does. But the recipient has visibility into the likely major program designation in advance and can prepare accordingly. The likely major programs are the largest dollar programs that have not been audited as major in the prior two audit cycles, and the smaller programs with known risk factors. The matrix flags the likely major programs and confirms the supporting evidence is ready before the audit fieldwork begins.

Internal Controls Testing The single audit tests internal controls over compliance with each major program's applicable compliance requirements. The auditor evaluates the design and operation of the recipient's internal controls and tests their effectiveness through samples. Internal control deficiencies are classified as control deficiencies, significant deficiencies, or material weaknesses based on the magnitude and likelihood of the resulting misstatement.

The recipient that has operated the compliance backbone with discipline carries internal controls that the auditor can test efficiently. The matrix is itself an internal control. Documented reviews, owner assignments, evidence locations, and review dates are the internal control artifacts the auditor samples. Recipients that have not operated the backbone present the auditor with controls that exist on paper but lack operational evidence. The classification of deficiencies tends to escalate in those situations.

Compliance Requirements Testing For each major program, the auditor tests the applicable compliance requirements identified in the OMB Compliance Supplement for that program. The applicable requirements are drawn from the fourteen compliance requirements enumerated in the Compliance Supplement: activities allowed or unallowed, allowable costs/cost principles, cash management, eligibility, equipment and real property management, matching/level of effort/earmarking, period of performance, procurement and suspension and debarment, program income, reporting, subrecipient monitoring, and special tests and provisions specific to the program.

The Compliance Supplement specifies, for each program, which of the requirements apply and what testing the auditor must conduct. The matrix incorporates the applicable requirements per major program and tracks the supporting evidence against the auditor's anticipated test set.

The Schedule of Findings and Questioned Costs Findings that surface in the single audit are reported in the Schedule of Findings and Questioned Costs. Each finding includes the specific federal program affected, the specific compliance requirement at issue, the criteria, the condition, the cause, the effect, the questioned costs if quantifiable, the context, the recommendation, and the views of responsible officials. The recipient develops a corrective action plan for each finding that addresses the criteria, the responsible person, the planned actions, and the anticipated completion date.

Findings classified as material weaknesses or significant deficiencies in internal control or as material noncompliance attract heightened attention from the awarding agency. Findings with questioned costs above $25,000 are reported at the federal level and trigger agency-level resolution. The recipient's posture in addressing findings, the timeliness of corrective action implementation, and the substantive quality of the corrective action plan all affect whether the recipient is designated high-risk under 2 CFR 200.208 for future awards.

Findings Resolution Under 2 CFR 200.521, the awarding agency or pass-through entity issues a management decision on each finding within six months after receipt of the audit report. The management decision states whether the agency concurs with the finding, what corrective action is required, and the consequences of failure to take the action. The recipient implements the corrective action and provides evidence of completion. The agency closes the finding when the corrective action is verified.

Recipients that treat findings resolution as a paperwork exercise generate findings that remain open across multiple audit cycles. Open findings compound. Each subsequent audit retests the same area and surfaces either the closure evidence or the continued deficiency. Recipients that close findings substantively the first time avoid the compounding pattern.

Bridge to Chapter 10 The single audit captures the recipient's performance against compliance requirements during the period of performance. Closeout captures the recipient's performance at the end of the period of performance and produces the final administrative record. The next chapter walks through what closeout actually requires under 2 CFR 200.344.

Closeout Discipline: What "Closing an Award" Actually Means

Closeout Discipline: What "Closing an Award" Actually Means

lly Means Closeout is the process by which the federal awarding agency determines that all applicable administrative actions and required work of the federal award have been completed. Under 2 CFR 200.344, the recipient submits all financial, performance, and other reports required by the terms and conditions of the federal award within 120 calendar days after the end date of the period of performance. The awarding agency uses the closeout submissions to verify completion. Closeout is not a paperwork step the recipient can defer. The closeout file is the final administrative record on the award and it is the artifact the agency uses to determine whether disallowed costs remain, whether equipment disposition has been completed, whether sub-recipient findings have been resolved, and whether the recipient's overall performance posture should affect future awards.

The Closeout Timeline The 120-day closeout deadline begins at the period of performance end date. The recipient submits the final SF-425, the final performance report, the equipment and property closeout documentation, the program income reconciliation, the cost share reconciliation, the contractor and sub-recipient final reports, and any program-specific final reports during that window. The awarding agency reviews the submissions, identifies any deficiencies, and either accepts the closeout or extends the resolution period to address deficiencies.

Recipients that have operated the matrix through the period of performance walk into closeout with most of the artifacts already assembled. Recipients that have not operated the matrix walk into closeout under reconstruction pressure. The 120 days is rarely sufficient to reconstruct three to seven years of administrative records. Reconstruction pressure produces gaps. Gaps produce findings at the closeout review. Findings at closeout can convert into agency-level disallowance determinations that the recipient now appeals or repays.

The Final Financial Reconciliation The final SF-425 must reconcile to the general ledger across the full period of performance. Cumulative federal expenditures, cumulative recipient cost share, cumulative program income, cumulative drawdowns, and final balance must all tie. Recipients that have submitted quarterly SF-425s with minor reconciliation discrepancies will find those discrepancies compound by the final reporting period. The fix is a final closing protocol that produces a complete reconciliation, traces variances to specific transactions, and corrects the cumulative figures before the final SF-425 is submitted.

The final reconciliation produces a federal balance owed to the recipient or owed by the recipient to the agency. Recipients with drawdowns in excess of allowable expenditures owe the difference back. Recipients with allowable expenditures in excess of drawdowns may draw the residual subject to award conditions. The reconciliation produces the dollar figure that closes the financial chapter on the award.

Equipment and Property Closeout The closeout package includes the final equipment and property inventory, the disposition documentation for any equipment no longer needed for the federal purpose, and the per-unit fair market valuations supporting the disposition decisions. Equipment retained by the recipient for continued use on federally supported activities is documented. Equipment sold or otherwise disposed of with compensation due to the federal awarding agency is documented and the compensation is remitted.

Recipients that have skipped the equipment management discipline through the period of performance face closeout reconstruction. The reconstruction is harder than the contemporaneous discipline by a substantial margin because items have moved, conditions have changed, original documentation may not survive, and valuations are dated. The matrix that has tracked equipment throughout the period of performance produces the closeout inventory from the working register.

Sub-Recipient Closeout Each sub-award must close before the prime award can close. Sub-recipient closeouts produce the same artifacts at the sub-award level: final financial reports, final performance reports, equipment disposition, and findings resolution. The pass-through entity reviews each sub-recipient closeout package, issues management decisions on any open findings, and ensures the sub-award is properly closed before incorporating the sub recipient information into the prime award closeout.

Sub-recipient closeout delays cascade to the prime award. A pass-through entity that has not enforced sub recipient closeout deadlines may find the prime award closeout delayed by the slowest sub-recipient. The matrix tracks each sub-award closeout status and prompts pass-through action when sub-recipient submissions lag.

Open Findings at Closeout Findings that remain open at the time of closeout do not necessarily prevent closeout, but they must be tracked through resolution. The awarding agency may accept the closeout subject to continuing findings resolution. The recipient's obligation to complete corrective action survives closeout. The corrective action evidence is filed in the same federal record system that supported the audit and the period of performance documentation.

Recipients that have resolved findings substantively during the period of performance walk into closeout with a clean schedule. Recipients with open findings carry them into the post-closeout period and continue to manage them until each is closed by the agency or pass-through entity.

The Closeout Certification The recipient certifies the final closeout submissions. The certification carries the same false claims exposure as any other federal certification. Recipients that have certified figures or representations that cannot be substantiated have created exposure under the False Claims Act and the federal program statutes. The closeout certification is signed by an authorized representative of the recipient. The authorized representative reads the submissions, understands the underlying support, and certifies with the same diligence applied to the recipient's annual audited financial statement signature.

Recipients that have built the matrix and operated it through the period of performance produce closeout submissions the authorized representative can certify with confidence. Recipients that have not built the matrix produce closeout submissions the authorized representative either signs without adequate review or refuses to sign until additional verification is performed. The latter scenario delays closeout and surfaces the matrix gap at the worst possible moment.

Post-Closeout Obligations Closeout does not end every obligation. Record retention under 2 CFR 200.334 generally requires records to be retained for three years from the date of submission of the final expenditure report, with specific exceptions for litigation, claims, audit, or extended retention required by program-specific rules. Equipment use restrictions may continue beyond closeout if the equipment retains federal interest. Audit obligations may continue if the closeout occurs within a fiscal year that subsequently exceeds the single audit threshold.

The matrix carries post-closeout obligations forward into a maintenance register that the entity reviews annually to confirm continued compliance with record retention, equipment use, and any other obligations that survive closeout.

Bridge to Chapter 11 The previous ten chapters describe the components of the compliance backbone. The final chapter addresses the meta-question of how to build the backbone concurrently with project execution rather than as a parallel exercise that competes with execution for resources.

Building the Backbone Concurrent With Execution

Building the Backbone Concurrent With Execution

The compliance backbone fails when it is treated as an overlay on the project rather than as an integrated dimension of the project's execution. Recipients that staff a grants administrator on the project from day one and embed the matrix into the project management cadence carry the backbone through execution without friction. Recipients that try to build the backbone in parallel, with the project team running ahead and the compliance team running behind, generate continuous gap-closure work that never quite catches up. The integrated approach is cheaper and more durable. It is also less common than it should be.

Staffing the Backbone The compliance backbone requires named staff capacity. For a single federal energy award of moderate complexity, the backbone runs on roughly 0.25 to 0.5 full-time equivalent of dedicated grants administration time, with additional time from finance, procurement, project management, and legal as transactions occur. For an entity carrying multiple federal awards simultaneously, the cumulative load is higher than the sum of individual award loads because the cross-award disciplines amplify. A single SAM.gov registration. A single set of internal controls. A single SEFA per fiscal year. A single set of indirect cost negotiations.

Entities that try to run federal awards on the residual capacity of staff whose primary roles sit elsewhere produce inconsistent backbone operation. The staff member runs the backbone on Tuesdays and Thursdays when other priorities permit. The Tuesday and Thursday work is competent but discontinuous. The discontinuity produces gaps the staff member would have closed if the work had been continuous. The fix is named staffing with named hours, even if the named hours are fractional, applied consistently against a calendar.

Integrating With Project Management The matrix should be visible in the project management cadence. The weekly project meeting includes a standing item on compliance status. The status item walks through any obligations due in the upcoming two weeks, any obligations recently closed, and any obligations at risk. The project manager and the grants administrator review the items together. Issues surface in the meeting rather than at the audit.

Recipients that have integrated this way report the practice as the single most useful change they made post award. The project team that previously treated compliance as an external imposition starts seeing the obligations as part of the project plan. The grants administrator that previously chased the project team for inputs starts receiving the inputs as part of normal project workflow.

Calendaring Across the Period of Performance The matrix should drive a calendar that captures every obligation deadline across the period of performance. The calendar includes reporting deadlines, audit milestones, sub-recipient monitoring milestones, equipment inventory dates, and closeout milestones. The calendar is maintained centrally and synchronized with the responsible owners. Deadlines do not surprise the entity because the calendar surfaces them well in advance.

The calendar also captures contingent deadlines that activate on specific triggers. Sub-recipient management decision deadlines activate on audit acceptance dates. Closeout submission deadlines activate on period of performance end dates. Property disposition deadlines activate on disposition decisions. The matrix maintains the triggers and the calendar reflects them.

Quarterly Backbone Reviews The matrix is reviewed quarterly at a level above day-to-day operation. The quarterly review confirms the matrix is current, the evidence locations are accurate, the owners are unchanged or properly transitioned, the review dates are within tolerance, and the risk ratings reflect current conditions. The quarterly review is documented and the documentation lives in the matrix itself.

The quarterly review is also when the entity asks the strategic questions. Is the staffing adequate. Are the controls operating effectively. Are sub-recipients performing within risk tolerances. Is the financial reconciliation tracking. Is the matrix surfacing issues at the right pace. The questions are uncomfortable when the answer is no. They are more uncomfortable when the audit notice lands and the entity has not asked them.

Cross-Award Disciplines Entities that hold multiple federal awards build cross-award disciplines that operate at the entity level rather than the award level. A single SAM.gov registration monitored by a named administrator. A single indirect cost rate agreement applied consistently across awards. A single SEFA per fiscal year built from a consolidated federal expenditure register. A single single-audit firm engagement that audits all federal awards as a unified scope. A single property management register that tracks federally funded equipment regardless of which award funded each piece.

The cross-award disciplines reduce the per-award administrative load and improve consistency. They also surface issues earlier because the consolidated views show patterns that per-award views obscure. An entity that runs five awards as five independent administrations carries five times the per-award load. An entity that runs five awards on a consolidated backbone carries roughly two to three times the per-award load.

Internal Audit and Continuous Improvement The backbone benefits from periodic internal audit independent of the day-to-day operators. The internal audit reviews the matrix, samples evidence, tests controls, and produces recommendations. The recommendations feed back into matrix improvements, training, and process refinements. Entities that have built this loop find that the single audit produces fewer findings each cycle because internal audit has already surfaced and addressed the issues the single audit would have flagged.

Entities without internal audit capacity can substitute periodic external review at a smaller scope and frequency. Even an annual review by an external practitioner familiar with the Uniform Guidance produces useful corrections at modest cost. The cost is cheaper than the cost of finding the issues at single audit.

The Recipient That Does This Well I have advised recipients that operate the compliance backbone with discipline. They share several characteristics. The grants administrator is a named person with adequate hours and adequate authority. The matrix is a living document referenced at every project meeting. The project manager treats compliance obligations as project tasks rather than as administrative overhead. The financial reconciliation runs contemporaneously with reporting submissions, not retroactively. Sub-recipients are monitored substantively, not nominally. Internal controls are operated, not merely documented. The annual single audit produces clean opinions or minor findings rather than material weaknesses. Closeout runs on time and on schedule.

Those characteristics are not exotic. They are the characteristics of any operationally disciplined entity, applied to a federal funding context that demands the discipline. Entities that have built this discipline can carry larger federal portfolios with less administrative friction than entities that have not. They also tend to win subsequent awards at higher rates because their administrative track record becomes a competitive asset.

Closing the Loop The compliance backbone is buildable. The Uniform Guidance is publicly available. The Compliance Supplements are publicly available. The agency policy directives are publicly available. The matrix template is standard. The reporting cadence is fixed. The procurement framework is documented. The cost principles are enumerated. None of the backbone elements are proprietary or secret. What is rare is the discipline to operate them consistently from day one of the period of performance through the final closeout submission.

The recipient that wants to operate at this level can. The recipient that hires Energy Compliance, Inc. for a Post-Award Compliance Administration scope gets the operational support that runs the backbone alongside the recipient's own team. Either way, the structure below the surface is the same. The work either gets done well or gets done badly. The post-award failure pattern shows that doing it badly is more expensive than doing it well.

Closing Note Most federally funded energy projects do not fail at the award decision. They fail in the months and years after. The administrative spine has to be built on purpose. The Compliance Obligation Matrix is the working artifact that makes that spine operational. The chapters above are the substantive content the matrix translates into action. Every recipient that has carried a federal energy award through to clean closeout has operated something resembling the structure described here, whether they called it a compliance backbone or not. The recipients that fail at closeout are the ones who never built it.

If this reference surfaced gaps you cannot close in time, the next step is a working conversation. Not a sales pitch. The engagement that follows is an exercise in closing the gaps with you, with the same backbone described here as the working artifact. The reference and the engagement are built on identical substance. The difference is who carries the workload.

Rob Smith, Founder, Energy Compliance, Inc.