Help
Setting your requirements
A requirement set is the checklist your authorized reviewer uses for each arriving COI. Automatic requirement checks are currently unavailable; saved non-COI settings also remain inactive.
What a requirement set is
One set is your default review checklist for every subcontractor. The form stores coverage limits, endorsement requirements, and non-COI document choices. COI limits and endorsement requirements can guide the active human review; W-9, license, safety-card, and custom-document settings remain saved but inactive.
Use the effective set when reviewing each COI. Changing a limit updates the checklist for later reviews; it does not mean Sealinn automatically reread every certificate or replaced an earlier customer decision.
Limits, and what a blank one means
Leave a limit blank and it is not part of the reviewer checklist. That is deliberate — a requirement you have not decided is not a requirement, and a default number invented by a vendor is exactly the sort of figure that ends up in a subcontract nobody can justify. Fill in the ones your prime contract and your own agent tell you to.
Be precise about which number you are setting. A general-liability per-occurrence limit and a general aggregate are different ceilings and a certificate prints both — three limit lines read as three different numbers is worth two minutes if that distinction is not already reflex. The aggregate in particular is shared across every job your sub works unless a per-project endorsement carves yours out.
A missing section blocks, just like a low number
Compare every limit you fill in during human review. A certificate below your minimum and one that shows no such coverage are different facts, but both need a recorded customer decision. The full COI review checklist sets out every row. Automatic checks are currently unavailable.
Endorsements and inactive document settings
The endorsement toggles — additional insured, waiver of subrogation, primary and non-contributory — tell the human reviewer which certificate claims to compare. A tick box is a report about a form rather than the form, so ask the issuing agent for the endorsement page by form number. No automatic endorsement check currently runs.
W-9, license, and safety-certification choices remain saved but inactive: Sealinn does not request those files or use their absence in status. The saved safety-card validity window defaults to 5 years from the issue date; that setting does not activate safety-card handling, and the window is your policy rather than a federal expiry rule, as the safety-card guide explains.
Custom document names can also remain in saved configuration, but they do not appear in request or upload choices and cannot make a subcontractor incomplete. Custom checks can remain saved as reviewer prompts, but new automated verdicts are unavailable while automated reading is disabled. Custom documents and custom checks keeps that boundary explicit.
When a project override earns its keep
A second requirement set can sit over the top of your default for one project. The case for it is specific: an owner whose contract demands higher limits than you normally carry, or a job with an unusual endorsement requirement. Everything not overridden falls through to your default, so an override is a short list rather than a second full set.
The thing to know, because the form does not say it: a project override is the checklist reviewers should use for subcontractors assigned to that project, including assignments made earlier. What a project does with that set covers the other half. Adding a stricter override does not automatically reread existing files; review the affected COIs and record any new customer decisions.
Reminders and escalation
Reminders are part of the same settings screen because they are the same decision: how early do you want to know. The default cadence is 90, 60, 30 and 7 days before expiry, and you can pick up to 6 points from 90, 60, 30, 14, 7, 3 or 1 days, or type your own.
Escalation is the other half. If a reminder goes out and nothing happens for 3 days, the next message goes to you rather than to the subcontractor — on the assumption that a sub who has ignored two automated emails needs a phone call from a person, and that person should be told. The window is yours to set.
One condition worth knowing, because it explains a silence: the countdown runs on documents that are approved and current. A certificate still sitting in your review queue is not on a clock, which is the right behavior — chasing a renewal for a document nobody has accepted yet would be chasing the wrong thing — but it does mean a full review queue is also a paused set of reminders.
Still stuck? Tell us what happened.
Include the page and workflow involved. Free for up to 10 subcontractors — no card.