Review the first design against the work you want to attract and the decisions a prospective client needs to make. Agree what the preview demonstrates, try a few realistic visitor tasks and return one clear set of comments. Each comment should identify the page, the problem and why it matters. Keep unresolved facts and requests for additional work visible before approving the next stage.
The first website preview often brings several opinions into the same conversation. A director wants the projects to feel more prominent. An estimator wants enquiries to reach the right person. Someone else prefers the colour scheme on another site. Those concerns need different responses, and a list of disconnected comments can leave the designer guessing which decision matters most.
This guide is for construction owners, marketing leads and architectural practices reviewing a commissioned website before the build is complete. It explains how to make that review useful without having to become a designer yourself.
01
Agree what you are reviewing
Ask the agency to describe the preview before circulating it. Is it a proposed page structure, a static design, a clickable prototype or a working development site? Which pages and interactions are ready for comment, and which are still being prepared?
A static image can show the intended hierarchy, imagery and visual treatment. It cannot demonstrate whether a menu opens properly, how a form behaves or whether an enquiry reaches your inbox. A working preview may demonstrate those features, but some links or integrations may still be temporary. Record the limits rather than treating every unfinished item as a fault.
Use one identified version for the review. Keep its link or filename, the review date and the decision the agency needs from you. If the design changes while colleagues are commenting, ask which version their comments refer to before combining them.
At Crafters, we agree the structure and design with you before building the approved pages. The proposal sets out the review milestones for your project. Our website-design service explains that process and the information your team supplies.
02
Start with the agreed audience and work
Put the original brief beside the preview. Write a short reminder of the services, project types and working areas the website needs to explain. Then consider what a visitor can reasonably understand from the opening, navigation and first relevant project.
For a specialist subcontractor, the important distinction might be between a complete package and one part of the installation. An architectural practice may need to explain its role on an illustrated project. A contractor may want more commercial refurbishment work while its current image library mainly shows homes. These are positioning and evidence questions as well as visual ones.
Flag a mismatch precisely. If the opening suggests a service you do not provide, identify the wording and supply the correct scope. If the photographs favour work you are moving away from, explain which approved projects would be more representative. The designer can then consider the page as a whole.
If the underlying brief is still unsettled, resolve that before approving a design around it. Our construction website planning guide can help you set those priorities.
03
Give the preview a few practical jobs
Choose tasks that a prospective client would actually attempt. For example:
- Find whether the business takes on a particular type of project in the required area.
- Find a relevant completed project and establish what the business contributed.
- Find the appropriate way to discuss that work, including what information to prepare.
Where the preview supports it, ask someone who resembles the intended audience to try a task without showing them the route first. Note the point where they hesitate, misinterpret a label or cannot find the information. If only a static design exists, discuss what they would expect to do next and leave interaction checks for the working version.
The GOV.UK Service Manual guidance on usability testing supports observing people attempting realistic tasks and avoiding instructions that reveal the answer. A colleague's quick review can reveal a useful question, but it does not establish that the site works for every customer.
Keep an observation separate from a proposed fix. “I expected to find commercial projects here and could not identify one” gives the agency a problem to investigate. “Move this button up” gives a solution without explaining the need behind it.
04
Review the content that will carry the design
Check the actual service names, project descriptions and contact details as well as their presentation. Placeholder text and sample images should be clearly identified so nobody approves them as finished content by mistake.
Look at one representative project page with the intended material. Does the headline make sense alongside the images? Can a visitor distinguish your work from that of the architect, principal contractor or photographer? Are credits and any agreed publication restrictions carried through? If an image needs replacing, name the approved alternative and say who will supply it.
Longer content also needs a place in the review. A short sample project title may look comfortable where your real titles wrap over several lines. Ask to see a realistic example rather than rewriting every title simply to fit the first mock-up.
Keep factual corrections separate from copy suggestions. An incorrect location or an unapproved client quotation needs a clear correction or a hold. A preference for a different introductory sentence can be discussed with the wider page hierarchy in mind.
05
Check the working preview on a phone
If a working mobile version is available, follow the same visitor tasks on your own phone. Check whether the service explanation, project captions and enquiry route remain understandable in the narrower layout. Note the device and page when reporting a problem so the agency can reproduce it.
For example, a wide project photograph might lose the feature you wanted to show when cropped. Explain which feature matters rather than asking for every photograph to stay uncropped. The appropriate solution may be a different image or a different presentation.
Ask the agency how it will check keyboard use, readable text and form labels on the built site. W3C's Easy Checks introduces these kinds of accessibility checks and explicitly warns that a quick review is not a comprehensive assessment. A visual approval should not be recorded as an accessibility sign-off.
Do not send test enquiries through a working preview until the agency confirms where they go and how tests will be identified. Design review and verified enquiry delivery are separate checks.
06
Return one usable set of comments
Choose a person to combine the team's feedback and resolve conflicting instructions. This does not mean every specialist opinion disappears. It means the agency can see what the business has agreed and what still needs a decision.
Use a short record for each point:
- Page and version: the link or file being reviewed.
- Observation: what is wrong, unclear or missing.
- Buyer consequence: why it matters to the intended visitor.
- Evidence or material: the correct fact, approved asset or brief requirement.
- Decision needed: what the agency should consider or clarify.
- Owner: who can answer the remaining question.
Distinguish something required by the agreed brief from a new request. A missing agreed project gallery and a newly requested recruitment section involve different work. Ask the agency to explain any effect on scope, fees or the timetable before authorising the addition. The agreed proposal governs that discussion; there is no universal number of review rounds.
07
A hypothetical contractor review
Imagine a fit-out contractor reviewing a homepage and one project template. This is an illustrative example, not a Crafters client result.
The director's first note says, “Make the projects more prominent.” During the review, the team realises that the real concern is relevance: the opening shows a domestic kitchen, while the current priority is workplace fit-out.
The combined feedback becomes: “On homepage version 2, the opening image and first project suggest domestic work. Our agreed priority is workplace fit-out. We can supply the approved reception and meeting-room images from Project A. Please show how those could support the introduction and the route to the commercial project page.”
The estimator also wants visitors to upload tender documents. That feature was not in the agreed brief. The team records it as a separate request for the agency to scope, including the information required and who would receive it. It is not slipped into the design approval as a small visual correction.
The result of this review is an identifiable content decision and an open scope question. It is not evidence of better rankings or more enquiries.
08
Record what approval allows next
When the revised design is ready, return to the agreed comments. Confirm which have been resolved, which have an agreed later check and which prevent the next stage from starting. A short decision record can name the approved version, the pages covered, outstanding content, the approver and the next milestone.
Be explicit about the boundary. Approving the structure and visual direction does not authorise publication of unfinished copy, certify a live form or resolve an unanswered ownership question. Those matters need their own checks at the appropriate stage.
For the final operational review, use our construction website handover checklist. It covers the access, updates, enquiry checks and support responsibilities that follow the design and build work.
If you are planning a new site or replacing an existing one, send us your current website, the work you want to attract and any deadline. We can discuss the scope and the decisions your team will need to make along the way. Discuss your website project.

