One calendar, every speaker, zero plan confusion
A large multi-brand digital publisher built a consolidated event operations hub in Airtable that links run-of-show schedules, speaker invitation trackers, and a master event calendar across bases, giving 35 team members a single source of truth and ending coordination gaps between Production and Audience Building.
The problem
The live events team was operating across fragmented tools: run-of-show schedules in one place, speaker contact lists in another, and event agendas scattered without a reliable link between them. With multiple publications running their own calendars, Production and Audience Building had no shared view of what was happening when.
Manual speaker data entry left contact fields incomplete. Coordinating tasks between teams required repeated status checks, and stakeholders outside the core team had no governed way to get visibility without being given edit access they did not need.
What they built
The team deployed Airtable as the single hub for all event operations. A run-of-show base tracks event timelines and schedules. A speaker tracker manages invitations, statuses, and contact details. A master event calendar links agendas across bases so every team sees the full picture in one view.
Viewer roles give editors and stakeholders read access without edit risk. Production and Audience Building coordinate in shared views. The team has also proposed Salesforce integration and AI-assisted speaker field completion to reduce ongoing manual data entry.
The outcome
The events team called the consolidated setup a game changer. With 35 users on a single source of truth, plan confusion dropped to zero and coordination between Production and Audience Building became routine rather than reactive.
Viewer roles extended visibility to 15 editors and additional stakeholders without governance risk. The architecture is already positioned for cross-brand standardization as the events function scales.
Inside the solution
Event Operations & Speaker Management
Events & Experience Management
Events & Live Operations
- Run-of-show schedules and event timelines
- Speaker tracker for invitations, statuses, and contact details
- Master event calendar linking agendas across bases
- Coordination views for Production and Audience Building
- Viewer roles for stakeholder visibility without edit access
- Proposed AI to auto-fill missing speaker fields
- Manual speaker data entry and missing contact details
- Plan confusion from decentralized event ownership
- Difficult cross-team task coordination
- No governed stakeholder visibility
- Inconsistent contact data for invited speakers
- Fragmented calendars across publishing brands
- Consolidated event operations in a single source of truth
- Wider stakeholder visibility via viewer roles
- Improved cross-team coordination without extra meetings
- Reduced manual coordination and data entry
- Foundation for cross-brand standardization
- Potential contact data accuracy via proposed Salesforce sync
- Live Events
- Content & Experience
- Production
- Audience Building
- Salesforce
- Legislative data platform
- Asana
- Splash
Event Operations & Speaker Management
Run every event from one hub: a master calendar linked to speaker invitation trackers, minute-by-minute run-of-show timelines, and cross-team task boards that Production and Audience Building share. Automations turn new and confirmed invitations into assigned tasks and send a weekly calendar digest, while AI fields draft speaker bios, follow-up emails, and stakeholder briefings for you.
From scattered calendars to a consolidated event operations hub
Start with the speaker tracker
Build the master event calendar
Extend visibility with viewer roles
FAQ
Frequently asked questions
A master event calendar links agendas from multiple run-of-show bases into a single view. Every team sees the same data, and a viewer-role structure means stakeholders can check status without editing anything by accident.
A dedicated speaker tracker records invitation status, contact details, and any follow-up notes for every invited speaker. The tracker links directly to the relevant event record so context is never lost.
Production manages run-of-show timelines. Audience Building tracks promotional coordination. Editors get viewer access to monitor progress. A small core team owns the base structure and handles updates.
Not yet in the deployed workflow. The team has proposed AI to auto-fill missing speaker fields and to keep contact data current via an integration with an external legislative data platform, but those workflows are in the proposal stage.
Yes. The base structure was designed with cross-brand standardization in mind. Adding a new brand means linking its run-of-show and speaker data to the existing master calendar rather than rebuilding the system from scratch.