Identify the certificate request source (insured self-service portal, agent request, or automated third-party requirement) and collect required inputs: named insured, policy numbers, certificate holder name and address, and description of operations
Validate that the referenced policies are active and in-force as of the certificate date by querying the policy admin system
Populate the ACORD 25 certificate fields including coverage types, limits, policy periods, insurer names and NAIC codes, and additional insured or waiver of subrogation endorsement status
Flag any additional insured or waiver of subrogation requirements for underwriting review if not already endorsed on the policy
Generate the ACORD 25 PDF using a document generation service or template engine with the populated data
Deliver the certificate to the requesting certificate holder and retain a copy in the policy file with an issuance log entry
Known gotchas
A certificate of insurance is evidence of existing coverage and cannot modify, extend, or alter the underlying policy; certificate holders sometimes request terms that are not reflected in the actual policy — these must be declined or referred to underwriting for endorsement
Automatic additional insured status on certificates requires that an additional insured endorsement actually be attached to the policy; listing a certificate holder as additional insured without an endorsement creates coverage disputes
Some states have regulations governing who may issue certificates and prohibiting certificates that misrepresent coverage; ensure the certificate generation workflow includes controls to prevent inaccurate certificates
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp