Most website projects do not stall because of design. They stall because nobody can locate the final logo file, the homepage copy is still sitting in a draft email, and no one is entirely sure who is allowed to approve the last version. A website redesign checklist sounds like administrative housekeeping, but in practice it is the thing that protects the momentum you already had when you decided to rebuild.
What follows is a practical pre-kickoff list built from how website projects are actually scoped and delivered: the assets to gather, the decisions worth making early, and the questions that tend to surface in the first week. If you want the wider picture of what the work involves, you can review what a website project includes before the first call.
The Five Things A Website Project Actually Needs From You
Every rebuild depends on inputs that only the business can provide. When those inputs arrive late, the delay shows up in design revisions, development rework and a launch that drifts.
- Brand assets. Collect the current logo in its usable formats, the approved color values, the typography choices and any brand guidelines that exist. If the guidelines live in someone’s memory rather than a document, that is worth knowing before design begins, because it changes how many decisions get made from scratch.
- Content. Gather the approved service descriptions, the pages you know you need, and a short list of the questions customers ask most often. Just as important: name the person who can approve final copy. Content without an owner becomes content without an ending.
- Imagery. Decide whether you are supplying photography, product shots, team portraits and location images, or whether visuals need to be sourced, licensed or created. Both paths are workable; only one of them is discoverable at the last minute.
- Access. Domain registrar, hosting, CMS, analytics, search console, form tools, CRM and any advertising accounts connected to the site. Access issues are the most common cause of a launch that is technically finished but cannot go live.
- Approvals. Name one decision-maker per area, not a committee. A single approver for messaging, a single approver for design and a single approver for technical sign-off removes most of the back-and-forth that stretches a project.
None of these items requires technical knowledge. They require ten minutes of honesty about what exists, what is missing and who owns it.
Why Content Readiness Changes The Project Shape
A rebuild where the copy already exists and a rebuild where the copy has to be written are two different projects. In the first case, the work moves from structure to layout quickly: pages get templated, sections get composed, and review rounds focus on hierarchy, tone and conversion paths.
In the second case, content decisions come first. Every page needs a purpose, a primary audience and a next step before its layout can be designed, because the structure of a service page and the structure of a resource page are not interchangeable. That is also why content decisions affect the number of review rounds, the sequence of the launch and how much of the design system can be reused across templates. If the writing is not ready, design work either waits or gets built on placeholder assumptions that later have to be unpicked.
This is the reasoning behind a strategy-first process: audience research, messaging and page structure are settled before visual design is finalised. It is also where the Creaxiones Growth System™ framework comes in, as the method used to sequence those decisions rather than as a promise about what any single page will produce.
One useful distinction before kickoff: is this project a visual refresh or a broader change in how the brand presents itself? If that question is still open, it is worth deciding between a brand refresh and a full rebrand before design starts, not after the second revision round.
A Simple Way To Prepare In Two Weeks
You do not need a formal project management system to get ready. A short, focused window is usually enough if the work is split into three moves.
Start With An Inventory
List every page on the current site and mark each one as keep, rewrite, merge or remove. Add the pages that do not exist yet but should. This single list does more to shape a project than any mood board, because it tells you how much content is genuinely required.
Collect Assets In One Place
Create a shared folder with clear subfolders for brand files, copy documents, images and credentials. Assign an owner to each subfolder. Anything nobody owns during preparation will become something nobody owns during the build.
Agree The Approval Path
Write down who reviews what, and in which order. A short approval path with named people moves faster than a long one with unnamed stakeholders, and it prevents the situation where feedback arrives after work has already moved forward.
Questions That Come Up Before Kickoff
How Much Copy Do We Need To Write Before Design Starts?
Enough to define each page’s purpose, its main message and its primary call to action. You do not need polished final paragraphs for every page, but you do need the substance settled, because layout follows meaning, not the other way around.
Who Should Be The Final Approver?
Whoever can speak for the business without needing to check with someone else. If that person is unavailable for long stretches, name a deputy in advance so reviews do not pause while a decision waits.
What If Our Photography Is Not Ready?
That is a planning detail, not a blocker. The important thing is to decide early whether visuals will be sourced, licensed, created or temporarily represented, since that choice affects the design direction and the sequencing of the build.
How Will We Know The Site Is Working After Launch?
By agreeing in advance which behaviours matter, such as form completions, quote requests, calls or bookings, and making sure the measurement setup is in place before the site goes live. If you are unsure which signals are worth tracking, it helps to understand what a conversion review covers before you commit to a larger program.
Do We Need To Hand Over Every Login?
You need to provide access, not transfer ownership. The accounts stay yours, and the practical requirement is that someone on your side can grant access when the work needs it and can confirm it again when the project is complete.
When You Are Ready, Talk Scope
Preparation does not need to be perfect before a conversation. It only needs to be honest. If you can describe your goals, what is currently getting in the way, which parts of the existing site must change and which pages matter most, that is already enough to scope a project usefully.
Send a short note with those details, and the first conversation can focus on the real decisions instead of on retrieving files. The work is strategy first and craft second, which is what we mean by Driven by Data. Powered by Creativity. To get started, request a proposal or contact the team and share where your website project stands today.
