IT Support Playbooks / IT Support Guides
Write a support handoff another engineer can act on
A good escalation explains what is still failing and which evidence changed the working hypothesis. It should let the next engineer continue without asking the user to repeat everything.
Environment and inputs: Everyday IT support · Windows PowerShell examples unless specified
Try the diagnostic command
Use the stated shell and platform. Replace sample domains, addresses, services and paths with values from the system you are authorized to support.
Get-Date -Format oHow to read the result
The PowerShell timestamp gives the handoff a precise observation time. Combine it with device, service and timezone details so evidence from separate systems can be aligned.
What to do next
Include impact, scope, reproduction steps, exact errors, tests and their outcomes, approved changes and rollback state. Name the specific next question, such as whether the server accepted the failing request.
Before you make a change
Separate observed facts from hypotheses. Redact secrets and avoid claiming that an untested component is healthy just because a nearby diagnostic command succeeded.