The venue and the operational question
Wall Walkers Bouldering operates in Capalaba, Queensland. Its public first-visit information includes a waiver as part of preparing to climb. The practical question is not simply whether a link was sent: the venue needs a completed record that its systems can recognise.
Public venue information: Wall Walkers Capalaba and first-visit guidance.
The verified workflow
- Complete the waiver. Wall Walkers uses Rock Solid Waivers. Operational verification has confirmed completed signed waivers, rather than just a rendered form or a shared link.
- Connect the completed record. An existing integration imports waiver information into the venue’s system. The useful boundary is a completed waiver becoming available downstream, not a claim that every booking or membership platform has a ready-made connector.
- Keep responsibilities separate. A signed record is one input to venue operations. It does not itself prove that a participant has completed every induction or meets all access requirements.
The product’s API and webhook module describes custom integration options. Developers should use the API reference for supported endpoints, authentication and event contracts.
What this case study does not claim
We have not measured a before-and-after reduction in check-in time, staff hours or cost for this account. No savings percentage, customer quote or legal guarantee is presented.
This account does not establish a Wall Walkers kiosk or offline deployment. Product capabilities, a particular venue configuration and measured operational outcomes are different kinds of evidence.
No participant records, signing links, personal identifiers or screenshots are published here.
Apply the questions to your own venue
Decide who signs, where staff check completion, and which system needs the result. Start with the climbing gym workflow, or compare other industry workflows. Review your own terms with a qualified adviser; this case study is not legal advice.
Discuss your waiver workflow