No. You do not need every word signed off before website design starts. You do need clear page goals, key facts and real sample content. Start with enough content to test the design, then finish the rest in planned stages.
Waiting for all the copy can hold up useful work. Designing the whole site with dummy text can hide gaps until the build is well under way. The better path sits between those two extremes.
Start with what you have, not a blank page
In our website planning work, we check what content exists, what can be reused and what must be sourced. We also ask who will write the first draft. Those are separate tasks, and each needs a place in the plan.
A folder full of files is a useful start. It does not mean the content is ready for the new site.
A report may hold the right facts but need a short web page to explain them. A photo may look great but leave no room for a heading. An old service page may describe an offer you no longer provide.
Review the content against the new site's goals before you move it across.
Before design: agree on the job of each key page
For each main page, write a short note that covers:
- Who is this page for?
- What question should it answer?
- What facts or proof does the reader need?
- What should they do next?
- Who can check that the content is true?
Then draft the main message and gather the facts that support it. These do not need to be polished. They do need to be real.
For example, a service page may need to explain who can use the service, where it runs and how to get help. If those facts are missing, a neat layout will not solve the problem.
During design: use real content on a small test set
You do not need to finish every page at once. Choose a small set that covers the main page types.
That might be the home page, one service page, a long resource and an enquiry page. Include a page with a long title or a lot of facts. The aim is to test the layout, not just show its best side.
Test the design with the content people need, not just the content that fits.
Use real headings, likely text lengths and the intended next step. Check the page on a phone as well as a large screen.
A simple example: a row of three short service names may look balanced. Real names may be much longer. Testing them early shows whether the cards still work.
Keep content in useful groups. The W3C guide to content structure explains how paragraphs and lists help people make sense of a page. Use numbered steps for a process, not one large block of text.
Know which gaps can wait
Not all missing content puts the same work at risk.
Pause the affected page if the gap could change its layout or purpose. This may be a missing service list, an unknown form flow or a key fact still being checked.
A small wording change can often wait. A short bio may also wait if the team has agreed on its length, fields and image shape.
Mark each gap with an owner and a due date. Be clear about what work it blocks. A missing page should not stop unrelated work, but it should not quietly become someone else's problem.
Plan images alongside the copy
Photos and video are part of the content plan, not a final layer.
Decide what each image must show. Check the crop, quality and right to use it. For photos of people, check the required consent before they go into the site.
If you need a shoot, our guide to briefing a website photographer will help you build a shot list. This gives the shoot a clear purpose and the design team useful assets.
Before launch: review the page, not just the document
A signed-off document is not the same as a checked web page. Copy can be missed during entry. Links can point to the wrong place. A heading that reads well in a document may be hard to scan on a phone.
- Check the facts and remove all dummy text.
- Check headings, lists and links in the built page.
- Check images, captions, consent and text alternatives.
- Test key tasks, including forms, through an agreed test plan.
- Get final approval from the named content owner.
Then set a review date. Our guide to website governance explains how clear owners and regular checks keep content useful after launch.
Ask for a content plan, not just a launch date
Before the project starts, agree who will audit, write, check, enter and approve the content. Ask which pages must be ready for each design stage. Confirm what is included in the agreed scope.
Content and design should inform each other. The goal is not to finish one in full before starting the other. It is to make the right content decisions before they become costly design changes.
If you are planning a rebuild and are unsure how much content to prepare, talk to IGNITE about your content and website plan. We can help you work out what is needed first and what can move alongside the design.