Configure it without waiting for IT.

Every client's exposure management process is different. ConfigHub gives your team complete control over validation rules, data models, workflows and export formats, fully integrated within your governance structure.

The choice of modules is configurable at client level and at individual user level.

  • Validation rules without an IT ticket
  • Data models and field mappings per client
  • Export formats and permissions you control

Every client's process is different. The platform follows yours.

exposurehub / confighubIllustrative
VALIDATION RULES3 / 5 ACTIVEPostcode requiredALL SOURCESInsured value in range0.01 – 500MDates in ISO 8601ALL SOURCESGeocode confidence ≥ 80%ADDRESS MATCHFlag duplicate locationsPER POLICYFIELD MAPPINGSOURCE FIELDPLATFORM FIELDpol_refsum_insloc_pcPolicy IDInsured valuePostcodeEXPORT FORMATCSVXMLAPI→ exposure_q1.csv · 12,408 rowsSCHEDULE · DAILY 06:00 UTCNO CODE · NO TICKETv14 saved · live 14:02

Client A · their column

PostCode → Zip

Try what your team would control.

The five lines of the ConfigHub description, as working examples. Flip the switches: nothing is saved, and the settings are fictional.

Customise validation rules without IT dependency

Change what counts as a good record yourself.

Go on, try one.

ConfigHub · validation rulesIllustrative
  • Expiry is after Inception
  • Latitude is between -90 and 90
  • TIV is greater than zero
  • Zip is present

Configuration in practice: a rollout, one class at a time.

A fast-growing specialty MGA customer writes on behalf of other carriers and owes each of them reporting. It configured ExposureHUB team by team, from a first class to seven.
0

classes of business now on the platform, after workshops with seven teams

How the project ran

  • Agree which underwriting teams were in scope
  • Assemble a project team: a core group and around 25 exposure management stakeholders
  • Run workshops with seven teams to fact-find what each wanted from an exposure management system
  • Prioritise the classes with a staggered go-live rather than launching seven business lines at once
  • Go live with Property D&F first, so a repeatable template could be applied to the other lines
  • Prioritise requirements in three groups: go-live (the minimum viable product), Phase 2 (within three months of go-live) and longer-term
Property D&F

went live first, so a repeatable template existed from the start

~25

exposure management stakeholders in the project team

3 groups

of requirements: go-live, Phase 2 within three months, then longer term

Read the customer story Source: Ebix Europe customer case study.

Start from something that already works, then adjust.

The template that worked for the first team becomes the starting point for the next.

Start from a template

Begin with a configuration that already works.

Adjust

Change rules, mappings and formats for your team.

Test

Check the result on real records.

Roll out

Apply it to the next team or class.

See ConfigHub in action.

Book a walk-through of this module on your own data, with your own questions.