Website project planning FAQ
TL;DR: Website project planning starts with the audience, task and business goal. Share the existing site, content, required functions and constraints. Agree on scope, responsibilities and launch checks before committing to a delivery plan.

Photography by LYCS Architecture / Unsplash
Introduction
Website project planning defines what a website must do, who it serves and what the team needs to deliver it. You can start with a clear problem and a few examples rather than a finished specification. This FAQ explains what to prepare and which decisions to make together.
What belongs in the brief?
A useful brief names the audience, their main tasks and the business goal. Include your current website, the pages or functions you expect to need, and any known constraints. Explain the problem before prescribing the solution.
Who makes the decisions?
Identify who supplies content, who reviews the work and who can approve a decision. A clear point of contact makes feedback easier to resolve when several stakeholders are involved.
- Project owner: brings the brief, dependencies and feedback into one place.
- Content owners: supply and approve the copy, imagery and product information.
- Design and development leads: explain options, constraints and the work required.
- Reviewers: assess the proposed experience against the agreed audience and tasks.
- Final approver: resolves conflicting feedback and confirms important decisions.
How is scope agreed?
Discuss the content, journeys, integrations and launch requirements together. Record what is included, what is assumed and what needs further discovery before estimating the work.
Define the audience and the main journeys
Name the people who need to use the website and the tasks that matter to them. A potential client may want to assess a service, see relevant work and make an enquiry. A returning customer may be looking for a specific product or document. Those journeys help determine the information architecture.
Choose priorities instead of treating every possible audience need as equal. Describe what a successful journey should make understandable and where the current experience causes difficulty. These decisions create a shared basis for page structure, content and the first prototype.
Bring content and technical constraints into the brief
A design depends on the material it needs to present. Identify who will prepare service descriptions, product information, photography and case studies. Review whether the content already exists, needs editing or needs new work. Waiting until the end to resolve it can leave the page structure disconnected from the actual message.
Discuss integrations and operational requirements at the same stage. Explain what the enquiry flow must do, which systems need to connect and who will maintain content after release. Be precise about the actual behaviour: an email draft, a form submission and a booking flow have different requirements and expectations.
Use tangible work to resolve uncertainty
A brief describes the intention; a sketch or prototype helps the team examine it. Walk through an important task and review whether the proposed information and controls support it. Keep the level of detail appropriate to the question, so the team can change direction without treating every visual choice as final.
Record the decisions and the reasons behind them. Feedback becomes easier to act on when people can connect a proposed change to the audience, task or constraint. A shared decision record also helps new contributors understand why the current approach was chosen.
| Artefact | Primary purpose | Useful review question |
|---|---|---|
| Project brief | Agree on purpose, scope and constraints | Are we solving the same problem? |
| Wireframe or sketch | Explore information and page structure | Can someone find what the task requires? |
| Prototype | Examine a proposed interaction | Does the journey make sense when used? |
| Content plan | Define information and ownership | Who will prepare what the site needs? |
What should we prepare?
Bring the available information into the first conversation. Mark missing material and uncertain requirements so the plan can account for them.
- Write a short project goal. Describe the change you want and who it should help. Include the business context that explains why the work matters now.
- List the priority journeys. Name the main tasks the first release must support. Use them to distinguish essential content and functions from ideas that can be reviewed later.
- Review existing material. Collect current pages, assets and examples of customer questions. Identify what can be reused, what needs editing and what still needs to be created.
- Assign decisions and contributions. Agree who supplies content, gives feedback and approves each stage. Make review responsibilities practical for the people involved.
- Discuss constraints openly. Share timing, budget and integration requirements early. Use those constraints to discuss a realistic release scope rather than leaving them to emerge during the build.
- Plan the release and the next review. Define what needs checking before launch and who maintains the site afterwards. Decide what real use should help the team learn next.
What causes avoidable delays?
Late content, unresolved approvals and changes to required functionality can affect delivery. Make those dependencies visible and agree on how changes will be reviewed.
- Starting with a list of visual references without explaining the audience or the task.
- Estimating the project by page count while leaving content, integrations and review responsibilities undefined.
- Using placeholder copy until the final stage, then discovering that the real message needs a different structure.
- Collecting feedback from several people without agreeing how conflicting priorities will be resolved.
- Treating launch as the end of ownership instead of planning content maintenance and later improvements.
Frequently asked questions
What should a website brief include?
Include your audience, business goal, main visitor tasks, current website, expected pages and required functions. Add available content and any known timing, budget or integration constraints. Mark assumptions that still need discovery.
Do we need a finished specification?
No. Start with the problem and examples of what people need to do. The first conversations can help define the scope and identify the research or technical review needed before a detailed specification.
What affects the project cost?
Content volume, custom functionality, integrations, design requirements, migration and testing all affect the work. A shared scope gives an estimate a clear basis. Review new requirements against that scope before adding them.
How is the timeline agreed?
The plan depends on the scope, content readiness, integrations and review process. Share your target launch date and approval constraints early. Agree on dependencies and milestones before committing to a schedule.
Who supplies the website content?
Agree on responsibility for copy, images, product information and legal pages at the start. List what already exists, what needs editing and what needs creating. Assign an owner and review point for each part.
Can we keep our existing URLs?
Yes, when the old page still has an equivalent, keep its established URL. Where an address must change, agree on a permanent redirect. Check internal links, canonical tags and the sitemap against the final URL map.
What should we do about integrations?
List the systems the site must connect with and the tasks each connection supports. Confirm access, data requirements and ownership with the relevant teams. Resolve technical unknowns before treating the integration as agreed scope.
What needs checking before launch?
Review the agreed user tasks, content, forms, mobile layouts, accessibility and important redirects. Confirm responsibility for hosting, domain changes and ongoing updates. The launch checklist should reflect the site and its actual scope.
How do we start with Webbies?
Use the contact form or email sales@webbies.co with a short description of the project, your audience and your current website. Include any target date or budget you can share so the team can discuss an appropriate next step.
Conclusion
Start with the task, available material and constraints. A shared brief gives design and development a realistic basis for scope and delivery. Explore our services or send the outline of your project to begin.


