The short answer: prepare decisions, not an optimistic date
Website projects often stall when the supplier cannot continue without a decision, an asset, access to a service or formal approval. Before commissioning the work, define the primary business goal, what belongs in the first release, who supplies each input, who can sign it off and how each milestone will be tested. Build the schedule around those dependencies afterwards.
That does not make every delay the client's fault. The supplier should break the work into understandable stages, flag risks, request inputs early and report exactly what is blocked. A better question than “when will it be ready?” is “what must happen before the next stage can start?”
Separate active work, waiting time and scope change
A project may be moving even when no finished screen is visible: research, content modelling and integration checks are real work. It is blocked when a task cannot proceed until a specific input arrives. A scope change is different again: it introduces a requirement that was not part of the accepted commission.
Use those three labels in status reports. “Design in progress” describes active work. “Waiting for photographs approved by the business” identifies both a blocker and its owner. “An appointment-booking system has now been requested” opens a decision about scope, cost and sequence. Treating all three as generic delay encourages blame without creating a next action.
- In progress: there is an assigned next action that can be completed.
- Blocked: a named input is missing and somebody can supply it.
- Change: the request alters an agreed feature, integration, content item or acceptance condition.
Give five decisions a clear owner
MDN advises website teams to begin with the outcome, prioritise their goals and turn them into actionable steps. For a commissioning business, that means settling five areas before visual design or technology starts to dominate the conversation. Every detail need not be fixed, but a strategic question should not arrive as a surprise halfway through the build.
Each decision needs somebody to prepare the information and somebody authorised to approve it; one person may hold both roles. If several colleagues need to comment, agree who will combine their feedback into one response. A supplier should not be expected to choose between contradictory instructions from the client's team.
- Outcome: the visitor action that matters and the offer it leads to.
- Scope: the pages, languages, forms and integrations included now—and the exclusions.
- Content: ownership of facts, copy, images, permissions and factual review.
- Operation: who will handle enquiries and maintain information, accounts and external services.
- Acceptance: the journeys, devices and states that must work before a milestone is approved.
Plan dependencies rather than collecting dates
A useful schedule can be expressed as relative milestones: discovery, content map, design, build, content entry, testing, corrections and launch. For each milestone, record the required input, owner, observable output and condition for moving on. This reveals a delay without pretending there is one universal delivery time for every website.
Not every stage must be strictly sequential. A supplier can prepare components while the business reviews copy, but laying out twenty pages around provisional content creates an obvious rework risk. MDN describes sequential processes, which favour more stable early specifications, and iterative processes, which handle change by shifting priorities. Neither removes the need for decisions.
- Discovery ends with accepted goals, audience, scope and exclusions.
- Content is ready when final assets have named owners and versions.
- Design approval covers journeys and states, not just an attractive homepage.
- Build completion makes the agreed functions available for testing.
- Acceptance records evidence for the agreed journeys and separates future improvements.
Worked hypothetical example: an air-conditioning website
Consider a fictional heating and air-conditioning company commissioning a website to generate quotation requests. The initial scope contains a homepage, three service pages, coverage areas, project examples and contact. During discovery, someone suggests online booking for site surveys, but the business has not defined availability rules or assigned anyone to manage exceptions.
The practical decision is to separate the outcome from the proposed feature. The first release can explain the services and collect requests with location, property type and contact preference. Automated booking moves to a later stage until the company has agreed opening slots, coverage, cancellations and operational ownership. The idea is not dismissed; it simply no longer blocks the whole launch.
Before design, the company appoints one person to validate commercial facts and another to provide photographs with permission to use them. The supplier produces the page map, proposes the enquiry journey and records which copy it will write. Acceptance covers sending the form on mobile and desktop, receiving it at the agreed mailbox, seeing understandable errors, navigating with a keyboard and confirming that published facts match the approved version.
If photographs arrive late, the tracker shows which pages can use placeholders and which must wait. If booking returns during the build, it is treated as a change: the team can replace another feature, schedule a later phase or revise the timeline. The example does not assume change can be eliminated. It makes the effect of change a deliberate decision.
What a proposal should reveal about delivery risk
A proposal cannot predict every incident, but it can explain how the project will be governed. Look for milestones with observable deliverables, responsibilities on both sides, a review mechanism, a change process and external dependencies. A page list paired only with a final date hides too many decisions.
Agree how approval will be recorded as well. One message naming the accepted version prevents old designs and copy returning to review. When an input is missing, the status should explain what can continue, what must stop and what the likely consequence is. That protects the business and supplier from expectations changing invisibly.
- What information or access is required before each milestone?
- Who supplies copy, and who confirms the underlying facts?
- What is a correction, and what becomes additional scope?
- What will be tested before design, functionality and launch are accepted?
- How will the sequence change if an external dependency is unavailable?
Bring quality and accessibility into the plan
Leaving all quality checks until the end creates a false finish: the website looks complete until testing uncovers unresolved decisions. MDN recommends considering accessibility from the start and including it in the testing regime. web.dev likewise encourages teams to communicate states, labels, focus order and alternatives in the design handover instead of leaving developers to infer them later.
For the commissioning business, this can become a concise set of acceptance criteria: relevant browsers and screen sizes, forms and messages to test, content requiring an alternative, and the person who validates business data. You do not need to write an exhaustive technical specification. You do need observable outcomes. Regulatory requirements vary by service and context, so seek suitably qualified advice where they apply.
When professional help earns its place
You can prepare goals, owners, available content and priorities internally. Professional help is useful when those inputs are difficult to turn into a testable scope, when the website connects to existing systems, when several stakeholders must approve work, when data or URLs are being migrated, or when design, development, content, accessibility and ongoing operation need coordination.
Useful project support should not merely add meetings. It should turn ambiguous choices into milestones, expose dependencies and offer alternatives when an input is missing. Before accepting a date, ask the supplier for a map of who provides what, in which order and with what evidence the work will be considered complete. That is more valuable than a calendar containing only launch day.
Sources and documentation
- MDN: How do I start to design my website? ↗
- MDN: Workflows and processes ↗
- MDN: What is accessibility? ↗
- web.dev: Design and user experience ↗
Content created with AI assistance. Check the sources, date and scope of each guide.