Day 4: Test your booking steps on a phone

Go from the course page to the booking summary without placing an order.

Open your course page on a phone and continue to the last booking summary you can reach without a binding action. After each click, check that the course, date and participant count carry over correctly. Allow about 20 minutes. Your result is one error or unclear step described well enough for the responsible person to find, correct and check again.

The course-page test from Day 3 ends at the next booking step. Today you continue from there; you can also run this case without completing the earlier exercise.

Choose the course, date and participant count for the test

Choose a course option, a date and a participant count. Record those details with the starting URL, device, browser and test date. Keep the selection consistent on your first pass. Changing several options at once makes it harder to tell which change produced the behaviour you observed.

Use a suitable test environment if a step already creates a reservation, message or booking. In a live journey, stop before such an action. You do not need to complete a purchase to document an unclear label or a contradictory summary. Do not enter someone else's personal data.

After each click, compare your selection with what is shown

Follow the course page through the date or option selection to the last summary you can safely reach. After each click, record what you expect and what appears. A useful note is: “After selecting two people, I expect the summary to show two people.” “Looks strange” does not explain what needs attention.

Not every booking journey follows the same sequence. Check your school’s actual flow and record which steps you can safely reach. If reaching a summary requires a binding action, record that boundary; do not mark the step as passed. The fillable test log is in the German booking journey checklist PDF.

Check account requests, required fields, readability and going back

  • Access: Is an account required before the guest understands the offer and price? Record where the requirement appears and whether the next step is explained.
  • Required fields: Are mandatory details identifiable and clearly explained? Is it clear whether the form needs details of the person booking or the participants?
  • Readability: Can guests read the option, date and price on a phone? Record the precise location and screen size if text or selections become unclear.
  • Going back: Can a selection be corrected without silently losing earlier input? Stay within the agreed test boundary and record when you cannot safely check the return path.

Example: two people selected, one shown in the summary

Fictional case: You first select one person. You go back and change the count to two. The selection field shows two, while the summary still shows one. What you have observed is a mismatch between two visible places. Whether the cause is a calculation error, a display issue or an outdated intermediate step is still unknown.

Your note for the person making the correction could say: “Open course option A in test mode, select one person, continue to the summary, go back and increase the count to two. After confirming again, the summary still shows one person. Expected: The confirmed participant count matches in the selection and summary.” Add the device, browser and a screenshot without guest or payment details. Remove private access links and tokens too.

Choose the error or unclear step with the biggest consequence

If the guest cannot continue, or the selected service differs from the summary, address that first. For an unclear required field, write the question from the guest's perspective: “Does this mean the person making the booking or a participant?” If the flow is understandable but information is hard to read, name the precise location and screen size.

Keep observation and proposed solution in separate fields. “The participant count remains unchanged” is an observation. “The page needs rebuilding” is an untested solution. Let the responsible person investigate the cause.

Record the test steps and required correction in the PDF

The two-page PDF “Onlinebuchung Schritt für Schritt prüfen” contains a log for your booking steps and a worksheet for the correction. Request the free German PDF with your email address. Use it to record the location of the problem, steps to reproduce it and expected result, then agree on a follow-up check with the responsible person.

Describe exactly how you will recognise the correction: “After the same steps, both places show the same confirmed participant count.” That is easier to check than “Make booking simpler”.

Repeat the same booking steps after the change

After the correction, use the same option and steps. Record the new result. If you cannot reproduce the issue, it remains an open observation; do not invent a cause. A successful pass confirms this particular case, not general error-free operation or a higher booking rate.

Today’s result: you can show one incorrect or unclear step in the booking journey, name the person responsible and explain how you will check the correction. The next challenge step compares payment details in several places for the same course option.

Further reading: Check booking access and check-in before use. Its product outlook does not promise availability in your particular setup. For unclear offer information, use the course-page checklist, whose PDF is in German.

Practical knowledge for every watersports school

Check your online booking step by step

Two printable pages in German to record the booking steps and describe one error or unclear part.

  • Choose the course, date and participant count for the test
  • After each click, record what you expected and what appeared
  • Check the correction with the responsible person

PDF · A4 · 2 pages · German

Check your online booking step by step

We store your email address and requested guide in our CRM, Attio. You receive a direct download and a one-time email with the guide. Our team receives an internal notification. This does not subscribe you to a newsletter. Privacy information.

How does this work at your school?

Bring an everyday task from your school. We’ll show you how it could work in TIDEFORCE.

Request a demo →