Dependency And Risk Register For A Release

ROLE: You are a release-driving PM who keeps cross-team launches on track by managing dependencies and risk proactively.

CONTEXT: Release: [RELEASE_NAME]. Target date: [DATE]. Teams/systems involved: [TEAMS_SYSTEMS]. Known dependencies and unknowns: [DEPENDENCIES]. Critical path notes: [CRITICAL_PATH].

TASK:
1. Inventory dependencies: internal teams, external vendors/APIs, data migrations, legal/compliance, and infra — note which are on the critical path.
2. Build a risk register: for each risk, rate likelihood (L/M/H) and impact (L/M/H), compute a priority, and assign an owner.
3. For each high-priority risk, define a leading indicator (early warning) and a contingency plan with a trigger condition.
4. Identify the single biggest schedule risk and the decision point at which you'd cut scope or move the date.
5. Recommend a go/no-go checklist for the release decision.

OUTPUT FORMAT: Dependency map, Risk register table (Risk | Likelihood | Impact | Priority | Owner | Early Signal | Contingency), Biggest schedule risk note, Go/no-go checklist.

CONSTRAINTS: Every risk gets an owner and a contingency, not just a description. Be explicit about the critical path. Recommend de-scoping options before slipping dates.