TRY IT / TICKET → WORKSHOP JOB SHEET
A ticket in plain text.
A job sheet to pick up.
Edit the ticket. Prepare the job sheet. Remove a piece of information and see the difference. The visible part of an integration starts here.
Fictional data · Explicit rules, not an AI model · Nothing is sent · No machine is controlled
THE RESULT
Your job sheet will appear here.
Choose an example or edit the text, then prepare the job sheet.
YOUR TABLE / CHOOSE THE COLUMNS
Same tickets.
Your format.
Choose the columns, match them to the ticket information and download the table. You can also save these settings and reopen them here.
Two fictional formats. No external software is connected.
A JSON settings file (20 KB maximum), read on this device only. Do not load private data.
Up to twelve fictional tickets. The “Status”, “To check” and “Original ticket” columns are always kept in the export: missing information must not disappear.
The destination can change without erasing your tickets.
You can attach your recipe to your message. It contains the mappings, not your tickets.
UTF-8 CSV, semicolon separator. Open it in a spreadsheet, then check it before importing. Cells that look like formulas are prefixed with an apostrophe to prevent them from running.
The useful link
before the AI.
Here, simple rules are enough. An AI could then help read free-form wording or varied documents. That would be another step to test.
What this small-scale demo shows
An input can become a structured object without vanishing into a black box. Missing information and contradictions stay visible.
It does not diagnose a fault, does not prioritize a safety risk and does not demonstrate an integration with your system.