Glossary
What is a clarification brief?
A short artifact that separates what is known from what is assumed from what is still an open question, produced when a raw request is shaped into a demand.
The split matters because a request written in one confident voice makes an assumption indistinguishable from a fact, and every downstream estimate then inherits it. The assumptions list is also a risk register before you have one.
Related terms
- Demand — A work request that has entered the delivery lifecycle — the unit a delivery governance system tracks from intake to decision.
- Demand management — The practice of deciding what happens to requested work — shaping raw requests into decidable demands, refusing or parking some on the record, and committing the rest against real capacity.
- Demand lifecycle — The path a work request takes from arrival to a closed outcome: Capture, Shape, Decide, Plan, Commit, Deliver, Learn — where a demand only walks the stages it needs.
This definition comes from building DeliverySheet — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date.
$189/month per workspace, unlimited members. 7-day free trial — card required, cancel before it ends and you're not charged. I answer the support email myself.