Delegated book overview
Every partner bordereau in one place: broker add-ons and the Police Federation OLP schemes. Figures are built from the risk and premium transactions imported each month.
Policies on cover
Rolling 12-month GWP by partner
Gross written premium by month
Net of cancellations and return premiumsBordereau status
Last six reporting monthsWho went on and came off cover
Pick a month to see new policies and scheme joiners, renewals, mid-term changes, cancellations, scheme leavers and expiries across every partner.
Policy lookup
Search by policy reference or insured name to see every cover period and transaction on file.
Import a bordereau
Drop in a broker's spreadsheet as it arrives. The hub finds the header, maps each column to the Addept standard, reads the dates and amounts, and flags anything that needs a human decision before it touches the book.
Drop a broker spreadsheet here
Risk, premium or combined bordereaux in .xlsx, .xls or .csv. The monthly underwriting MI report goes here too.
Import log
Officers Legal Protection scheme
Members on cover by force, joiners and leavers, and the premium collected through payroll. Each month's premium is deducted when that month's payroll runs and the Federation remits it early the following month, so cash normally runs one month behind cover.
Members on cover
All forces, at each month endPremium due vs remitted
By payroll monthBy force
Claims and loss fund
Legal expenses and assistance claims reported by the claims handler each month, tied back to the policies and members on cover, with the loss fund they are paid from.
Loss ratio by partner and product
Incurred (paid plus reserves, less recoveries) on claims notified in the 12 months, against premium earned in the same 12 months.
Loss fund
Held by the claims handlerWatchlist
Open claims that need a lookPanel firm spend
Last 12 monthsPaid development
Cumulative paid by notification quarter, £Cost by matter type
Claims notified in the last 12 monthsClaims register
Ask Addy
Addept's in-house AI. Addy reads every bordereau, payroll remittance and claim in the hub, so you can ask in plain English and get an answer with the records behind it.
What Addy can see
- Every policy, member and transaction imported
- OLP members by force and payroll remittances
- Claims, reserves, payments and the loss fund
- Addept's own UW MI each month
Prospects reviews
Addy reads each legal expenses claim file and gives its own view of prospects of success. Where it disagrees with the panel solicitor near the 51% line, the claim goes on the watchlist.
Bordereaux vs underwriting MI
Policy counts and premium from each broker's bordereau, checked against Addept's own underwriting figures for the month. The OLP scheme is reconciled against payroll on its own tab.
How the data is stored
The demo keeps everything in the browser. In production the same structure sits in PostgreSQL, so every import, mapping decision and exception is kept and auditable.
Tables
PostgreSQLDesign choices
- One transaction per bordereau line. New business, renewals, adjustments and cancellations are all rows in transactions. Cover periods and on-cover counts are derived from them, never typed in.
- A shared core, with product extras in JSONB. Every product shares the core bordereau fields. Police force and warrant number, monthly rent, turnover and other product fields live in a jsonb column, so a new product such as marine legal needs no schema change.
- Scheme members are policies too. An OLP member is a row in policies with an open-ended cover period. Joiners and leavers are transactions, and payroll remittances are matched against members on cover each month.
- Claims tie back to cover. Every claim links to the policy or member, so the hub can check the incident date against the cover period and work out loss ratios against earned premium.
- Mappings are remembered per broker. Once someone confirms how a broker's columns map, the next month's file from that broker maps itself. A changed layout drops back to review.
- Nothing is lost on import. The original file, the mapping used and every flagged exception are stored against the import batch, so any figure traces back to the broker's own cell.
- Excel still works. Underwriters can connect Excel or Power BI to read-only views for ad hoc analysis without touching the source data.