Planning and workload tools
Event work breakdown builder
Your committee has a long list of things to do and needs to see how they fit under a few deliverables.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
…
The short answer
This builder turns a list of rows into a numbered hierarchy: deliverables at the top, work packages beneath. Each item can carry an owner role and an acceptance condition.
Items without an owner or an acceptance condition are listed for follow-up. If a parent is removed, its children stay on the list and are flagged, so nothing is orphaned silently.
How to enter the breakdown
- Give every row a short ID such as A, A1 or A2. IDs must be unique.
- Name the deliverable or work package in plain words.
- Put the ID of the parent row in Parent ID. Leave it blank for a top-level deliverable.
- Add an owner role, not a person's name.
- Write the acceptance condition: how someone will know the item is done.
How to read the result
The table shows each item with a code such as 1, 1.1 or 1.2.1, indented under its parent. The Flags column shows No owner, No acceptance condition, or Parent not found.
The numbers follow the order in which you entered rows under each parent. Reorder your rows to reorder the numbering.
What happens when you delete a parent
If you remove a parent row, its children are not dropped. They are shown at the top level with the flag Parent not found until you give them a new parent or remove them on purpose.
The tool therefore never leaves a task orphaned without telling you. Deciding whether the child tasks still belong in scope is a committee decision.
Limits
The breakdown shows the structure you entered. It does not decide whether the scope is complete or whether a work package is the right size.
Use the dependency mapper once packages exist and you need to know what must finish before what, and the responsibility matrix builder to settle who is accountable.
Worked example · Fictional example
A fictional conference breakdown
Fictional organisation and items, to show the flags.
A fictional society enters six rows: Programme with two child packages, Venue and suppliers with one, and a Registration page whose parent X does not exist. The schedule row has no owner and no acceptance condition.
The result shows the numbered tree, lists the schedule row as without owner, and flags the registration page as Parent not found rather than hiding it.
Use this yourself
Work breakdown worksheet
Fill in one row per deliverable or work package. Children use the ID of their parent.
| ID | Deliverable or work package | Parent ID | Owner role | Acceptance condition |
|---|---|---|---|---|
| A | ||||
| A1 | A | |||
| A2 | A | |||
| B |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The event has a familiar format and the previous breakdown can be reused.
- One person can keep the breakdown current and chase owners.
Outside planning help earns its fee when
- Scope keeps growing and nobody can say what is in or out.
- Several teams work in parallel and acceptance conditions are never written down.
- A funder or senior committee needs a defensible scope before approving spend.
Want the breakdown turned into a project plan?
An Event Blueprint places a breakdown like this alongside the timeline, responsibilities and supplier requirements, so scope and ownership are agreed in one pack. Send your current list as it stands.
Questions organisers ask
How many levels can the breakdown have?
As many as your IDs allow. Two or three levels usually keep it readable.
Why is a task shown at the top level with a flag?
Its parent ID does not match any row. Fix the parent ID or remove the task on purpose.
Can I name people as owners?
Use roles. Roles survive changes in who holds them and keep personal names out of exports.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.