When is an interactive architectural project tour worth commissioning?

Open a project page and imagine seeing the building for the first time. A photograph might show a room beautifully without explaining where it sits, how it connects to an extension or which part of the work your team delivered.

Choose one of those gaps. “Show how the new living space connects to the original house” is a more useful objective than “make the page interactive”. It suggests which views and explanations to include, and gives you something concrete to assess later.

Keep the project introduction outside the tour. Visitors should be able to understand the brief, your contribution and the next step without learning a new interface. Our guide to writing a construction project case study can help prepare that account.

Ask an agency to explain which format answers the question using the material available. The word “walkthrough” can describe quite different experiences, so agree what the visitor will actually be able to do.

• A gallery with a labelled plan may be enough when visitors need to locate a small number of photographs.
• A room-by-room photo tour can let them choose an area and see the relevant views in their own order.
• A film can guide them through an explanation where the sequence matters more than personal exploration.
• An interactive model can help explain how spaces relate, provided its level of detail and limitations are clear.

These are options to assess, not a progression in which the most elaborate treatment is always best. Ask what each additional feature helps the visitor understand. If the answer is unclear, leave it out of the first version.

You can explore the distinctions on Crafters' architectural walkthroughs and interactive project tours page. Its Old Till House example is an interactive concept by Crafters, using architecture by Hayward Smart Architects and photography by Richard Chivers. The model is an interpretation for presentation, not a measured survey or architect-verified construction model.

Prepare a small, approved selection of photographs and the relevant plan or drawings. Record which project stage each file represents, who supplied it and any required credits. Mark material that is awaiting permission or factual confirmation.

Check that the photographs and plan describe the same version of the project. A photograph taken after a layout change may not match an earlier drawing. Someone who knows the building should resolve the difference before it becomes part of the tour.

Then ask the agency to identify gaps. Does the collection show how two rooms connect? Are all the proposed viewpoints supported by supplied material? Would an unfamiliar visitor mistake an illustration for a photograph of completed work?

Agree which details may be interpreted, which must follow approved information and which should be omitted. If a proposal needs a measured survey, new photography or verified modelling, those requirements need their own scope. An interactive presentation should not quietly take on the role of technical design information.

Ask whether the proposal can begin with one representative section: perhaps a plan with two connected rooms and a few photographs. Agree the cost, deliverables and decision point for that stage. It does not need every animation or finish to reveal whether the idea is useful.

Use that first version to answer practical questions:

1. Can a new visitor work out how to begin without an explanation from the designer?
2. Can they find the space relevant to the project question?
3. Can they tell whether they are looking at photography, a drawing or an interpretive model?
4. Can they return to the project page and find the enquiry route?
5. Does the experience still make sense on a phone?

Give a colleague who was not involved in the design a specific task and watch where they hesitate. Ask them to explain what they understood afterwards. Treat this as a useful editorial check, not proof of how every prospective client will behave.

An architectural practice has approved photographs of a completed extension, a ground-floor plan and permission to publish both. It wants prospective clients to understand the connection between the existing kitchen, the new living area and the garden. This is an illustrative scenario, not a Crafters client result.

The first test could show a simple plan with three labelled views. Selecting a view reveals the matching photograph and a short explanation. The practice checks that the locations and captions are accurate; a colleague tries to follow the route without help.

If that version answers the question clearly, the practice may have no reason to commission a full model. If the relationship between levels remains difficult to explain, it could discuss an additional view with the agency. That is a specific production decision, with a reason and an approval point.

Review the tour in the page where it will appear, including on a phone. Check the labels, controls, loading behaviour and route back to the rest of the website. A successful demonstration on a large screen does not answer those questions.

Include keyboard operation in the requirements. W3C's guidance on keyboard accessibility explains that people need a way to operate content through a keyboard interface, with a limited exception for functions that depend on a movement path. Ask the developer how visitors will choose views, close panels and leave the experience without a mouse.

Keep an ordinary project summary and useful images available alongside the interactive element. Agree how the information will be presented if the tour cannot load or a visitor chooses not to use it. This is part of making the project understandable; a short buyer check does not establish that the whole website meets an accessibility standard.

A tour needs a home and a responsible person. Before accepting a proposal, ask where it will be hosted, how it connects to your website and what ongoing charges or third-party services are involved.

Also agree who can change captions, replace an image or correct a plan. Separate routine content updates from changes that need the original developer. If you want editable files or the ability to move the experience later, include that in the agreed handover instead of assuming it is part of delivery.

Write down the supported devices, review process, revision allowance and responsibility for checking future changes. Keep image credits and permissions with the approved files. For unfinished projects, name the person who will confirm when a design revision makes the presentation out of date.

At review, return to what the visitor needed to understand. Check that the published experience answers it and leads naturally to the project information or a relevant conversation.

Usage data can help identify whether people open the tour or choose particular views, where suitable measurement is agreed. Those actions do not establish that someone understood the project, became a suitable enquiry or appointed the practice. Combine them with direct feedback and the enquiries you actually receive.

To discuss a possible tour, send Crafters a link to the project page, a representative sample of approved material and the question you want visitors to answer. Discuss your project presentation, and we can agree an appropriate format and production scope.