Higson decision tables

Decision Table Software for Business Rules

Model tariffs, underwriting rules and eligibility checks as decision tables. Your business teams edit them in Higson Studio without code; your systems read them in microseconds, even at a million rows.

Why decision tables

Business Rules in One Readable Grid

Each row is one business rule, so a whole tariff or underwriting policy fits in one grid instead of hundreds of if-then-else lines in code.

  • Business rules, outside the code

    In Higson, decision tables live in Higson Studio, separate from your application. Change a rule without a release.

  • One grid instead of nested logic

    The logic an if-then-else program or a decision tree would hold, in rows anyone can read and check.

Tariff decision table: risk code Fire with sum insured 0 to 1,000 returns factor 0.231; above 1,000 returns 0.215

How it works

Anatomy of a Decision Table

Inputs describe the situation, outputs carry the decision, and the matrix connects the two, row by row.

  • Input columns

    Conditions such as coverage code, driver age or sum insured. Each reads its value from your input data, for example quote.driver.age, or from the result of a function.

  • Output columns

    The decision. A table can return a single value, several values or a whole sub-matrix.

  • Matrix

    The rows with your rules. Tables have no size limit and stay fast at 1,000 or 1,000,000 rows.

  • Settings

    Match required returns an error when no row fits; Distinct removes duplicate results; In-memory index keeps the table in the application cache.

Example

From a Rule to a Table

A billing team sends a reminder when an invoice is unpaid and overdue, for household and company customers. As a decision table, that rule is four columns and two rows anyone can check at a glance.

Decision table with columns InvoicePaid, Overdue, Segment and Action
  • 01. Input columns

    Put each condition in its own input column, here InvoicePaid, Overdue and Segment.

  • 02. Output column

    Put the decision in an output column, here Action.

  • 03. One row per case

    Add one row per case. Ranges, sets and a default row keep the table short.

Matchers

Match Values Your Way

Matchers decide how a value in your data is compared with a cell in the matrix. Fewer rows, the same rules.

  • Ranges

    between matchers define numeric intervals, closed or open on either side, such as an age band or a sum-insured bracket.

  • Sets

    in, not in and contains compare a value or a list of values with a set in the cell, such as a list of postcodes.

  • Text patterns

    like and regex match text by pattern, such as every product code that starts with MTR.

  • Defaults

    An asterisk matches any value. In Best Match mode it applies only when no exact row fits, so it works as a fallback.

Fast at Any Size

Decision tables run from memory. Measured on released versions, one laptop, no tuning (Intel Core i7-13700H, Java 17).

Per rule execution
0.23 ms
In 29.88 MB of heap
1.1M rows
To import 1,292 decision tables
122 s

Use cases

Where Decision Tables Work

  • Insurance Rating

    Tariffs, factors and surcharges in one place. Update a rate by changing a row, not a release.

  • Underwriting

    Every requirement for issuing a policy. Check occupation, income or assets and define what happens when an applicant does not qualify.

  • Lending Eligibility

    Every condition for approving a loan. Income, history and amount checked the same way for every applicant.

  • Discounts and Fees

    Discounts, rates and promotions. Business teams adjust them as the market moves.

Governance

Manage Hundreds of Tables

Beyond the grid

More Than a Static Table

Some decisions need data that changes every day, a fixed list of values, or a model. Higson treats all of them as decision tables.

  • External Data

    Use the result of an SQL query on your own database as the matrix, for example daily fund unit prices.

  • Dictionaries

    Limit a column to a list of allowed values, so entries stay consistent across tables.

  • AI Models

    Use a trained ONNX model as the matrix, for example to predict a monthly premium from customer data.

  • AI Assistant

    Design and refine tables in conversation in Higson Studio 4.3 (beta, enabled per installation).

Best practices

How to Build Good Tables

Start early, keep tables small and make them complete.

  • Start early

    Plan tables when you design the system. You can also add them later, for example to move rules out of a legacy system so experts can change them.

  • Keep tables small

    Several small tables are easier to read, test and run than one big table.

  • Cover every case

    A table is complete when every combination of inputs has a result. Ranges and a default row keep it short.

FAQ

What is decision table software?

Software that lets you define business rules as tables of conditions and outcomes, outside your application code. In Higson, business users edit decision tables in Higson Studio and your systems call them through the Java library or the REST API.

How many rows can a decision table have in Higson?

There is no size limit. Higson searches decision tables of a million rows and more in microseconds when the table is kept in memory (the In-memory index setting, on by default).

Can I import decision tables from Excel?

Yes. Import a decision table from an XLSX file, and export one or many tables to a ZIP that holds their data and configuration.

How do I test a decision table before publishing?

Create test cases in the Tester to check one set of inputs, then group them in the Batch Tester to run series of data and see how a change affects the results.

Do I need to code to use decision tables?

No. Business users create and edit tables in Higson Studio. Developers connect Higson to your systems once. Where a table is not enough, functions add custom logic.

What is the difference between a decision table and a decision tree?

Both hold the same logic. A tree shows it as branching paths, a table as rows, which stay readable as rules multiply. Our decision table guide compares them in detail.

Higson Is a Part of the Gartner® Toolkit

Decision Management Suite Vendor Profiles.

Used by the World's Leading Companies

  • Allianz
  • BNP Paribas Cardif
  • Sompo
  • Aviva
  • Fiserv
  • Nationale-Nederlanden
  • Husqvarna
  • Bravado Health
  • Senior Insight
  • Neo Intelligence
  • InterRisk
  • Warta
  • TUW
  • Notus

Put Your Rules in a Decision Table

Open Higson Studio in your browser and edit a decision table yourself.