Trade Show RAID Log
This is a practical guide to building a raid log for a trade show project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of planning a trade-show presence.
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 trade show project it plays the same role, tuned to this kind of work.
Why it matters for a Trade Show project
Trade Show projects live or die on planning a trade-show presence. 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 trade show projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Trade Show-specific considerations
Tailor the raid log to the risks that most often derail trade show projects:
- Booth and logistics deadlines
- Lead capture
- ROI measurement
Example
On a real trade show project, the raid log would be shaped by planning a trade-show presence. In particular, it should explicitly account for the project’s biggest risks — booth and logistics deadlines, lead capture, ROI measurement — rather than treating them as afterthoughts.