Published

A missed-visit complaint is closed after staff record a replacement visit as completed. The customer then sends a cancellation message concerning that appointment. Does the new evidence belong in the closed case? What if the customer is instead reporting another missed visit two months later?
Reopen a case when the authorised process continues or reconsiders the same matter. Create a linked new case when the new work has its own occurrence or separate decision process. Record the reason for the choice and preserve the original outcome. The customer's identity alone does not determine which case should hold the work.
Start with the original occurrence, scope and outcome. Ask what the new information changes. Evidence challenging the recorded completion of the same replacement visit can require reconsideration of that case. A complaint about a different appointment needs its own assessment, even if the customer and service team are unchanged.
Record the incoming message while the routing decision is pending. A request to reopen and an authorised reopening are different events. Give the request an owner and next action so the customer is not left waiting because the earlier file is marked closed.
Connect the message to the original occurrence, outcome and any separate event or review route.
Approve reopening, create a linked case or use the applicable appeal or follow-up process.
Preserve earlier history while the responsible people assess the new evidence and response.
| New information | Possible treatment | Reason to record |
|---|---|---|
| Evidence challenges the original outcome | Reopen the same case when authorised reconsideration is permitted. | The evidence concerns the same occurrence and the decision already recorded. |
| A separate event involves the same customer | Create a new case and link relevant earlier context. | The new event needs its own scope, owner, response and outcome. |
| The person requests a formal appeal | Follow the defined appeal route, which may use a separate linked case. | The review authority, evidence requirements and response rules may differ. |
| An agreed follow-up action is still outstanding | Continue the owned action, or reopen if the closure itself needs correction under the process. | Distinguish incomplete action from reconsideration of the original finding. |
These routes can coexist. A new incident may also reveal that an earlier corrective action failed. Give the new occurrence its own record and link the evidence needed to reassess the earlier action. Avoid forcing every related concern into one indefinitely reopened file.
Retain the original decision, its reviewed version, closure reason, completion evidence and issued response. Add the reopening request, new information, approving person, accepted scope and next action. A later outcome should explain its relationship to the earlier one, including what was confirmed or corrected.
New evidence may require a fresh review of the proposed resolution. Keep the earlier review and its decisions intact. The document-review guide explains how a completed review and later concerns stay distinguishable.
Show the current case position without erasing past milestones. In reporting, distinguish first closure, the reopening request, authorised reopening and the later outcome. Configure how a reopened period is measured and explain the measure. A changed status should not make the original closure disappear or silently count the same matter as a new occurrence.
This fictional follow-up extends the CASE-1042 workflow. Staff have issued the final response and closed the complaint using the recorded replacement-visit confirmation. The customer now supplies a cancellation message that appears to concern that same appointment.
The caseworker retains the customer's message with its source and received time, linked to CASE-1042. The original response and closure remain visible. The request is awaiting assessment; receipt alone does not change the accepted outcome.
The caseworker compares the appointment reference and dates with the case chronology. The message concerns the replacement visit already recorded as completed, rather than a new service request. Any uncertainty remains visible for the responsible reviewer.
The designated owner approves reconsideration of that completion evidence. The application records the reason and responsible caseworker. The team sets the next response target under its procedure and requests the records needed to resolve the discrepancy.
The caseworker compares the new evidence with the earlier confirmation and submits an explained proposal. The reviewer confirms or returns it for further work. If a replacement action or corrected response is approved, it remains connected to the original decision and the evidence now considered.
Staff record the approved response and required completion evidence before the next closure decision. Reporting retains both the earlier closure and the later work. The file explains why it reopened and what changed, rather than replacing the original record with a new final status.
For a different missed appointment two months later, the configured procedure instead creates CASE-1043. It has its own intake, evidence requirements, owner and response target. A relationship to CASE-1042 can show the recurring issue without copying every earlier document or merging the two outcomes.
The next reviewer may belong to a different department or business process. Confirm the information that person needs and apply the corresponding document permissions. A linked case or shared customer identity does not itself authorise access to all earlier evidence. Apply the same assessment where customer tenants form part of the deployment.
Keep the old owner, new assignment and handover reason in the history. Confirm applicable retention and hold instructions with the records owner when the work changes; do not assume that a reopening label determines the schedule. The investigation case-file guide covers the underlying evidence, findings and follow-up relationships.
Use the same case for authorised continuation of the same matter, and a linked case when a separate event or decision process needs its own record. Preserve the earlier outcome, explain the route chosen and give the new work a clear owner and next step.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.