Reports and exports

The four reports

Sealinn generates four compliance reports — organization, expiring documents, subcontractor and project — plus your subcontractor roster and the audit log. The four compliance reports exist because four different people ask you four different questions, and handing over the wrong one is how a simple request turns into a meeting.

Each generates as PDF, Excel or CSV. PDF is for handing to somebody; Excel and CSV are for somebody who is going to do their own arithmetic on it. Reports build in the background and land in your notifications when they are ready, which matters on a large book — a long report is not something to sit and watch.

Your subcontractor list, as a file

The fifth entry in that dialog is the subcontractor roster, and it is not a compliance report — it makes no judgment about anybody. It is your list: every company, with the contact name, email, phone, mailing address, trade, tags and notes you hold against it, plus its current status. The compliance reports name a subcontractor and tell you where they stand; none of them hands you back the phone number.

The part worth knowing before you need it: the first six columns are the same six column names the importer reads, in the same order. So a roster taken as CSV is a file Sealinn can read straight back — which is what you want when you are moving a list between workspaces, or handing your own data to someone who asked for it. The four columns after those six (address, city, zip and tags) are not importable and are ignored on the way in; they are there because they are yours, not because they round-trip.

The audit log, which is a different kind of thing

The four reports describe the current state of your compliance. The audit log describes what happened: every approval, every override and the reason given, every rejection, every requirement change, with a name and a timestamp against each. It exports as PDF, Excel or CSV.

Reading the log itself — what lands in it, how to find one entry, and the one thing it does not record — is its own short page. It is deliberately a separate permission. Somebody who can approve documents can generate the compliance reports; reading the log of everyone's decisions is a different level of access and is restricted to the roles that should have it — which roles, and why.

The property that makes it worth anything is that the application cannot edit it. Update and delete on that table are revoked from the role the app connects as, so the record is append-only from the software's side — the security page states the boundary.

Getting the documents themselves out

Reports describe your documents; sometimes you want the documents themselves. You can download your certificates as a zip, organized by subcontractor. The file ledger — every document across every subcontractor — exports separately as Excel or CSV, which is the index to go with the archive.

If what you want is not a document but a list you build yourself — bond numbers, who signed what, the four columns your controller asks for — that is a spreadsheet rather than a report. The reason to know the bulk download exists before you need it is that the day you want it is rarely a calm day. It is usually a claim, an acquisition, or a decision to leave.

One archive is bounded. A large book comes out as several scoped archives rather than one enormous file — narrow by subcontractor or by project and take them in passes. An archive that hit the ceiling says so in its own name and in the manifest inside it, so you can tell "that is everything" from "that is the first part" without counting.

A report is a snapshot, not your record

A generated report describes the moment you asked for it and never changes afterwards. Send Monday's organization report on Friday and it still describes Monday — which is usually fine, and is occasionally the difference between a document that helps you and one that misstates your position to an owner.

That is why generated reports clear themselves out after 3 days rather than piling up, and a failed one after 1. They are cheap to regenerate, so the current answer is always a click away and there is nothing to hoard. The artifact that is meant to be kept is the audit log, which is not on that clock — a snapshot is what you hand someone, and the log is what says what you did.

The project report is only as meaningful as the assignments behind it, which is a separate piece of setup — projects and per-job requirements covers assigning crews to a job and the stricter rule a job can carry. And a compliance report can only describe the subcontractors that are actually on your roster. A crew somebody hired and never entered is not shown as missing — it is absent, which looks identical on the page and is not the same thing. Getting the roster in is the step that makes every number here mean something.

If you cancel

Canceling moves the organization to the free plan rather than locking the account, and export is gated on permissions rather than on plan. So the certificates and the audit log come out after cancellation exactly as they did before.

That is written down here, on the security page and in the pricing FAQ because it is the promise a buyer has least leverage over once they have signed, and the only useful time to make it is before. If you are weighing that against handing the work to somebody else, where an outsourced service holds your history is the same question from the other side.