Use the complete credential key
Fictional issuer I1 credential C9 is verified for S22. Upload U2 claims I1/C9 for S23 but supplies no subject evidence. Local register permits one staff subject per issuer-number key. Another issuer I2/C9 is a distinct key. This is an internal record check, not a regulated qualification decision.
| Submission | Issuer/number | Subject evidence |
|---|---|---|
| Existing | I1/C9 | S22 verified |
| U2 | I1/C9 | S23 unverified |
| Alternative key example | I2/C9 | Different issuer key |
Inspect the subject conflict
- Match complete issuer/number key
- Retain verified S22 association
- Hold U2 as subject conflict
- Request source subject evidence
Same number from another issuer is not automatically the same credential.
How many verified holders exist for I1/C9 now?
Show the worked answer
One, S22. U2 stays unresolved for S23; the conflict does not establish fraud or a second holder.
Request evidence without judging authenticity
| Case | Action or result | Evidence boundary |
|---|---|---|
| Approve U2 from matching number | Hold | Subject evidence absent |
| CompareI2/C9 with I1/C9 | Distinct keys | Issuer differs |
Keep the unresolved upload and verified association separately. No actual role, access or staff eligibility changes from this demonstration.