How to describe a technical issue clearly
GOAL
Make the problem reproducible.
INCLUDE
What you expected, what actually happened, exact error text, steps to reproduce, when it started, frequency, and business impact.
SCOPE
Say whether the issue affects only you, a team, a location, a customer, or everyone.
WHAT CHANGED
Mention recent password changes, updates, new devices, new files, travel, permissions changes, or software installs.
GOOD FORMAT
Use bullets or numbered steps. Support teams love structure almost as much as they love logs that are not screenshots of screenshots.
RESULT
Clear descriptions reduce back-and-forth and speed up resolution.