Complaints

Intake, triage, and escalation from first contact to formal case work.

In the live application this area is reached at /complaints. Day-to-day screens require sign-in; this page is a public overview for stakeholders and partner agencies.

What this engine covers

Complaints is where dispute-resolution intake lives—from the public and from staff—with enough structure that reviewers see the story, the people involved, and license context from the first screen. Queues, assignment, and response-time expectations keep work moving. When a matter should become a formal enforcement case, handoff preserves the record so teams are not re-entering the same facts.

Public and staff intake: Channels that capture what happened, who is involved, and what the agency already knows.
Triage and queues: Prioritization and routing that respect deadlines and team roles.
Full context: Linked people, businesses, and license information on every file.
Handoff to enforcement: A clean path when intake becomes a formal investigation or case.

Other engines

Explore another engine.

Engines as modules. Each CORE engine is structured as its own module so it can mature, scale, and release on a timeline suited to its workload, without dragging every other engine along. Its data may live in the shared CORE database with strict separation from other engines, or in a dedicated database when your agency needs stronger isolation—using the same supported integration patterns either way.