Overview
The handoff document is used when a project transitions from the BD/pitch phase to active production. It ensures the production team has full context on what was sold, what was promised, and what the client expects. Based on the Uber Calgary Stampede 2026 handoff.
What the Handoff Document Should Include
- Project Overview: Client, project name, dates, location, budget range
- What Was Sold: Summary of the approved proposal — scope, deliverables, and any client-specific requests
- Budget Summary: Approved budget breakdown (OOP, services, margin targets)
- Key Client Contacts: Names, roles, email, communication preferences
- Client Expectations: Specific deliverables, timelines, and approval processes discussed during the pitch
- Open Items: Anything unresolved from the pitch phase that production needs to address
- Creative Direction: Approved creative concepts, mood boards, or references
- Risks & Considerations: Known risks, tight timelines, budget constraints, or political sensitivities
Handoff Process
- BD/Account Lead completes the handoff document
- Schedule a 60-minute handoff meeting with the production team
- Walk through every section of the document
- Production Lead asks clarifying questions and documents action items
- Handoff document saved in the project's Drive folder
- Production Lead initiates the Kickoff Checklist
Best Practices
- Complete the handoff within 48 hours of project award
- Include the BDPM, Account Lead, and Production Lead at minimum
- Be explicit about what was NOT included in the scope — this prevents scope creep
- Flag any verbal commitments made to the client that aren’t in the written proposal