COI intake previously required a lot of manual effort from reviewers: vendor and tenant matching was too strict and often failed on minor formatting differences. This update was built to cut down that repetitive work by loosening the matching logic, giving extracted policies a clear mapping path, and simplifying the validation and approval experience.
Step 1: Extraction Summary
After a COI is processed through AI extraction, the reviewer first lands on a summary page rather than jumping straight into a detailed review. This page shows an overall compliance badge (Compliant or Non-Compliant), a count of policies that still need to be mapped to a Cove policy type, and whether the certificate holder name matches the expected record. Each extracted policy is listed along with its compliance status, or a No Requirements label when the matched Cove policy type has no compliance rules configured.
Step 2: Mapping Unmatched or Custom Policies
Extracted policies that don't automatically match an existing Cove policy type are flagged as Needs Mapping on the summary page. Reviewers can map the policy to an existing Cove policy type, which triggers an immediate compliance check, or skip the policy so it's excluded from intake. If no suitable policy type exists yet, a new one can be created directly from the mapping flow; new policy types default to No Requirements until compliance rules are added. Custom or Other coverage found on a COI, which was previously dropped during extraction, is now also captured as a draft item so it can be mapped or skipped the same way.
Step 3: Detailed Review
The full review screen, now labeled Extracted Fields for Review, shows the certificate holder match along with each auto-populated policy type and its entries. Policy types tied to a vendor or tenant requirement display a Compliant or Non-Compliant badge, with inline validation messages next to any non-compliant fields. Policies are sorted in the order they appear on the source document, so a type such as Commercial General Liability typically appears first, making it easier to cross-reference against the original COI.
Related to