Published project durations provide context.
MEET’s project records describe three different production scopes:
- Roborock: one 30-slide Keynote corporate presentation, completed in seven working days.
- Momenta: one 25-slide Keynote conference presentation, completed in six working days, with on-site conference support.
- SUN·Day: four Keynote presentations totaling 120 slides, with a production period of twenty working days and on-site delivery support.
Those are durations recorded for specific projects. They are not a standard rate per slide or a guaranteed turnaround for a new enquiry. The content, approval process and delivery conditions must be assessed for each brief.
The readiness of the content changes the schedule.
A signed-off script, approved product figures and accessible brand assets let a team move into design with fewer unresolved inputs. A folder of departmental material may first need a new structure, technical clarification and agreement on the main message.
List missing inputs before production starts. Give each one an owner and a due date. Product images, engineering diagrams, terminology decisions and translated copy can affect several slides at once. Mark which parts can proceed and which parts depend on approval, so incomplete information does not spread through the deck.
Count the types of work inside the slides.
Ten slides can contain ten simple layouts, or a mixture of 3D sequences, data visualization and a technical system diagram. Discuss the work behind the slides rather than using slide count as the only scheduling measure.
Language versions can require terminology review and layout adaptation. A panoramic event screen can require a different composition from the follow-up deck. If you need both PowerPoint and Keynote delivery, include adaptation and destination-software testing in the schedule. Confirm which production assets already exist and which need to be created.
Agree five review milestones.
- Brief and inputs confirmed: audience, objective, required format, available content and missing-material owners.
- Story structure approved: key messages, slide sequence and the evidence supporting the presentation.
- Representative slides approved: visual direction and examples of the most important slide types.
- Complete deck reviewed: consolidated content, design, language and technical feedback.
- Playback and handover checked: the final version, required exports, rehearsal files and backup arrangement.
Assign an approver and review window to each milestone. Collect feedback in one place and distinguish corrections from additions to the agreed scope. A new product section or another language version can change the work remaining.
For a live event, treat rehearsal as a delivery date.
Tell the design team when the event operator needs files, when the venue can test them and when the speaker will rehearse. Confirm who can approve changes after those points. The event date alone does not describe the technical handover.
If the deadline is close, share the actual material and identify the essential presentation first. The team can assess a focused scope, prioritize the core argument and discuss which additional assets or adaptations are realistic. Availability and production time still need confirmation; a short deadline should not be treated as an automatic promise.
Send the event date, rehearsal date, current draft and required format with the initial enquiry. Those details support a more useful schedule discussion than a slide count on its own.