In infrastructure contracting, we spend considerable time discussing supplier outreach, participation goals, and opportunities for small and diverse businesses. We measure the number of firms engaged, contracts awarded, and dollars committed. These are important indicators of progress, and they deserve attention.
But there is another side of compliance that I believe we need to spend more time talking about.
What happens when the project is complete, the contractors have been paid, and an auditor comes back two or three years later asking for the documentation supporting everything that was reported?
Can the project team verify that subcontractors performed the work credited to them? Can it reconcile reported participation with actual payments? Can it produce the records supporting payroll certifications, subcontractor changes, and other decisions made during construction?
These are reasonable questions, but the answers are not always as straightforward as we might expect.
Having worked on complex infrastructure projects, I’ve seen how much information is generated and how many people are involved in managing contractual requirements. Procurement teams, construction managers, compliance personnel, finance departments, and subcontractors all contribute to the process. Even with experienced teams and established procedures, information can become fragmented, responsibilities can become unclear, and issues can remain unresolved longer than anyone intended.
That is why I believe we need to look beyond compliance reporting and pay more attention to compliance management.
When the Work Is Done, the Records Still Matter
A federal audit involving a global consulting firm offers an interesting example.
The firm had performed work on an international government-funded program when auditors reviewed its contract expenditures. Some original records had been destroyed or misplaced following a building collapse and related problems at an outside document-storage facility.
The audit identified approximately $328,000 in costs that could not be adequately supported and recommended that the firm provide the documentation or return the questioned amount.
This was not a finding that the firm had intentionally misrepresented its work, nor does the published audit establish that it ultimately repaid the money. The issue was whether the organization could produce sufficient records to substantiate its expenditures.
What I find particularly relevant is that the documentation problem involved a third-party storage provider. The firm had relied on an established process, but the available safeguards were not sufficient to protect the information when something unexpected happened.
The firm subsequently reported implementing electronic document-retention procedures to strengthen its controls.
It’s a useful reminder that documentation is not simply about collecting paperwork. It’s about ensuring that critical records are accurate, accessible, and preserved for as long as they may be needed.
And this is not unique to financial records. The same principle applies to supplier participation, workforce compliance, subcontractor payments, and the many other requirements associated with major infrastructure projects.
Reporting Participation Is Not the Same as Verifying It
Consider how supplier participation is managed on a large infrastructure project.
A contractor may have an approved participation plan, executed subcontracts, current certification records, and monthly utilization reports. From a reporting perspective, everything may appear to be in order.
But what happens if the payments reported do not reconcile with the underlying records? What if a subcontractor’s scope changes and the participation plan is not updated? Or what if the documentation needed to verify the work performed is incomplete?
None of these situations necessarily means someone has intentionally done something wrong. They may simply indicate that a process needs attention or that information has not been properly reconciled.
The important question is whether the project has a system for identifying and resolving those issues.
For organizations managing supplier participation commitments, compliance involves understanding not only which firms have been awarded contracts, but whether the work is being performed as represented, whether payments are properly documented, and whether changes are addressed in accordance with applicable requirements.
This becomes more challenging as projects grow in size and complexity, particularly when multiple contractors and subcontractors are reporting information through different systems.
The objective should not be to question everyone’s work or create additional administrative burdens. It should be to establish reasonable controls that allow project teams to identify discrepancies, ask questions, and resolve issues while the information is still readily available.
Where Compliance Gaps Often Begin
In my experience, many compliance challenges are less about a lack of effort and more about the way information moves through an organization.
A subcontractor submits updated documentation, but the information doesn’t reach everyone responsible for reviewing it. A participation commitment changes, but the supporting records are not updated. A payment discrepancy is identified, but responsibility for resolving it is unclear. A project manager leaves, and the rationale for an earlier decision becomes difficult to reconstruct.
These are situations that can occur in almost any organization.
Individually, they may seem like manageable administrative issues. Over the life of a large project, however, they can create gaps between what has been reported and what the organization can actually substantiate.
This is where follow-through and quality control become essential.
It is not enough to establish a compliance process at the beginning of a project. Someone must be responsible for ensuring that the process is followed, that exceptions are reviewed, and that outstanding issues are resolved.
The strongest compliance systems don’t simply collect information. They help people recognize when something requires attention and provide a clear process for addressing it.
Why Compliance Deserves Greater Executive Visibility
One of the challenges I see in the marketplace is that supplier participation and compliance are sometimes managed as separate activities.
Outreach teams focus on identifying and engaging qualified businesses. Procurement teams focus on contract awards. Project managers focus on delivery, while compliance teams prepare reports and respond to documentation requests.
Each function has an important role, but the quality of the overall compliance process depends on how well those functions work together.
For example, an executive dashboard may show that a project is meeting its participation goals. That’s useful information, but it doesn’t necessarily tell leadership whether reported payments have been verified, whether subcontractor documentation is current, or whether outstanding compliance issues have been resolved.
I believe these questions deserve greater visibility.
Executives don’t need to review every invoice, payroll record, or subcontractor certification. They do need confidence that appropriate controls are in place, that the information being reported is reliable, and that someone is accountable for addressing problems when they arise.
That is where compliance becomes part of effective project management rather than simply an administrative requirement.
Building Compliance Into the Life of the Project
A strong compliance program should begin well before an audit or project closeout.
It starts with a clear understanding of the contractual requirements, the documentation needed to demonstrate compliance, and the individuals responsible for maintaining that information.
Throughout the project, there should be regular opportunities to reconcile reported participation with supporting records, review outstanding exceptions, verify payments, and ensure that important decisions are documented.
Equally important is the ability to identify patterns. If documentation is consistently late, payments are difficult to reconcile, or the same issues continue to appear across multiple reporting periods, leadership should know about them.
These are opportunities to improve processes, provide additional support, and address problems while the people and information needed to resolve them are still available.
By the time a project reaches closeout, the objective should be to have a complete and reliable compliance record, not to begin reconstructing one.
Of course, the specific documentation and retention requirements will vary depending on the contract, funding source, and applicable regulations. That makes understanding those requirements at the outset particularly important.
A Different Way to Think About Compliance
At Jean Kristensen Associates, we believe effective compliance management requires more than meeting reporting deadlines or producing participation statistics.
It requires an understanding of how contractual obligations translate into day-to-day project activities, how information is verified, and how issues are identified and resolved.
Our experience supporting major infrastructure programs has reinforced the importance of bringing these activities together so that project leadership has a clearer picture of performance and potential risk.
I also believe there is an opportunity for the industry to change the way we think about compliance.
Rather than viewing it primarily as a requirement imposed by an agency or a process designed to prepare for an audit, we should recognize it as an important part of quality control and sound project management.
Good compliance practices support better decisions, improve accountability, and help protect the investments being made in our infrastructure.
No organization is immune to administrative errors, missed handoffs, or unexpected circumstances. The difference is often whether the organization has the processes, oversight, and discipline to identify those issues and address them before they become larger problems.
A successful project should leave behind more than completed infrastructure and a favorable participation report. It should leave behind a reliable record of how the work was performed and how contractual obligations were managed.
Because the real measure of a compliance program isn’t simply whether the reports were submitted. It’s whether the organization can stand behind the information long after the project is complete.
