Defect Reports That Survive Handoffs

Good defect reports reduce ping-pong. We teach a four-line minimum: environment, reproduction, expected, actual — then attachments last. Screenshots help, but the Mobile Web Responsiveness QA course stresses device context: orientation, font scaling, and network profile. The second paragraph covers API issues. For contract drift, paste the smallest failing payload diff; for performance, attach percentile tables rather than a single spike screenshot. Readers should reconstruct your thought process without a live call. We end with empathy: developers are juggling priorities. A crisp report earns attention; a theatrical one gets deprioritized. We share phrasing that signals uncertainty honestly — "likely client-side" reads better than guessing disguised as certainty.