The distinction matters because a tool outside the database can only read what you export to it. A system that holds the policy, the endorsement, the contract requirement and the county permit can compare them — and comparing them is what certificate verification is.
Accounts & contacts
The system of record for the business, not for the contact.
The account is the insured entity — its locations, officers, operations and relationships — with every policy, document and conversation attached to it. Verified against the state registry, not retyped from an email signature.
Policies & coverage
Coverage as structured data, frozen at the moment it matters.
Limits, endorsements and effective dates live as fields you can query and compare — not as a PDF you re-open every time. When a certificate or endorsement is issued, the policy state it relied on is snapshotted.
Servicing & the work queue
The inbox becomes a queue with owners and due dates.
Email, WhatsApp and portal requests become work items with an owner, a deadline and the account context attached. Nothing lives in somebody’s personal inbox, and nothing falls between chairs on a Friday.
Certificates
The highest-volume, highest-liability task, done first.
Requests are read, checked against the contract, drafted from the audited wording library and queued for approval. Renewal reissues all holders automatically — each one re-checked against the new policy before it sends.
Documents
PDFs in, cited fields out, nothing written without approval.
Policies, endorsements, loss runs and contracts are read page by page. Extracted values carry a citation to the exact page they came from, and land in the approval queue — never directly in the record.
Property & business records
Public record, prefilled and cited — no other agency system does this.
County parcel data, permit history and the state business registry, pulled into the submission with source and fetch date on every field. Underwriters see where each number came from.
Your book comes with you.
At signup you pick the system you run today — AMS360, EZLynx, HawkSoft, Epic, QQ, Jenesis, or a spreadsheet — and the migration engine maps your accounts, policies and documents into Certova. A migration engineer checks the result before you go live.