elan1 DECIDE · DECISION PACKS
One kind of case, set up once.
A Decision Pack packages one kind of case, such as insurance claims triage, AML alert triage, KYC review or a payment dispute, as a ready set of typed decisions, routes and review rules. Packs compile to elan1 Govern's seven-block declarations, so any write that follows a decision is checked and recorded like every other write.
Available now, in every elan1 Decide plan.
Diagram · illustrative specimen. Not customer data.
01What it does
A pack is configuration, not code and not a brand.
A pack holds schemas from Decision Studio, a calibration plan, routing tiers, review queues and the write types it may propose. It compiles to Govern's seven blocks: identity, shape, permissions, write_types, gates, proof_binding and channels.
Who it's for
- Operations owners starting from a known case type rather than a blank schema.
- Systems integrators and BPO partners delivering elan1 Decide to several clients.
03How it works
From a known case type to a checked declaration.
- Choose a pack for one case type.
- Set it to your policy: thresholds, risk tiers and review queues.
- Calibrate it on your own golden set in the Calibration Lab.
- Compile it. The pack produces a Govern declaration, and Govern checks it before any write type goes live.
- Version it. Every Ledger entry and proof record names the pack version that applied.
Packs in the catalogue
Claims first-notice-of-loss triage · AML alert triage · KYC document checks · AP exception routing · support ticket triage. Each is calibrated on your cases before any route goes live.
- Schemas
- policy_in_force · Boolean · yes | nohandling_path · Choice · fast_track | standard | investigatedamage_severity · Score · 0 to 100
- Write types it may propose
- claim.set_handling_path · claim.assign_queue
- Status
- Available · a usual first lighthouse
Illustrative. Schemas and write types are set with you and calibrated on your cases before any route goes live.
- Schemas
- alert_disposition · Choice · close | escalate | investigatecustomer_risk · Score · 0 to 100screening_match · Boolean · yes | no
- Write types it may propose
- alert.set_disposition · case.open_investigation
- Status
- Available · a usual first lighthouse
Illustrative. Schemas and write types are set with you and calibrated on your cases before any route goes live.
- Schemas
- document_legible · Boolean · yes | nodocument_type · Choice · PAN | passport | voter ID | othername_match · Score · 0 to 100
- Write types it may propose
- kyc.set_document_status
- Status
- Available
Illustrative. Schemas and write types are set with you and calibrated on your cases before any route goes live.
- Schemas
- exception_type · Choice · price variance | quantity variance | missing PO | possible duplicatewithin_tolerance · Boolean · yes | no
- Write types it may propose
- ap.route_exception · ap.hold_invoice
- Status
- Available
Illustrative. Schemas and write types are set with you and calibrated on your cases before any route goes live.
- Schemas
- ticket_category · Choice · billing | access | defect | otherurgency · Score · 0 to 100needs_specialist · Boolean · yes | no
- Write types it may propose
- ticket.set_queue · ticket.set_priority
- Status
- Available
Illustrative. Schemas and write types are set with you and calibrated on your cases before any route goes live.
04In the console
Decision Packs in the elan1 Decide console.
A screen from the elan1 Decide console design, shown as an illustrative specimen. Not customer data.
Every decision you run, the lifecycle stage it has reached and its health, so you can see which have earned automation and which are still proving themselves.
- A decision moves through five stages, from Draft through Shadow and Canary to Live, one gate at a time.
- Certification needs a named decision owner and risk owner, neither of them the author.
- Versions are pinned, so callers never get “latest” by accident.
What it connects to
Writes go through elan1 Govern.
Every pack compiles to an elan1 Govern declaration, so writes go through elan1 Govern and its gates, never through anything the pack builds. Decide builds no gate, approval store, seal, meter or verifier.
What it costs
Decisions a pack makes are counted like any other decision, inside your elan1 Decide plan. Every plan includes the Decision Packs module; individual packs from the catalogue are also priced per pack.
| What | Price · excl. GST | Includes |
|---|---|---|
| Growth — self-serve and developer teams | ₹4,80,000 per year | Typical volume 1,00,000 decisions a month |
| Mid-market | ₹36,00,000 per year | Typical volume 15,00,000 decisions a month |
| Enterprise — BFSI and insurers | ₹1,50,00,000 per year | Typical volume 1 crore decisions a month; SSO and SLA |
| Decisions beyond the plan allowance | ₹30 per 1,000 decisions | |
| Decision Packs | Priced per pack | The Decision Packs module is in every plan; each catalogue pack is priced individually |
| A write intent Govern refuses | 40% of a governed action | Metered by elan1 Govern, not by Decide; the decision itself is counted once, as a decision |
All prices are exclusive of GST. Prices are current list prices; GST is added at the applicable rate on the invoice.
- First purchase: a claims or AML lighthouse, or an LLM Decision Offload audit.
All prices are exclusive of GST. GST is added at the applicable rate on the invoice.
Status
- Available: the Decision Packs module, in every elan1 Decide plan.
- Catalogue packs for claims, AML, KYC, AP exceptions and support triage, each priced per pack.
- Governed actions in Mode B, through elan1 Govern: available.
- A marketplace for partner packs is on What's next.
Available now. See what’s next
What it does not do
- It does not carry its own logo or brand.
- It does not build its own gate. It compiles to Govern's.
- It does not work out of the box. Every pack is calibrated on your cases first.
- It does not cover a regulation by itself.
FAQ
Claims first-notice-of-loss triage, AML alert triage, KYC document checks, AP exception routing and support ticket triage. Claims and AML are the usual first lighthouses.
No. A pack structures how cases are answered and routed: unsure or high-risk cases go to a person, and any write that follows, such as a claim payout or an alert closure, is checked and recorded by elan1 Govern like every other write.
The Decision Packs module is included in every elan1 Decide plan, and each catalogue pack is priced individually. Talk to us for the price of a specific pack; all prices are exclusive of GST.
Yes. A pack is configuration, built from schemas in Decision Studio and compiled to a Govern declaration.
No. It structures how alerts are answered and routed, and it records each step. Your obligations stay yours.
Next steps
One write path, four layers
Work and Decide propose. Govern and Run assure. Only Govern allows.
// elan1 DECIDE · DECISION PACKS
Bring one decision to a lighthouse.
Pick a high-volume decision. We run it in shadow beside your current process before any route goes live.