Before You Commission a Business Website: A Practical Preparation Checklist

c
ceofounder
5 min read 37 views
Before You Commission a Business Website: A Practical Preparation Checklist
Website Planning

Before You Commission a Business Website: A Practical Preparation Checklist

A short preparation exercise won't answer every design question — but it makes the whole project easier to scope, quote and finish.

A website project can stall before the first page is built. The owner expects the developer to “make it look professional,” the staff are unsure which services should appear, and essential photos or prices arrive one at a time. The result is slow approvals, unnecessary revisions and a website that reflects whoever spoke last rather than the organisation's priorities.

Start with the business job, not the page count

Write down what the website should help the organisation do. It might need to generate qualified enquiries, explain a complex service, help members find information, showcase completed work, or make it easier for people to contact a branch.

Choose one primary outcome and two supporting outcomes. Notice the difference:

✗ A preference

“We need a modern website.”

✓ A brief

“We need property owners to understand our services and request a site visit.”

Only the second version can guide content and design.

Gather the raw material

Prepare the organisation's approved name, contact details, service descriptions, opening hours, service area, leadership or team information where appropriate, and any credentials that may be displayed.

  • Approved name & contacts
  • Service descriptions
  • Opening hours
  • Service area
  • Team / leadership info
  • Credentials
  • Authentic photos
  • Logos in usable formats
  • Publishable examples of work
If a claim depends on a certificate, award, client result or testimonial, confirm it before it reaches the website. Missing material should be recorded as a task — not disguised with invented copy.

Agree who decides

Nominate one project owner and identify the people who must approve factual, legal, brand or technical details. Several colleagues can contribute ideas, but a single person should consolidate feedback.

Set realistic review windows and agree how changes will be submitted. This avoids receiving contradictory comments from five people after a page has already been approved.

Make the scope explicit

Discuss page types, forms, integrations, languages, content migration, analytics, email, training and post-launch support. Ask what is included, what is excluded, how revisions work, who supplies copy and images, and what the client must provide by each milestone.

Treat features that sound small — such as importing hundreds of records or connecting an existing booking tool — as requirements that need to be assessed.

Prepare for launch day

Decide who will verify contact information, test forms, review the site on real phones, approve the wording and keep access credentials. Confirm domain ownership, hosting arrangements, backups, security responsibilities and the way future changes will be requested.

A launch is a handover point, not the end of the organisation's responsibility for its website.

Rank requirements by launch priority

Separate launch-critical items from features that can safely wait. A working contact route, accurate service information and clear ownership are usually more important than a complicated animation or several optional integrations.

Record each request with its business reason, who benefits and how success will be checked. This makes trade-offs easier when budget or staff time is limited, and helps prevent late additions from quietly changing the project scope.

Keep a decision log

A short decision log can record the agreed navigation, page list, content owner, integrations and any deferred features. Include the date and the person who approved the decision.

If a new request contradicts a previous agreement, the team can discuss it deliberately instead of reopening the same debate repeatedly. A simple shared document is sufficient — the important part is that the project team can find the latest decision.

Define acceptance in practical terms

Before work begins, decide how the organisation will judge the finished site. Acceptance criteria should be testable and agreed in advance. They make the review more objective than asking whether a site “feels finished.”

  • Main pages display correctly on common phone sizes.
  • The enquiry form reaches the intended inbox.
  • Links work.
  • Key content matches the approved copy.

Plan who will supply each content item

A content tracker can list each page, required copy, image or document, its owner, approval status and deadline. Mark unavailable content clearly and decide whether the page should launch without it or wait.

Do not treat placeholder text as final copy. Content responsibility is often the hidden schedule risk in a website project, especially when several departments must confirm facts.

A practical way to prepare the project

1

Hold a short internal meeting to agree the audience, main website outcome and the person authorised to make final decisions. Write the answers down before discussing page design.

2

Create a content tracker for each launch page, including a content owner, required evidence, image needs and review date. Mark uncertain claims and missing materials openly rather than filling the gaps with assumptions.

3

Ask the developer to turn the brief into a scoped proposal with inclusions, exclusions, delivery dependencies, acceptance tests and handover responsibilities. Review any optional feature by asking which reader task it supports and whether it is necessary at launch. Revisit the scope before approving changes.

Example

A Nairobi training firm might prepare its course list, target learners, instructor bios, sample training materials, enquiry questions and a decision-maker for approvals before a project begins. That preparation makes it easier to distinguish essential launch content from improvements that can wait for a later phase.

Frequently asked questions

How detailed should a website brief be?

It should be detailed enough to agree the audience, outcomes, scope, content responsibilities and acceptance checks. Technical choices can be refined with the developer.

Can some content be added after launch?

Yes, provided the launch version still communicates the core service accurately and the later work has an owner and deadline.

Action checklist

  • Primary business outcome and intended audience are written down.
  • Content owner and final approver are named.
  • Logos, images, service details and evidence have been checked.
  • Required integrations and excluded work are recorded.
  • Ownership, training, support and launch checks are agreed.

Final thought

A useful website brief is not a long technical document. It is a shared understanding of the audience, business objective, content, scope and responsibilities.

Ready to scope your website properly?

Use this checklist to start a focused conversation with a developer. Stonehenge Digital KE's Portfolio & Organisational Website service is a relevant starting point for discussing scope and fit.

Explore the Portfolio & Organisational Website Service →
Share Written by ceofounder

Interested in Portfolio & Organisational Website?

Let's build this for your business

A professional, mobile-first website that makes your business look credible and gets found on Google.

Leave a Comment

Share Your Thoughts