DecisionRadarQuality
Quality guardrails

A radar is only as honest as its criteria.

DecisionRadar makes structure visible. Users remain responsible for evidence, framing and final judgment.

User-defined options
The tool does not invent the decision alternatives.
Guardrail
Editable criteria packs
Presets are starting points, not authoritative checklists.
Guardrail
Visible weights, fit scores and calculation choice
Every weight can be inspected and changed; 0 means weak fit and 10 means strong fit. Weighted balance is standard; alternative calculation lenses stay under Advanced and are explained in plain language when selected.
Guardrail
User-defined triage rules
The process owner defines each check and evidence rule. DecisionRadar does not invent eligibility criteria, weight, rank or automatically reject cases.
Guardrail
Cover-first blocker check
Each user-defined Triage rule declares Cover, Dossier or Cover + dossier. Cover Scan may surface a possible blocker, but a human reviewer must explicitly confirm it before the case state changes.
Guardrail
Session-only source PDFs
Up to 10 PDFs can be attached to the active case. Source files are not stored in the DecisionRadar draft; a connected LightAssist may suggest evidence, but the reviewer explicitly applies each state.
Guardrail
SharePoint source-of-truth intake
An authorised Microsoft 365 host may import the case queue and resolve only the active case cover/PDFs. Native SharePoint permissions remain authoritative; DecisionRadar stores no access tokens and does not bulk-copy the document library.
Guardrail
Email / Outlook intake
An authorised mailbox host may create or refresh cases from intake messages and provide active-case attachments on demand. DecisionRadar keeps no mailbox credentials and does not bulk-copy the inbox.
Guardrail
CSV / TSV queue intake
A spreadsheet export can populate up to 5,000 lean case records using reference and name fields. Source documents remain separate.
Guardrail
Recommendation separated from decision
The user can confirm or explicitly override the highest score.
Guardrail
Action field
The workflow ends with a next step, not only a graphic.
Guardrail
Not professional advice
High-stakes legal, medical, financial, security or personnel decisions require appropriate expertise and process.
Limit
Recovery-safe persistence
The fast local draft is mirrored into IndexedDB where available, and optional host write-back can provide institutional versioning/audit. Source documents never enter either draft path.
Guardrail

Recommended use

  1. Rate every criterion as fit: 0 means weak fit and 10 means strong fit. If a raw measure is “lower is better” (such as cost or risk), score the option’s fit rather than copying the raw number.
  2. Leave the standard Weighted balance calculation in place unless there is a clear reason to use a different lens. Changing the calculation changes the result/ranking, not the radar or the underlying ratings and weights.
  3. Use five to ten decisive criteria where possible; very large radars are harder to read.
  4. Record the evidence and assumptions behind unusual ratings.
  5. Check whether a non-negotiable constraint should disqualify an option instead of merely lowering its average.
  6. Use the override openly when judgment differs from the numerical result.

Triage

  1. Define the process checks and evidence rule before reviewing cases; DecisionRadar supplies no authoritative eligibility list. Mark each rule as Cover, Dossier or Cover + dossier.
  2. For volume triage, scan the cover first. Treat a LightAssist blocker finding as a flag for confirmation, never as an automatic rejection.
  3. Use Met only when the evidence satisfies the defined rule. Use Review when evidence is unclear or incomplete; use Blocker only for a defined blocking condition.
  4. Let LightAssist extract or suggest evidence where approved, but require an explicit reviewer action before a state changes.
  5. Keep source PDFs in the authoritative host repository for institutional-scale use; DecisionRadar session attachments are temporary.
  6. For SharePoint deployments, import the current view/selection as the queue and fetch cover/dossier files only for the active case. Do not export or replicate the full document corpus into DecisionRadar.
  7. For email intake, use an authorised mailbox/Outlook adapter and fetch attachments only for the active message/case; never make the mailbox itself a DecisionRadar database.