Sign in
Start free7-day free trial
Records & access

How to organize a request for a signed waiver

Identify the requester, exact document, authorized purpose and delivery route before exporting a record.

A request for “the waiver” may mean a blank template, a particular signed version or every record associated with a participant. Clarify the request before downloading anything. The right document and the right recipient are separate checks.

Identify the requested item

Ask which participant, visit and document the requester means, using the minimum context required. A person may have several records across activities or locations. Do not assume the newest PDF is the document relevant to the request.

Distinguish a current blank form from a historical signed record. The search vocabulary guide can help staff ask this clearly. If the person only needs general wording, that does not automatically call for an export containing participant information.

Confirm the request route

Follow the organization’s process for checking the requester and their authority to receive the material. An organizer, purchaser or accompanying adult may have a different role from the participant or required guardian. Do not infer access solely from familiarity with a name.

Assign one owner to the request. Keep the task in an appropriate system and avoid forwarding it through several shared inboxes with copies of the record attached. General coordination notes should identify the task without reproducing private contents.

Verify the source before exporting

Find the exact record, confirm its version and state, and check whether the PDF is available. If it is not, investigate the actual condition rather than substituting another document. The export verification guide provides a focused checklist.

Use a request log that records:

Detail Purpose
Request reference Keeps follow-up attached to one task
Intended record Prevents a similarly named substitution
Review outcome Records who authorized the next step
Delivery destination Confirms the appropriate route
Completion state Makes outstanding work visible

Check the file and close the task

Open the downloaded file from its saved location before sharing. Confirm the attachment or chosen destination contains that file, not an older document with a similar name. Use the organization’s approved delivery and retention process for the exported copy.

Record the completed action without copying the document into the task log unnecessarily. If the request remains unresolved, explain the next action and responsible role. A sent email, an available PDF and a completed request are not always the same state.

THE PRACTICAL DETAILS

Common questions

Should we send every record with the participant’s name?

Clarify the requested scope and authorized purpose first. A broad name match is not a reason to export every possible document.

Can a current template replace an unavailable historical PDF?

Do not present a different document as the requested signed record. Explain the availability issue and investigate the correct source.

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