Notice: applying this to your agency.
The IT Project Resources are not meant to replace your agency’s internal project management practices or prescribe how you must operate. Instead, they offer concepts and tools that can strengthen delivery by providing a scalable framework for project level coordination. All project documentation should be maintained throughout each stage in alignment with agency policies and, where applicable, WaTech requirements and oversight expectations.
For Projects and Programs
Create a unified framework for tracking and managing key is essential. Some embed this in the PMP, and some have a dedicated plan. The RAIDc Plan framework ensures traceability, accountability, and oversight visibility throughout the lifecycle. Establishing and maintaining RAIDc tool, covering risks, action items, issues, and decisions as well as change requests impacting changes to scope is required. This tracking is essential for effective governance, cross-agency coordination, and WaTech oversight.
Special note to projects who do not have a documented Change Plan, and we support a streamlined approach to include the tracking of change requests within your RAIDc tool WaTech is recommending the development of a RAIDc (Risks, Actions, Issues, Decisions and changes) that establishes a centralized location for efficient project management and reporting.
For Programs with Agency‑Led Sub‑Projects
The RAIDc Plan must define individual ownership at both the program and sub-project levels, ensuring each agency is accountable for maintaining its own logs while contributing to the enterprise view. Establish a unified framework, including standardized categories, severity ratings, and escalation protocols that apply across agencies. Enable traceability across sub-projects, showing how local risks, actions, issues, decisions, or changes impact the broader program and enterprise outcomes. Clarify update frequency and reporting cadence, including how sub-project logs roll up into program-level dashboards and WaTech milestone reviews. Support cross-agency resolution workflows, especially for shared RAID items, or enterprise-wide change requests. Integrate with program reporting tools, such as governance dashboards, implementation schedules, and impacted group engagement plans.
The RAIDc Plan should be initiated early and actively maintained throughout the lifecycle of the program. It must be reviewed and accepted by the program’s governance body and updated in coordination with all participating agencies to ensure there is transparency, accountability, and timely decision-making across respective sub-projects.
Key Activities:
- Define categories, severity ratings, and escalation protocols
- Assign ownership for each RAIDc element
- Establish update frequency and reporting cadence
- Integrate with governance dashboards and milestone reviews
- Maintain logs in collaboration site and oversight reporting tools
WaTech available template: Risk, Action Item, Issue, Decision, & Change Plan