# Facility identity correction workflow

Status: generic educational method. This document contains no company-specific audit findings, credentials, personal account data, performance claims, or legal ownership assertions.

## Purpose

Keep every public facility record traceable to a current source while separating customer-facing identity, operating status, platform access, and legal relationships.

## Workflow

1. **Scope the exact record.** Start with a stable facility ID and the exact first-party page or local-profile URL. A generic search result is not the record.
2. **Collect current evidence.** Compare the governed portfolio register, approved operating schedule, first-party page, exact local profile, and any authorized status record.
3. **Classify the mismatch.** Mark the issue as identity, address, telephone, office hours, access hours, lifecycle state, category, platform status, access role, or legal relationship.
4. **Freeze unsupported inference.** Do not treat brand presence, a platform user role, or a directory listing as proof of legal ownership or operation.
5. **Assign approval.** Route each field to its named owner. Keep platform-access recertification separate from public-field correction.
6. **Implement by surface.** Change only the affected record. Preserve redirects, legacy-state notes, and effective dates when a facility changes status.
7. **Capture the visible result.** Record the public URL, final value, submission or change-ticket ID, reviewer, and verification date. A sent request is not a completed correction.
8. **Recheck and govern.** Review active records monthly, access roles quarterly, and every record at an opening, closure, transfer, rebrand, or material schedule change.

## Minimum release gate

- The facility ID is unique and stable.
- The current name, address, telephone, office hours, access hours, status, and canonical URL have named sources.
- Active, opening, temporarily closed, legacy, and transferred states are not merged.
- Platform verification and user-access state are recorded separately from public fields.
- Any owner or operator relationship is backed by a governing record.
- The approved value is visibly verified after implementation.
- Credentials, personal account identifiers, and private contractual terms are excluded from the public record.

## Editorial limitation

This method is a control framework, not evidence that a specific operator has improved revenue, occupancy, customer experience, search performance, or compliance. Any case example requires separate permission, current source evidence, and an explicit limitations statement.