There is no need to pretend someone sits at the desk all night. People asking about event production briefs just need a clear way to leave the right details.
Mahmoud WahbaProject manager, exhibition build and production team
CS1310 working daysWisconsin
Catching event production briefs interest after closing time
Exhibition build and production team, Green Bay, Wisconsin. The evening route gathers event format, venue and technical requirements, sets honest expectations about response times and describes the road to a scoping discussion with the production team.
- Client
- Exhibition build and production team
- Region
- Green Bay, Wisconsin
- Team
- 16 staff; one locally managed operation
- Timeline
- 10 working days after content approval
Q0200:02:00Before
Where they started, and what kept going wrong
Starting point
Evening visitors interested in event production briefs faced a choice: call an empty office or send an unstructured message into the dark.
The problem
For event production briefs, the team could not prioritize what it could not parse. The first working hour went on assembling the queue instead of answering it.
Q0300:04:30Build
What we built
Answer: The evening route gathers event format, venue and technical requirements, sets honest expectations about response times and describes the road to a scoping discussion with the production team. Automated messages are labeled as exactly that.
Features used
After-hours request form
Staff response window
Morning request summary
Clear acknowledgment
Q0400:07:00Schedule
10 working days, approval to handover
Answer: 10 working days after content approval, including staff review and handover.
- Day 0
Content approved
The clock starts once the client approves the content the work is built from.
- Build
What we built
After-hours request form, Staff response window, Morning request summary, and more.
- Review
Staff review
The exhibition build and production team's own team checks the work before it goes live.
- Day 10
Handover
Handed over 10 working days after content approval.
Q0500:09:30After
What changed
Answer: Day to day with event production briefs, overnight interest lands as an organized morning queue. Expectations are honest about response times.
Q0600:11:40Q and A
Questions about this case study
How long did this project take?
10 working days after content approval, including staff review and handover.
Which plan includes this work?
Everything this project used is included on every EventWebStudio plan (Load-In, Showtime, Encore), from $127 a month with the $697 build fee invoiced after launch.
Why is the client not named?
On purpose. The case study names the type of business (exhibition build and production team) and the region (Green Bay, Wisconsin) only, so no business name, web address or logo appears. The quote is Mahmoud Wahba's own words, used with permission.
Q1300:29:00Curtain
See what this would look like for your event business
A 30-minute walk-through on your screen, starting from this case study. Plans from $127 a month, the $697 build fee invoiced only after launch.