Annotated proof example

Annotated sample · not a learner record

Review the work, not a résumé claim.

This fictional sample shows the structure of a DiamOps proof record. The scenario, identity and actions below are demonstration data; no real person completed this investigation.

Work a practice ticket How recruiters should use proof

Evidence boundary

What this sample can prove

Demonstration data

It demonstrates the fields and audit trail DiamOps can expose. It does not prove employment, production access, independent work by a real candidate, or a hiring outcome.

Simulated incident

Repeated account lockout after a password change

Service desk · Intermediate

Reference	DEMO-INC-0841	Priority	P2 · High
Affected service	Microsoft 365 sign-in	Scope	One simulated Finance user
Outcome	Resolved	Close code	Resolved — fix applied
Completed	29 July 2026	Environment	Simulated workplace

Recorded actions

Investigation audit trail

Step	Learner record	Reviewer can check
1. Scope	Compared the reported times with other account failures and found no matching pattern outside the affected user.	The conclusion is limited to the supplied simulated evidence.
2. Investigate	Reviewed Entra sign-in events showing repeated lockout code 50053 from Windows credentials after the password change.	The record distinguishes observed log data from interpretation.
3. Act	Removed the stale credential, unlocked the simulated account and asked the requester to re-authenticate Outlook and OneDrive.	The action follows the stated finding and avoids unrelated changes.
4. Verify	Recorded a successful re-authentication and no repeat lockout during the scenario verification window.	Verification is explicit; a real employer should still test the skill independently.

Evidence register

Sources and interpretation

Source	Recorded interpretation	Limitation
Simulated Entra sign-in log	Repeated 50053 failures support an account-lockout pattern.	Does not identify the stale credential by itself.
Simulated service-health view	No wider authentication incident was shown.	Only covers the supplied scenario window.
Simulated requester confirmation	Sign-in succeeded after credentials were refreshed.	Not an independently witnessed production result.

Operational record

Communication, closure and reference

Requester update: The account was unlocked; saved Windows credentials using the previous password were removed. Re-authentication was requested for Outlook and OneDrive.
Internal note: Pattern isolated to one simulated user. No service-health incident observed.
Knowledge reference: DEMO-KB-1042 · Clear stale Windows credentials after a password change.
Verification: Successful sign-in recorded; no repeat lockout during the simulated observation window.

Assessment disclosure

How this example would be reviewed

Guided mode · one hint shown

Area	Recorded judgement	Reason
Triage	Meets scenario standard	Scope and priority are stated before action.
Evidence use	Meets scenario standard	Relevant sources are interpreted and limitations are retained.
Verification	Meets scenario standard	An observable result is recorded after the change.
Independence	Guidance disclosed	One hint was shown; this must not be presented as fully independent work.

DiamOps assessment describes performance inside this simulation. It is not an autonomous hiring verdict and does not guarantee the same result in a live environment.

Reviewer guidance

Use a candidate’s private proof link to ask specific follow-up questions: why they trusted a source, what they ruled out, what they would do with broader access, and how much guidance they used. Combine it with interviews, references and your own technical assessment.

Read recruiter guidance

Try the workflow

Build a record from your own practice.

Choose a role, investigate a simulated ticket and keep the resulting proof private until you decide to share it.

Start a practice ticket Compare role paths