taiaio+INDEPENDENT WEB DESIGN

03 / A FOCUSED FIX

One problem.
A clearer
starting point.

A link goes nowhere. A section does not fit on a phone. A page still describes an old offer. Describe the specific problem so the next step can be checked, rather than guessed.

Describe a website issue See what to include

No technical vocabulary required. This guide is not a live diagnosis or an emergency-support service.

FICTIONAL ISSUE REPORT

Page: /services

Expected
The “Ask about a project” link opens the enquiry section.
Actual
It goes to a page that cannot be found.
Steps to reproduce
Open Services → select “Ask about a project” → see the missing-page message.
Illustrative only. No real website has been tested or repaired here.

SMALL REQUEST, CLEAR BOUNDARIES

A focused change,
not a blind promise.

Some issues are contained. Others reveal a dependency or a larger problem. Feasibility and the extent of the work need review before a fix is agreed.

DESCRIBE THE CHANGE

A specific visible issue

  • A link points to the wrong public page.
  • Text, hours or a service description needs updating.
  • A particular section overflows or overlaps on a phone.
  • A form shows an unclear error or next step.

These are examples of requests to investigate, not a promise that every issue can be solved on every platform.

FLAG THE DEPENDENCY

Something behind the page

  • A third-party booking or enquiry tool is involved.
  • The issue appears only after signing in.
  • It affects several pages or appeared after an update.
  • A new feature would change how customer information is handled.

Say that a dependency exists. Do not share the login or private records in the initial enquiry.

HELP MAKE THE ISSUE REPEATABLE

What happened,
and where?

Use what you know and leave the rest as unknown. You do not need to test every browser or diagnose the cause yourself.

Use the issue-report worksheet
  1. The public page. Include its address, without private tokens or account links.
  2. The steps. What did you select or enter just before the problem? Use made-up, non-sensitive values if an example helps.
  3. Expected and actual behaviour. Say what you thought would happen and what happened instead.
  4. Your setup. Phone, tablet or computer; browser name if known; whether it happens every time or sometimes.
  5. The impact. Who is affected, what cannot be completed, and any real deadline. Do not include customer identities.

A FICTIONAL WRITING EXAMPLE

More useful than
“the site is broken.”

“On the public Services page, selecting ‘Ask about a project’ opens a missing-page message. I expected to reach the enquiry form. It happens each time on my phone in Safari. The main navigation’s contact link still works.”

Illustrative report, not a real customer enquiry or a diagnosis.

YOUR NEXT STEP

Start with one clear example.

Describe the problem in the existing enquiry form. A worksheet is optional; sending a short summary is enough to begin a discussion about fit and scope.

An enquiry starts a conversation. It does not book work, accept an estimate or take a payment.

Request a tailored quote