# Phase 9 — Preserve existing referrals link, retire Form C

Date: 2026-11-01
Status: Owner-approved page-routing decision; operational form acceptance and site cutover remain separate

## Decision and live reference

The current public [referrals page](https://www.azinstitute4autism.com/referrals)
has a button-like **Refer a Client** link to
`https://form.jotform.com/231638510219149`.
The owner explicitly requests that the Astro migration preserve that direct
hosted-form destination rather than implement a separate Form C.

This overrides previous Form C referral-initiation planning. Earlier two-form
contracts, form-creation batches and checklists remain historical evidence, not
live instructions to create or launch a form. Physical Form B remains retired.
Form A remains a separate single form at its 16 approved existing placements.

## Code and publication behavior

- `src/content/pages/en/referrals.mdx` retains its button-like CTA and source
  content; the CTA now links to the exact existing HTTPS Jotform URL with no
  tracking/prefill/query parameters.
- `src/layouts/PageLayout.astro` no longer adds `FormShell` on `/referrals`.
- The unused `referral` native-form mapping and type are removed. The existing
  `FormShell` is retained for applicable family consultation pages only.
- No new iframe, Jotform script, webhook, provider integration, form ID, field,
  server POST, API origin, measurement, redirect or protected-data collection
  is added to the Astro site.
- `/referrals` remains its own published route with existing title, canonical,
  body and SEO policy. The Form A allowlist remains unchanged and explicitly
  excludes `/referrals`.

## Privacy and operational acceptance

A live-page link is evidence of the intended **URL**, not proof of the linked
form's configuration or compliance. The hosted form presently identifies
itself as a program-consultation form and visibly asks for child and family
details, so the form owner must confirm that this remains an appropriate
professional-referral journey.

Before cutover, the owner should verify the existing Jotform account's access,
PHI handling, privacy settings, recipients and notifications, retention,
attachments, integrations, confirmation behavior, accessibility and
availability. Do not infer a new form's safe defaults from Form A's reviewed
configuration. No account edits or submissions are authorized or performed
by this repository change.

## Regression acceptance

For both default staging and indexing builds, `/referrals` must include one
button-styled `Refer a Client` anchor pointing to the exact external destination,
with no local lead form, `#form-title` fallback or Form A iframe. All other
contact/consultation/landing routes retain their existing behavior.

Updated unit/publication assertions cover the external link, removal of the
inactive referral form, route mapping, and preservation of other form surfaces.
These are source-level assertions until run by the repository owner or CI.
No production deployment, DNS change, Jotform mutation or site cutover is
included in this PR.