Cases
Bulk Case Review
Use multi-select on the Cases list to review, approve or reject a batch of cases, generate notices, update statuses and export the print bundle.
Start from the cases list
Bulk Case Review is a batch workflow inside case management. It uses the normal Cases list and multi-select controls so officers can review multiple cases in one session instead of opening each case individually.
Click Start Bulk Review. CORE can run the review as review only, or review with document when each approved case needs a notice generated for printing or mailing.
Choose review mode and template
When reviewing with documents, select the document template that should be rendered for the approved cases. For infringement workflows, choose the infringement or notice template that matches the batch.
Enrich cases before review
If selected cases do not have a data enrichment match or address on file, CORE will stop the review before documents are generated. Enrichment gathers the vehicle owner, driver and address details needed for mailing the document.
Select the local law
Select the local law for the batch. Every approved case in the review will be infringed under this law, so make sure it matches the offence type and document template.
Review and decide cases
Once the local law is selected, CORE renders the document preview beside the case evidence. Review the case details, evidence, document output and selected law before making a decision.
Use the decision controls at the bottom of the screen to approve, reject or skip each case. The item counter and decided count show progress through the batch.
- Left and right arrows move to the previous or next case
- A approves the current case
- R rejects the current case
- S skips the current case for later review
Finalise status outcomes
After all cases have a decision, click Finalise Review. The finalisation screen shows the total number of cases, approved cases, rejected cases and skipped cases.
For approved cases, enable Update Case Status and choose the case status, sub-status and reason to apply when finalising. A common workflow is to move approved cases to Enforced, set the sub-status to Initial Notice - Sent, and record the officer initials in the reason.
Rejected cases can be mapped separately. For example, rejected cases may be archived with a reason such as Not enough evidence. Skipped cases can also have their own status update if your workflow requires it.
Print and export documents
When documents are included, CORE submits a print job after finalisation. It queues the print job, renders and bundles the documents, then marks the bundle as ready.
Once rendering is complete, export the bundled documents for a print house or internal printing. The exported bundle can then be printed as one consolidated pack.