ACORD 25 PDF Fillable: How to Issue Certificates of Insurance Without Retyping the Same Policy Info

The ACORD 25 is the single most-requested form in commercial insurance. Landlords want it. General contractors want it. Vendors want it. The DMV wants it. Your client is on the phone right now asking for one because their new lease starts Monday.

Each one is mostly the same data: named insured, carriers, policy numbers, limits, effective dates. The only thing that genuinely changes between certificates is the certificate holder block at the bottom and a few lines of description. And yet the standard workflow has the agent retyping the whole top of the form every time.

There's a better way. A saved policy profile turns a 5-minute COI into a 30-second one and removes the typo risk completely.

What ACORD 25 actually contains

The ACORD 25 (Certificate of Liability Insurance) has roughly four blocks of data:

1. Producer block: Agency name, address, phone, fax, email, license number, contact name. This is your agency — it never changes.
2. Insured block: Named insured, address. This changes only when the insured changes (rare).
3. Coverages block: Each policy in force — carrier, NAIC code, policy number, effective and expiration dates, type of coverage, limits, deductibles, additional insured / waiver endorsements. This changes once a year on renewal.
4. Certificate holder block: The landlord, GC, vendor, or counterparty. This is the only block that changes per certificate.

Look at the ratio. Three blocks of data that change once a year. One block that changes every time. The whole point of a profile is to fill the three from saved data and only ask you for the one.

The data you'll retype if you don't have a profile

A real ACORD 25 has around 40 prefilled fields and the certificate holder block. The 40 fields, repeated on every certificate:

• Agency name, address, phone, fax, email, contact
• Named insured legal name and address
• Each in-force policy: insurer, NAIC, policy number, effective date, expiration date, limits (each occurrence, general aggregate, products-completed ops, personal & advertising injury, medical expense, fire damage), umbrella details
• Auto policy: combined single limit, bodily injury, property damage
• Workers' comp: employer liability limits, statutory or other
• Description of operations / locations / vehicles (mostly boilerplate)
• Cancellation language (almost always the standard ACORD language, sometimes carrier-specific)

Typing this 40-field block fresh for every certificate request is the single biggest waste of agency time. Multiply by 30 COIs a week and you've lost an entire afternoon.

Building a policy profile in FillWizard

Three sections in the FillWizard policy profile.

1. Producer. Agency name, address, phone, fax, email, primary contact, license number. Set this once per agency and forget it.
2. Insured. Named insured legal name, DBA, address, FEIN if needed for the line, business type. One per insured.
3. In-force policies. Each policy as a row: line of business, carrier, NAIC code, policy number, effective date, expiration date, all relevant limits, deductibles, and the endorsement forms that apply (CG 20 10 for ongoing operations, CG 20 37 for completed operations, CG 24 04 for waiver of subrogation, etc.).

The endorsement form numbers are the part most agencies forget to standardize. A profile makes them dropdown-selectable, so the description of operations block on the ACORD 25 fills correctly without anyone hand-typing "CG 20 10 04 13" while squinting at a screen.

The certificate holder library

Beyond the policy profile, the second part of the speed gain is a certificate holder library. Every recurring counterparty — your client's main landlord, their three largest GCs, their warehouse operator — gets saved as a holder record.

A holder record has:

• Legal name (the way the landlord legal department wants it spelled, which is usually different from the way the building manager wants it spelled)
• Address
• Any special requested provisions (additional insured forms, waiver of subrogation, cancellation language)

When a certificate request comes in from a saved holder, you select the holder, the profile fills the rest, and the certificate generates in one click.

The cancellation language problem

The single most painful part of commercial COIs is non-conforming cancellation language. A landlord's lease will demand "30 days written notice of cancellation" or "notice of cancellation for any reason." The underlying policy doesn't provide that. The agent has to either insert language the policy can't honor (creating E&O exposure) or push back on the landlord (which delays the lease).

A profile-based workflow doesn't solve the legal problem, but it makes it visible. Each holder record can flag the cancellation language the holder demanded last time, so the agent knows up front whether this is a clean COI or a "let me call the underwriter" COI. Surfacing the conflict before the certificate is issued saves the post-issuance E&O scramble.

End-to-end: issuing a COI from a saved profile

A real ACORD 25 issuance from a saved profile takes about 30 seconds:

1. Open the insured's policy profile in FillWizard (5 seconds).
2. Select the certificate holder from the library, or add a new one if it's a first-time request (10 seconds for a saved holder, 60 seconds for a new one).
3. Confirm the description of operations and any additional insured / waiver checkboxes for this certificate (10 seconds).
4. Export the ACORD 25 PDF (5 seconds).
5. Send to the holder (whatever your standard delivery flow is).

Compare that to typing all 40 fields fresh. On the 30-COI week, that's the difference between two hours of certificate work and ten minutes.

Renewals propagate automatically

When a policy renews, you update the policy row in the profile once. New policy number, new effective dates, new limits if they changed. Every subsequent ACORD 25 pulls the renewal data automatically. No "I forgot to update the policy number on this COI" calls from a vendor in February who needed proof of current coverage.

That single property — that renewal updates propagate — is the part most agency operations leads underestimate. It removes a whole class of certificate errors without anyone changing their certificate-issuance habits.

Start a policy profile

If your agency issues more than a handful of COIs a week, the policy profile is the single most useful asset you can build for the team. Set one up, seed it with your in-force policies and saved holders, and watch the certificate workload turn into a one-click flow.

For the supplemental commercial paperwork, see the ACORD 125 guide and the insurance claim workflow guide.