How to get useful bug reports from clients
A simple framework to get the URL, technical context and reproducibility in the very first message.
Read guideResources
Guides to receive better bug reports.
Practical resources to make website support clearer, faster and more structured.
Three practical guides are live now. More focused resources will follow.
What to ask when a client says the site does not work
A practical checklist to quickly understand whether the issue comes from browser, content, network or JavaScript.
Read guideBug report template for freelancers
A reusable structure for retainers, handoff clients and ongoing support work.
Read guideHow to collect screenshots, browser details and console logs
A lightweight way to collect screenshots, technical environment and logs without dragging support out.
Coming soonHow to reduce useless support messages
Small process rules to reduce pointless pings and speed up bug resolution.
Coming soon