- Industry
- Insure AI
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Compliance Officer
- Code
- DSN-05
It maintains the shared components of the insurer's design system, such as the premium breakdown, cover comparison table, excess selector, document upload and claim timeline, deciding whether a requested component is added, extended or refused. It schedules breaking changes so policyholder and broker journeys do not break mid-renewal season.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the agent and broker portal: where the component is used across policyholder and broker journeys..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Compliance Officer with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the agent and broker portal: it publishes the component decision and release notes to the design system page. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design system: components, their usage rules, the insurance patterns (price display, cover tables, disclosures), the change process and the release calendar.
Reads from
the agent and broker portal: where the component is used across policyholder and broker journeys.
Acts in
the agent and broker portal: it publishes the component decision and release notes to the design system page.
Hands back
An object with decision (add, extend, refuse or deprecate), component, variants, release_month, notice_date, migration_steps (a list) and reason.
Asks a person when
The change is breaking, or alters how price, fees, excess or disclosures are shown.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Use cases for a new component | 3 | Fewer, and it stays a local pattern. |
| Breaking changes only in | January, May, September | Months for breaking releases, away from peak renewal. |
| Deprecation notice (days) | 60 | Teams get this much notice. |
| Most variants per component | 4 | More is a new component. |
| Price display pattern is locked | On | When on, changes to how premiums, instalments and fees show need compliance. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Add a component only with 3 or more use cases.
- Make breaking changes only in January, May, September, with 60 days notice.
- Keep variants to 4.
- When on is true, any change to how premiums, instalments, fees or the excess show goes to the Compliance Officer.
- A component carrying disclosures must keep them visible in every variant.
See the Design System Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.