Skip to main content
VCPMS Schedule a demo

Behind the platform

State machines, all the way down.

Every work-item type in VCPMS — VcClaim, FrClaim, Payment, Award, 40+ in total — is driven by a state machine configured per tenant. What follows is the canonical lifecycle; your program configures the rules that move claims from one state to the next.

Victim Compensation Claim lifecycle

Draft → Intake → Pending Review → Under Review → Pending Determination → Pending Board Determination → Approved / Denied / Rescinded / Withdrawn.

VCPMS claim lifecycle: Draft → Application Intake → Ready for Award → Award in Process → Approved, with Denied/Withdrawn exits from any active state
From the VCPMS platform documentation — actual state machine colors rendered from the live system.

Denials carry a structured, tenant-configurable reason code (Collateral Source, Late Filing, No Jurisdiction, Criminal Conduct, Failure to Report, Not Crime Related, Duplicate, Two-Year Filing Deadline) and feed the formal appeal track.

Expense Bill lifecycle

Every expense bill a victim submits is linked to a parent VcClaim and follows its own 4-state lifecycle — Draft, In Process, Completed, or Withdrawn.

Expense Bill lifecycle: Draft → In Process → Completed, with Withdrawn exit

Bulk Document Intake pipeline

Every uploaded document set runs through an orchestrated pipeline — split, OCR, classify, extract fields, then route to the right claim.

Bulk document intake pipeline: input sources → InDocumentSet → Split → OCR → Classify → Extract → Route → Auto-linked or Review Required

What programs configure

See your state's workflow configured on VCPMS.

We'll walk you through how VCPMS fits your program.

Schedule a demo