One cover, a thousand shipments: where broker management systems stop

Ask a cargo broker what their busiest day looks like and you will not hear about placing risk. You will hear about declarations.
They arrive by email and spreadsheet. They sit in a queue waiting to be entered, checked and invoiced. Somebody keys them, somebody else notices the ones that were keyed wrong, and by the end of the month the operations team has spent more time on data entry than on clients. Meanwhile the book of business lives in several places at once and nobody fully trusts any single version of it.
Every broker in this market knows that picture. What fewer people say out loud is why the software does not fix it.
The policy record was never the hard part
A general agency system is built around a policy. One risk, one document, one renewal date. That model works well for most commercial lines, which is why the market leaders built it and why they are hard to beat on that ground.
A cargo book does not look like that. At the centre sits an open cover. Hanging off it are hundreds of individual declarations, mid-term adjustments, coinsurance splits and the bordereaux that go back to carriers. All of those things have to stay attached to each other, and they have to stay attached for years, because a declaration made in 2023 may still be relevant to an adjustment made this quarter.
That is not something you configure your way into. It is a difference in how the data is shaped. A system that treats the cover as one more policy record will hold your declarations as a pile of loose documents next to it, and every process you build on top of that pile will be manual.
Two policies that answer the same question differently
Two things get called open cover. Only one of them is your problem.
An open cover written on declarations works on notification. The assured or their forwarder declares each shipment on an agreed rhythm, often monthly, and each one is a record. Hundreds a month is normal in a working cargo book.
A turnover-related policy works on the client’s sales or freight figures adjusted at the year end. Individual shipments are never declared separately, which is exactly why some clients prefer it.
Both get described as open cover when a broker talks about their book. Only the first generates the volume that breaks a spreadsheet. If your book is mostly the first kind or you run stock throughput programmes on top of it, the rest of this article is about you. If it is mostly the second, your problem is somewhere else and you should not let anyone sell you a solution to a problem you do not have.
What to look for instead
Five questions we would put to any system, including ours.
- Is the open cover a record in its own right, with declarations attached to it as relationships rather than as separate policies that happen to share a client name?
- When a cover is adjusted mid-term, does the declaration history stay intact and still reconcile, or does it become historical data you can read but not use?
- Can the system hold a coinsurance split, and a master and local policy structure, without a development project?
- When a booking is made, does the money resolve itself? Client premium, insurer payable, broker commission and insurance tax are four separate things, and in a cross-border book they behave differently in every market.
- Can you open a new country, currency or trade lane without adding an administrator to absorb the extra keying?
Few general agency systems were built to answer yes to all five, and that is not a criticism of the vendors. It is a consequence of what they were built for. But notice how rarely declarations, running policies and bordereaux appear as named functions in broker management system marketing at all. Ask for the answers in writing rather than a demo.
Why we built it this way
tigerlab Brokerage was built for open cover with declarations because it was built with a global cargo brokerage, in co-creation with the brokers using it every day. Open cover, declarations, bordereaux and adjustments are in the product, not on a roadmap. Four ledgers post on every booking, per jurisdiction. First markets are live and the platform is rolling out across more than 30 countries.