# Prioritization & Scope Guardrails
**Protect delivery by ranking work and defining clear boundaries**  
*Prodora Template · prodora.io*

List candidate features, modernization items, or work packages. Score them on business impact and effort/risk. Use the results to decide what is in scope for the first release and what waits.

---

## Project details

| Field | Value |
|-------|-------|
| **Project** | |
| **Target Release / Phase** | |
| **Date** | |

---

## Work Item Ranking

| # | Work Item / Feature | Business Impact<br>*(1–5)* | Effort / Risk<br>*(1–5)* | Priority<br>*(Impact ÷ Effort)* | In Scope?<br>*(Y / N / Later)* |
|---|---------------------|----------------------------|--------------------------|---------------------------------|--------------------------------|
| 1 | | | | | |
| 2 | | | | | |
| 3 | | | | | |
| 4 | | | | | |
| 5 | | | | | |
| 6 | | | | | |

*Tip: Higher impact + lower effort = higher priority. Use the ratio as a guide, not a rigid rule.*

---

## Scope Guardrails

**We will ship when…** *(definition of done for this phase)*



**We will not…** *(explicit exclusions)*



**Change requests must…** *(how new ideas get evaluated)*



---

## Decision Summary

| In Scope for this phase | Deferred (Later / Next phase) |
|-------------------------|-------------------------------|
| | |
| | |
| | |

---

**How to use:** Complete the ranking with the core stakeholders present. Lock the guardrails before detailed design or development begins. Revisit only when a change request meets the criteria you defined.

---

*Prodora · prodora.io · Product-led software. Built to fit.*