Legal and Waivers

This standard governs how legal pages and customer waivers are maintained in the content management system and presented for acceptance. It is used by the Legal function, which owns the text of every legal page and waiver; by Content Editors, who place approved text into the console; and by Front Desk staff, who present waivers at booking and check-in. One rule governs the whole subject: published legal and waiver content comes from the governing documents in the Company's document library. The console displays that text; it does not author different text, and no operator shall publish legal wording in the console that differs from the governing document.

Roles and duties

• Legal function: approves all legal and waiver text, sets effective dates, and decides whether a change is material.
• Content Editor: places approved text into the policy store exactly as approved, writes change notes, and never edits legal wording on the Editor's own judgement.
• Front Desk: presents the current waiver version before the appointment and confirms acceptance is captured before service begins.

Where legal content lives

Legal pages and waivers are held in the policy store. The public site renders them at the policies addresses, where each page's address is derived from its title. The Legal and Waivers screens and the policy manager both write to this same store, and saving under an existing title updates that record rather than creating a duplicate. Operators shall edit legal content only in the policy store. Page records elsewhere in the console have no public rendering for policies, and waiver text found in general settings keys is a defect: the Content Editor shall move it into the policy store and report it.

The policy store has no delete function and no required-acceptance flag. Operators shall keep the store pruned by editing a superseded policy into its current form rather than accumulating near-duplicates. Whether acceptance is required is a property of the flow that presents the policy: booking or check-in: not of the policy record.

Placing and changing legal text

1. The Legal function issues the approved text and its effective date. The source of the text is the governing library document; where the console text and the library document differ, the library document governs and the console shall be corrected to match it.
2. The Content Editor places the text in the policy store under the existing title, so the address the public uses does not change unless the Legal function directs a new page.
3. A correction that does not change meaning: a typographical error: may be made in place. Any change to a fee, a time window, a risk allocation, or any other obligation is a material change: it is issued as a new version with a new effective date, a change note that states what changed and when it takes effect (for example, "Raised no-show fee from $25 to $35, effective November 1"), and a plain-language summary of the change at the top of the page for customers.
4. Acceptances already captured remain attached to the version the customer saw. Operators shall never rewrite an earlier acceptance to point at a newer version; the earlier record is the evidence of what that customer agreed to.

Writing and presenting the waiver

Waiver text issued by the Legal function follows these rules: short sentences, plain words, and the order a customer would ask the questions: what the customer is agreeing to, what the risks are, and what happens if the customer does not sign. The presentation flow matters as much as the text: the waiver shall be presented, and acceptance captured, before the appointment. A waiver signed after the service does not evidence informed agreement and shall not be relied on.

Acceptance records

An acceptance record states the customer, the policy, the version accepted, the time, and the network address from which acceptance was given. The acceptance ledger is the record Front Desk and the Legal function consult in any dispute about what a customer agreed to. Operators shall observe the following

1. Before relying on a waiver in a dispute, verify that an acceptance record for that customer and version exists in the ledger.
2. Never alter or backfill an acceptance record. A missing record means acceptance was not captured through the system, and staff shall say so rather than represent otherwise.
3. Where a signed waiver is needed and no system record exists, the waiver shall be obtained on paper and filed, until the acceptance is recorded in the ledger.

Controls

Only the Legal function may approve legal text, and only Content Editors with publishing rights may place it. Both waiver screens record each save in the audit log with the operator and the resulting state. The Legal function shall compare the published console text against the governing library documents whenever a governing document is amended, and at the review below.

Records

This standard produces policy records in the policy store, revision and audit history for each change, and acceptance records in the acceptance ledger. Acceptance records and legal revision history are retained permanently.

Escalation

Any request to change legal or waiver wording: from any team: goes to the Legal function at legal@aapawz.com; Content Editors shall not act on such a request from any other source. Service of legal process and subpoenas goes to legal@aapawz.com on the day it is received. Operational problems with the waiver screens go to support@aapawz.com.

Review cadence

The Legal function reviews every published legal page and waiver against its governing library document quarterly, and confirms the acceptance ledger is capturing current versions.