COI Tracking for Municipalities and Public Agencies
Public agencies need an orderly record of what a vendor submitted and how it was reviewed. Insurance is only one part of procurement, and a standard COI may not be the only proof a permit or public contract requires. Certy helps one responsible account collect certificates against a shared baseline, review extracted fields and follow renewals. Use the agency’s procurement process for contract-specific forms, approvals and records.
A familiar handoff
For example, a parks department renews a mowing contract while public works starts a separate construction project. Both businesses supply certificates, but the construction bid has a different insurance schedule and proof requirements. A single baseline should not be mistaken for a review of both public contracts.
Translate the awarded insurance schedule
Before sending requests, identify the contracting public entity, awarded scope and approved insurance clause. Have the agency’s insurance adviser identify any required endorsements or special state proof forms. Keep the original schedule in the procurement file. Certy can compare certificate fields with the shared account baseline, but it does not determine statutory form sufficiency or interpret bid language.
Collect current certificates consistently
Import the approved vendor list by CSV after checking duplicate names and contact details. Give each vendor its private upload link, which accepts certificates without a vendor account. Review the extracted insured identity, dates and limits against the submission, correcting read errors. Retain any separate official proof documents using the agency’s established recordkeeping process instead of assuming an ordinary COI replaces them.
Route deficiencies to an authorized decision
When the document differs from the requirement, describe the exact gap and request issuer-prepared evidence. Contract changes and exceptions should go to the person authorized under the agency’s process. Record the decision and conditions externally; editing the account baseline to fit one vendor can hide the original requirement for everyone else. A status screen does not substitute for procurement approval.
Prepare a repeatable renewal record
Use expiration reminders 30, 14 and 7 days ahead and review unresolved items before the next work period. Export vendor records for reconciliation with active awards and keep the dated supporting documents under the agency’s retention policy. If a contract is extended or its scope changes, review insurance again even when the existing policy has not reached its expiration date.
Prepare these records
- The awarded insurance clause and correct public-entity names.
- Current liability and employee coverage certificates.
- Official state coverage proof forms where the contract process requires them.
- Supporting additional insured and waiver documents.
- Authorized exception, extension and renewal-review records.
Where Certy fits
Certy does not provide public procurement workflows, public-records management, SSO, multiuser approval permissions or separate bid-specific requirement sets. Confirm any hosting, security and procurement conditions independently. Use Certy for a consistent certificate baseline only when those needs are satisfied elsewhere; evaluate broader tooling if they must be part of the same platform.
Certy’s paid plans include certificate tracking. Free tools are available separately without signup; there is no free account tier. Review the current plan limits before importing your vendor list.