A small water or sewer authority sits in a peculiar spot: it runs like a utility, procures like a municipality, and staffs like a small business. The general manager who negotiates the chemical contract is often the same person who fields the 2 AM main break call and signs the SRF paperwork. Vendor compliance lands on that same desk.
The good news: the job has a knowable shape. Here it is.
The four vendor populations
An authority's roster sorts into four groups, each with its own document profile.
Construction contractors. Main replacements, plant upgrades, tank rehabilitation. The full public works document set applies: certificate of insurance with limits per the contract, additional insured endorsement naming the authority's exact legal entity, performance and payment bonds at award, licenses for the trades involved, and, on state or federally funded projects, the certified payroll stream.
Consulting engineers. Design, permitting, construction administration. A different insurance profile: professional liability (errors and omissions) alongside general liability, plus current professional licensure for the engineers of record.
Suppliers with a delivery clock. Treatment chemicals above all: chlorine, coagulants, fluoride, polymers. The compliance concern follows the delivery, not the calendar: current insurance including auto liability for the trucks entering the plant, product certifications for anything touching potable water, and current safety documentation.
The on-call roster. Excavators, electricians, pump specialists, and others who respond when something breaks. Their documents must be current before the emergency, because no one checks paperwork during one.
Where authority compliance overlaps with municipal, and where it diverges
The overlap is large. Bidding thresholds, bond statutes, prevailing wage on public work, right-to-know exposure on the files: an authority carries most of what a township carries, and the general tracking disciplines (one roster, category requirements, request cadences, contact logs) transfer directly.
Three things diverge:
The funding overlay. State Revolving Fund loans, which finance a large share of small-system capital work, attach federal requirements to the project and its contractors: prevailing wage documentation, American Iron and Steel records, and program reporting. These arrive as project-anchored document streams with their own deadlines, and a draw request can wait on them.
The consequence profile. When a township's landscaper lapses, grass grows. When an authority's chemical supplier has a delivery problem, treatment is affected. More of an authority's roster is operationally critical, which changes how quickly a red status needs a human.
The clock. Authorities run around the clock, and part of the roster exists specifically for nights and weekends. Compliance for the on-call pool is a readiness function: the paperwork must be complete in advance and refreshed on a cycle, because its whole value is being already done.
Building the authority's roster
The sequence mirrors any vendor roster, with two authority-specific additions. Build the roster from accounts payable and the contract files; set requirements by the four categories above; put every standing document on a request cadence with silence follow-up; gate new contracts at signing. Then add: tag every vendor touching an SRF or grant-funded project, so the federal overlay documents get tracked with the project; and tag the on-call pool for a standing readiness cycle rather than a lazy annual one.
An authority that can answer "which documents expire in the next 60 days, and is the on-call roster current" in one minute has the system. Everything else is refinement.