A deliverable category is not yet a scope
“Social assets” could mean two static posts or a launch package across four channels. “A deck” could mean a ten-slide narrative or a reusable sales template with several versions.
A useful deliverable names enough of the output for the team to count it and understand where it needs to work.
Turn a category into countable work
Describe the output in one line, using only the details that change the work.
Campaign module
Add the business moment, message hierarchy, participating channels, dependencies, and the relationship between campaign assets. State which deliverable establishes the direction and which ones adapt it.
Name the campaign-wide source truth. If several teams own copy, offers, photography, or legal claims, show the owner of each input.
Social module
List the platform, placement, quantity, aspect ratio, duration where relevant, call to action, and source assets. Count crops and copy variants explicitly.
Separate standing platform specs from the campaign message. The team should be able to reuse production requirements without carrying old creative direction into the next request.
Product launch module
Add the release truth, target audience state, approved claims, review requirements, launch milestones, and an asset matrix. Product, legal, and go-to-market dependencies should be visible before creative review.
Explain what the audience already knows about the product and what changes with this release. That distinction shapes the amount of context the creative must carry.
Count the work before estimating it
Read the scope back as a list of final outputs. If two people produce different totals, the request still contains ambiguity.
Leave genuine unknowns open. Name an owner and note when the answer will affect estimation or production.