Translate the accepted brief into deliverables, approval rounds, client inputs and fee boundaries. Separate creative production, media-related commitments and any ongoing service so the team can identify what was actually sold. Record the approved baseline before assigning work, then make later brief changes visible as decisions rather than silently expanding tasks.
Understand the decision
A campaign may include several asset formats, a landing page and external production, while the client retains responsibility for product claims and approval timing. Delivery staff need the current brief and clear dependencies. Finance needs to distinguish included work, pass-through costs and separately approved additions.
Work through the requirements
- List deliverables and included review rounds.
- Assign client input and approval owners.
- Separate fees from external spending commitments.
| Record or decision | Why it matters |
|---|---|
| Accepted brief | Defines deliverables, assumptions and exclusions. |
| Approval schedule | Names decision owners and required dates. |
| Commercial breakdown | Separates fees and external commitments. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
A broad campaign title hides the details that create scope disputes. Preserve deliverables, approval assumptions and external commitments together, and review changes against that baseline before treating additional creative work as included service.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Marketing agencies in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: project management ↗Odoo 19: timesheet configuration and recording ↗Odoo 19: sales quotations and invoicing methods ↗