Web Project Brief: ALLFORWEB’s Method for Success

A project brief is more than a feature list

Writing “modern, fast and professional website” is not enough. Those words describe an intention, not a result that can be verified. The brief must explain the problem, the people affected and the value expected.

For an SME, the objective may be to increase qualified quote requests. For an association, it may be to simplify registration, present activities and reduce repetitive questions. A measurable objective makes later trade-offs easier.

1. Summarise the context and problem

Begin with a page that makes sense without jargon: business activity, current situation, difficulties, opportunity and reason for the project. Describe existing tools and known constraints. If users mainly access the service by phone or internet connectivity can be unstable, record that reality from the beginning.

Also state what is outside the project. This prevents an interesting idea from suddenly becoming a contractual obligation halfway through development.

2. Define audiences and their journeys

List the main users and what each one needs to accomplish. A potential customer wants to understand the offer and contact the business. A member may want to renew registration. An employee may need to publish news without calling the developer.

Describe one priority journey for each audience—for example: arrive from Google, understand the service, review evidence, request a quote and receive confirmation. These journeys later become test scenarios.

3. Turn objectives into indicators

Select a few observable outcomes: qualified enquiries, completed forms, online registrations, time required to publish a page or fewer repetitive emails. Indicators do not guarantee success, but they stop the project being judged only by the colour of a button.

Record a baseline as well. Without a starting value, improvement is difficult to demonstrate.

4. Set the functional scope

Organise functions by priority: essential for launch, important but deferrable, and future ideas. For each feature, identify who uses it, required data, expected outcome and important exceptions.

• Main pages and navigation.
• Forms, notifications and consent.
• Search, member areas or payments where necessary.
• Languages, administrative roles and publishing workflow.
• Connections to CRM, newsletters, payments or other tools.

A focused and dependable first version is more valuable than a large unfinished system.

5. Prepare content before it blocks delivery

Identify every page, its owner, status and delivery date. Plan text, photography, video, logos, downloadable documents, translations and usage permissions. An image found online is not automatically free to use.

Ownership should name a person. “The team will provide the content” sounds comfortable until nobody knows who “the team” means.

6. Include SEO, accessibility, performance and security

These requirements should not appear the night before launch. Plan a coherent heading structure, descriptive URLs, meta descriptions, internal links and a monitoring approach using Google Search Console.

Accessibility includes contrast, keyboard access, alternative text, form labels and understandable error messages. W3C recommends integrating accessibility during planning and evaluating it regularly.

Define backups, updates, administrator access, form protection, data retention and recovery. Collect only necessary information and clarify who can access it.

7. Clarify budget, schedule and responsibilities

The budget should distinguish design, development, content, licences, hosting, maintenance, training and possible evolution. Include a proportionate contingency for identified risks instead of choosing a magical round number.

The schedule should expose dependencies: sitemap approval, content delivery, design, development, integration, testing and launch. State who decides, produces, is consulted and approves.

8. Define acceptance and launch

Acceptance criteria turn an opinion into a test. A form is accepted when it works on target devices, validates fields, sends notifications, protects data and displays a clear confirmation.

Prepare a checklist covering backups, redirects, indexing, analytics, forms, mobile display, links, performance, permissions and rollback. Launch should be an organised event, not a collective leap into the unknown.

The ALLFORWEB method in eight steps

1. Listen to stakeholders and restate the need.
2. Define objectives, audiences and indicators.
3. Map priority journeys.
4. Prioritise features and content.
5. Document constraints and quality requirements.
6. Estimate budget, schedule and responsibilities.
7. Approve the brief before production.
8. Update decisions throughout delivery.

Sources

• Google Search Central — SEO Starter Guide
• Google — Helpful, people-first content
• W3C WAI — Planning and managing accessibility
• WordPress — Official documentation