Download signNow app
4.7 / 5 rating on

Release, Waiver, Assumption Of Risk And Hold Harmless Form

Use a Release, Waiver, Assumption Of Risk And Hold Harmless template to make your document workflow more streamlined.

What this release form does

A Release, Waiver, Assumption Of Risk And Hold Harmless Form records a participant’s acknowledgment of identified risks and agreement to release or protect specified parties from stated claims. It usually identifies the activity, participant, released parties, assumed risks, signature, date, and sometimes emergency or guardian information. Its effect depends on clear language, informed consent, applicable state law, and the facts of the event. ESIGN and UETA can support electronic execution when their requirements are met, but they do not make every liability provision enforceable or replace required legal review.

Who uses this release form

Recreation providers

Recreation operators use this form before activities, collecting participant acknowledgments, emergency information, and signatures from adults or authorized guardians. The document should identify the activity, stated risks, release scope, indemnity language, and governing terms. State law can affect enforceability, especially for minors and negligence claims.

Business teams

Construction, healthcare, legal, and property teams adapt the form for site access, treatment-related acknowledgments, client engagements, or property activities. They should not treat it as a substitute for a contract, consent form, deed, court document, or family-law filing when those documents have separate legal requirements.

How the release signing flow works

Prepare the activity-specific language first, then use signNow to place fields, route the release, capture signatures, and preserve evidence.

  • Upload form: Upload the completed release PDF to signNow.
  • Check fields: Auto-detect fillable fields and review their placement.
  • Assign signers: Assign signature, initials, date, and acknowledgment fields.
  • Complete record: Send the release and store its completed audit trail.

Quick steps to complete the release

Use this sequence to turn the activity-specific release into a signed, traceable record without changing its legal wording.

  • Upload:

    Upload the release PDF.
  • Prepare:

    Review detected fields and add missing ones.
  • Assign:

    Assign each participant’s signing fields.
  • Finalize:

    Send, monitor, and download the completed record.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

Ways to send and sign the release

  1. Use the web app when an administrator prepares the release, assigns fields, and sends it to participants from a desktop workflow.
  2. Use the mobile app when staff collect signatures at a facility, event, job site, or other location away from a desk.
  3. Use kiosk mode when multiple participants sign consecutively on an organization-controlled device, with each signing session handled separately.
  4. Use a shareable signing link when a participant needs access without an individually prepared email invitation.

Recommended setup for this release

Configure the release workflow around signer identity, evidence preservation, restricted access, and the retention rule for the activity involved.

SettingRecommendation
Authentication methodEmail link with SMS verification
Signature typeTyped or drawn electronic signature
Audit trailCapture timestamps, IP, and action history
Document retentionSix years for HIPAA records
EncryptionTLS 1.2/1.3 and AES-256 encryption

What the audit trail records

The audit trail separates the signed release from its supporting evidence, showing who acted, when they acted, and how the completed file was preserved.

01

Authenticate signer:

Records the selected authentication method.
02

Timestamp action:

Captures the exact signing time.
03

Track actions:

Logs viewed and completed fields.
04

Hash document:

Preserves document integrity evidence.
05

Seal record:

Seals the completed PDF against unnoticed changes.
06

Export audit trail:

Allows authorized users to retrieve or export history.

Features that support signed releases

signNow connects the form’s risk acknowledgments and signature requirements with a traceable workflow for preparation, signing, and record storage.

Fillable fields

Place participant names, activity details, risk acknowledgments, signatures, initials, and dates directly on the release before sending it for execution.

Signer routing

Route the same release to participants, guardians, witnesses, or representatives in the required signing order without manually circulating paper copies.

Audit trail

Capture timestamps, signer activity, and completion evidence so the organization can connect each signature to the executed release.

Mobile signing

Use the mobile workflow to collect signatures at an event, facility, construction site, or other location where participants complete the activity release.

Secure records

Preserve the final PDF and associated completion history for later review, subject to the retention policy governing the underlying activity.

Reusable template

Reuse an approved release template while keeping activity-specific risks, released parties, and participant information accurate for each signing event.

Integrations for release records

Connect the signed release workflow to the systems that store participant records, manage activities, and coordinate operational approvals.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Privacy pitfalls in signed releases

  • Personal health details or emergency contacts may remain visible to every document recipient without careful field and access design.
  • A signer may not receive clear consent information before electronically signing the release, weakening evidence of informed agreement.
  • Shared links can expose a waiver to unintended participants when access controls, expiration, or signer identification are not configured.
  • Copying one participant’s completed release into another person’s record can create attribution and privacy problems.

Record-keeping practices for signed releases

Keep the executed release, evidence of signer identity, and audit history together under a documented retention and access policy.

Export the audit trail with every completed form

Export the completed release and audit trail together after every signing event. Preserve the signer’s name, email, timestamps, IP information, and completion certificate so the organization can reproduce the executed record during a contract dispute or compliance review.

Match retention to the underlying activity

Set a documented retention period based on the release’s business context and state requirements. If the form contains protected health information, retain it for six years from creation or last effective date under HIPAA, 45 CFR 164.530(j).

Archive the original signed PDF securely

Store signed releases in a restricted repository with separate permissions for senders, reviewers, and administrators. Keep the original PDF unchanged, prevent casual replacement, and record any approved correction as a new version rather than editing the executed document.

Review risk language before each new use

Review the waiver template whenever the activity, covered risks, indemnity language, or signer population changes. Obtain legal review for state-specific enforceability questions instead of assuming one release works identically across every U.S. jurisdiction.

Retention periods for signed releases

A release has no single federal retention period; apply the rule tied to the activity, information, and record system containing it.

01

Three years: business records

Apply the organization’s approved policy to participant releases.
02

Six years: HIPAA records

Use six years when the signed release contains PHI, under HIPAA 45 CFR 164.530(j).
03

Thirty years: OSHA exposure records

Retain exposure records for the required OSHA period when attached to an occupational record, under 29 CFR 1910.1020.
04

Five years: OSHA injury records

Retain an injury-related release with the applicable injury record, under 29 CFR 1904.33.
05

State-specific period: verify requirements

Verify longer state or contractual requirements before deletion.

Questions about completing this release

These answers address signing, authentication, privacy, retention, and plan questions that arise when organizations use this specific release workflow.

Business includes legally binding eSignatures, templates, audit trails, mobile apps, ISO 27001, SOC 2, and GDPR controls. For a release, upload the PDF, place signature fields, and preserve the completion record. Electronic enforceability still depends on intent, consent, attribution, and record retention under ESIGN and applicable state law.

Business Premium adds bulk send, kiosk mode, request payments, and quick invite links. Use it when the same release must reach many participants or signatures must be collected on an organization-controlled device. The release language and state-law requirements remain the sender’s responsibility.

Enterprise adds advanced signer authentication, formula fields, conditional fields, and advanced workflow controls. Use stronger authentication when the release involves sensitive information or the organization needs additional evidence connecting a named participant to the completed document.

signNow is ESIGN and UETA compliant, but that status does not decide whether a particular waiver is enforceable. Check state law, clear risk disclosure, participant capacity, guardian requirements, and exclusions for wills, family-law decrees, and court filings before relying on the form.

If a release contains protected health information, signNow identifies HIPAA compliance as requiring a BAA. Configure restricted access, preserve the audit trail, and apply the six-year HIPAA retention rule under 45 CFR 164.530(j) to the covered record.

Business plans include 100 signature invites per user per year, with overage fees. The Site License is usage-based at $1.50 per signature invite and supports unlimited users. Confirm expected participant volume before selecting a plan for recurring release campaigns.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.