Every walkthrough is recorded in the real thing, with English voice-over.
Start freeEvery card here has a «more» link, and it is easy to miss. Open it, and the film stops being a demo and starts talking about you: which company you are signed in to, whether the module is switched on there, and a button straight into it when there is somewhere to go. A green check means the module is on for your company. No check means the film shows you what you would get, and how to switch it on. The search field at the top looks in the words: type what you work with, and if nothing matches, let the AI pick the films that fit what you described. Nothing here changes your access — it only reads what already applies.
Search that forgives typos and spacing, clickable rows, barcodes with a check digit, several order lines in a row and scanning at goods receipt.
On the phone: scan the shelf, quick in, count the shelf against the list, move to the service van as one action, and the overview grouped by warehouse with minimum right in the table.
One GS1 scan gives product, lot and expiry on receipt; the lot follows the product card and overview; labels on sheets or rolls; an unknown barcode becomes a product with one tap.
Small items without barcodes are checked by weight: weigh a handful to get the weight per unit, weigh the packed box against the order, and get suggestions for what a deviation could be. Optional per company.
Drag a job from the unassigned list straight onto a technician’s hours. The card hangs from the pointer all the way, and technician, day and time are set by the same drop. Move it on, lay out the rest of the week in the week view, and see the system speak up – with the reason, not just a question – when you are about to schedule a job waiting for a part.
A bike workshop with four stations. The job is written as plain text on each work step, and the checklist is created from the text, with a preview before anything is saved. One flag decides whether the repair is included: one bike just needs a wash, one needs repairs. On the board the checklist follows the card from station to station, every answer is saved at once and remembers who and when, and the overview shows where the checklist was used and which bikes raised a deviation.
A bike workshop that builds bikes. The seller finds the bike in the catalogue, picks the tyre size the customer wants, and gets a delivery date calculated from free stock, supplier lead times and station capacity, with the bottleneck named. The order becomes a sales order, production orders with sub-orders for the wheels made in house, and draft purchase orders per supplier, all sharing one reference. The second half shows the setup: bill of materials with minutes and setup time, choice groups, the internal cost breakdown, supplier lead times and pack sizes, and the station calendar with closed days.
The supplier sends a new price list. You download what is in the system, correct it in a spreadsheet, and upload it again. Before anything is written the system shows what will be new, what changes with the old and new value field by field, what is unchanged, and which rows have errors. Afterwards the whole run sits in a log with who, when and row by row, and the same changes appear on the product itself. Stock goes the same way, but is booked as a count in the movement log. Finally: products with an end date that leave the search without leaving the history, barcodes that several products may share, documentation on the product, and the build record showing everything that actually went into a production order.
The support desk. The customer gives an e-mail, a phone number or her own order number, and you get cases, sales orders, the production behind them and deviations on one page — including the deviations the customer reported herself. Phone numbers are found whatever the spacing and country code, and a single unambiguous hit opens straight away. If she says something that is written down nowhere, it is written down there and then as a deviation and a case that are linked. The case opens straight from her card, and the rest becomes one log: the comment with the photo and the report she sends in the same entry, a checklist for what the plumber should go through, and who takes it and by when.
Press Record in the Quick actions panel, do the job the way you normally do, and press Stop. The server cuts that span out of the usage measurement that already runs on every page, so nothing new is collected and nothing you type is ever stored — only how many characters it was. Then the AI writes a work instruction using the real button and field names, and says what took time: a form sent five times, a field you kept pasting into, a search that never hit. One click turns it into a routine with a version and an approval. And the last part is the point: a colleague opens the same recording and gets pointed through it, one step at a time. It points — you click. Nothing happens by itself. For systems that are not ours, a trade system or Altinn, there is a browser extension that does the same thing. English narration.
Quick actions is off until you switch it on. Bind a key to a field, build a recipe of seven steps as you work, give it a key, and read the run log afterwards. The pages are unchanged.
Mark your own activity and get a draft recipe. Paste a sheet from Excel, map the columns, run every row as a draft, and see each change before you approve. If a row was changed by someone else, nothing is written.
The browser extension installs with one command. It downloads nothing: it writes a single policy file, and the browser fetches the extension itself, and every update after it. Connect it to your account with a key that can only deliver a recording and reads nothing back. Then open it on a supplier system, give access to that one site, and record the task the way you always do it. It stores which buttons and fields you used, never what you typed into them. Chrome, Edge and Brave.
A declaration of conformity is signed for one machine, not for a product type – so the documentation hangs on the serial number. Open a produced unit and you see what it is built from, what was logged during production, and which requirements are confirmed, by whom and when. Before anyone signs, the page lists what is ‘not confirmed’: you sign with your eyes open, and the gaps become part of the declaration exactly as they stood that day. The name and the authority are entered by hand, because it is the manufacturer who declares conformity – not the system, which only records what the documentation showed. A declaration that turns out to be wrong is withdrawn with a reason, never deleted. Nothing new is asked of the people building the machine: the serial number, the bill of materials and the production log are already there. The list before the signature is not only the requirements: a residual risk that has not been passed on to the user – no warning on the machine, no section in the instructions – stands there too.