MarvelX Team
Policy Amendments Without the Retyping
The policy amendment workflow at an underwriting agency (MGA): where an agent takes the admin and where the underwriter keeps the mandate.
A broker sends over a new licence plate. The person handling it at the agency opens the policy and checks it is still in force. They look the vehicle up in the national vehicle register and type the new details into the policy admin system, which rates the change and produces the schedule and the green card. The broker gets an email, and at month end the change goes into the bordereau to the insurer. That takes about twenty minutes when the file is complete.
An underwriting agency, an MGA outside the Netherlands, deals with several hundred to a few thousand of these a month. Most are plate and address changes. The rest are extra drivers, higher sums insured and cancellations. Almost none of it needs an underwriter, and most agencies are small teams with no development department, so the volume gets handled by hand. MarvelX builds agentic AI for financial services and highly regulated industries, and agencies have been asking us which parts of this work an agent can take over.
Only one of the six steps is underwriting
An amendment goes through six steps, and the section below walks through them for a plate change. Acceptance is the only step that involves an underwriter's judgement, and even there it often doesn't. If a plate change falls inside the acceptance rules, the insurer's mandate has already approved it. If the new car sits in a heavier category or the sum insured goes up, the risk has changed and an underwriter needs to look at it. The other five are checking data and copying it between an email, a public register and the policy admin system.
There is a reason agencies still do this by hand. The agency acts on the insurer's behalf, and at audit the insurer wants to see who made each change, on what basis and when. A macro can't show that. A person working through a checklist can, and that is where the twenty minutes go.
We run the same steps in claims today
A claim is handled the same way an amendment is. A document comes in and gets checked against the policy and a register. Someone decides within their authority and the answer goes back out. Those steps run in production in claims workflows at insurers, and pointing them at amendments is a matter of configuration. We have worked through it with underwriting agencies on their own amendment types.
Each field the agent extracts is linked to the place in the document it came from, so every value in the file has a source. The agent doesn't work inside your policy admin system either. It hands the record over through an API if the system has one and as a prepared file if it doesn't, and your system stays the system of record.
What that looks like on a plate change
Step
What this gets you at the next audit
When an insurer audits an agency it has delegated authority to, it wants a reason it can check on every change and a named person wherever that authority was used. An agent that writes its own trail gives you both, on the routine plate changes and on the exceptions. That makes the next audit easier and gives you a stronger case when you ask the insurer to widen the mandate.
If you run an amendments desk, request a demo and bring three real files. Bring one inside the mandate, one outside it and one where the broker forgot the attachment, and we'll run all three.
FAQ
Does the agent approve amendments on its own?
Only what the mandate already covers, and it records the rule it applied each time. Anything that changes the risk or falls outside the acceptance rules goes to a named underwriter with the file already assembled.
Do we have to replace our policy admin system?
No. It stays the system of record and keeps doing the rating and the documents. The agent connects through REST APIs and webhooks where the system has them and hands over a prepared file where it doesn't.
Does this only work with Dutch registers?
No. The RDW and KVK are the registers we connect to in the Netherlands. The same check runs against whichever public vehicle or company register your market uses, and against your own policy data.
Where should an agency start?
Vehicle and address changes. They are the highest volume, there is a register to check them against and the acceptance rules are clear enough to agree the agent-underwriter split with the insurer up front.
