Which of the following is a valid reason to cancel a case?

• A. The Case was created in error
• B. The Case was resolved
• C. The Member is unavailable
• D. The case was moved to a different system

Answer: (A)

Understanding when canceling a case is appropriate hinges on whether the case entry actually represents work that needs to be done. If a case was created in error, there isn’t real work to address, so canceling cleanly removes the mistaken entry and keeps the system data accurate. It prevents confusion and keeps reporting from reflecting a non-existent issue.

If a case has been resolved, you wouldn’t cancel it. You’d mark it as closed or resolved, preserving the history of what was done. The status should reflect that the work was completed, not erased.

If the member is unavailable, cancellation isn’t the right move. You’d typically put the case on hold, reschedule, or follow the organization’s policy for temporary delays, rather than deleting the case.

Finally, if the case was moved to a different system, the correct action is to update the record to show the transfer or link to the migrated case, not cancel it, so the history and context aren’t lost.