Help
Setting your requirements
Manual requirement entry is supported. New COI requests, uploads and replacements are currently available only for the authorized pilot workspace with a verified reviewer. In-app human COI review is in early access, open only to our authorized pilot organization for now. New uploads are not read with AI; entered values can still show rule issues during human review. Saved non-COI settings remain inactive.
What a requirement set is
One set is your default requirement record for every subcontractor. The form stores coverage limits, endorsement requirements, and non-COI document choices. COI limits and endorsement requirements can guide a human review where reviewer access is available; 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. Entered values can still show blocking rule issues; a plain approval cannot bypass them. Correct the fields or record an accepted exception with a reason. The full COI review checklist sets out every row. New uploads are not read with AI, and a rule result does not verify coverage.
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. Entered certificate claims can still show rule issues during human review; they do not verify the endorsement form. Sealinn does not currently accept separate endorsement files.
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 project can have a complete requirement set of its own, for example when the owner requires higher limits or an unusual endorsement. The saved project set replaces the workspace default as a whole. A blank project limit stays blank rather than inheriting the default limit, so check the entire project set before using it. If no project set exists, the workspace default applies.
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
Open Settings → Reminders to set the cadence and owner alerts. Requirements live separately in Settings → Compliance defaults. 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.
When escalation and owner alerts are enabled, an unanswered expiry reminder can trigger an additional email to the active workspace owner after the configured period, which defaults to 3 days. The window is yours to set. This alert does not redirect or cancel later scheduled subcontractor reminders, and it is not a promise of delivery.
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.
Need help with requirements or reminders?
Tell us which page and workflow you used and what happened.