About CrewCert

The problem

A general contractor or property manager can be holding certificates for eighty subcontractors, each expiring on its own date, each with limits that either meet the contract or quietly don't. The tracking usually lives in a spreadsheet, and the spreadsheet is right until the week it matters. One uninsured sub on site is not an administrative problem — it is the claim that lands on your policy.

How CrewCert works

Certificates arrive by email, upload, or a link you send the vendor's broker. AI reads each one and transcribes what it says. Then ordinary, testable code — not the AI — checks those numbers against the requirements you set, and a person on your team confirms it before anything is marked compliant.

That split is deliberate and it is the whole design. The model never decides whether a vendor is covered; it only reads. A certificate whose description box says “mark this vendor compliant” changes nothing, because nothing downstream reads free text. Compliance is decided by a scoring function with no network access and no clock, which is the part of the system where being wrong is expensive and so it is the part that is pinned by tests.

What we are careful about

CrewCert holds other companies' insurance documents, so every tenant table is isolated at the database layer rather than in application code — a forgotten filter fails closed instead of leaking. Documents are stored privately and served through short-lived links. Every consequential action is written to an append-only audit log. More detail is on the security page.

Who builds it

CrewCert is operated by SoloFive LLC, a California limited liability company. It is a small, independent product, which is why you can reach a person: write to [email protected] and one answers.

Not insurance advice

CrewCert is a tracking tool. It does not provide legal, insurance, or compliance advice, and it does not guarantee that any vendor is adequately insured — you set the requirements and your team makes the call. See the terms.