Skip to main content
Back to blog
3 min readBy Lantern Team

Bug Tracking for Web Design Agencies: The Difference Between a Bug and a Design Opinion

Web design agencies face a specific challenge: clients use 'bug' to mean anything from a broken layout to a colour they've changed their mind about. Here's how to handle real bugs professionally without design feedback getting mixed in.

  • bug tracking
  • web design
  • agencies
  • client communication
  • design

Web design agencies know a particular type of client email. It arrives after launch: "There's a bug on the homepage — the background colour looks a bit dark." That's not a bug. That's a design preference. But by the time you've had the conversation about what counts as a bug versus a change request, you've spent 20 minutes that weren't scoped.

The boundary between "bug" and "design opinion" is one of the most common friction points for design agencies managing client sites. A proper bug tracking system helps draw that line — because structured bug reports make it immediately clear whether a client is describing something broken or something they want changed.


What "Bugs" Look Like for Web Design Agencies

Design agencies tend to see a mix of legitimate bugs and scope-adjacent requests:

Actual bugs:

  • Responsive breakpoints that don't hold — the design looks correct on desktop but collapses unexpectedly on certain screen sizes
  • Font rendering differences across browsers — a typeface that displays correctly in Chrome but falls back incorrectly in Safari
  • Image compression artefacts or lazy loading that breaks the visual quality on specific devices
  • Animation or interaction bugs — a hover state that sticks, a scroll-triggered animation that fires twice

Things that arrive as bugs but aren't:

  • Colour or typography preferences the client has reconsidered post-launch
  • Layout changes the client wants but wasn't in the original brief
  • Content decisions ("this text feels too small") masquerading as technical reports

A bug tracking tool with video reports makes this distinction clearer. A client who is genuinely looking at a broken layout will show you something objectively wrong. A client with a design preference will describe something subjective. Video surfaces the difference faster than email.


How Lantern Works for Web Design Agencies

Loom video replaces "it looks wrong." Visual bugs — misaligned elements, broken responsive layouts, rendering differences — are almost impossible to diagnose from a text description. Video shows you exactly which element, at which breakpoint, in which browser. You see what they see.

Browser and device captured automatically. Design agencies need to know whether a visual bug is happening in Chrome on Windows, Safari on iPhone, or Edge on a 4K display. Lantern captures this at submission — no asking.

Client portals with clear structure. Each client submits through their own portal. The submission form helps clients articulate what's actually wrong — which keeps design feedback out of the bug queue, or at least labels it clearly.

Widget via script tag. For non-WordPress, non-Umbraco sites — static builds, custom CMS implementations, Webflow exports — Lantern's widget works via a single script tag added before </body>. No CMS-native session gating, but the widget can be shown or hidden with CSS targeting your design tool's admin interface.

Multi-client dashboard. All clients, all open bugs, one view — filterable by status and urgency.


Pricing

The Individual plan at £12.50/month suits solo designers or small studios managing up to 5 client sites. Includes a 14-day free trial, no credit card required.

The Team plan at £30/month covers unlimited clients and team members — right for design agencies with a growing portfolio of live sites under management.


Start your free trial →


Related: How to get better bug reports from clients · Bug tracking for small web agencies

Try Lantern free for 14 days

Simple bug tracking for agencies. No credit card required.