# Project Launch Review Checklist

Use this reference to review a Basecamp project launch plan before execution. Classify findings by severity and return the reviewer output contract at the end.

## Severity Levels

### Blocking
A blocking issue means the launch should not proceed until the issue is fixed or an explicit override is recorded. Blocking issues create a high risk of launching the wrong project, notifying the wrong people, or starting without authority.

Blocking examples:
- No goal is stated.
- No DRI is named.
- No success criteria are defined.
- Timeline is impossible.
- External visibility is unknown.
- No Basecamp approval is documented.
- Missing `Vorlagen` with no fallback.
- Notification behavior is undisclosed.
- Existing project was not inspected before planning.
- No cautious execution plan is provided.

### Important
An important concern means the launch may proceed only with awareness and mitigation. Important concerns can cause confusion, rework, stakeholder friction, or schedule pressure.

Important examples:
- Timeline is aggressive.
- Owner appears overloaded.
- Too many placeholders remain.
- Dates are speculative.
- Too many check-ins are planned.
- Stakeholder approval is unclear.
- Kickoff plan is over-optimistic.
- Project Brief needed but missing.

### Minor
A minor improvement makes the launch clearer or easier to execute but does not materially change readiness.

Minor examples:
- Wording improvements.
- Clearer milestones.
- Cleaner task descriptions.

## Review Guidance

- Prefer concrete evidence from the project plan over assumptions.
- Escalate uncertainty about authority, visibility, or notifications to Blocking.
- Escalate repeated Important concerns to Blocking when they make execution unsafe.
- Keep recommendations practical and tied to launch readiness.

## Project Launch Review

### Status
Approved | Approved with concerns | Blocked

### Blocking Issues
- Issue:
  Why it matters:
  Required fix or override:

### Important Concerns
- Concern:
  Possible consequence:
  Recommended mitigation:

### Minor Improvements
- Improvement:
  Suggested edit:

### Reviewer Recommendation
Proceed | Proceed after acknowledgement | Do not proceed yet