AnantState
Industry · Public sector

Decisions that can be reconstructed years later.

Public-sector decisions get challenged, sometimes years later. AnantState records the evidence, the reasoning and any disagreement behind each conclusion, so a decision is defended with a record rather than with memory.

In plain termsDecisions you can reconstruct and defend.

A case, from arrival to a defensible decision

The entities are the things a service is delivered through: a case, a claimant record, an entitlement, a service point, a payment, a referral. The platform keeps their state and the team keeps the decision, and the record connects the two.

A case, from arrival to a defensible decision

  1. A case arrivesLane: Case teamLeads to: Backlog and risk state
  2. Backlog and risk state: Updated as events arriveLane: AnantStateLeads to: Ranked by value at stake
  3. Ranked by value at stake: With evidence and conflictLane: AnantStateLeads to: Verifies, refers or decides
  4. Verifies, refers or decides: A person, with the case in front of themLane: Case teamLeads to: Reasoning on record
  5. Reasoning on record: Evidence, decision, who, whenLane: AnantState
The platform keeps the state of each case and ranks the queue by value at stake, a person verifies, refers or decides, and the evidence and reasoning stay on record for a challenge years later.

What makes a decision defensible

  • Evidence, provenance and conflict travel with every conclusion, which is what makes a decision challengeable and defensible.
  • Receipts and attribution cover decisions taken and decisions declined.
  • Priced interventions. Verify, refer, request evidence or escalate, each with a cost, compared against the cost of a wrong payment or a delayed entitlement.

What moves in a service

StateBaseline driversUnexpected drivers
Backlog pressureArrival rate, staffing, policy cyclePolicy change, surge, system outage
Error and fraud postureHistorical rates, verification depthOrganized activity, insider patterns
Service loadPopulation, season, channel mixMigration, local economic shock
Payment integrityAward rules, cycleDuplicate payments, undeclared change of circumstance

Where it goes wrong today

  • Decisions are held to account that cannot be reconstructed, so the organization is defensible only by assertion.
  • Backlog is managed by adding people, because the shape of the queue is unknown: throughput is visible, but which cases are about to become difficult is not.
  • Fraud and error work is retrospective, with intervention arriving after payment, which is both more expensive and more politically fraught.

A worked example

Ten thousand cases, and verification applied to the ones most likely to go wrong.

Round, illustrative figures for cases: they show the arithmetic, leave out the subscription, and are for you to change in the calculator.

InputValueWhat it stands for
Cases in scope10,000Everything the team is responsible for
Value at stake per one$2,000Exposure on one case from a wrong or delayed decision
Cost of the action per one$80Verifying evidence or referring the case
Share acted on12%The cases most likely to become difficult: 1,200 of 10,000
Modeled, USDPessimisticExpectedOptimistic
Share of value at stake avoided5%12%25%
Cost to act, in total$96,000$96,000$96,000
Avoided loss$120,000$288,000$600,000
Net position$24,000$192,000$504,000

Break-even is 4.0%: each action costs $80 against $2,000 at stake, so it has to avoid that share of the loss to pay for itself.

Procurement notes

What exists today

Public-sector worlds exist as catalog templates (the catalog carries budget to report, assess to treat and similar value chains). They are not a live simulated world.

See a decision reconstructed from its record

Bring a decision that was challenged. We will show what the receipt, the evidence and the provenance would have given you.