Decide once. Apply everywhere. Evidence everything.

The decisions that define a redress programme — who is paid, who is written off, who must be contacted, what needs governance sign-off — usually live in a policy PDF and a senior manager's memory. Praxis makes them configuration.

How it works

Three building blocks

1️⃣

Fields — describe your population

Define the questionnaire your analysts complete for each cohort: member status, scheme structure, benefit type, value bands, vulnerability flags — any dimension, with conditional visibility so the form only asks what's relevant.

2️⃣

Outcomes — name what must be decided

Remediation approach, redress approach, payment mechanism, communication requirement — the determinations your governance expects for every cohort, whatever you choose to call them.

3️⃣

Rules — connect them

Plain-language conditions over your fields drive each outcome. First matching rule sets the position; append rules add governance caveats. Ordered, named, and visible — your strategy reads like a policy document that executes.

Worked example

A de minimis policy, encoded

A typical fragment of an underpayment strategy — exactly as it appears in the Praxis rules editor:

1. "Below de minimis" WHEN Impact Direction is "Underpayment" AND Value Band is "Low" SET Redress Approach"Below de minimis — route per policy; no direct payment."   2. "Payable to customer" WHEN Impact Direction is "Underpayment" AND Value Band is one of "Medium", "High" SET Redress Approach"Above de minimis — payment made to the customer."   3. "Visible correction comms" WHEN Correction Mechanism is "Manual" SET Communication Requirement"Correction visible in history — customer letter always required."   4. "Governance override" WHEN Governance Override is ticked APPEND"NOTE: standard thresholds may not apply — governance sign-off required."

As an analyst classifies a cohort, Praxis evaluates the rules live and proposes each outcome — citing the rule that produced it. The analyst applies the suggestion or overrides it; either way, the decision and its provenance are on the record.

Why it matters

Consistency you can show the regulator

Every cohort treated identically

The same inputs always produce the same determination — across analysts, across workstreams, across the years a large programme runs.

Strategy review becomes config review

When governance changes a threshold, you change a rule — not a hundred spreadsheet rows. The rule history is your change record.

Portable institutional knowledge

Your encoded strategy exports with your white-label template. New programme, new team — same doctrine from day one.