Assumption Of Risk, Indemnity Agreement And Release From Form

Use a Assumption Of Risk, Indemnity Agreement And Release From template to make your document workflow more streamlined.

What this assumption-of-risk form does

An Assumption Of Risk, Indemnity Agreement And Release From Form records that a participant understands identified hazards, accepts specified risks, agrees to indemnify another party where the contract says so, and releases stated claims to the extent applicable law permits. The signer should review the activity, parties, risk description, exclusions, emergency terms, dates, and signature fields before execution. In the United States, ESIGN and UETA generally support electronic signatures when intent, consent, attribution, and reproducible records are present, but state contract law controls enforceability.

Activity providers

Adventure operators, gyms, camps, event organizers, and recreation providers use this form before participation to document disclosed hazards, participant acknowledgment, emergency permissions, and release language. They should tailor the text to the activity, age of participants, state law, and any required guardian or witness process.

Business teams

Construction contractors, healthcare organizations, legal practices, and property operators may use related releases for site access, services, or participation. The form does not replace required contracts, medical consent rules, safety duties, or attorney review of indemnity and waiver provisions.

Business types that use this form

The form is most useful when an organization repeatedly documents informed participation, disclosed hazards, indemnity terms, or release language.

A regional recreation operator uses reusable releases for participant enrollment, collecting activity-specific acknowledgments and guardian signatures before scheduled sessions begin.
A construction company uses site-access releases for visitors and subcontractors, documenting disclosed hazards and signed acknowledgments at the project location.
A healthcare or legal enterprise uses controlled templates and role-based sending for specialized consent or release workflows, with counsel reviewing state-specific enforceability before deployment.

Clear fields

Place participant names, activity details, dates, initials, signatures, and indemnity acknowledgments in clearly labeled fields so each signer understands exactly what the agreement covers.

Reusable template

Send the same approved release template to participants before an activity, reducing transcription errors and keeping risk disclosures consistent across locations, sessions, and responsible staff members.

Audit trail

Capture email delivery, signer actions, timestamps, and completion evidence in an audit trail that supports later review of consent, attribution, and document history.

Signer verification

Require SMS authentication or another available signer-verification method when the organization needs stronger evidence that the named participant completed the release personally.

Mobile signing

Use mobile apps or browser signing when participants arrive on site, allowing construction, recreation, healthcare, and event teams to collect completed forms without paper handoffs.

Secure storage

Keep the executed release and completion certificate together in a controlled repository, making the participant’s signed assumptions and indemnity terms easier to retrieve during review.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

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.

Setting	Recommendation
Authentication method	Email invitation with SMS verification
Signature type	Intent-based electronic signature
Audit trail	Export with signed PDF
Document retention	Six years for HIPAA records
Encryption	TLS 1.2/1.3 and AES-256 at rest

Complete and sign the form online

Use this workflow to prepare the assumption-of-risk terms, capture each required signature, and preserve evidence of execution.

Upload the form:
Upload the completed assumption-of-risk and indemnity agreement.
Check the fields:
Review detected fields and add missing signer, date, and initials fields.
Add the signers:
Enter each participant’s email and signing order.
Send for signature:
Send the document through signNow for review and signatures.
Store the record:
Download the completed PDF and audit trail.

Authenticate:

Records the signer’s authentication event.

Timestamp:

Captures signing time and action.

Hash record:

Associates document content with completion evidence.

Seal history:

Preserves changes through completion history.

Track actions:

Logs delivery, viewing, and signing activity.

Retrieve evidence:

Exports the audit trail with the signed PDF.

Record-keeping practices for signed releases

Preserve the signed assumption-of-risk agreement, release, indemnity terms, and evidence of execution as one retrievable record.

Set a documented retention period

Keep the completed form, signer identity details, timestamps, and certificate of completion together. For healthcare-related releases containing protected health information, retain records for six years from creation or the last effective date under 45 CFR §164.530(j). Apply a longer period when state law or contract terms require it.

Export the audit trail

Export the audit trail after every completed form and preserve it with the signed PDF. The record should show signer actions, timestamps, and authentication details, allowing the organization to demonstrate intent, attribution, and record integrity under ESIGN and applicable state electronic-transactions law.

Archive records securely

