MoSCoW Prioritization Template
Categorize features into Must Have, Should Have, Could Have, and Will Not Have. This template helps your team align on scope, manage stakeholder expectations, and prevent the scope creep that derails releases.
Why MoSCoW works for product teams
MoSCoW is the simplest prioritization framework that actually changes behavior. Unlike numerical scoring systems, MoSCoW forces a binary conversation: is this feature in scope or out? That directness is what makes it effective in stakeholder meetings where scope negotiations happen.
The framework works because it replaces vague priority labels like “P1” and “P2” with categories that have concrete definitions. A Must Have is not just “important” but “the release fails without it.” That distinction changes how teams discuss trade-offs.
MoSCoW is best used at the beginning of a project to define scope, and again before each release to confirm what is in and out. It pairs well with more granular frameworks like RICE or Impact-Effort when you need to order items within a category.
The MoSCoW template
Four categories with clear definitions, examples, and tips for keeping each bucket honest.
Must Have
Non-negotiable requirements
These are the features without which the product cannot launch or the project fails. If a Must Have is missing, the release has no value. Be ruthless here. Most teams put too many items in Must Have. A good rule of thumb: if the product can still ship without it, it is not a Must Have.
Example: "User authentication and login flow. Without this, no user can access the product. This is a hard requirement for launch."
Tips
- Apply the "would we cancel the release?" test
- Must Haves should be fewer than 60% of total scope
- Regulatory and compliance requirements are usually Must Haves
- If everything is Must Have, nothing is prioritized
Should Have
Important but not critical
Features that are important and expected by users but the product can function without them for a short period. Should Haves are typically included in the release unless time or resources run out. They are the first things to cut if scope pressure appears, but they are planned for the current cycle.
Example: "Email notification preferences. Users will want to control which emails they receive. The product works without this, but users will complain if it takes more than one release to add."
Tips
- Should Haves are painful to omit but survivable
- Plan to build them but accept they may slip
- Differentiate from Must Haves by asking: can we launch without this?
- Typically 20-30% of total scope
Could Have
Nice to have, not expected
Desirable features that would improve the experience but are not expected by users. Could Haves are included only if there is remaining capacity after Must Haves and Should Haves are delivered. They are the first to be deferred to a future release.
Example: "Dark mode toggle. Some users have requested it and it would improve the experience for night-time usage, but no one will choose a competitor because we lack dark mode at launch."
Tips
- Low cost of exclusion from the current release
- Often good candidates for quick wins if scope allows
- Keep a shortlist of Could Haves for backfill opportunities
- Typically 10-20% of total scope
Will Not Have (this time)
Explicitly out of scope
Features that have been discussed but are explicitly excluded from this release. Listing them is just as important as listing what you will build. It prevents scope creep and sets expectations with stakeholders. Will Not Haves may appear in a future cycle.
Example: "Multi-language support. Valuable for international expansion but not in scope for the initial launch targeting the US market. Planned for Q3."
Tips
- Explicitly listing exclusions prevents scope creep
- Include a reason for each exclusion
- Note which Will Not Haves are planned for future cycles
- Use this to manage stakeholder expectations proactively
Related templates
RICE Prioritization Template
Score features numerically using Reach, Impact, Confidence, and Effort.
View template →Impact-Effort Matrix Template
Plot features on a 2x2 grid to find quick wins and strategic bets.
View template →Feature Audit Template
Audit your existing feature set for usage, value, and maintenance cost.
View template →Frequently asked questions
Scope your next release with confidence
Vantage helps you categorize and prioritize features using your actual product data. Free to start.
Free to start. No credit card required.