Beyond slides and documents
Teams run their most complex work through decks, documents and spreadsheets. Each one shows a fixed picture, goes out of date the day it is sent, and lives in someone’s inbox. A Slate replaces them with one living page that the whole team builds and reads.
What a Slate can hold
| On a Slate | What it does for the team |
|---|---|
| Interactive charts | Readers filter and explore the figures instead of reading a screenshot |
| Dashboards | The state of a project or a team, on one screen |
| Tables to fill in | Editors fill in data fields and everyone sees the change |
| Checklists | Tasks ticked off on the page, not in a separate tracker |
| Layers and tabs | A one-screen summary, with the detail one click below |
| Timelines and plans | Milestones, owners and dates in one view |
| Animated process flows | A process that plays step by step, instead of a static diagram |
| Org designs | Teams, roles and reporting lines that readers can explore |
| Decision logs | What was decided, when and by whom, next to the work |
| Comments on a section | A question about one section, naming the person who should answer |
How a team builds a Slate together
- Someone starts it. An owner publishes a Slate through their AI model or from the portal in minutes, with no app to build.
- Everyone adds their part through their own AI. Each editor asks their own AI, such as Claude, to add a section from their own context.
- Each AI draws on the shared project. Before it writes, each person’s AI reads the whole Slate as it stands, with its comments. It works from the team’s shared context, not only from its own person’s, so every new section builds on what the team already knows.
- It looks like one piece of work. Every section uses your organisation’s design, or the standard Substrait design.
- Nothing is lost. Every change is saved as a version, and any earlier version can be restored.
Kept inside your company
- Every Slate stays behind your company’s sign-in.
- Owners, editors, commenters and readers each have their own permission, and only an owner shares or deletes.
- A Slate shared with the whole company appears in Explore, and Slates sit in folders.
- A Slate nobody has touched for 90 days is flagged to its owner, who keeps it or removes it.
Good uses for a Slate
- A cross-team project, from plan to status, on one page
- A board or management pack that readers can explore
- A proposal or business case with live models in it
- A team’s operating rhythm: goals, owners, decisions and checklists
- An org redesign, with the structure readers can click through
- A one-off analysis with interactive charts, shared without building an app