ATT004_SurvivorCCE_Template_RAIDLog.xlsx
XLSX spreadsheet 39 KB Posted
- Attached to
- Solicitation - World Trade Center Health Program - Survivor Clinical Center of Excellence
- Solicitation number
- CDC-75D301-01-Solicitation-WTCHP
About this file
The file is a Risk, Action, Issue, and Decision (RAID) Log template for a World Trade Center Health Program (WTCHP) contract, designed to systematically track and manage project risks, issues, actions, and decisions. The template provides comprehensive guidelines for documenting potential and existing project challenges, including detailed criteria for assessing probability, urgency, impact, and priority across different functional areas such as contract management, member services, case management, and pharmacy services.
The RAID log includes structured columns for categorizing items by contract type, risk probability (low/medium/high), urgency, impact, priority, and response strategy. It enables project stakeholders to track items through various statuses (open, pending, closed) and capture essential metadata like date identified, mitigation strategies, and responsible owners. The template also includes a "Lessons Learned" section to document implementation or operational insights that could improve future transition planning and operational performance for the World Trade Center Health Program Survivor Clinical Center of Excellence contract.
View the file
Other files
Show all 41
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Introduction and Definitions
| RAID Introduction |
| The Risk, Action, Issue, and Decision (RAID) Log is meant to be used to document the following items to bolster their tracking: |
Risks are about potential problems that could have an adverse impact on the project. The information for risk's functional area, status, mitigation strategy, important POCs, and date identified are included.
Issues are problems that have occurred throughout the project. The information related to the issues are designed to capture ongoing problems by program arm and to assign a relative priority level.
Actions are built for the future documentation of high-level program actions to mitigate risks.
Decisions are meant to capture important decisions made by the program to mitigate risks and issues.
| Column Definitions |
| RAID Category: describes the item in sufficient detail to understand it in context and the likely impact. |
| Contract: delineates which contract the item is associated with (PBM, NPN, CCE, HPS, etc.). Program wide items that impact more than a single contract are labeled WTC. |
| Risk Probability: likelihood the risk will be triggered without response (see below criteria for Low/Medium/High). |
| Urgency: likelihood a risk or issue will be triggered or cause a major consequence based on the timeliness of a resolution (see below criteria for Low/Medium/High) (time based). |
| Impact: anticipated level of negative effect on transition (including schedule, cost, performance, and/or quality impacts) should the risk or issue occur (see below criteria for Low/Medium/High). |
| Priority: combination of impact and urgency; the items with the highest priority will require active handling. |
| Risk Response: Approach to handle the risk (Accept, Avoid, Mitigate). |
| Mitigation Strategy: planned action(s) to respond to the risk with focus on steps that decrease the probability or impact of the risk. |
| Status: item is open, pending, or resolved (closed). |
| Due Date: date when an item is due, considering the impact score attached to the item. |
| Date Closed: date on which an item was marked "resolved" on the RAID after being managed. |
| Criteria for Risk Probability |
| Low: risk is unlikely to occur; there is minimal chance to realize this risk, and historical evidence suggests the risk is unlikely to be occur. |
| Medium: risk has a reasonable likelihood of being triggered; historical evidence suggests the risk may happen. |
| High: risk has a significant likelihood of being triggered; historical evidence suggests the risk has occurred previously and is likely to occur again. |
| Criteria for Risk and Issue Urgency |
| Low: action could be taken to achieve resolution if time and resources permit but contract/Program operations are not dependent on said action. |
| Medium: action should be taken as soon as feasibly possible, given existing time and resource constraints. Contract/Program operations are dependent on eventual action. |
| High: action must be taken immediately with surged resources to avoid immediate and major negative impact on contract/Program operations and member care. |
| Criteria for (Risk, Action, and Issue) Impact |
| Low: item should have minimal impact on cost, schedule, performance, or quality. |
| Medium: item will have a moderate impact and may affect cost, schedule, performance, or quality; impact is manageable and/or acceptable. |
| High: item will have a significant impact affecting cost, schedule, performance, quality and/or inhibits multiple interdependencies. These impacts will require active management and may require substantial changes to the contract, requirements, or approach. |
| Criteria for Status |
| Open: item is awaiting decision or unresolved without currently being managed. |
| Closed: item has reached a resolution and is closed. |
| Pending: item is either newly added or ready to be review for closure. |
| Lessons Learned |
| This tab is intended to provide documentation of implementation or operational items that were identified during the transition but were previously not widely known. Previous knowledge of these items would have either been useful in transition planning or should be disseminated for improved operational performance. |
RAID
| ID # | RAID Category | Contract | Functional Area | RAID Description | Date Identified | Identified By | Probability | |
| (Risk) | Urgency | |||||||
| (Risk, Issue) | Impact | |||||||
| (Risk, Issue) | Priority | |||||||
| (Risk, Issue) | Response | |||||||
| (Risk) | Risk Mitigation Strategy | Status | Due Date | Date Closed | Notes | Owner | ||
| 1 | ||||||||
| 2 | ||||||||
| 3 | ||||||||
| 4 | ||||||||
| 5 | ||||||||
| 6 | ||||||||
| 7 | ||||||||
| 8 | ||||||||
| 9 | ||||||||
| 10 | ||||||||
| 11 | ||||||||
| 12 | ||||||||
| 13 | ||||||||
| 14 | ||||||||
| 15 | ||||||||
| 16 | ||||||||
| 17 | ||||||||
| 18 | ||||||||
| 19 | ||||||||
| 20 | ||||||||
| 21 | ||||||||
| 22 | ||||||||
| 23 | ||||||||
| 24 | ||||||||
| 25 | ||||||||
| 26 | ||||||||
| 27 | ||||||||
| 28 | ||||||||
| 29 | ||||||||
| 30 | ||||||||
| 31 | ||||||||
| 32 | ||||||||
| 33 | ||||||||
| 34 | ||||||||
| 35 | ||||||||
| 36 | ||||||||
| 37 | ||||||||
| 38 | ||||||||
| 39 | ||||||||
| 40 | ||||||||
| 41 | ||||||||
| 42 | ||||||||
| 43 | ||||||||
| 44 | ||||||||
| 45 | ||||||||
| 46 | ||||||||
| 47 | ||||||||
| 48 | ||||||||
| 49 | ||||||||
| 50 |
Lessons Learned
| # | Title | Description | Functional Area | Identified By | Date Identified | Notes |
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
| 4 | ||||||
| 5 | ||||||
| 6 | ||||||
| 7 | ||||||
| 8 | ||||||
| 9 | ||||||
| 10 | ||||||
| 11 | ||||||
| 12 | ||||||
| 13 | ||||||
| 14 | ||||||
| 15 | ||||||
| 16 | ||||||
| 17 | ||||||
| 18 | ||||||
| 19 | ||||||
| 20 | ||||||
| 21 | ||||||
| 22 | ||||||
| 23 | ||||||
| 24 | ||||||
| 25 | ||||||
| 26 | ||||||
| 27 | ||||||
| 28 | ||||||
| 29 | ||||||
| 30 | ||||||
| 31 | ||||||
| 32 | ||||||
| 33 | ||||||
| 34 | ||||||
| 35 | ||||||
| 36 | ||||||
| 37 | ||||||
| 38 | ||||||
| 39 | ||||||
| 40 | ||||||
| 41 | ||||||
| 42 | ||||||
| 43 | ||||||
| 44 | ||||||
| 45 | ||||||
| 46 | ||||||
| 47 | ||||||
| 48 | ||||||
| 49 | ||||||
| 50 |
Reference
| Functional Area | Status | Category | Risk Probability | Urgency | Risk Response | Impact | Priority |
| Contract Management | Open | Risk | N/A | Low | N/A | N/A | N/A |
| Member & Medical Services | Pending | Issue | Low | Medium | Accept | Low | Low |
| Case Management | Closed | Action | Medium | High | Mitigate | Medium | Medium |
| Coordination of Benefits | Decision | High | N/A | Avoid | High | High | |
| Pharmacy Services | |||||||
| Data Collection, Transfer, and Reporting | |||||||
| Performance Monitoring & Quality | |||||||
| Communications | |||||||
| Other |
List
| Risk Response | Status | Functional Area | Priority | Probability | Impact |
| Accept | Open | Contract Management | High | High | High |
| Avoid | Closed | Member Services | Medium | Medium | Medium |
| Mitigate | Benefit Administration | Low | Low | Low | |
| Provider Network Management | |||||
| Claims Processing | |||||
| Communications | |||||
| Data Management | |||||
| Reporting | |||||
| Certification | |||||
| Transition |
File details come from the government source that posted it. Updated .