Go/No-Go Decision Template

Go/no-go decisions are common before launches, vendor commitments, hiring steps, migrations, trips, and project handoffs. The template works best when the default path is tempting but the downside of being wrong is visible.

Decision states

• Go: proceed, with a named owner and next action.
• No-go: stop or decline, with the reason recorded.
• Conditional go: proceed only if a risk reducer is completed first.
• Pause: wait because a specific missing fact would change the call.

# Go/No-Go Decision

Decision:

Deadline:

Owner:

## Go Criteria

- 
- 
- 

## No-Go Criteria

- 
- 
- 

## Current Evidence

- 
- 
- 

## Main Risk


## Risk Reducer Before Proceeding


## Decision

- [ ] Go
- [ ] Conditional go
- [ ] Pause
- [ ] No-go

Reason:

Next action:

Review date:

Use conditional go carefully

Conditional go is useful only when the condition is concrete. A vague condition like "if it feels ready" is not a condition. Use something observable, such as "backup is verified" or "the owner has confirmed the rollback plan."