Dashboard¶
The dashboard is the landing page every user sees when they log in. It is a real-time Kanban board showing all in-flight risks, organised into columns by processing status and tabs by product type or custom filter.
Dashboard versions¶
| Version | Status |
|---|---|
| V1 | Stable, production. Legacy layout. |
| V2 | Current target. Enhanced filtering, card metadata, and improved UX. |
Kanban columns¶
Columns on the board correspond to risk processing statuses:
| Status | Typical meaning |
|---|---|
PRE_SUBMISSION |
Risk shell created but the submission has not yet been made (e.g. from Smart Submissions intake) |
LOGGED |
Risk submitted but no work started yet |
WORK_IN_PROGRESS |
Active underwriting in progress |
QUOTE |
A quote is being structured |
QUOTED |
A quote has been issued |
BOUND |
The risk has been bound |
BOUND_NOT_BOOKED |
Bound but not yet booked into the policy administration system |
COMPLETE |
Risk fully processed |
Other risk processing statuses also exist in the platform's RiskProcessingStatus enum (including inactive values used for cancellation, lapsed, and similar end states) — check the enum on your active core platform version for the full set.
Warning
Never change a risk processing status code — only its label. Code changes break dashboard column configuration and action history.
Tabs and views¶
Top-level tabs are configurable per client. Each tab can have:
- Its own Kanban columns and their order
- Default filters pre-applied when the tab is opened
- Card metadata fields shown on each risk card
The risks_board_config.json in applicationconfig/ defines the board structure. A typical Open Market view defines columns drawn from the active risk processing statuses (e.g. LOGGED, WORK_IN_PROGRESS, QUOTE, QUOTED, BOUND) and default role visibility for users such as UW, UWA, UWT.
Risk cards¶
Each card on the board represents one risk. Standard configurable fields include: line of business, insured name, assigned underwriter, inception date, and priority indicators.
Clicking a card opens a spotlight panel on the right with additional configurable fields. Clicking the button at the bottom of the spotlight opens the full risk record.
Filtering¶
| Filter type | Description |
|---|---|
| Default filters | Set per view in configuration. Applied automatically when the tab is opened. |
| Ad-hoc filters | Users add, remove, and combine filters on the fly using the filter panel. |
| Saved filters | Users save their own filter combinations. User-specific and persistent across sessions. |
Creating a new risk¶
Clicking the + button on the dashboard opens the submission form — a multi-step wizard configured in open_market_submission_config.json. See Submission Forms: Overview.
On successful submission: the risk is created in LOGGED status, initial pipelines are triggered, and the risk card appears on the dashboard immediately.
MTAs and renewals¶
- MTAs appear on the risk record of the original risk. They create a new version linked to the original.
- Renewals appear on the dashboard 90 days before the risk's expiry date. Once processed, they become new risks in
LOGGEDstatus on the main board.
Tasks¶
Tasks are assignable work items attached to a risk — separate from risk actions. They appear in the Tasks panel on the risk record. Task templates are configured in task-templates/.
Masters and declarations¶
MASTER placing type risks (DUA contracts) appear in a separate tab from Open Market risks. Declarations linked to a master appear as child records within the master risk record.
Note
Linking a risk to its binder (master) is required for the Rules Engine Facility Risk Validation group to function. If risks are not showing as linked, check the masterRiskConfig block in be_config.json (S3 business config) and the binder reference fields in the submission config.