Your status slides, played as one plan

From ten slides to one story

A project manager has kept the schedule in a PowerPoint slide and updated it before each status meeting: dates slipped, new work appeared, something was dropped. The slides tell the project’s history, but only one at a time. Played as one plan, stakeholders see in half a minute what changed, when and why.

One Gantt slide from each status meeting
Your AI assistant reads them and makes the plan
Tidigar plays the project, meeting by meeting

Watch a project’s history

This is the customer portal project, as an assistant made it from six status slides. The plan is the latest version; the story opens on the plan at kickoff and plays each meeting in turn. The line marks the day of the meeting. Watch the requirements run late, an integration API and a security review appear, a brochure disappear and go-live move from July to September.

The story the assistant wrote

# 2 February: the plan at kickoff, before anything changed.
0:00 hide("Integration API")
     hide("Security review")
     hide("Training")
     update("Rollout", {"title": "Launch"})
     update("Requirements", {"end": "2026-02-20", "progress": 0})
     update("Design", {"start": "2026-02-23", "end": "2026-03-27", "progress": 0})
     update("Build portal", {"start": "2026-03-30", "end": "2026-06-05", "progress": 0})
     update("Pilot", {"start": "2026-06-08", "end": "2026-06-26", "progress": 0})
     update("Launch", {"start": "2026-06-29", "end": "2026-07-24", "progress": 0})
     update("Go-live", {"date": "2026-07-27"})
     add("activity", {"title": "Print brochure", "start": "2026-06-15", "end": "2026-06-26", "Team": "Rollout"})
     today("2026-02-02")
     caption("2 February · Kickoff: go-live on 27 July")
0:04 update("Requirements", {"end": "2026-02-27", "progress": 100})
     update("Design", {"start": "2026-03-02", "end": "2026-04-03", "progress": 25})
     show("Integration API")
     update("Integration API", {"end": "2026-05-15", "progress": 0})
     update("Build portal", {"start": "2026-04-06", "end": "2026-06-12"})
     update("Pilot", {"start": "2026-06-15", "end": "2026-07-03"})
     update("Launch", {"start": "2026-07-06", "end": "2026-07-31"})
     update("Print brochure", {"start": "2026-06-22", "end": "2026-07-03"})
     update("Go-live", {"date": "2026-08-03"})
     today("2026-03-02")
     caption("2 March · Requirements took a week more, and the portal needs an integration API")
0:09 update("Design", {"end": "2026-04-10", "progress": 100})
     update("Integration API", {"end": "2026-05-29", "progress": 50})
     update("Build portal", {"start": "2026-04-13", "end": "2026-06-26", "progress": 25})
     update("Pilot", {"start": "2026-06-29", "end": "2026-07-24"})
     update("Launch", {"start": "2026-07-27", "end": "2026-08-21"})
     update("Go-live", {"date": "2026-08-24"})
     today("2026-04-13")
     caption("13 April · Design is done; the build needs two more weeks")
0:14 update("Build portal", {"end": "2026-07-03", "progress": 75})
     update("Integration API", {"progress": 100})
     show("Security review")
     update("Security review", {"progress": 0})
     update("Pilot", {"start": "2026-07-13", "end": "2026-08-07"})
     remove("Print brochure")
     update("Launch", {"start": "2026-08-10", "end": "2026-09-04"})
     update("Go-live", {"date": "2026-09-07"})
     today("2026-06-01")
     caption("1 June · A security review must pass before the pilot; the brochure is dropped")
0:19 update("Build portal", {"progress": 100})
     update("Security review", {"progress": 100})
     update("Pilot", {"progress": 25})
     show("Training")
     update("Training", {"progress": 0})
     update("Launch", {"title": "Rollout", "start": "2026-08-24", "end": "2026-09-18"})
     update("Go-live", {"date": "2026-09-21"})
     today("2026-07-13")
     caption("13 July · The pilot starts; training comes before a phased rollout")
0:24 update("Pilot", {"progress": 100})
     update("Training", {"progress": 100})
     update("Rollout", {"progress": 75})
     today("2026-09-07")
     caption("7 September · Rolling out; go-live on 21 September")
0:30 loop()

Try it with your own slides

Take a picture of each version. Screenshot the Gantt slide from each status meeting, or export the slides as images, and note each meeting’s date if the slide does not show it.
Connect your assistant to Tidigar Business. Screens belong to plans your organisation keeps in Business. Connect ChatGPT, Claude or another assistant.
Ask for the history. Attach the pictures and ask, in your own words, for something like the request below.
Show the link. Open it on the wall screen at the next steering group, or put it in a frame on your intranet. It plays again by itself.

Here are the Gantt slides from our six status meetings for the customer portal, oldest first. Use Tidigar to make the plan as it stands now, and a screen that plays how it changed from meeting to meeting. Say in a caption what changed each time.

I made the plan Customer portal in your organisation, with the eight activities and go-live on 21 September from the last slide. Its screen Status history plays the six meetings in 30 seconds, from kickoff to today. Here is its link: Status history

What the assistant does

It reads every slide, matches the activities from one meeting to the next, also when one was renamed, and keeps the latest version as the plan. Your team keeps working in that plan.
It writes a story in Tidigar’s story language: at the start it sets the plan back to the first meeting, hiding what came later. Each later meeting is one step with its date, its changes and a caption.
It makes a screen of a saved view of the plan, with the story. Tidigar checks the story against the plan and tells the assistant about any step a viewer would miss, so it can fix it before it gives you the link.

Anyone holding the link sees the screen’s view without an account, so your assistant asks before making one. When the plan changes, the screen follows within a minute and the story starts from the new plan. An organisation’s owners can keep making screens to people; see screen links.

Read the guide for agents or play a story on your own page.