Identify both case contexts
Synthetic S44 returns under new joining J44. Old departure L40 has unresolved device task DEV-OLD; the local policy does not waive it because the person returns. New J44 requests desk and contact card. No device issue is authorised by J44 and no possession evidence for DEV-OLD is supplied.
| Task | Case | State |
|---|---|---|
| DEV-OLD disposition | L40 | Unresolved |
| Desk request | J44 | New pending |
| Contact card | J44 | New pending |
Retain the old device task
- Verify S44 identity link
- Retain DEV-OLD under L40
- Open desk/card under J44
- Track both case scopes
Do not reinterpret return-to-team as return-of-device evidence.
How many old unresolved and new pending tasks remain?
Show the worked answer
One old device task and two new administration tasks. No old task is closed or transferred into J44.
Create new-case requests independently
| Case | Action or result | Evidence boundary |
|---|---|---|
| Close DEV-OLD because staff rejoined | Reject | No device outcome evidence |
| Keep L40/J44 task links | Accept | Different case obligations |
The staff overview may show both cases together, but task evidence remains case-specific. Close the old task only on its own actual device disposition.