levelgroundstandard.org

Rule 17

Leaving actually works

Software company Version 0.1  ·  Working Draft

The rule

When a campground decides to leave its software company:

  1. notice takes effect when the campground sends it in writing, with no further step needed from the software company;
  2. the old system keeps taking and honoring reservations for N days · open;
  3. the campground can still download every future reservation and deposit;
  4. guests' prepayments for stays after the exit date are paid to the campground, or its new payment processor, within that same period;
  5. the download and exit period continue whatever the account's payment status, including during a billing dispute or a "past due" notice; and
  6. there is no charge for leaving or for the export. This doesn't cover charges for the rest of a fixed term the campground agreed to.

What this looks like

A campground decides to switch systems in the off-season. For the published notice period, its old system keeps taking reservations, and the manager can export every future reservation and deposit to load into the new system.

A disagreement over the last invoice doesn't lock the data.

Why

One software company may delete customer data 30 days after termination and has no export clause. Another limits retrieval after termination to customers "not in default."

How it's checked

Software company

Read the contract, including sampled order forms (see "For testers").

Pass

  • It states the period and all of (a)–(f).

Fail

  • Any is missing.
  • Export depends on being "not in default."
  • An order form overrides any part.
Evidence
Contract
Source
S15 · O3, O8 · Evidence E17. Part (d) goes beyond S15.