LifeRaft OSTM
← All add-ons

Adventure & Marine

RLX Waivers

Versioned waiver templates, participant acknowledgement status, guardian context, expiry, and privacy-aware evidence references.

FoundationVersion 0.1.0

This add-on is in the foundation stage. Ask about its current scope and availability before planning your build.

Product images coming soonA closer look at RLX Waivers.

What it does

Features at a glance

  • Versioned waiver templates, participant acknowledgement status, guardian context, expiry, and privacy-aware evidence references

Built for your workflow

Who it’s for

  • Adventure & Marine projects that need this focused capability
  • Owners who want to activate only the workflows their site needs

Setup and fit

Compatibility

Requires a valid LifeRaft OS core license and a supported installation.

No additional add-on is listed as a required dependency.

Optional connections

From setup to everyday use

A straightforward starting point

  1. Track acknowledgements without hiding document context
  2. Store structured template version, participant reference, guardian context, acknowledgement date, expiry, evidence reference, jurisdiction, and retention rule
  3. Run independently with local records and exports; listed integrations are optional enhancements

Before you choose

Common questions

What does RLX Waivers do?

Versioned waiver templates, participant acknowledgement status, guardian context, expiry, and privacy-aware evidence references.

What does RLX Waivers need to run?

RLX Waivers runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.

How ready is RLX Waivers for deployment?

Foundation module: intended as a building block and may require project-specific configuration before customer launch.

Review the launch checklist
  • Admin setup — Confirm settings, navigation placement, permissions, and any required starter content before launch.
  • Public QA — Review the public page, empty states, mobile layout, and activated/deactivated states.
  • Package QA — Confirm the module fits the selected product package and does not expose unused workflows.
  • Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.

Make RLX Waivers part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk