How long does a website redesign take—and what causes delays?

A calendar connected to three project milestones.

“How long will it take?” is a reasonable question to ask before a website redesign. A useful answer needs more than a number of weeks.

The schedule depends on what is changing, how much content is ready, which systems are involved and how decisions will be made. Two websites with the same page count can require very different work.

Rather than offering a universal turnaround time, this guide shows what a realistic schedule should contain and where delays usually enter the process.

A date is only useful when its assumptions are visible

A provider may estimate a build on the assumption that approved copy, photographs and account access will be available at the start. You may assume those things will be sorted out during the build.

Both people can be acting in good faith while planning different projects.

Ask what the estimate depends on. Which inputs must you supply? How long is allowed for feedback? Are there partner teams whose availability affects launch? What happens if the scope changes?

The answer should distinguish active production from the time spent waiting for decisions and materials. A website can involve relatively little building time and still span a long calendar period if the approvals are spread out.

Map the project around decisions

A sensible plan has checkpoints. The labels can vary, but each should have an outcome and a person who can approve it.

CheckpointDecision or deliverableWhat it depends on
Discovery and scopeWhat is included and what staysGoals, existing-site review and key people
StructurePages, navigation and visitor routesService priorities and content inventory
Design directionApproved approach for key layoutsBrand assets, representative content and feedback
Build and contentWorking pages and agreed featuresApproved layouts, content and system access
TestingImportant journeys checkedWebsite build and partner configuration
LaunchApproval and deployment planTest results, access and responsible people
HandoverEditors can carry out agreed tasksTraining, documentation and support arrangements

Do not turn the table into seven equal blocks on a calendar. Some work can overlap. Other work needs a decision before the next part can proceed.

For example, entering approved product information can run alongside work on another page. Building a complex form before agreeing what data it must send is more likely to create rework.

The delays you can reduce early

Content without an owner

A request to “send the website content” can drift because nobody knows what is required or who should approve it.

Give each page or content group an owner and a due date. Mark what can be reused and what needs rewriting. Identify photography or specialist review that must be booked.

A missing paragraph and a missing product catalogue are different risks. Tell the agency which materials are uncertain so the plan can allow for them.

Feedback that arrives in fragments

One colleague replies on Monday, another on Thursday and a third reopens the direction the following week. The team keeps moving, but previous decisions keep changing.

Nominate someone to consolidate the comments. Agree when the people with approval authority will review the work. An unavailable approver is a schedule dependency, not an administrative detail.

Features added after design approval

A member area, new language or booking integration can affect page structure, permissions, testing and maintenance. Even when the addition looks small on the screen, the work behind it may be substantial.

Ask for the effect on scope and timing before accepting the addition. Keep a list of ideas that can be considered after launch.

Access arranged late

A developer may be ready to connect the CRM while the account administrator is away. The launch may depend on hosting access held by a previous provider.

Identify the owners of the domain, hosting, analytics and connected systems early. Arrange appropriate invitations securely. The first request for critical access should not arrive on launch morning.

What makes a migration take longer?

An established website may contain useful posts, files, products and search landing pages that need individual decisions.

Some content will move unchanged. Some will merge. Some will retire. Existing forms, redirects, tracking and third-party tools also need to be accounted for.

A larger content inventory does not always require a completely different design, but it does increase the work of checking and moving information. Ask whether the quote includes that work and who provides any migration decisions.

Where another SEO agency or IT department is involved, include its responsibilities and review dates in the project plan. Being ready on the website side does not mean every partner is ready to launch.

Build the schedule backwards from a real deadline

If launch must happen before an event or campaign, explain why the date matters. Then work backwards with the provider.

  • When must testing begin?
  • When must the content be approved?
  • When must the main layouts be approved?
  • Which features are essential for that date?
  • How much time is reserved for corrections?
  • Who must be available for launch?

The solution may be a smaller first release. It may also be moving the launch date. Agreeing an achievable scope is more useful than keeping an attractive date attached to an impossible plan.

An illustrative schedule problem

Imagine a business planning a new service campaign. This is a made-up example.

Its website layouts are approved, but the new service pages still need input from three department heads. A CRM partner is also waiting for a decision about where enquiries should go.

Adding more developers would not resolve either dependency. The useful actions are to appoint a content approver, collect the missing information and agree the enquiry routing.

The example shows why “speed up the build” is not always the right response to a delay. First identify what is stopping the next decision.

Questions to ask before accepting a timeline

  1. What exactly is the completion milestone: staging ready, launch ready or live?
  2. What do you need from us before work starts?
  3. Which content deadlines must we meet?
  4. When will we review the structure and design?
  5. How will additional requests affect the schedule?
  6. What will be tested before launch?
  7. Which partner teams need to be involved?
  8. What is the fallback if an essential dependency is late?

Keep the answers with the scope. If something changes, update the plan instead of quietly treating the old date as a promise.

Start with a schedule your team can support

You do not need every detail settled before a conversation, but be candid about your team’s availability and the materials still missing.

Our website redesign service explains the work we can help with, and our website investment page explains what shapes a project. Tell us about your website and any deadline it needs to meet.

Leave a Reply

Your email address will not be published. Required fields are marked *