PlatAtlasHow starting worksWhat does your team already decide?
Drop in a spreadsheet of past decisions: invoices paid or held, requests approved or sent back, tickets routed, anything your team answers over and over. In about a minute you see the rules your team already follows, the calls that take judgment, and the cases worth a second look. It all happens in this browser. Nothing is uploaded.
Drop an Excel or CSV file here, or
One row per case, one column that says what was decided. An export from your ERP, ticketing system or a shared spreadsheet.
Or paste rows copied from a spreadsheet
No file handy? Try a made-up one: ·
Your history
The rules your team already follows
Found by counting your own rows, with no AI involved. A rule is shown only when it held on at least 9 in 10 of the cases it covers, and on at least 4 of them. With a small history, some can be coincidence: they are for your team to confirm.
Worth a second look
In our tests with mistakes planted at random in a history of 60, these flags found 90 to 100% of a single mistake, with a few decisions that were in fact right flagged alongside (the measurements).
What PlatAtlas would do with this
How would an AI do on your history?
The counting above used no AI. This check sends a sample of your past decisions to an AI decision model (JEV, from TypeSafe) and compares its answers with what your team decided. It judges each case by descriptions drafted from the rules in the other half of your history, so the score is honest: no rule has seen the case it is graded on. In our own tests, descriptions drafted this way cut an AI's mistakes by about half compared with none; a steward's own words took it the rest of the way (the measurements).
Keep it: make it your team's playbook
A playbook is your team's know-how as plain files your organization owns: the question, each answer in your words, who may decide what, and these past decisions as the test every AI model must pass before it is trusted with anything.
Create makes a private repository in your GitHub organization holding the playbook, in one commit, and opens its inbox. You sign in with GitHub first if you haven't; what you prepared here waits in this browser tab. Only then is anything sent, and only to your own repository. Download keeps it on your computer: create a private repository (GitHub's page, filled in) and upload the unzipped files.
Want us to do the first setup with you? Write to us.