How Coily works
Watch one request become a certificate.
Five stages, one unbroken flow: read, verified against the policy, issued, and provable forever. This page follows a real request the whole way through.
Certificate request: Meridian PM
Please provide a COI naming us as additional insured, waiver of subrogation, $1M/$2M GL for janitorial at 400 Commerce Park Dr, needed by Friday.
opened in Coily · 9:41 AM
Stage 01 · It arrives
Start where the request already lives
A holder emails your desk, a client fills your form, or the AMS pushes one over. Coily meets the request in Outlook, Gmail, or the dashboard. Nothing gets retyped, nothing gets re-keyed.
- Reads the original email
- No new portal to babysit
- Works beside your AMS
Certificate request: Meridian PM
Please provide a COI naming us as additional insured, waiver of subrogation, $1M/$2M GL for janitorial at 400 Commerce Park Dr, needed by Friday.
opened in Coily · 9:41 AM
Stage 02 · Coily reads it
Every requirement, pulled and scored
The AI extracts the holder, the insured, each coverage line and limit, and every provision (additional insured, waiver of subrogation, primary & non-contributory), then scores its own confidence on each field before anything moves forward.
- Finds the clause buried in ¶14
- Two requirements, not one
- Low confidence → a human
Stage 03 · FormLock verifies
Checked against the policy, not a checkbox
Requirements match to the insured's live policies, and every provision is verified against the endorsement forms actually on file. FormLock fails closed: if the policy doesn't back it, Coily won't assert it.
- CG 20 10 vs CG 20 37: caught
- Expired policy: flagged
- Unbacked waiver: refused
Stage 04 · It issues, or it asks
Verified issues in seconds; unsure asks a human
Clean requests draft a compliant ACORD 25 and issue on the spot. Anything ambiguous routes to a licensed professional with the exact question attached. The fast path and the correct path are the same path.
- Issued in seconds
- Ambiguity → routed, not guessed
- Speed never overrides review
Certificate of liability insurance
ACORD 25 · CY-2026-01847
HolderMeridian Property Mgmt
Additional insured✓ CG 20 10
Waiver of subrogation✓ CG 24 04
Stage 05 · Delivered & provable
The holder gets the cert. You get the receipt.
Every certificate ships with a Verification Report: the forms cited, the policy snapshot frozen at issuance, a tamper-evident ID and hash. Eighteen months later you produce the proof; you don't reconstruct it.
- Tamper-evident vrf_ ID
- Policy state frozen forever
- Audits become lookups
reportvrf_9f2ka31mc84
sha-256b3a1…e56f (tamper-evident)
policy statefrozen at issuance
forms citedCG 20 10 · CG 24 04
Where it meets your day
One engine. Wherever the request shows up.
Gmail add-on
The same one-click issuance in the Gmail side panel.
Dashboard
Queue, clients, policies, certificates. All verified and logged.
API & AMS
Issue programmatically; Enterprise keys, webhooks, connectors.
2.1s
A verified certificate, issued
from the moment the request is read
5/5
Stages on every certificate
read · match · verify · decide · prove
∞
How long the proof lasts
tamper-evident, frozen at issuance
Now watch it read yours.
Paste a real certificate request into the live demo (no signup) and watch the whole flow start.
FormLock runs on every certificate, on every plan. No configuration.