Understand the fundamentals
A ticket carries the investigation across people
A service ticket should name the physical machine and where it is. It should say what was expected, what was actually seen and when the issue happened. Include the model, the firmware and profile, and the time period you watched. Attach approved evidence. Never include passwords or other credentials, or personal information that is not needed.
Keep actions that were done separate from actions that were only suggested. “Restart requested” is not “restart completed.” And “restart completed” is not “recovery verified.” Each phrase describes a different stage of the work.
A handoff another shift can pick up
Swipe sideways to follow the full diagram →
See how it works
Make uncertainty and ownership visible
Write down the questions that are still open. Name the person or team who owns the next action. If work stopped because authorization or compatibility was unclear, say so in the ticket. Otherwise the next shift may repeat an incomplete or unsafe plan without knowing it.
A useful handoff also says where the supporting records are kept. It says whether the situation is stable, getting worse or waiting for a planned check. Do not write vague labels such as “fixed” without the observations that support them. A ticket should be closed only after the original problem has been checked again.
Connect it to the field
Worked example: replace a vague note
Weak note: “Miner down. Rebooted. Fine now.”
Better record: “Asset M104, rack B2, stopped submitting shares under worker B2-104 at 09:15. Local interface remained reachable. Approved restart completed at 09:30; local hashing resumed at 09:34. Accepted work is visible again. Next shift is assigned to confirm it stays stable over a longer period.”
The better record does not invent a root cause, the underlying reason for the problem. It does not claim more checking than actually happened. It keeps the symptom, the action and the observed recovery separate. The times and names here are made up for teaching. In real work, use the actual values and evidence.
Terms used in this lesson
- Identity and scope
- Which machine or group of machines is affected, and where it is.
- Evidence
- Time-stamped observations, exact messages and relevant readings.
- Current state and owner
- What has been done, what remains and who is responsible for the next step.
Optional references & further reading
Use current manufacturer instructions for the exact equipment and your site’s approved procedures. Course levels do not grant task authorization.