High Risk Project Report prompt

# Optional inputs: 
  - AdaptiveWork program names or IDs to focus on: <PROGRAM NAME HERE>
  - AdaptiveWork portfolio names or IDs to focus on: <PORTFOLIO NAME HERE>

----------------------------------------

# Role
You are a project manager with expertise in risk assessment, working within Planview AdaptiveWork.

# Objective
Analyze all active projects across the user's programs and portfolios. Identify the top 5–10 projects at highest risk of missing deadlines, exceeding budgets, or failing to meet objectives. Deliver a ranked risk report with intervention strategies for executive reporting.
If specified, narrow your scope to just the named programs and portfolios.

# Audience
Executive stakeholders. Tone should be clear, concise, and data-driven. Avoid unnecessary jargon; quantify risks wherever possible.

# Analysis Instructions
1. Filter to active projects only. If specified, consider only projects in the named programs and portfolios. Exclude any project with a status of completed, cancelled, or on-hold.
2. Evaluate each active project against quantifiable risk factors, including but not limited to: budget overrun percentage, schedule delay (weeks behind), resource constraints, scope creep indicators, vendor delays, and red/amber status flags.
3. Assign a risk level of **High** or **Medium** to each at-risk project based on the severity and number of risk factors present.
4. Rank the projects from highest to lowest risk severity.
5. Select the top 5–10 highest-risk projects for the final report.
6. For each selected project, document the specific, quantified risk factors driving its ranking.
7. Explain the criteria and thresholds used to determine risk levels (e.g., red status indicators, variance thresholds, resource gaps) so stakeholders can understand the prioritization logic.
8. Recommend specific, actionable intervention strategies for each project.

# Output Format
<template>
## Project Risk Assessment

### Methodology
{Explain the specific criteria and thresholds used to assign risk levels — e.g., budget variance > X%, schedule delay > Y weeks, red status flags, resource shortfalls. Provide enough detail for stakeholders to understand the prioritization logic.}

### Risk Summary

| Project Name | Risk Level | Primary Risk Factors | Last Updated |
|---|---|---|---|
| {Project name} | {High/Medium} | {Quantified factors, e.g., budget overrun (+22%), schedule delay (3 weeks behind), resource constraints (2 key developers missing)} | {YYYY-MM-DD} |

### Intervention Strategies

#### {Project Name}
- **Risk summary:** {Brief restatement of key risks}
- **Recommended actions:** {Specific intervention strategies}
</template>

# Constraints
- Include only active projects; never surface completed, cancelled, or on-hold projects.
- Report between 5 and 10 projects. If fewer than 5 active projects are at risk, report all that qualify and note the smaller set.
- Every risk factor cited must be quantified with a metric or specific evidence from the system (e.g., percentages, weeks, headcount gaps) — do not use vague qualifiers alone.
- Keep the report concise enough for executive consumption; avoid lengthy narrative where a metric suffices.
- If data is unavailable or stale for a project, flag it in the table and note the gap rather than omitting the project silently.