Child cases, relationships and duplicate detection
Updated 19/11/2026
A child case represents related work with its own lifecycle. Relationships can link cases without requiring that hierarchy. Duplicate detection helps identify similar requests but requires an explicit matching policy; similar names alone may not mean the requests are duplicates.
A case type describes a repeatable business outcome. Stages group major milestones; processes organize work inside a stage; steps describe user tasks or automations. Assignments wait for a person or queue. Routing selects the responsible resource. Goals and deadlines describe service expectations; urgency helps prioritize work but does not replace a routing policy.
Decide whether document verification merits a child case. Define two duplicate-match inputs and explain how legitimate repeat requests remain distinguishable.
Return to curriculum