How to Organize Certificate of Insurance Files
Organize insurance evidence around stable vendor identity and policy periods, with links to the applicable agreement and review decision. A folder named “current COIs” is convenient for today but weak for reconstructing a past project.
Establish a naming convention
Use a stable vendor identifier, legal name, document type, policy period and version or receipt date. For example, a hypothetical internal filename could identify vendor V014, GL evidence, the 2026 period and the receipt date. Avoid relying on a building nickname or an agent’s original attachment name alone.
Keep the original file intact. If you rename a copy, preserve enough metadata to trace it to the submission. Do not edit the insurance content itself to make a file fit your record system.
Connect documents without flattening their meaning
A certificate, endorsement, declarations page, broker response and exemption record have different purposes. Store them as related evidence with clear labels. Associate review notes with the actual version reviewed rather than an unversioned folder.
Use one policy-period row in your tracker to connect the evidence to renewal dates. If one certificate lists several policies, link the same file to multiple rows rather than inventing a single combined date.
A hypothetical retrieval problem
A property manager searches for the certificate used during a 2024 elevator project. The vendor’s current folder contains only a 2026 renewal. A versioned archive would let the manager retrieve the relevant period, supporting endorsements and the reviewer’s decision without asking a former employee to search an inbox.
Protect access and preserve history
Choose an approved repository with access controls and backup arrangements. Restrict sensitive policy or claims material to the people who need it. Record any legal hold and follow the approved retention policy before deleting earlier evidence.
Make the handover testable
Ask someone who did not perform the original review to retrieve one vendor’s work-period evidence and explain which requirements were checked. If the answer depends on personal memory, add the missing context to the record. At project end, use the closeout checklist to assign continuing obligations and archive ownership.
Certy can keep vendor certificates and extracted fields together. It should not be described as replacing every policy archive, legal hold system or project document hierarchy your organization may require.
Frequently asked questions
Should I store only the newest certificate?
Keep the historical evidence required by your contracts, claims and retention process. A current certificate does not document every prior work period.
Can one certificate belong to several policy records?
Yes. A single document may list several policies with different dates. Link it clearly to each relevant policy period.