A managing director asked me in a first call: "How do I know the thing is working and not just running?" That is the right question, and most vendors answer it with a dashboard. Curves, traffic lights, a counter ticking up. That is not an answer. That is decoration.
Our answer is a weekly protocol with eight lines. It goes to management by mail on Mondays, one table per service, no chart. Here are the eight lines, with the question each one answers.
How many cases came in? Mails with orders, orders in the portal, positions from telematics, invoices in the mailbox. Without this number all the others are meaningless. Zero bookings at zero intake is a quiet day. Zero bookings at 300 intakes is an outage.
How many of them did the service complete without a person? Booked, confirmed, notified. This is the number vendors like to show as a percentage. We show it as a count next to intake, because 80 percent of 50 is something different from 80 percent of 5,000. For a contract logistics provider's portal agent this line swings between 900 and 5,300 per run, and the swing comes from the customer.
How many did the service hand to a person, and with which reasons? The reasons are the part worth money. If it says "unknown article number" three times from the same customer, that is a conversation with the customer, not a fault of the service.
How many review cases have been sitting for more than two days? This is the line that shows whether the person behind the service is keeping up. If it grows, the service is not the problem.
How often did the service not run or end without a result, and what did the watchdog do? At our place this says when the alarm went out and when the service delivered again. A service without this line has no watchdog, and a service without a watchdog is a script that will stand still at some point. We lived through that ourselves, for a week, in our own operation.
What was changed on the service? New reading rule, new price matrix, new customer in the master. With date and reason. Management does not have to understand it, but it has to see that somebody maintains the service and that a change never happens unnoticed.
How many minutes did a person spend on the process this week? Deciding review cases, maintaining rules, follow-up questions. This is the line the savings are calculated against. For a wholesaler's order capture it was three and a half hours a day before the service, under one after, almost only review cases.
What did operating the service cost? Runtime, model calls, maintenance. Next to line 7 that gives the calculation promised in the first call, fresh every week.
A dashboard shows trends. The management of a forwarder with 40 trucks does not need a trend, it needs the answer to "did it work this week, and what did it cost". Eight numbers in a mail answer that in a minute. Whoever wants more clicks on the run and sees the protocol per step.
There is a second reason. Strategy& and BVL found among 115 logistics providers in November 2025 that a quarter do not measure the success of their digitalization at all. A dashboard nobody opens measures nothing either. A mail on Monday gets read.
A caveat: eight lines are enough for a service with one to four runs a day. With twenty services the mail becomes a table with twenty rows, sorted by line 5. It still does not become more curves.
What does your report on an automated process say today, and who reads it? Send me an example. I will tell you which of the eight lines are missing. Ask for a process check: 30 minutes, no sales pitch.
