# Channel Ownership Map

Map business ownership, editorial authority, publishing access, maintenance, incident response, and escalation across every active content channel.

## Usage note

Inventory every channel where the organization regularly publishes or maintains content, including neglected and third-party surfaces. Record roles rather than credentials, and store secrets elsewhere. Confirm assignments with owners and platform administrators; a name in a spreadsheet does not grant authority, capacity, or emergency access.

## How to use this template

1. Inventory all active, automated, dormant, partner-operated, and archived channels that can still reach an audience.
2. Separate business, editorial, technical, production, maintenance, and incident responsibilities for each surface.
3. Record the channel purpose, audience, allowed content, workflow, source of truth, and lifecycle rules.
4. Test normal publication, owner absence, correction, access loss, and urgent removal scenarios with the assigned roles.
5. Resolve orphaned channels and excessive access, publish the map to contributors, and schedule owner confirmations.

## Blank template

### Channel identity

- **Channel name:** [Public and internal name]
- **Platform or vendor:** [System used]
- **Public location:** [URL or discovery path]
- **Status:** [Active / Limited / Dormant / Retirement planned]
- **Purpose:** [Why this channel exists]
- **Primary audience:** [Who it serves]
- **Permitted content:** [Formats and topics]
- **Prohibited content:** [Sensitive or unsuitable material]
- **Canonical source:** [Where authoritative content lives]

### Ownership and access

- **Business owner:** [Strategy, budget, and continuation]
- **Editorial owner:** [Standards and content decisions]
- **Platform administrator:** [Access and configuration]
- **Publishing role:** [Creation, scheduling, or upload]
- **Maintenance owner:** [Evergreen review and retirement]
- **Moderation owner:** [Comments, replies, or community conduct]
- **Incident decision maker:** [Correction, pause, or removal]
- **Backup role:** [Coverage during absence]
- **Access record location:** [Secure system, not a password]

### Operating model

- **Intake and approval:** [Describe or link workflow]
- **Publishing cadence:** [Expected frequency]
- **Accessibility checks:** [Required controls]
- **Correction method:** [Edit, notice, deletion, or follow-up]
- **Retention or archive:** [Rule and owner]
- **Measurement:** [Useful signals and data owner]
- **Automation:** [Feed, scheduler, integration, and pause owner]
- **Third-party constraints:** [Material limits or terms]

### Resilience review

- [ ] Two authorized roles can respond to an urgent publishing incident.
- [ ] Departed users and unused integrations have been reviewed.
- [ ] The canonical source and correction path are clear.
- [ ] Dormant channels have an explicit maintain-or-retire decision.
- [ ] Owners confirmed the assignment and response expectation.
- **Next confirmation:** [YYYY-MM-DD]
- **Open issue:** [Owner and resolution date]