Stop tracking certificates of insurance in spreadsheets.

COI Review is the product that parses and validates an individual certificate. COI tracking is the ongoing program around your whole roster: collecting, validating, monitoring expirations, and proving compliance over time. What makes it different on 1099Policy is that we can also issue the coverage, so part of the roster never needs a certificate chased at all.

Yes. That's the collect-and-validate half. Forward any vendor's ACORD certificate and it's parsed, checked against your requirements, filed, and watched for expiration, whether or not the coverage came from us.

That's the gap a spreadsheet can't close. Instead of chasing a certificate that may never come, have the contractor enroll in coverage in their own name through 1099Policy. The certificate then issues automatically with your entity as additional insured, so the empty row becomes compliant and stays current on its own.

Every collected certificate is monitored by its expiration date and surfaced ahead of the lapse, so you can request a renewal while there's still time, not during an audit or after an incident.

No. Issued certificates are generated per engagement with your entity as additional insured and a window that matches the work. They don't lapse mid-engagement and there's nothing to chase, which is what shrinks the tracking burden as you move more of the roster onto issued coverage.

Yes. Every certificate, validation result, and requirement is archived and exportable. When a client, insurer, or auditor asks you to prove the roster was compliant, you export the record instead of reassembling it from email.

Set the requirement per engagement, not per roster. General liability is the baseline most contracts expect. Add workers' comp where an uninsured injury would land on your policy or your premium audit, and professional or cyber lines where the deliverable or data access warrants them. The requirements builder stores those rules by vendor class, so every incoming certificate is scored against the requirement you actually set.

Ask for an ACORD 25 issued by the vendor's broker, with your entity named as certificate holder and, where the contract calls for it, as additional insured. On 1099Policy the request is a link: the vendor forwards the certificate, it's parsed and checked against your requirements on arrival, and a vendor who can't produce one can enroll in coverage in their own name instead.

Your organization, as the party requiring the proof. The certificate holder box records who the certificate was issued to; it doesn't extend any coverage. Protection under the vendor's policy comes from additional insured status, which is why validation checks the additional insured wording too, rather than treating a certificate with your name on it as done.

On an ACORD 25, additional insured status shows as a checked box on the liability line plus wording in the Description of Operations section naming your entity. The certificate holder box at the bottom is not the same thing. Manual reviews conflate the two constantly, so the parser reads the description wording, not just the checkbox, before a certificate counts as compliant.