Accepted risks reveal five recurring systemic impediments.
The principal opportunity is to correct the governance, lifecycle, requirements, scope, and transition-management systems that repeatedly create issues.
Register Summary
Fourteen Risks. Five Findings.
AFN's Accepted Risk Register documents fourteen formally accepted riskswhich produce a pattern: The same five organizational failures recur across nearly every entry.
14Accepted Risks
5Systemic Findings
3Critical Risks
7High Risks
4Significant Risks
Accepted risk is visible risk, not resolved risk.
01 AFN has examined its own performance honestly, including where the organization has outgrown its own standards.
02 Some risks are within AFN's ability to mitigate directly, and AFN is acting on those.
03 Many require decisions by WMA, DISA, the Services, or ATSW(PA) — authorities AFN does not hold.
04 The purpose of this synthesis is to improve decision quality, customer outcomes, accountability, and efficiency.
05 Accepting a risk documents exposure. It does not close it.
06 These findings describe systems and authorities, not personalities.
Primary Synthesis
Five Systemic Findings
Each finding below aggregates a recurring pattern across multiple accepted risks. Select a finding title or a risk chip to trace its relationships in the matrix further down this page.
1
Finding
WMA / Enterprise Decision
Decisions affecting AFN capabilities and local service delivery are made without consistently including AFN headquarters, installation leaders, or the personnel closest to the operational requirement.
Observable Pattern
In July 2026, WMA headquarters staff gave an AFN region direction across four separate areas — a legal matter, staffing workarounds, PCS rotation structure, and the modernization timeline — without AFN HQ coordination. A WMA-directed laptop procurement was fielded to AFN units without AFN requirements vetting, arriving without CAC readers and without a communicated operational purpose. The AFN vetting process exists but carries no enforcement mechanism, so when it is perceived as the slower path, direction and procurement continue around it.
Mission Consequence
Poorly informed decisions, conflicting direction, unusable procurements, rework, reduced customer trust, and capabilities removed without a complete understanding of local mission effects. Combatant command public affairs offices are not AFN's only customer — installation commanders and installation public affairs leaders depend on AFN for local command information, force protection, emergency communication, and crisis response.
Management Intervention
Establish mandatory stakeholder consultation and AFN requirements vetting before decisions, procurements, mission changes, or capability divestments affecting AFN field operations.
2
Finding
WMA / Enterprise Decision
WMA lacks an authoritative lifecycle management program and consistent professional project management for critical AFN systems.
Observable Pattern
The Radio Refresh Project is three years overdue, with replacement equipment sitting in boxes — some already approaching its own lifecycle end — and no installation plan. WMA has no known funding plan, procurement pipeline, or authoritative roadmap for critical equipment such as radio transmitters. AFN continues to operate a live, local overseas radio mission on aging transmitter infrastructure with no O&M funding stream confirmed to sustain it.
Mission Consequence
Aging transmitters, unsupported systems, failed or delayed projects, equipment purchased without installation plans, cybersecurity failures, emergency repairs, unmanaged outages, and increasing probability of mission failure.
Management Intervention
Create an authoritative lifecycle portfolio, assign accountable program and project managers, establish replacement schedules, connect requirements to budgets, and use measurable project gates.
3
Finding
Shared: WMA Directs, AFN Vets
The organization often begins with a preferred product, procurement, or technical solution before validating the operational requirement, intended outcome, user need, sustainment model, and cybersecurity constraints.
Observable Pattern
The Radio Refresh Project's equipment will not pass RMF scrutiny or meet cybersecurity requirements as currently built, and has no installation plan. A WMA-directed laptop procurement, at roughly $10,000 per unit, was fielded without CAC readers or a communicated operational purpose, generating field complaints. The requirement-to-delivery cycle time across the AFN, WMA, and DISA procurement chain is long enough to function as a structural incentive to route acquisitions around requirements vetting altogether.
Mission Consequence
Expensive but unusable equipment, requirements churn, field complaints, cybersecurity remediation, delayed fielding, wasted labor, and repeated rework.
Management Intervention
Require outcome-based requirements, user validation, alternatives analysis, lifecycle cost assessment, RMF involvement, and AFN technical vetting before acquisition decisions.
4
Finding
DoW / WMA Decision
AFN is being encouraged to assume additional media functions without a formal determination that they are common functions and without resources tied to the expanded workload.
Observable Pattern
WMA leaders actively seek additional tasks for AFN — video documentation, still photography, print content — to demonstrate relevance beyond broadcast, without resourcing tied to that output. DMA/WMA has operated since 2005–2008 without a formal, Service-inclusive review of what constitutes a "common function" in the current technology and resourcing environment, so neither WMA nor the Services have a mechanism to decline new taskings or attach resources to confirmed scope.
Mission Consequence
Core radio, television, streaming, command-information, and crisis-communication work competes with photography, video documentation, print, social media, and other tasks that may duplicate Service capabilities.
Management Intervention
Conduct a formal Service-inclusive common-function review, define AFN's current mission boundary, identify duplication, and attach personnel and funding to any confirmed expansion.
5
Finding
WMA / ATSD(PA) / Navy / DISA Decision
Major cost reductions and divestment decisions have been made before replacement capabilities, transition plans, dependencies, and sustainment funding were fully established.
Observable Pattern
Funding was removed to force an accelerated Riverside facility closure before AFN had an approved plan, design, or cost estimate for its replacement cloud playout system. The Deferred Resignation Program removed the AFN Broadcast Center's Director, Chief Engineer, and Resource Manager within the same window that every other accepted risk on this register depends on that expertise to mitigate. DTS satellite funding was cut, with continuation resting on Navy O&M funds that are not yet confirmed. DTH funding was left to expire without regard for dependencies, placing 29 over-the-air transmitters in jeopardy before an IP-based replacement was ready. And the BOSS contract was eliminated — the right call — but without a clear inventory of the roughly 40 FTE functions it covered, leaving AFN to identify requirements and convert positions after the contract expires.
Mission Consequence
Capability gaps, loss of institutional knowledge, unfunded dependencies, emergency contract actions, uncertain mission coverage, and the possibility that legacy capability ends before replacement capability is operational.
Management Intervention
Require transition-readiness criteria before removing funds or capabilities: approved replacement design, cost estimate, accountable owner, funded dependencies, workforce transition plan, and verified initial operational capability.
Cross-Cutting Friction
Decision Latency
AFN spends significant time waiting for decisions, approvals, funding, requirements validation, contracting action, ownership determinations, and stakeholder coordination. The organization does not appear to measure the time from requirement identification to management decision.
Procurement cycle time alone is not enough (Risk 14 addresses that stage specifically). Decision latency — the time consumed before a requirement is even validated and assigned a decision authority — should be measured separately.
Customer & Stakeholder
Operational Customers Must Be in the Decision Loop
AFN supports more than combatant command public affairs offices. Installation commanders and local public affairs leaders use AFN for command information, force protection, emergency communication, crisis response, and connection with geographically dispersed military communities.
Removing an installation communication capability solely from a headquarters perspective is like deactivating the installation's fire hydrants because they appear lightly used during routine operations. The capability is built, maintained, exercised, and trusted before the emergency — not improvised after it begins.
Risk-to-Finding Matrix
Where Each Accepted Risk Lands
All fourteen accepted risks, cross-referenced against the five systemic findings. Several risks support more than one finding.
Select a risk or a finding to isolate its relationships.
Matrix of fourteen accepted risks against five systemic findings. A filled dot indicates the risk supports that finding.
Accepted Risk
Critical High SignificantF1 Governance Disconnected From the Operational CustomerF2 Absence of Lifecycle and Project Management DisciplineF3 Requirements Weak, Solutions Over-PrescribedF4 Scope Expands Without Charter Clarity or ResourcesF5 Short-Term Savings Create Long-Term Operational Risk
This matrix is an analytical synthesis prepared to support an organizational effectiveness review. It does not replace the authoritative AFN Accepted Risk Register, which carries the full text, action owners, and escalation triggers for every risk: risks.dx1.dev.