Provenance and linked evidence
Keep the source beside the value
COI uploads retain the original artifact beside the human review and decision history. Manually recorded values remain connected to the evidence a reviewer used.
Product
What Sealinn does
Sealinn is an evidence workflow for subcontractor requirements, not a coverage verdict. It collects certificates, keeps manually recorded values beside their sources, supports a human comparison with the requirements and work dates you enter, coordinates corrections, and preserves the customer decisions that follow.
Sealinn currently supports COIs only for new document uploads, requests, status checks, and reminders. Saved W-9, license, safety-card, and custom-document settings remain inactive; they are not requirements a customer can be asked to satisfy in Sealinn today.
Nothing below is a claim about accuracy or hours saved. It is a description of what the software records from requirement through handoff, written so you can check each statement against the product itself. Your team still decides what to require and what the evidence means for the work.
XYZ Electric
ExpiringCertificate of Insurance (COI)On file · expires in 12 days
Next reminder to XYZ Electric in 5 days
One subcontractor’s current certificate: what is on file, when its next supported coverage date arrives, and when the next reminder goes out without anyone sending it. The five steps below are how it got that way.
Step 1
Collect
You request documents from a subcontractor and they get a link. No account, no app, no password — they open it on a phone, attach what their agent sent, and that is the end of their side of it. That single decision is what makes the rest of this work at all, and it is the objection most worth reading in full: what your subcontractors actually have to do.
Step 2
Review
A certificate arrives as a PDF or a photo taken in a truck. Sealinn keeps the original ACORD 25 beside the record while your team reviews the named insured, insurer, Y/N columns, dates, and limits. Automated AI field extraction and confidence routing are currently unavailable. How automated reading is designed to work describes that paused capability without presenting it as part of today’s workflow.
Step 3
Check
Your team reviews the COI against the requirement set you entered — your limits and your endorsement requirements — not against an opinion we shipped. A project can carry a different set, so the job that demands higher limits does not have to stay in someone’s head. Automatic requirement checks are currently unavailable. What Sealinn checks lists what your reviewer should compare and which items need separate evidence.
Step 4
Chase
Coverage lapses on a date nobody is watching, and the certificate’s own cancellation clause promises you almost nothing — 30 days notice of cancellation explains why. Sealinn runs the countdown instead: reminders ahead of supported COI coverage expiry dates on file, escalation to you when a sub goes quiet, and a rejection that arrives with a fresh COI upload link attached rather than as an email somebody has to answer.
Step 5
Prove
The reason to do any of this is the day somebody asks. Sealinn attempts to log key approvals, overrides and rejections. The ordinary tenant-facing database role cannot update or delete those audit rows, although privileged maintenance access and an independently failed audit write remain outside that boundary. Every report and the audit log export to PDF, Excel or CSV, and you can download your certificates as a zip, organized by subcontractor — including after you cancel. The mechanics are on the security page, and what to have ready on audit day covers what an auditor actually asks for.
The record around the certificate
Collection and review are the center of the loop. These shipped workflows keep the surrounding requirements, evidence, responses, actions, and selected handoffs connected to the same customer-controlled decision record.
Assignments and work periods
Review the dates that matter to the job
Project assignments carry work dates. Your team can compare those dates with manually recorded evidence periods and keep any gap visible for a human decision rather than turning a certificate expiry into a coverage opinion.
Requirements and phase packs
Move from cited language to approved prerequisites
Contract-derived candidates retain citations and cannot change a rule until a person approves and applies them. Versioned templates and phase packs keep each project stage explicit.
Broker and supplier responses
Collect corrections in a scoped workspace
Revocable response links support uploads, corrections, comments, project questions, renewal history, and accountable change notices without opening the customer’s full workspace.
Actions, checks, and decisions
Record who has the next move
The action queue combines missing evidence, recorded source checks, exceptions, and customer work or payment decisions in a chronology that can be reviewed later.
Reports, analytics, and handoffs
Package the selected record for the next person
Growth adds scheduled in-app reports and bounded workflow analytics. Professional adds selected expiring evidence rooms and manual downstream snapshots without claiming another system received or enforced a decision.
See the exact capacity and workflow boundary for each tier on the pricing comparison.
The parts worth reading in full
Three pages, each answering the question that actually decides whether a compliance tool is worth the trouble.
- How automated certificate reading is designed to workCOI uploads and human review are available today. Automated AI field extraction, confidence routing, and automatic requirement checks are currently unavailable.
- What to review on a certificate — and what it cannot proveSealinn currently keeps the COI beside a human review and customer decision. Automated field extraction and automatic requirement checks are unavailable.
- What your subcontractors actually have to doThe fastest way to kill a compliance tool is to ask a two-person crew to create an account. So we don't. Here is the whole of what your subs are asked to do.
If you are still working out what to require in the first place, start with what to require before a sub starts — and if you are here because of one line in a subcontract, the COI terms pages decode that sentence phrase by phrase.