How to use the MoSCoW prioritisation template

Start a board from it
Use this template opens a new Freero board with the MoSCoW prioritisation template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “MoSCoW prioritisation”.
Follow the instruction on the board
“A must-have is something the release fails without. If more than half the items are musts, go round again. Writing the won’t-haves down ends repeat debates.”
Fill in each part
- Must have Without it we can’t release. No workaround exists.
- Should have Important, but a workaround exists for now.
- Could have Nice if time allows. First to drop.
- Won’t have this time Agreed out of scope, so we stop debating it.
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the MoSCoW prioritisation board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

RICE scoring
Score ideas by reach, impact, confidence and effort, so the backlog order has reasons.
Release plan
Work per stream across four sprints as task cards in swimlanes, with the release marked.
Design brief
Frame a design project before anyone opens a design tool: the problem, people, constraints, what success means and what to deliver.
Product requirements (PRD)
A one-page spec: problem, goals and non-goals, prioritised requirements, metrics and open questions.
Customer feedback board
A kanban for feature requests and feedback: inbox, under review, planned and shipped.
Launch plan
Who does what before, during and after a launch, in swimlanes per team.