Bring parking, permits, inspections, evidence and reporting into one practical council workflow.
Cases Configuration
Case Flows
Case flows define the repeatable case journey: which tasks, inspections, notices, enrichments, status changes and decision branches happen from opening a case through to resolution.
What case flows are
A case flow is the template that tells CORE how a case should progress. It links operational work such as inspections and tasks with administrative steps such as status updates, document generation, data enrichment, letters, fees, review points and closure.
Flows are reusable. Once a flow is configured for a case category, officers can open new cases into a consistent process instead of manually remembering every next step. This is useful for councils, universities, airports and private operators where the same compliance pathway is repeated many times.
When to use case flows
Use a case flow whenever a case type has predictable stages, review decisions or required actions. Examples include abandoned vehicles, no stopping infringements, building work without a permit, street trading, unlawful signs, food premises, residential noise, fire breaks, animals at large, littering, camping, verge obstruction and short-stay accommodation matters.
- Simple flows can guide a case from open → inspection → decision → close.
- Enforcement flows can add enrichment, local law selection, notice generation, printing and status updates.
- Investigation flows can pause for follow-up dates, collect inspections, branch on evidence and return to monitoring.
- Review flows can route cases to approval, rejection, appeal, archive or further action.
The case flows list
The case flows list is the admin view for finding, checking and creating flows. Use search to locate a flow by name, filter by date range or category, and switch between active, inactive and all flows.
Each row shows the flow name, category, description, status and last updated details. Keep inactive flows for draft or retired processes; only active flows should be used for live operational work.
Creating or editing a flow
When you create or edit a flow, start with the core details: name, description and category. The category is important because it controls where the flow is available and which case types it is designed to support.
You can start from a blank canvas or use a category template, such as a vehicle management template. Templates are useful when the process already follows a known pattern, for example case opened → inspection → monitor compliance → issue notice → close.
Building the flow canvas
The flow canvas is a node-based editor. Each node is a step in the process, and the connectors between nodes show the order of work. Drag nodes to organise the canvas, zoom in or out, and use tidy controls to make larger flows easier to read.
A typical vehicle case might begin with Case Opened, move to Initial Inspection, then branch into monitoring, infringement, archive or closure depending on the evidence and outcome selected by the officer.
Step types
Use Add a step to place new actions into the flow. Different step types control different parts of the case:
| Step type | What it is used for |
|---|---|
| Tasks | Create work for an officer or team, usually with an owner and due date. |
| Inspections | Require an inspection template to be completed before the case can move forward. |
| Status / Sub-status | Update the case position, for example Open, Enforced, Appealed, Closed or Archived. |
| Branches | Split the process based on decisions, outcomes or conditions. |
| Fees / Enforcements | Apply financial or enforcement actions as part of the case pathway. |
| Enrichments | Request vehicle, driver or address data before document or mail steps. |
| Print, Email and SMS | Generate communications and notices at the right point in the flow. |
| Pause and Repeat | Wait for a time period, follow-up date or repeated monitoring cycle. |
| End | Finish the flow once the case is resolved or no further action is required. |
Most operational steps can be configured with due dates, owners and instructions. Inspection steps can also define outcomes, which are used by branches to decide the next path.
Branches, outcomes and loops
Branches turn the flow from a straight checklist into a decision tree. For example, an inspection outcome of Compliant might close the case, while Non-compliant might create a follow-up task, issue a notice or return the case to monitoring.
Loops are useful where a case needs repeated review. For example, a vehicle may be inspected, monitored for a set period, then inspected again. If the issue remains unresolved, the flow can progress to enforcement; if it is resolved, it can close.
Publishing and maintenance
Before making a flow active, review the path from start to finish. Check that every branch reaches a sensible next step or end step, required inspections and documents are attached, enrichment occurs before mailed notices, and status updates match the reporting rules used by your team.
- Name flows clearly so officers can identify the right process when creating cases.
- Use inactive status for drafts until the pathway has been checked.
- Keep statuses consistent with your Case Statuses configuration.
- Review document and enforcement steps whenever templates, local laws or fees change.
- Test branches with common outcomes so cases do not get stuck without a next step.
Part of Cases · Configuration · Home
