A QR code can take someone straight to a waiver. It can also take them to an expired page, the wrong activity, or a staff-only screen they cannot open. The code itself does not tell the guest whether they are in the right place.
A good QR setup combines a reliable destination, a clear instruction, and a location where people can finish the task. Test all three. A successful scan on your own phone while you are signed into the staff dashboard is not enough.
Use the public signing link
Start with the link intended for participants to complete the published waiver. Do not copy the builder's address bar, an internal preview link, or a confirmation URL from someone's completed submission.
Open the destination in a private browser window where you are not signed into the business account. Check the venue, activity, and form title. Read the opening instructions. If a first-time visitor needs context to choose the right form, put that context on the sign as well as the page.
A venue with several activities should decide deliberately whether a sign leads to one specific form or to a page where the guest chooses. One code labeled “Waiver” beside several different activities leaves the choice unexplained. A sign labeled “Complete your climbing waiver” makes its purpose much clearer.
Waiver.com's QR code waiver tools provide a route into the signing flow. The operating checks below apply even when the code was generated correctly.
Keep signing codes and check-in codes separate
There are two different jobs a code can do:
| Code | Who uses it | What it should accomplish |
|---|---|---|
| Public signing code | A guest arriving at the venue | Open the correct form so the guest can complete it. |
| Confirmation or check-in code | Staff verifying a completed submission | Find and check the relevant signed record. |
A public sign should never reuse a particular guest's confirmation code. That could point everyone toward the same record instead of a fresh signing flow. Likewise, scanning a public signing code does not establish that a person has completed a waiver.
Train staff to explain the difference in one sentence: “This sign opens the form; once you've finished, we'll check your record.” If your process uses a confirmation code, tell the guest where it appears and when staff will scan it. The waiver check-in workflow is a separate step from collecting the signature.
Write the instruction around the task
A large QR image with no explanation makes people guess. Put the venue name, activity, and action next to it. Include a readable URL for someone whose camera cannot scan the code and a clear way to ask staff for help.
For example:
Climbing today? Complete your waiver here.
Scan to open the form on your phone. For a child, follow our parent or guardian signing instructions. When finished, come to the desk so we can check your record.
Can't scan? Visit [your public signing URL] or ask a team member.
Replace the bracketed address with the actual public URL. Do not print an example URL or promise that completion always takes a particular number of seconds. Form length, family size, reading needs, and connectivity vary.
Keep unrelated actions off the sign. A customer who is trying to check in should not have to choose between a waiver, a newsletter, a review request, and a social account. Put promotional links somewhere else.
Test the printed sign where it will live
A code that works in a design file may fail behind reflective glass or in poor lighting. Print a sample at its intended size and place it in the actual holder. Scan it from the distance a guest will naturally stand, without zooming the camera or leaning across the counter.
Try at least two different phones if available. Use both venue Wi-Fi and cellular data where practical. Finish the form rather than stopping when the page loads. A phone can reach the first screen and still fail to load a later step or submit the result.
Check these details before printing a batch:
- The code is sharp, has clear space around it, and is not distorted.
- The fallback URL is readable and reaches the same destination.
- The form opens without a staff login.
- The venue and activity are correct.
- Required fields, the keyboard, and the submit button remain usable on a phone.
- The completed record can be found by the staff member doing check-in.
Use the printed QR code verification guide for a short distribution procedure. Use the full waiver testing checklist when the form itself is new or has changed.
Plan for a guest who cannot use their phone
A dead battery, an inaccessible camera control, or a poor signal should not leave staff improvising. Decide whether your fallback is a staffed device, a waiver kiosk, or another approved process.
A shared device needs a between-guest check. Confirm that the previous person's details and completed page are no longer visible before handing it over. Do not tell guests to use someone else's already-open signing session without verifying that it is a fresh form.
Place the sign before the point where unfinished forms block check-in. Guests need room to read, ask questions, and handle a family form. If you are running a party, send the link ahead of time as well. Our birthday-party arrival plan explains how the invitation and roster fit together.
Assign an owner for the code after launch
Printed signs last longer than people expect. Keep a simple list of where each code appears: the front desk, booking messages, posters, and event materials. Record the destination and who is responsible for replacing it.
Recheck those locations when a form is archived, a venue changes its process, or the public URL changes. Do not assume that editing a template changes every previously printed destination in the way you intended. Scan an old sign and verify the actual result.
Include a quick physical inspection in opening checks. The FTC describes scams involving replacement QR stickers and misleading destinations. Inspect the sign for tampering and confirm its URL, especially in spaces accessible to the public. See the FTC's explanation of QR code scams.
QR waiver questions
Does scanning the code complete the waiver?
No. A public signing code opens the form. The participant still needs to provide the required information and complete signing. Staff should verify the resulting record rather than treating a scan as completion.
Should I print a separate code for every event?
Only if the destination or event workflow requires it. Avoid creating extra codes that all do the same job without a clear reason. Whatever you choose, label the sign accurately and test how the completed record connects to the event.
Will the QR code work without internet access?
The camera may read the address without a connection, but opening and completing the online form depends on the signing service and connectivity. Test your actual conditions and establish a fallback. Do not advertise offline completion just because a phone can recognize the code.