Case
One transaction — a charter, a clearance, a survey, a booking — carried as a single numbered record from the moment it is opened to the moment it is closed.
A case is a transaction with a reference, a fixed sequence of steps, one owner on every step, and a written reason whenever it stops. This page sets out what a case holds, who is permitted to read which part of it, and the words the engine is allowed to use.
Four words carry most of the platform. They mean the same thing on every case, in every division, and nothing on this site uses them loosely.
One transaction — a charter, a clearance, a survey, a booking — carried as a single numbered record from the moment it is opened to the moment it is closed.
One unit of work inside a case. A step has a number, a name, exactly one owner, a status, and the documents it requires. A case is its steps, in order, and the sequence is set by the process rather than by whoever opened it.
The role that owes the next action on a step. Always a role — shipper, owner, surveyor, customs broker — and never a named individual, so a case does not stall because one person is travelling.
A line in the record. An entry states what happened, which role did it, and when. Entries are appended and never rewritten, so the history of a case is the case.
The same case as the home page, shown here for the detail rather than for the argument. Step 4 is blocked on an expired attestation; the three steps that depend on it are held rather than silently late, and the step running against a clock shows what is left of it.
BSL-2026-0417
12,400 MT bagged urea
Completed byBluesealine
Trade licence and sanctions screening cleared on both principals.
Completed byBroker
Terms agreed and countersigned. Freight and demurrage recorded on the case.
Completed bySurveyor
Bag count, moisture and stow condition attended and reported at the load port.
Owed byShipper
Chamber-attested origin is required before the bill of lading can be issued.
EXPIRED_CERT
The chamber attestation on file expired on 2026-02-28. A current attestation is needed from the shipper before this step can clear.
Owed byOwner
Class certificates and P&I cover are under review against the fixture.
14h left of 48h
Owed byOwner
Cannot be issued until origin is attested.
Held until step 04 clears.
Owed byCustoms broker
Lodged against the bill of lading and the attested origin.
Held until step 04 clears.
Owed byAgent
Laytime and demurrage are computed from the signed statement of facts.
Held until step 04 clears.
This is a worked example, not a real case. No company shown here is a customer, and the reference, cargo and dates are invented to show how a blocked step holds the steps that depend on it.
Visibility is resolved per role every time the case is read. A party is shown the case, not a copy of it, so nobody has to decide what to forward and nobody is left off a thread.
An observer is the reason this matters. A bank or a cargo underwriter can watch a case move and see where it has stopped without being shown the freight rate, because the record answers per role. There is no setting that widens that, and no document is emailed around to achieve it.
A step is in exactly one of five states. The word is always shown; the colour beside it is a second channel and never the only one.
The step is complete and the evidence for it is on the record.
Work is happening now. The step has one owner and, where the process sets one, a time limit running against it.
Something is required before the step can move.
A blocked step always carries an issue code and a written reason, and every later step that depends on it is shown as held behind it.
Queued behind an earlier step. Nothing is wrong; the step cannot start yet.
Paused deliberately, by the parties or by an authority. A hold stops the clock on the step rather than letting it run out against whoever is waiting.
A blocked step names one code from a closed list, and then states in a sentence what is actually wrong and who can fix it. The list is closed on purpose. Free text cannot be counted, compared between cases or escalated, and a code that anyone can invent means nothing a week after it was written.
A document the step requires has not been filed by its deadline.
Effect The step is blocked, and its clock keeps running.
Clears when The owner of the step files it.
A certificate the step depends on has passed its expiry date, whether it was filed on the case or held in the company's registry record.
Effect The step is blocked, and the steps that depend on it are held behind it.
Clears when The holder of the credential files a current one, recorded with its issuer, issue date and expiry.
A field on a document contradicts the case record — a tonnage, a cargo description, a port or a date.
Effect The step goes to correction. One retry, then it escalates.
Clears when The party that submitted it files a corrected document.
A verifier has declined the submission and given a written reason.
Effect The step goes to correction, and the reason is visible to the parties.
Clears when The owner of the step addresses the reason and resubmits.
An external body — customs, a port, a chamber, a class society — has stopped the file, and nobody on the case can move it.
Effect The case is flagged and the clock is paused, because the delay is not the owner's to answer for.
Clears when The broker or agent returns the authority's decision to the case.
A fee the step depends on has not been settled.
Effect The step is blocked until settlement is confirmed.
Clears when The payer settles it and the settlement is recorded against the step.
A step has run past the time the process allows for it.
Effect It escalates to Bluesealine and counts against the provider's record on the platform.
Clears when Raised by the system, not by a party. It closes when the step completes.
A party has lost its verified status while the case was running.
Effect The case is flagged and no new step opens until it is resolved.
Clears when The party restores verification against the same checks a listing requires.
Six properties of a case, each of which holds on every case or is not worth writing down.
A case is opened with a reference, and that reference carries every step, document, entry and message belonging to it. There is no second identifier to reconcile.
Exactly one role owes the next action at any moment. A step owned by two parties is a step neither of them moves.
A blocked step names a code from the closed list and states in a sentence what is required and from whom. A case never simply goes quiet.
Entries are appended. A correction is a new entry that states what it corrects, and the entry it corrects stays readable.
Where a process sets a time limit, the limit and what is left of it are shown on the step itself, and a hold by an authority stops the clock rather than running it down.
What a party may read differs by role, but there is a single record. Nobody is working from a copy that somebody else chose to forward.
Where this stands today The case engine is specified and being built. Bluesealine is not operating cases for customers yet, so nothing on this page is a record of one. What is open now is the registry: a company can ask to be listed, and verification is what listing requires.
Tell us what your company does and which division it belongs in. We will write back with what we need to verify it.