Sign in
Start free7-day free trial
Run & improve

How to train your front desk on digital waivers

Build a short playbook for matching records, checking status and handling the cases that interrupt a busy arrival.

Good training gives staff a repeatable sequence and a clear point at which to ask for help. It should cover the ordinary guest and the few exceptions that can stop a queue. Begin with actual test records and the access employees will use on a real shift.

Teach the normal arrival in order

Show staff how to identify the guest, locate the correct record and check the required status, participant details and flags. Explain how this fits with payment, equipment, orientation or other venue checks. A signed waiver is one part of the arrival process. Use the check-in help section for current product steps and keep the operational reference focused on what the desk must verify before moving to the next task.

Practice the cases that cause hesitation

Create test scenarios for a guest with no record, a returning participant with an expired waiver, a guardian with multiple children and two people with similar names. Include someone who says they signed but cannot find their confirmation. Have staff search and resolve each case using the approved process. Do not use real participant information in a casual training exercise. The goal is to build recognition of the next action, not memorization of one perfect demonstration.

Give exceptions a named owner

Write down who handles document questions, uncertain guardian authority, flagged answers and system problems. Include the backup when the usual supervisor is unavailable. Define when the desk pauses the next operational step. Avoid vague directions such as “use your judgment” where the organization expects a consistent decision. Staff should be able to tell the guest what happens next without offering legal or medical interpretations outside their role.

Walk through the equipment and privacy checks

Teach the difference between a public signing QR code and a participant confirmation code. Show the kiosk start, completion and reset behavior on the actual tablet. Explain which screen should face the guest and how to avoid exposing previous answers. Use individual staff accounts and the supported role permissions. Give employees a private way to discuss a flagged response, and make clear that they should not ask a guest to change an accurate answer simply to clear a warning.

Keep the reference current between shifts

Finish training by having the employee complete the scenarios independently. Record unresolved questions and correct the instructions before expanding the rollout. Assign someone to update the playbook when templates, renewal rules or equipment change. Put the current version where every shift can reach it, with links to detailed help and the escalation contact. Review repeated arrival problems in a short team check-in so the process improves from specific examples rather than accumulating unofficial workarounds.

THE PRACTICAL DETAILS

Common questions

How long should the desk reference be?

Keep the everyday sequence short enough to consult during a shift, then link to detailed help and the exception owner. A one-page reference can work if it covers the real decisions. Do not shorten it by leaving staff to guess about minors, expired records or flagged answers.

How do we know someone is ready to use it?

Ask them to complete realistic test scenarios using their normal account and the written instructions. They should find the correct record, distinguish the relevant status, recognize a flag and know when to escalate. Watching a demonstration alone does not show whether the handoff is understood.

KEEP GOING

Useful next steps

MAKE YOUR NEXT ARRIVAL EASIER

A clear process. A better start.

Build your form, try the guest experience, and give your team a workflow they can follow.

Compare plans