Waiver renewal workflows your team can explain
Set appropriate validity rules, recognize expiring records and give returning guests clear instructions when a fresh submission is needed.

Returning guests expect the desk to know they have visited before. They may also assume that an old waiver covers every future activity. A dependable renewal process makes the distinction clear: the team recognizes the participant, checks the applicable record and explains when a new form is required.
Define the rule before configuring it
Choose the validity approach your organization has approved for the activity. Consider what should happen after a period of time, a seasonal program change or a revised document. The software can apply configured expiry behavior, but it cannot decide the legal effect of a document for your business. Record the reason for the rule and who approved it. Staff need a simple explanation for guests, especially when a frequent visitor is surprised by a renewal request.
Review the record for today’s visit
Check the participant, template and status together. A current form for one activity may not be the form required for another. An older confirmation message can help locate a record but should not be the only source used to decide whether it is ready for today's visit. If a form is expiring, follow your policy about when a replacement is needed rather than improvising different deadlines at different desks.
Make a fresh submission straightforward
Send the correct current signing link and explain why the guest is being asked to complete it. Keep the instruction brief and specific. Do not describe a new signature as a clerical correction to an old record when the guest is actually agreeing to a different document. If the form offers a returning-participant or prefill workflow, have the guest review the information presented and complete the required signing step themselves.
Keep past and current records distinct
A new submission should not erase the history of an earlier visit. Staff may need to identify which form was signed at a particular time, so search and export with the relevant dates and template in mind. When document wording changes, confirm how the published version relates to existing records. Do not assume that publishing a new template automatically changes the status or content of every older waiver.
Include renewal cases in desk training: a record that is still valid, one near expiry, one expired and one for a different activity. A shared decision process helps guests receive the same explanation regardless of which team member is working.
Common questions
Does publishing a new version rewrite existing waivers?
No. Existing signed records retain their version relationship. Decide separately how your organization will request new submissions when wording or participation requirements change.
Are renewal reminders automatically sent?
Do not assume that an expiry rule schedules messages. Use the communication tools actually configured in your workspace and assign responsibility for reviewing and contacting returning participants.
Useful next steps
A clear process. A better start.
Build your form, try the guest experience, and give your team a workflow they can follow.