Tips & Tricks

A Website Bug Report Template Your Clients Will Actually Fill In

A copy-paste website bug report template for clients, a four-question short version, and which fields a feedback widget can fill in automatically.

A clipboard checklist next to a browser window, with a green line joining a form row to a spot on the page.
A practical field guide
In this article 7 sections

“The form doesn’t work.” No page, no device, no idea which of the four forms on the site they mean. So you send the client your bug report template, all twelve questions of it, and it never comes back.

The problem is rarely the client. Most bug report templates are written by developers for developers, and they ask things a client does not know and cannot find. Below is a website bug report template built the other way round: short, in plain words, and in an order a non-technical person can follow. After that, we look at which of its fields you can stop asking for at all.

Why most bug report templates go unfilled

Three things kill a template:

  • Length. Every extra field is a reason to put it off until later. Later usually means a phone call.
  • Questions the client cannot answer. “Browser version”, “viewport”, “console output”. Most clients do not know what these mean, and they should not have to.
  • Nothing to copy from. A blank form with no example leaves people guessing how much to write. Some write one word, some write an essay.

A good template asks only what the client knows better than you do: what they were doing, what they expected, and what happened instead. Everything else is either optional or something you can collect another way.

The template

Copy this into your review email, your project portal or a shared document. The fields marked optional can be skipped, and the note at the top says so, which makes the rest more likely to be filled in.

REPORTING A PROBLEM ON THE WEBSITE
Fill in what you can. Fields marked (optional) can be left empty.

1. Page address (copy it from the address bar):

2. What were you trying to do?
   Example: "Send the contact form with my phone number."

3. What did you expect to happen?

4. What happened instead?

5. Where on the page? Attach a screenshot and circle the spot.

6. Does it happen again if you try once more?
   [ ] Yes   [ ] No   [ ] Not sure

7. (optional) The steps, if you remember them:
   1.
   2.
   3.

8. What were you using?
   [ ] Phone   [ ] Tablet   [ ] Laptop or desktop
   Browser, if you know it (Chrome, Safari, Edge, Firefox):

9. (optional) When did it happen? Date and approximate time:

10. How much does it get in your way?
   [ ] I can't continue
   [ ] It's wrong, but I can work around it
   [ ] It's cosmetic

11. Your name and email, in case we have a question:

Two details matter more than they look. Question 2 comes with an example, because that shows how much detail you want. And question 10 replaces “priority” with a question about the client’s own situation: nobody picks “low priority” for their own problem, but most people will honestly tick “it’s cosmetic”.

The short version for email and chat

Sometimes a full form is too much, for example when a client pings you on Slack or WhatsApp about something they just noticed. Keep this four-line version ready to paste as a reply:

Thanks! To fix it quickly, could you send me:
1. The page address
2. What you did, and what happened
3. A screenshot with the spot marked
4. Phone or computer?

Four questions get answered. Twelve get postponed.

How to get clients to use it

A template only works if the client has it in hand at the moment they spot something. A few habits help:

  • Send it before the review starts, in the same email as the staging link and the review deadline, not after the first vague report.
  • Include one filled-in example. A real-looking report about a fake problem (“the Book a call button on the pricing page does nothing on my iPhone”) shows the expected level of detail better than any instruction.
  • One problem per report. Say it explicitly. A list of nine issues in one email is hard to track and easy to half-fix.
  • Say thank you for good reports. It sounds trivial, and it is what makes the next report just as good.

What a widget fills in for you

Now the other side. Look at the template again and count how many fields are about the environment rather than the problem: the page address, the device, the browser, when it happened, where on the page. Those are exactly the fields clients skip or get wrong, and a feedback widget running on the page can read them without asking.

Here is how the template maps onto a report sent through the Zorko widget:

Template fieldFilled in by the client (email)With the Zorko widget
1. Page addressCopies it, sometimes from the wrong tabAutomatic
2-4. What they did, expected, gotWrites itWrites it, in one message box
5. Where on the pageScreenshot plus circle, attached separatelyViewport screenshot with a pin; the pin’s position on the page is saved
6-7. Reproducible, stepsDescribes itCan record the screen instead, up to 3 minutes with voice, in desktop browsers
8. Device and browserGuessesAutomatic: browser, OS and device
Screen sizeAlmost never knownAutomatic: viewport size
9. WhenRemembers roughlyTime of the report, plus timezone
10. How badTicks a boxAI analysis suggests a type (bug, design, content) and a priority; your team decides
11. ContactTypes itOptional email field
Console errorsNeverAutomatic: last 10 errors and 10 warnings

The page’s referrer and language come along too. The full list is on the features page.

What remains for the client is the part only they can give you: what they expected, and what happened instead. That is the core of the template, and it fits in one message box next to a screenshot they have already marked. The widget cannot guess intent, so the client still has to write a sentence. It just no longer has to be eleven.

If you are unsure whether a still image is enough for a given problem, we covered when a screenshot is enough and when a video is better in a separate post.

Count it for your own projects

Take the last 20 bug reports you received from clients and check each against the template:

  • How many had the page address?
  • How many said which device or browser?
  • How many needed at least one reply before anyone could work on them?

Say 12 of 20 needed a follow-up question, and each round trip cost 15 minutes plus half a day of waiting. That is three hours of your time and several days of calendar time on 20 reports. If a project collects 60 reports, multiply by three.

Keep the template either way. It is useful for anything that reaches you outside the widget, for phone calls and for clients who prefer to write. For everything else, a tool fills in the fields you were chasing. If you are still comparing options, start with our guide to choosing a website feedback tool.

Try Zorko free on one project and compare its reports with your template.

FAQ

What is the most important field in a bug report?

“What happened instead?” paired with “What did you expect?”. A report that has both, plus the page, is usually enough to start. Everything else speeds things up but rarely decides whether the bug gets fixed.

Should clients write steps to reproduce?

Ask for them, but keep them optional. Most clients do not remember the exact steps, and a wrong list is worse than none. A short screen recording shows the steps more reliably than a written list.

Should clients set the priority?

Ask how much it affects them instead, as in question 10 of the template. Priority is a decision about your whole backlog, and the client sees only their part of it.

Can reports go straight to Jira or Trello?

Zorko has no native Jira or Trello integration. Each project can send new reports to a webhook, and a tool such as Zapier, Make or n8n can turn them into tickets. Reports can also arrive by email or in a Slack channel.

Zorko news in your inbox

Product updates and practical tips for agencies, about once a month. Nothing else.

Put it into practice

Give clients the right way to show what they mean.

Zorko keeps screenshot and desktop video feedback together with the page details your team needs to act.

Start free See how it works

Free includes 1 project and 10 feedbacks a month. No credit card required.