ChatGPT collaborative slides for sprint and incident reviews
This research library uses AI-assisted source research and drafting. Linked sources support product claims; analysis and proposed exercises are our interpretation. Unless an article documents a test and its results, do not read it as a hands-on review or an independently verified benchmark.
ChatGPT collaborative slides are coming, but you cannot use them yet. At DevDay on 29 September 2026, OpenAI said they arrive for Pro, Business and Enterprise in the coming weeks, per the DevDay 2026 recap. You will build slides from a conversation or your own template, then edit and comment on them with teammates and agents at the same time.
For engineering teams, the obvious first use is the recurring review deck: the sprint review and the incident review. This guide separates what is announced from what is documented, and shows what to prepare now.
What is announced for ChatGPT collaborative slides?
The recap and the ChatGPT Space launch page are the only official sources so far. There is no help article for slides yet.
| Question | What OpenAI has said | Documented yet? |
|---|---|---|
| Availability | Pro, Business and Enterprise, in the coming weeks | Announcement only |
| Starting point | A conversation, or your own template | Announcement only |
| Editing | Multiple teammates and agents edit at the same time and comment | Announcement only |
| Presenting | Present in ChatGPT | Announcement only |
| Export | PowerPoint or Google Slides, with formatting intact | Announcement only |
| Admin controls, retention, file limits | Nothing published | No |
| Price | Part of the listed plans, no separate price announced | No |
Collaborative spreadsheets are announced as coming soon as well. Both will sit in ChatGPT Space next to pages and files.
Can you export ChatGPT slides to PowerPoint?
OpenAI says yes: slides will export to PowerPoint or Google Slides with formatting intact. That matters if your leadership reviews happen in existing decks or if you archive postmortems outside ChatGPT.
Treat "formatting intact" as a claim to test. Nobody outside OpenAI can check it until the feature ships. When it lands, export one real deck and open it in the tool your team uses. Check fonts, charts, speaker notes and links before you retire your current workflow.
Prepare the review source material now
Slides are only as good as the material behind them. You can build that material today with ChatGPT Pages and scheduled tasks, both available now.
For a sprint review, create a page per sprint with these sections: goal, merged changes, what slipped, open risks and demo links. The scheduled tasks docs list "create reports about recent codebase changes" as an example task. You can create one from a ChatGPT or Codex chat.
- Test a prompt in a regular chat that summarizes merged pull requests for one repository and one date range.
- Ask ChatGPT to turn it into a weekly scheduled task, or trigger it on GitHub pull request merges.
- Point it at the sprint page and review the first run against the pull requests.
- Add human sections by hand: what slipped and why, and what you are changing.
For an incident review, keep a page with the timeline, impact, the fix, follow-up actions and owners. Codex helps with the technical part. Run codex resume to reopen the session where the fix happened, and ask Codex to explain the change and its tests. Paste that explanation into the page and keep the link to the pull request next to it.
The Codex CLI /review command runs a review against a base branch, uncommitted changes or a commit. Its findings are useful evidence for an incident page when you want to show what the fix changed and what the review flagged.
Turn the page into slides when the feature lands
Once slides are live, the announced flow is to create a deck from a conversation or from your template. Start from the sprint or incident page, not from a blank prompt. The page holds reviewed facts with source links. The deck should repeat them, not invent new ones.
Keep one rule for agent edits on a shared deck: a number on a slide must trace back to a line on the source page. If an agent adds a figure that is not on the page, remove it or add the source first.
This is the Delegate, Review, Own split from our methodology. Delegate the first draft to an agent, review every figure against its source, and keep ownership of decisions and follow-ups with named people.
What to check on the first deck
- The deck uses your template, not a default layout.
- Every metric and date matches the source page.
- Comments from teammates and agents are resolved before you present.
- The PowerPoint or Google Slides export opens cleanly and keeps charts editable.
- Incident slides leave out customer data that should not leave the page's audience.
Next step: pick one sprint, create its review page today, and schedule the merged-changes report so the source exists before slides arrive.