Store signed assumption-of-risk forms in access-controlled repositories with encryption at rest and in transit. Separate broad operational access from legal review access, and maintain a documented deletion process that prevents premature removal of records subject to a dispute or legal hold.

Verify retrieval and reproduction

Use a consistent file name containing the participant name, activity, execution date, and version. Keep the original signed PDF and completion certificate together, then test retrieval periodically so the organization can reproduce the record in an accurate, accessible format.

Retention periods for related records

The form itself has no single federal retention period; apply the rule governing the record’s actual context and verify state requirements.

Six years: healthcare records

Retain healthcare records for six years from creation or the last effective date under HIPAA, 45 CFR §164.530(j).

Three years: federal tax records

Retain tax-related records for three years from filing under IRC §6501(a), unless the six-year understatement rule or an indefinite exception applies.

Three years: Form I-9 records

Retain employee-related records for three years after hire or one year after termination, whichever is later, under 8 CFR §274a.2(b)(2)(i)(A).

Five years: injury records

Retain OSHA injury records for five years following the year covered under 29 CFR §1904.33 when the release is part of an occupational incident file.

Thirty years: exposure records

Retain OSHA exposure records for 30 years under 29 CFR §1910.1020 when the agreement accompanies an exposure-related employee record.

State rules and document exclusions

State notary rule

Notarization required

Overbroad waiver

Release may be challenged

Real-estate deed

Deed transfer may fail

Family-law document

Court filing rejected

Will or codicil

Testamentary document excluded

Mobile options for signed releases

Participants can complete this release through signNow’s mobile app or a browser on a supported device. The product ground truth confirms mobile apps and offline signing; verify current iOS, Android, browser, and camera permissions before deployment.

iOS app signNow mobile app
Android app signNow mobile app
Document capture Camera capture available

Field teams should manage device access, confirm connectivity before sending, and define how offline work is synchronized. Organizations handling health information should apply HIPAA controls, execute a BAA, and restrict completed releases and audit trails to authorized personnel.

Real estate operations

Tim Martin, founder of Martin Properties, describes processing and executing documents online, including mobile and offline work, while returning forms efficiently to the necessary parties.

Mobile and offline document handling

Martin Properties’ experience illustrates how a distributed real-estate team can move signed documents between field personnel and counterparties without relying exclusively on in-person meetings. The customer story does not identify this exact form, so the use case should be treated as an operational example rather than proof of legal enforceability.

Healthcare administration

Fertility Centers of Illinois uses signNow with an API for healthcare document workflows, where patient-facing forms may require controlled handling and documented signatures.

API-supported healthcare workflows

The customer story identifies responsive support and a successful API experience, but does not specifically name an assumption-of-risk release. A healthcare organization adapting this workflow should execute the required HIPAA business associate agreement and separately confirm state-law requirements for patient consent, indemnity, and release language.

Troubleshooting signed release workflows

Resolve field, authentication, compliance, and record-preservation questions before relying on a completed assumption-of-risk agreement.

On the Business plan, open the document, use the field-detection workflow, and manually add any missing signature, initials, date, or acknowledgment fields. Save the corrected template before sending the assumption-of-risk release. Templates and audit trails are included in the plan’s documented feature set.

Use the signer’s email invitation or enable an available stronger authentication method, such as SMS verification, before sending. The audit trail records the signing event and timestamps. For regulated workflows, choose controls appropriate to the information and confirm any organizational identity-verification policy.

Business includes legally binding eSignatures and audit trails at $8 per user per month when billed annually. Subscription plans include 100 signature invites per user per year; additional invite charges may apply. Business Premium adds bulk send at $15 per user per month annually.

For a healthcare release containing protected health information, signNow identifies HIPAA compliance as requiring a business associate agreement. Execute the BAA and configure access, authentication, and retention controls before collecting that information through the form.

ESIGN and UETA generally recognize electronic signatures when intent, consent, attribution, and record retention requirements are satisfied. A release must still comply with applicable state contract law, and electronic signing does not guarantee that every indemnity clause is enforceable.

Export the signed PDF and audit trail from the completed document, then store both together in an access-controlled repository. Preserve the record in a reproducible format and apply the organization’s legal-hold process before deletion when a dispute is pending.

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.