WEBSITE BRIEF CHECKLIST

What should you prepare before requesting a website quote?

You do not need a technical specification. A useful brief explains the business, the customer action, what already exists and which decisions still need help.

BUSINESS AND CUSTOMER

Explain the commercial job first.

These answers determine the page structure more than a list of preferred effects or features.

Offer

List the real services or product groups, important differences, starting prices where appropriate and what is not offered.

Audience and market

Describe who buys, the language they use, the real countries or service areas and any important business or consumer distinction.

Primary action

Choose the most valuable next step: call, enquire, request a quote, book, buy, register or visit a location.

Current friction

Explain where customers become confused and where the team repeats work, loses information or waits for missing details.

Evidence

Gather genuine reviews, work examples, qualifications, policies or process details that can be published and verified.

CONTENT AND FUNCTION RULES

Collect examples and decisions, not just a feature list.

For each requested function, describe what the customer does, what the business receives and who is responsible afterwards.

Page and content inventory

List existing pages, copy, images, documents and languages; mark what can be reused, rewritten or removed.

Enquiry rules

Note the questions, files, urgency, service areas and qualification rules needed for a useful response.

Booking rules

List services, durations, staff, locations, availability, preparation, cancellation and payment conditions.

Sales or account rules

Define products, options, fulfilment, taxes, refunds, customer roles and the information visible after sign-in.

Legal and consent material

Identify the business details, privacy wording, terms and regulated claims that require the client or a qualified adviser to approve them.

ACCESS, OWNERSHIP AND DELIVERY

Prepare safe access and a person who can approve decisions.

Do not paste passwords, recovery codes or payment details into a general brief. Create named access only after the project route is agreed.

01

Domain and email ownership

Identify the owner, provider, renewal date and current administrators without sending secret credentials.

02

Existing website and data

Record the current address, content system, forms, analytics, redirects and data that must be preserved or exported.

03

Decision and content owners

Name who approves scope, brand, copy, legal material and launch, with one route for consolidated feedback.

04

Timing and dependencies

Separate a preferred date from fixed events and list photography, copy, integrations or approvals that can delay launch.

05

Budget and ongoing responsibility

Give a realistic working range and decide who will manage hosting, updates, backups, support and future content.

COMMON QUESTIONS

A few useful things before we start.

Must all content be finished before requesting a quote?

No. State what exists and who will create the missing material. Content responsibility and readiness still affect scope and timing.

Should I send administrator passwords with the brief?

No. Identify the systems and owners first. Use secure, named access after the project and required permissions are confirmed.

What if I do not know which functionality is needed?

Describe the customer action and the current manual process. A suitable simple route can be recommended from that information.

YOU DO NOT NEED A TECHNICAL SPECIFICATION

Turn plain business answers into a structured starting brief.

Review and edit the summary before it is sent to JAMT for a manual scope check.

Scroll to Top