For insurance agents and brokers

There is no account for you, and that is deliberate

Start here, because it saves you looking. Sealinn has no agent or broker login. There is no agent account to create or use, and saying otherwise here would send you hunting for a signup that does not exist.

Everything below is about a certificate moving between you, your client and their contractor, plus endorsement pages they may retain through a separate approved evidence process. There is nothing to set up, nothing to learn, and no charge to you at any point.

What the upload link is

A general contractor using Sealinn sends your client a link to a single-purpose COI upload page. There is no account and no password on it. It names the contractor, asks only for the outstanding certificate, and expires on its own. If your client forwards it to you, it works in your hands too — the link is tied to the subcontractor, not to a person, which is deliberate, because in practice you are often the one holding the certificate.

You do not have to use it. Emailing the certificate and endorsement copies to your client, as you always have, works exactly as well; the link exists to save one step on the COI, not to route around you. A certificate sent through the link goes into the contractor's record with a date attached rather than into an inbox where it gets lost by the third renewal.

Why they are asking for the endorsement, not another certificate

This is the request that generates the friction. It is not a challenge to the accuracy of what you issued. The certificate's own disclaimer settles it — the form states that it amends, extends and alters nothing, which is a statement about the document rather than about the person who filled it in. The ADDL INSD and SUBR WVD columns report what is on the policy; they cannot be the thing that puts it there.

So a contractor whose subcontract requires additional-insured status is asking for the page that grants it. When a blanket form already covers it, a copy of that blanket endorsement answers the request completely and is usually the fastest possible reply. The practical suggestion, and the only one this page really makes: send the certificate and the relevant endorsement copies in the same message the first time. It ends a loop that otherwise runs three or four emails, usually in the week the crew is meant to start.

What happens to what you send

Here is what the system does with what you send.

• A person reviews the original certificate. The contractor can record the limits, policy dates, named insured, endorsement columns, and its customer decision. Automated AI reading and automatic requirement checks are currently unavailable.
• Nothing is inferred about the carrier. A reviewer may record the insurer name as plain text. Sealinn does not rate carriers and does not check financial strength — that lookup is the contractor's own job, and this software does not do it for them.
• Only that contractor sees it. Other subcontractors working for them cannot see your client's certificate, and neither can any other company using Sealinn. How the data is held sets out the mechanism rather than the adjective.
• Manually recorded supported expiry dates drive reminders. When a policy is approaching its recorded expiry the contractor's system contacts your client, not you — though you will often be the next call your client makes, which is why the schedule is worth knowing.