Case management

Turn every case into an owned path from intake to closure.

Build case-management tools with structured records, server-side queues, scoped decisions, and an attributable history. Your team defines the stages and policy in real code.

Build the case workflow Inspect the operating model
data · audit PROD
Data audit append-only
  1. UPDATE assignments 26.06.2026 · 14:02:11
    allocation_percent: 40 → 55 m.alvarez@acme-inc.io
  2. INSERT time_entries 26.06.2026 · 13:47:36
    logged_hours: ∅ → 6.5 j.kim@acme-inc.io
  3. UPDATE projects 26.06.2026 · 11:20:58
    status: planned → active p.nwosu@acme-inc.io

tenant roles hold SELECT + INSERT only · captured by AFTER triggers

The case problem

A status field does not explain who owns the next decision.

Operational cases collect context, evidence references, handoffs, decisions, and follow-up work over time. Spreadsheets and inboxes split that record across people and make closure difficult to reconstruct.

Case controls

Model the record, queue, and decision rights together.

Relpin provides governed data, application, workflow, permission, and audit primitives for the case process your team implements.

01

Structured case records

Keep case type, priority, stage, owner, evidence status, and decision fields in typed tables instead of free-form tracking columns.

02

Owned work queues

Filter, sort, and paginate active cases server-side by team, assignee, stage, deadline, or operational priority.

03

Scoped case decisions

Limit escalation, approval, remediation, and closure actions to the roles or app permissions responsible for them.

Case lifecycle

Intake, assign, decide, and close without losing context.

The lifecycle can stay linear for routine work or branch into additional review when the case type or policy requires it.

  1. 01

    Open the case

    Create a typed record with the required category, source context, priority, ownership, and initial evidence state.

  2. 02

    Route the work

    Assign the case and move it through code-defined stages, escalations, tasks, or approval steps.

  3. 03

    Record the outcome

    Close the case only through a permission-scoped action that preserves the decision, actor, timestamps, and resulting changes.

Case evidence
Typed case and evidence state
Server-side owned queues
Permission-scoped decisions
Actor-linked change history
Case-management questions

What teams build and what Relpin governs.

Is case management a prebuilt Relpin application?

No. It is a solution pattern teams build on Relpin. Your team owns the case types, stages, policy, integrations, and user experience.

Can different case types use different review paths?

Yes. Application code and durable workflow branches can route case types through the stages, approvals, and escalation rules your organization defines.

Can operators work with a large case backlog?

Yes. Relpin is designed for server-side SQL filtering, sorting, and pagination so the console retrieves the working set instead of loading the full backlog into the browser.

Cases with accountable ownership

Build a case process that remains explainable after closure.

Keep intake, ownership, staged decisions, and audit evidence in one code-first internal tool.

Create a Relpin account Discuss case management
Open beta · Solution pattern