PN-2026-S3YBPS · Northgate Advisory Ltd · professional indemnity notification · opened 4 days ago, on the web

Waiting on 2 answers before this can be decided

Outstanding: What are they saying went wrong; Have they put a figure on it. Nothing is attached from a register, because this is not a loss about the policyholder's own property.

2 outstanding

What this one turns on

The 1 answer that decides whether the policy responds, before the account rather than inside it. A person still decides what they mean.

What are they saying went wrong?

Not answered. This one has to be established before the case can move.

Their version, as they put it, rather than yours. Notifying it early is what keeps the cover available.

The account, as the policyholder gave it

Their words, not a summary of them. The tool call is shown because it is the answer to the question any handler has about a claim that arrives already populated: the items came off a register that existed before the loss, not out of the conversation.

No account yet

The policyholder has not said what happened. That is the request to raise, and it is the one thing on this case nobody else can supply.

Engine

Nothing was attached: this loss is not about property on the register.

{ "tool": "get_asset_register", "args": { "profile_id": "audit_5ga6ly" }, "result": { "items_matching_the_loss": 0, "replacement_value": 0, "with_purchase_record": 0, "with_serial_number": 0, "oldest_line_dated": null } }

Everything else asked

When did the client first raise the issue?: They emailed on the 3rd
Which client, and what was the engagement?: A logistics client, on the operating model review we finished in May

The position at the date of loss

What is held against what is on the claim. The two numbers, side by side, and no third number worked out from them.

Professional Indemnity

Northgate Advisory Ltd

Line	Figure	Source
Cover recorded	£1,000,000	Set on 1 Mar 2024 and not revisited since.
On this claim	not a property loss	No item list belongs on this kind of claim, so nothing was attached.

A person decides this claim. Nothing on this screen computes a settlement, applies a policy term or expresses a view on whether the policy responds.

Flagged before the loss: Professional Indemnity is held at £1,000,000 against an indicated £2,000,000

A liability limit pays in full up to the limit and nothing above it, so this is not a proportional shortfall like an under-set sum insured. It is the point at which a large claim stops being covered, and the limit was last set in March 2024.

Nothing is attached to this one

This loss is not about property on the register, so no item list belongs on it. The register is intact and irrelevant here.

What this needs next

2 requests to raise

What are they saying went wrong? Have they put a figure on it? In a live system this is one message to the policyholder rather than 2 separate ones, and the case sits here until it comes back.

This screen assembles, it does not decide

No step here accepts a claim, declines one, sets a reserve, values anything for settlement or pays. Those are a person's, and the engine has no route to any of them by design rather than because they have not been built yet.

Where the evidence came from

Every attached line was on the policyholder's register before the loss, most of it put there by a bank statement rather than typed. That is what a handler is being asked to rely on, so the register says per line whether a purchase record exists and this screen repeats it rather than flattening both into "evidenced".

Demo case against a fictional business with synthetic transactions. Nothing here is a real claim and no part of this prototype agrees, values or pays anything.