Life underwriting software for a schedule your team owns

Automated underwriting usually came with the reinsurance treaty. Decisimo runs the debit schedule your team edits against application answers.

Start free See the rating stages

A debit schedule your team can read and change

Owned schedule

The underwriting team edits the scorecard

Readable debit schedule

Five predictors, named bands and ranges share one scorecard

Portal revisions

Change a band and release it on the same endpoint

Visible blank bands

Each predictor opens with a no-debit band for a blank field

Policy postponement

An open investigation gets a row: postpone, review in 3 months

Report-waiting cases

When a report changes a read value, the decision task runs again

A life application, from answers to terms

  1. Application data arrives

  2. One named band

  3. Blank response band

  4. Debit total

  5. Terms table

  6. Terms from one row

  7. Release the schedule

One scorecard for the debit schedule

  • Five predictorsBuild, pressure, alcohol, conditions and pursuits have named bands.
  • One debitOne point adds one per cent of extra mortality above the standard table.
  • No-debit bandEach predictor opens with a band for an unanswered field.
Scorecard lists predictor bands for BMI, blood pressure, alcohol, conditions and pursuits with ranges, debits and weight 1
The scorecard shows five predictors and each band's range and debits.

Terms from the row the total falls in

  • Five debit bandsEach row sets a decision and its extra mortality
  • Investigation openIts row postpones the application and sets review in 3 months
  • One matching rowEvery rating row also reads the investigation status.
Decision table maps total debit ranges and investigation status to standard, rated, decline, or postpone decisions
The decision table reads total debits and an open investigation, then writes decision, extra mortality and review.

Change a band and read the rating back

  • Portal editsValues, debits and order change there, and each save creates a revision.
  • Rating breakdownThe studio shows each value, band and debit. Live calls do so on request.
  • New releaseA band change stays on the endpoint. Sign-off can apply before deployment.

Endpoint and release practice

An application waiting for a medical report

  • Decision taskIt runs the schedule copied into the case type's release.
  • Changed valueWhen a read value changes, the decision task runs again on its own
  • Review historyA review that read it returns as a new task. The earlier review stays on file.

Life applications as cases

EU AI Act and GDPR Article 22 in life underwriting

  • EU AI ActLife and health risk assessment and pricing are high-risk from 2 December 2027
  • GDPR Article 22It applies today to an automated decision
  • Insurer's PostgresDecision inputs and outputs can be written and browsed

AI Act and Article 22

What stays with the insurer

  • Demo caseEvery band, debit, threshold and term shown comes from a demo case.
  • Insurer's scheduleDecisimo runs that schedule on the details the insurer supplies
  • Extra mortalityThe design leaves premium pricing outside the schedule

Questions we get asked

What are mortality debits in numerical rating?

Mortality debits express extra mortality above the standard table, with one debit equal to one per cent. Decisimo runs the insurer's scorecard and terms table as one decision flow.

How does the schedule handle an unanswered application question?

A blank falls into the band the underwriting team set for missing information. In the shown design, that band carries no debits.

Can our underwriting team change debit bands without developers?

The team edits band values, debits and order, with no code. Each save creates a revision.

Can claims and standard risk run in one insurance decision flow?

Claims can run as cases and standard risk can be decided in one call across insurance. See insurance decisioning

Put your debit schedule in one place

Start free