Marketing Campaign RAID Log
This is a practical guide to building a raid log for a marketing campaign project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of planning and running a marketing campaign to deadline.
What a RAID Log is
A raid log is a consolidated log of Risks, Assumptions, Issues and Dependencies. For the full concept and how it works in general, see RAID Log. On a marketing campaign project it plays the same role, tuned to this kind of work.
Why it matters for a Marketing Campaign project
Marketing Campaign projects live or die on planning and running a marketing campaign to deadline. A well-built raid log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how marketing campaign projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Marketing Campaign-specific considerations
Tailor the raid log to the risks that most often derail marketing campaign projects:
- Shifting creative direction
- Fixed launch dates
- Cross-agency coordination
Example
On a real marketing campaign project, the raid log would be shaped by planning and running a marketing campaign to deadline. In particular, it should explicitly account for the project’s biggest risks — shifting creative direction, fixed launch dates, cross-agency coordination — rather than treating them as afterthoughts.