GASB 34 Infrastructure Reporting, MS4 Stormwater Permit Documentation, FEMA Public Assistance Damage Records and Prevailing Wage Rules on Capital Work: Compliance for US Public Works Software

The Same Records Serve Four Masters

Public works compliance software has an unusual shape: four distinct obligations draw on the same underlying asset, condition and work records.

The financial statements need infrastructure assets reported, and one of the available approaches depends on condition data this department holds.

The stormwater permit needs the system mapped and the maintenance documented. Disaster assistance, when it is needed, needs pre-event condition and post-event damage established quickly. And construction funded from federal or many state sources needs wage documentation collected and retained.

Which means a platform built for operations is public works compliance software whether or not anybody designed it that way, and a department that built operations only will assemble each of these by hand under deadline.

A fifth obligation runs underneath all of them, which is the liability framework around what a municipality knew.

Compliance is the regulatory layer of the full custom software development guide to asset management platform development, and most of the evidence is captured through custom mobile app development in the field. This is educational content, not legal advice.

GASB 34 Infrastructure Reporting

Infrastructure on the Statements

Governmental accounting standards require general infrastructure assets to be reported in government-wide financial statements, which brought roads, bridges, water and sewer systems and similar assets into financial reporting in a way that previously did not apply.

Capitalization policies, useful lives and valuation approaches are accounting determinations made with the entity’s auditors.

The Modified Approach

An alternative to depreciating eligible infrastructure, available where a government maintains an asset management system that keeps an up-to-date inventory, performs condition assessments at defined intervals using a measurement scale, estimates the annual amount needed to maintain and preserve at a disclosed condition level, and documents that assets are being preserved at or above that level.

The conditions are specific and the decision to use the approach is the entity’s with its auditors.

What the Platform Supplies

The inventory, the assessment records with their dates and methods, the condition results, and the maintenance and preservation expenditure.

It supplies data and produces reports. It does not determine the approach, make capitalization decisions or assert that a condition level has been met, which are accounting conclusions.

MS4 Stormwater Permit Documentation

The ongoing regulatory obligation most public works departments live with, and the one where the documentation burden is continuous rather than periodic.

Municipalities operating separate storm sewer systems hold permits issued under the federal clean water framework, administered in most states by the state environmental agency. Permit terms vary by permitting authority, by system classification and by the specific permit cycle.

Common program elements include mapping the storm sewer system including outfalls, detecting and eliminating illicit discharges, controlling runoff from construction and post-construction sites, pollution prevention in municipal operations, public education and involvement, and annual reporting on all of it.

Which translates into asset and work records: the drainage system inventoried with outfalls identified, inspection and cleaning recorded against structures, illicit discharge investigations logged with outcomes, and maintenance on catch basins, pipes and treatment devices captured as work.

The annual report then assembles from those records rather than being reconstructed from memory and spreadsheets, which is how most departments currently produce it.

Inspection frequencies, reporting content and record retention are set by the permit, and departments should work from their own permit rather than from a general description.

Establishing which of these apply to your department is part of what a sprint does, covered in The Discovery Phase Explained.

FEMA Public Assistance Damage Records

The obligation that arrives without warning and rewards preparation more than any other here.

Following a declared disaster, federal public assistance may reimburse eligible costs for debris removal, emergency protective measures and the repair or replacement of damaged public facilities and infrastructure.

Eligibility and reimbursement depend substantially on documentation: what was damaged, where, its condition before the event, the nature and cost of repair, the labor, equipment and materials used, and photographs establishing the damage.

Pre-event condition is the item departments most often cannot produce, and it is precisely what an asset management system holds if it was maintained before the event.

Force account labor and equipment records matter, with eligible costs calculated under defined rules, which is another reason crew and equipment time capture earns its place.

Procurement requirements attach to contracted recovery work, and insurance proceeds interact with reimbursement.

Documentation is examined, sometimes years later, and recovered amounts can be reduced on review.

So the platform’s contribution is structural: assets and condition recorded continuously, damage assessment capture ready to deploy with location and photographs, and recovery work tracked against assets with its costs. Obtain qualified disaster recovery advice.

Prevailing Wage Rules on Capital Work

The obligation attaching to construction rather than to assets, and the one where the platform’s role is narrowest.

Federal law requires that laborers and mechanics on covered federally funded or assisted construction contracts be paid not less than the locally prevailing wages and fringe benefits determined for the work classification, with related statutes extending similar requirements to work funded under particular programs.

Many states have their own prevailing wage laws applying to state and local public works, with their own thresholds, classifications and procedures.

Contractors submit certified payroll records attesting to what was paid to whom in what classification, and the contracting agency collects, reviews and retains them.

Which places the municipality in a review and retention role rather than a determination one.

The platform’s contribution: collecting certified payroll against the correct project and period, flagging what is outstanding, retaining it for the required period, and supporting review.

And the boundary: the attestation is the contractor’s. The platform does not determine compliance, does not validate that a submitted payroll is accurate, and does not conclude that classifications were correct, which are matters for the agency’s compliance staff and ultimately the enforcing authority. Obtain counsel.

Other Obligations

The liability framework around notice, which varies by state and includes immunities, notice requirements and claim procedures.

Transportation funding reporting on condition and expenditure for federally assisted systems. Drinking water and wastewater regulatory reporting where the department operates utilities.

Bridge and structure inspection regimes with qualified inspectors and defined intervals. Underground utility location obligations, both as an operator marking its facilities and as an excavator.

Traffic control device standards and signal inspection practices. Worker safety requirements including excavation, confined space and traffic exposure.

Environmental permitting for construction activity, procurement rules on capital work, public records obligations with the caveat that location data for certain infrastructure may be treated differently, and records retention under the jurisdiction’s schedule.

What This Means for the Build

Five positions follow and belong in a first release.

Deficiency records complete, permanent and reportable, with response and closure documented, since this record serves both the operational purpose and the legal one.

Condition assessments carrying their method, their date and the qualified person who made them, because the accounting approach and the inspection regimes both depend on that provenance.

Crew and equipment time captured against assets and activities, since it serves work costing, disaster reimbursement and the capital argument simultaneously.

Stormwater system assets and their maintenance recorded as a program rather than as ordinary work, so the annual report assembles rather than reconstructs.

And prioritization criteria constrained in the model itself to condition, risk, consequence, use and cost, with valuation and demographic proxies excluded by design rather than by policy.

All five are inexpensive at the start. All five are assembled by hand under deadline if they are not. Which obligations become concrete product features is mapped in Public Works Software Features: Core Modules and Daily Workflows.

Conclusion

Keep deficiency records complete, because the instinct to record less produces the weaker legal position and the worse operation.

Carry provenance on every condition assessment, which is what makes public works compliance software defensible rather than decorative. Capture crew and equipment time, since it serves costing, reimbursement and the budget argument at once. And build stormwater documentation as a program so the annual report assembles itself.

This is educational content, not legal advice. Work with the jurisdiction’s attorney, its auditors and its permitting authority before building, and brief the software companies in the United States quoting you on where the platform’s job stops.

If you are scoping a platform, asking whether you could document pre-event condition for a damaged culvert tomorrow is the question that shows what your records would be worth after a storm.