DI-ADMN-82531
Hot Issues Report
A daily status report provided by the contractor on the status of high priority/high visibility telecom network outages and/or telecom service installations.
Approval DateApril 23, 2026
AMSC Number10650
Preparing ActivityDC
Project NumberADMN-2026-006
OPR—
DTIC Applicable—
GIDEP Applicable—
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
A daily status report provided by the contractor on the status of high priority/high visibility telecom network outages and/or telecom service installations.
Preparation Instructions
1Reference documents.The applicable issue of the following documents shall be as specified in the contract:
1.1Approved Contract and Task/Delivery Order(s)
2.1The Hot Issues Report shall be provided in a standardized format.
2.2Deliverables shall be submitted electronically in one or more of the following formats:
2.2.1Microsoft Word (.docx)
2.2.2Microsoft Excel (.xlsx) for tabular issue tracking
2.2.3Email-formatted report when rapid dissemination is required
2.3.112-point Times New Roman font (Word reports)
2.3.2Clear section headers and date/time stamps
2.3.3Concise, executive-level language suitable for daily review
2.4Reports shall be unclassified unless otherwise authorized.
3Content.The report shall contain the following:
3.1.1Reporting date and time
3.1.2Reporting period covered
3.1.3Contract and Task/Delivery Order number(s)
3.1.4Call Order Number (if applicable)
3.1.5Contractor point of contact
3.2Issue Summary (Executive View)
3.2.1Total number of open hot issues
3.2.2Newly identified issues since last report
3.2.3Issues resolved or downgraded
3.2.4Overall operational impact assessment
3.3Hot Issue DetailsFor each identified hot issue, the report shall include:
3.3.1Issue identifier or tracking number
3.3.2Affected service(s) (e.g., network, hosting, compute, storage, telecom)
3.3.3Affected site(s), system(s), or Mission Partner(s)
3.3.4Date and time issue was identified
3.3.5Issue severity / priority level
3.3.6Description of the issue and operational impact
3.4.1Known or suspected root cause (if identified)
3.4.2Current status (investigating, mitigating, resolved, monitoring)
3.4.3Actions taken to date
3.5Mitigation and Resolution Plan
3.5.1Immediate mitigation actions
3.5.2Planned corrective actions
3.5.3Lessons Learned (if applicable)
3.5.4Estimated time to resolution (ETR)
3.5.5Dependencies or external constraints
3.6Government and Contractor Actions
3.6.1Actions required by the Government
3.6.2Actions required by the Contractor
3.6.3Decision points requiring government direction
3.7Risk and Impact Assessment
3.7.1Mission impact assessment
3.8Communications and Notifications
3.8.1Stakeholders notified
3.8.2Frequency and method of updates
3.8.3External communications (if applicable)
Schema v3.0Community-maintained · Verify against ASSIST