Help the visitor work out what to do next.

A visitor planning a private group activity needs to know whether the offer fits before choosing a date. For a hypothetical New Zealand operator replacing its website, that means describing the activity, the information needed to assess a group and the next step when a date is uncertain. We can plan the pages and enquiry together, then give staff a manageable way to keep them current.

Choose the languages with the task

If the organisation wants English and te reo Māori content, first decide which visitor tasks each version will support. The organisation supplies suitable language and cultural reviewers; a translation should be assessed in the finished page, including navigation, captions and form messages. We do not assume every organisation needs the same language scope.

Suppose an approved activity description changes while its translation is still under review. The editor needs an agreed choice: retain the last accurate version, hold the affected page or explain which information is available. Silently keeping an outdated promise would leave visitors making different decisions from different pages.

Keep useful existing links

We map the current activity pages, documents and enquiry addresses before replacement. A link saved by a group organiser should reach the relevant information or a clearly explained successor. The migration review includes the enquiry context and any third-party booking step, rather than just the new homepage.

Try the visitor and editor journeys

Using sample details, ask someone to assess the activity on a phone, request a date and recognise what remains unconfirmed. Then ask the intended editor to change one approved detail and arrange its language review. Those tasks help set the scope for design, publishing, accessibility and handover.

Bring the current address and one visitor question that takes too much explanation. Discuss the website journey →