Climbing Wall Route Changes: A Public Notebook Kept Apart From Session Bookings

When a climbing wall resets routes, visitors want to know what changed before they arrive. Booking systems are built to sell and count places, not to describe holds and grades. This proposed workflow keeps a public route-change notebook separate from session bookings, so that updating one never forces edits to the other. It is an example process, not an observed result.

Why separate them

A booking entry answers who can climb and when. A route note answers what is on the wall. If you mix them, a route reset can tempt staff to edit sessions, and a session edit can accidentally erase route information. Keeping two records, linked only by a date and a wall section, avoids both problems.

Notebook entry fields

Each entry should have:

Wall section name, using the same labels painted or taped on the wall.
Route label as it appears on the wall tag.
Change type: new route, removed route, grade changed, holds changed, or temporarily closed.
Date the change took effect on the wall, not the date it was typed.
The setter or checker who confirmed it on the wall.
A short plain description, such as left traverse now starts on the blue volumes.
Status: planned, in place, or reverted.

Use planned only when the setters are confident of the date. A planned change should never appear as in place.

Decision branches

The route is physically changed and checked: publish as in place, with the check date.
The change is scheduled but not yet done: publish as planned if useful, with a note that it may move.
A route is closed for safety or maintenance: publish the closure with a short reason that does not speculate. Link nothing to bookings. If a session needs to be changed, staff handle that in the booking tool separately.
A grade is disputed: leave the published grade until setters agree, then publish a grade-changed entry rather than silently editing the old one.
A reset is cancelled: change the status to reverted and keep the entry.

Never delete entries. Keep them in date order so regulars can see the history.

Stop conditions

Stop publishing and ask the head setter if the wall tag and the notebook disagree on a route label. Stop if an entry would imply a safety judgement the setters have not made. Stop if someone asks you to edit a booking from within the notebook; that belongs in the booking tool.

Example

Proposed example: the wall has sections A, B and C. On a Tuesday the setters strip two routes in section B and tag three new ones. After a second setter climbs and checks them, the notebook gets three new route entries and two removed entries, each dated Tuesday, each naming section B. The Wednesday evening booking page is untouched. A visitor reading the notebook sees what is new in B. A visitor booking a session sees the usual availability. If section B was closed on Monday while setting, a separate closure entry records Monday, and staff decide in the booking tool whether any session needs a note.

Linking the two lightly

If you want visitors to find the notebook from the booking page, add one plain link or sentence such as check the route notebook for recent changes. The booking data itself stays unchanged.

Practical acceptance test

Prepare five sample changes: one new route, one removal, one grade change, one planned reset, and one closure. Ask a staff member who did not write them to publish all five using only the field list.

Pass if:

Every entry has section, label, change type, effective date and status.
The planned entry is clearly not shown as in place.
No booking record was opened or edited during the exercise.
A second person can read the notebook and correctly tell you what is on section B today.

If any step required touching the booking tool, the separation is not clean yet; revise the field list.

Conclusion

A route notebook works when it is dated, labelled with the wall's own names, and independent of the booking tool. Regulars gain a trustworthy history, and staff avoid unintended booking edits when the setters change a wall.