DecisionCase

    Employee relations cases that stay with the people on them

    Concerns, investigations, findings, appeals and accommodations in one confidential record, where the org chart is treated as a possible conflict and not as a permission structure.

    Access follows the roster

    Every case has its own roster on top of role permission. Someone without a seat gets a not found, not a refusal that confirms the case exists. A privileged case needs legal permission as well, and an administrator who opens a case they are not on is written to the audit trail.

    A finding for each allegation

    "Complaint upheld" is not an answer when the complaint contained four things and two happened. Each allegation gets its own finding, and entries are amended with a history rather than overwritten.

    Conflicts are checked before assignment

    Routing checks the investigator against the reporting line before it assigns. When the reporting line cannot be resolved, the case escalates to legal instead of falling back to the matched rule.

    What is actually in it

    Four areas, from the moment a concern arrives to the review date nobody should forget.

    From concern to case

    The first hour of a case decides who sees it. Intake, routing and the conflict check happen before anyone is assigned.

    • Report a concern in the app at three disclosure levels, including anonymous, where no reporter identity is stored on the case
    • An anonymous reporter gets a private follow-up link, so the team can ask a question and the reporter can answer
    • Rules route by category, department and severity band, and unroutable intake goes to a configurable triage owner
    • Start from a DecisionCapture form built to open a case from each submission
    • An AI assistant can file a concern over MCP, but has no tool to read one: the tool is intake only

    The case file

    One record for the whole matter, kept the way an investigator would keep it and a lawyer would want to read it.

    • Allegations with a finding on each one, and outcomes and actions with verification
    • Interviews recorded as verbatim or summary, with the Upjohn warning noted as given
    • Evidence uploaded, replaced or withdrawn, plus snapshots of DecisionDocs and Sheets taken as PDFs
    • Amendment history on every section: entries are amended, never overwritten
    • Email from the case, with replies kept in it and anything blocked shown as withheld

    Judgement, with the law in view

    Assistance for the person deciding, clearly labelled as assistance, and never a substitute for counsel.

    • A per-case legal review against company policy and catalogued law, with a manual override
    • A law catalogue covering federal law and 19 states, with per-tenant corrections and a stale citation view
    • The jurisdiction for the legal review is taken from the reporter's employment record
    • A banded severity score from harm, scope, protected characteristic and power
    • Findings labelled as assistance, not legal advice

    Accommodations and appeals

    The parts of employee relations that run for months, where the risk is the date somebody forgot.

    • An accommodations roster, a create form, an interactive process log and an append only decision history
    • The employee chosen from the directory, never typed in, because you cannot accommodate someone you cannot identify
    • Medical documents stored apart: access takes a permission plus a written reason, and every read is recorded
    • Review dates reach the coordinators as DecisionTasks obligations
    • Appeals are filed against a specific finding through the API, and the portal lists them
    • An appeals panel is drawn from a committee and refused if any member is on the case roster

    It is not a separate product

    A case sits inside the platform, so its intake, its obligations and its signatures are the same ones the rest of the company already uses.

    DecisionCapture

    A Raise a concern form opens a case from each submission, with the category and disclosure level it asks for.

    DecisionTasks

    Outcome actions and accommodation review dates arrive in the same inbox as everything else a person owes.

    DecisionSign

    Through the API, an agreement can be raised from a case action, and is refused unless an allegation is substantiated.

    Committees

    Appeals ride the committee subsystem, so a panel votes where votes are already recorded, not in a second engine.

    Built for the case nobody wants to leak

    Two gates on every read, a refusal that does not confirm the case exists, and an audit trail that records the administrator as well as the investigator.

    Role plus roster Amended, never overwritten Off roster reads audited Legal permission for privileged

    Keep the case where the decision is

    DecisionCase runs on the same platform as your decisions, tasks and signatures. Nothing to integrate, and no second inbox to reconcile.