Speaker materials follow-up often becomes urgent for the wrong reason: the first real status check happens after the presentation deadline. A speaker may believe the slides are complete while the producer still needs an editable deck, video files, fonts, accessibility checks or a version that matches the event’s technical format. By the time rehearsals begin, a missing asset can affect the agenda, stage playback and session recording.
An effective follow-up workflow starts with agreed submission checkpoints, named reviewers and questions that distinguish “drafted”, “received” and “approved”. Scheduled calls can collect updates for event teams using monday.com, but speaker relationships and editorial decisions should stay with people.
Work backwards from the technical ingest deadline
Doors-open time is not the right deadline for presentation files. The producer needs time to receive materials, review them, load them into the show system and test the intended playback path. A complex live broadcast may also require rehearsals, captioning, translation or prerecorded content checks. Build those milestones into the event plan before sending the original speaker brief.
The PCMA Institute’s event planning checklist includes speaker confirmation, presentation collection, review and rehearsal preparation as distinct tasks. That distinction helps teams avoid treating “slides submitted” as the final approval. Assign the content lead, technical director and speaker liaison their own responsibilities, with a defined handoff between them.
A straightforward board may track Speaker, Session, Required assets, Draft due, Final submission due, Version received, Technical review, Content approval and Escalation owner. Each field should have a documented meaning. For instance, “file received” should not automatically mean “file technically usable”.
Set a follow-up cadence speakers can understand
The initial speaker briefing should communicate the accepted formats, upload route, required assets, contact for questions and the internal deadline. A first check-in can test whether the speaker understands the requirements. Later reminders should correspond to meaningful progress milestones, not indiscriminate daily chasing.
For a fictional conference, consider an initial materials request several weeks before the programme, a draft-status check ahead of content review, and a final confirmation before technical ingest. The exact dates depend on venue technology, rehearsal slots and the production partner’s lead time. A speaker who has already submitted and received confirmation should not be called merely because a global reminder schedule exists.
Choose the channel thoughtfully. Many speakers will prefer email or the event portal for file transfers; an approved short phone follow-up can be useful for a missing acknowledgement, unresolved blocker or imminent decision. Inform recipients if calls are automated, set reasonable hours and honour opt-outs or an agreed alternative contact method.
Ask questions that reveal whether materials are genuinely ready
Start by identifying the specific session. Ask what has been delivered, the current file version and whether required video, audio, fonts or supporting documents are included. Then ask whether anything prevents the agreed final deadline and whether the production team needs to provide a template, upload access or technical clarification.
A useful voice script might ask: “For your keynote session, have you submitted the current presentation version through the approved link?” followed by “Is there any separate video or audio that the technical team must ingest?” and “Does a reviewer still need to approve any changes?” The caller should not request that a speaker dictate confidential presentation content or passwords over the phone.
Avoid open-ended conversations with no recordable outcome. A speaker saying “I sent it yesterday” should lead to a verification task if the production folder contains nothing. The team needs a confirmed file location and version, not a new status label that says “done”.
Handle file versions and reviews as separate tasks
Presentation version control is a common source of event confusion. A speaker can submit final-v2.pptx while the producer has already loaded an older export. A robust workflow records which version was received, which version was reviewed and which specific file was approved for playback. If the version changes after a lock date, route it through the technical director rather than silently replacing assets.
Think of three distinct gates: received, technically checked and content approved. The technical team may validate aspect ratio, embedded media and format compatibility. The programme owner may review timing and claims. Accessibility or legal reviewers may have additional responsibilities. An AI call may report progress across these gates but should never stand in for their approvals.
The event production team can use monday.com project calling with Autoza AI for the appropriate outbound follow-up and mapped board notes. The publicly described product offers scheduled calls, item updates, retries and summaries. It does not claim to inspect uploaded files or certify presentation content on its own.
A practical example of a late speaker deck
Consider an illustrative panel session with three speakers. The session owner confirms that two slide decks are in the approved upload folder; the third speaker reports that a video export is still rendering. The call records the affected session, asset category and the speaker’s next estimated update. The content producer, not the AI, decides whether a presentation-only fallback is acceptable.
If the speaker misses the next checkpoint, the team may use a short permitted retry or escalate directly to the speaker liaison. The producer might allow a late file, move the video to a different cue or agree a no-slides format. Each option affects different teams; it should become an explicitly approved change to the run of show, not a hidden software update.
Never infer consent from a booked speaking slot alone. Respect the applicable rules for automated calls and call recording, use only the required contact details and maintain a straightforward human contact route.
Measure fewer surprises, not more reminders
Track the share of required assets received by the agreed review milestone, the number of outstanding approvals, late version replacements and rehearsal issues caused by missing materials. Audit the call notes against actual submissions. The most useful metric may be fewer unresolved dependencies at the technical briefing rather than a high number of completed calls.
The AI Workflow Design articles cover other project follow-up situations in monday.com. For a speaker programme with multiple sessions, identify the single communication problem producing the most last-minute rework, then request a workflow review to determine whether scheduled calling belongs in that part of the process.
Frequently asked questions
When should an event team start following up on speaker slides?
Set milestones backwards from rehearsal and technical ingest, not simply from doors opening. Use an initial request, a meaningful progress check and a final review deadline agreed with the production team.
Can the AI automatically approve a speaker presentation?
No. The caller can log whether slides or video have been submitted and identify blockers. Content, legal, brand, accessibility and technical acceptance should remain with the designated reviewers.
What if a speaker sends the wrong file version?
Track the version, owner and date received, flag the mismatch and ask for a corrected submission. Do not mark the material approved until the human reviewer confirms the exact version.
Should all speakers receive phone calls?
Not necessarily. Use the least intrusive useful channel and contact only recipients who have been appropriately informed and are suitable for the agreed phone follow-up process.
How do we handle a speaker who cannot meet the deadline?
Capture the revised estimate and the specific blocker, then escalate to the producer or content lead. They decide whether to change the agenda, use a backup format or agree an exception.
Next step: test a focused workflow
To see how scheduled check-ins could fit your own process, request a workflow walkthrough using one real project board and a non-sensitive sample task. Review every proposed script, field mapping and escalation rule with your team before using it in live operations.
Related reading
- Event Rehearsal Follow-Up: Calls, Task Owners and Exception Rules
- Building a Run-of-Show Follow-Up Schedule Across Multiple Vendors
- AV and Stage Setup Check-Ins: What an Event Producer Should Ask
- How to Run Vendor Readiness Calls Before a Major Event
- Campaign Launch Delays: 7 Status Questions to Ask Every Task Owner
- How to Follow Up on Creative Approvals in monday.com Without Endless Emails
- Autoza AI for monday.com: scheduled status calls
- Workflow automation services
- Daily Check-in Agent