I cared about the redirect map as much as the redesign. Too many people hold our old event production briefs link for it to be treated as an afterthought.
Nigel CoburnProduction coordinator, corporate event production company
CS1520 working daysOhio
No dead ends: migrating event production briefs properly
Corporate event production company, Akron, Ohio. Legacy addresses were inventoried, each mapped to a relevant destination, and the full redirect plan reviewed before launch.
- Client
- Corporate event production company
- Region
- Akron, Ohio
- Team
- 7 staff; one locally managed operation
- Timeline
- 20 working days after content approval
Q0200:02:00Before
Where they started, and what kept going wrong
Starting point
Nobody had a complete list of where the event production briefs pages were linked from. The redesign was about to find out the hard way.
The problem
Day to day with event production briefs, every old address was a potential dead end for someone following a saved link. Nobody had an inventory, so nobody knew the size of the risk.
Q0300:04:30Build
What we built
Answer: Legacy addresses were inventoried, each mapped to a relevant destination, and the full redirect plan reviewed before launch. The new reference content covers production responsibilities and previous event formats under navigation that matches the new structure.
Features used
URL inventory
Redirect map
Internal link updates
Missing-page checks
Launch review
Q0400:07:00Schedule
20 working days, approval to handover
Answer: 20 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
URL inventory, Redirect map, Internal link updates, and more.
- Review
Staff review
The corporate event production company's own team checks the work before it goes live.
- Day 20
Handover
Handed over 20 working days after content approval.
Q0500:09:30After
What changed
Answer: For event production briefs, previously shared links now arrive at relevant current information rather than a dead end. The scope protects continuity of access; it does not assume search rankings are unaffected.
Q0600:11:40Q and A
Questions about this case study
How long did this project take?
20 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 (corporate event production company) and the region (Akron, Ohio) only, so no business name, web address or logo appears. The quote is Nigel Coburn'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.