Separate the subscription from the submission bill.

A base price is only part of the estimate.

Before comparing totals, write down what the bill counts. Is it a signed document, a participant, a device, a location or a staff account? Keep that list beside the estimate so a low base price does not hide a second charge that grows with a busy season.

WaiverForever describes its bill as a subscription plus waiver usage and offers prepaid usage packs. Its published monthly bases are $19 for Essential, $39 for Standard and $129 for Scale. Use the current pricing calculator or a written quote for your expected submission volume rather than treating the subscription alone as the final total.

Count the devices and people who need access.

The number of guests is not the only planning input. A small venue might use one shared kiosk, while a weekend event needs tablets at several entrances. Decide which devices must work offline and which staff members need their own access before choosing a plan.

WaiverForever’s pricing differentiates device, template and team allowances. Essential lists one offline device and three templates; Standard lists ten offline devices, 25 templates and seven team users. Its online and app workflows may suit a team that needs dedicated offline collection. Test synchronization and staff access with the intended setup.

Keep the pricing question connected to operations.

A good plan should support your approved documents without encouraging shortcuts. If a new activity needs a different form, the decision should start with the activity and wording. Review how many distinct templates you operate now, who maintains them and how often a version changes.

Waiver.com’s Starter price is $9 per month or $90 per year for one location, with unlimited waivers and 200 monthly SMS. Growth is $14 per month or $140 per year, with unlimited locations, unlimited waivers and 500 monthly SMS. Extra texts cost $0.02 each. Annual billing changes the subscription payment, not the monthly SMS allowance.

For a business comparing integrations, walk through one complete record. Start with the reservation, follow the signing link, find the signed record and test a cancellation or replacement participant. Ask about the exact integration you need instead of assuming every product with an API already connects to your booking system.

A careful switch protects the work you’ve already done.

Start with one program or location. Keep the existing service available while you check the archive and rehearse the new process with the people who will use it.

1. Export and inspect.

   Download original signed PDFs and available CSV data. Open a sample across different dates and document versions, then confirm where staff can find the archive. Verify historical access logs separately.

2. Rebuild the approved structure.

   Use your current approved wording, required fields and signer rules. Compare the published form with the source document. A new template does not change or replace an old signed record.

3. Run the awkward cases.

   Try a guardian with siblings, a changed participant, an expired record and an unsigned arrival. Confirm what staff should do when a record needs review.

4. Change links after the check.

   Update booking messages, QR signs, website embeds and kiosk instructions together. Confirm any import requirements with the provider before ending access to your previous account.