Why decision documentation after a pilot
A pilot ends with a decision: we move to production, extend the test or stop. The board decides on the basis of a document it reads in a dozen minutes, so it must contain numbers, not general impressions. The decision documentation on moving to production presents the pilot data, for example stage times and routes per warehouse, as the justification.
The document is best prepared in parallel with the pilot, not after it ends. If the team collects data from the first day, the final report is a matter of organising, not of searching for information in the memory of the participants.
Four groups of data worth collecting
The pilot result usually consists of four groups of information. Each answers a different question from the board.
Execution measures
For the patrol pilot these are patrol completeness and response time to a fault. The morning report shows the manager the effect already on the first day, so the data series can be kept from the start. Execution measures answer the question of whether the system does what it was deployed to do.
Stage times and routes
For delivery traffic and internal logistics, the valuable data are the times of successive stages (entry, transit, unloading, exit) and the routes per warehouse or per gate. They show where vehicles lose time and give the board an operational argument.
Illustrative events
Three or four described events from the pilot: a fault reported and closed, an unauthorised stop detected by the dispatcher, a point skipped on a patrol. The board remembers events better than tables.
Users and costs
The number of active users, the use of licences and the actual monthly cost of the pilot make it possible to calculate the cost of production. More precise rules for counting licences are described on a separate page about licences in the pilot.
Cost data in the document: sample monthly pilot costs (net)
How to structure the document for the board
A good decision document has a stable structure, so that the board quickly finds what it is looking for. The decision we ask for and the recommendation come first. The data and the justification follow.
In past InnerWeb projects the transition from pilot to production deployment reached 100%. This indicator can be quoted as context, but it does not replace the plant's own results: the board wants to see what worked under its conditions.
It is also worth stating what the pilot did not test. An honest list of limitations builds trust and protects against disappointment after the production deployment. If the pilot covered one route, the document states that the result concerns that route, and scaling requires further assessment.
Equipment and the cost of the transition in the document
The board will ask about the cost of the next steps. The answer should state that devices used in the pilot can be transferred to ownership on a 1:1 basis, to avoid a double purchase. The pilot in real traffic confirms how the system works before the production network is bought, that is the transmitters, locators, charging stations and the subscription.
The document should contain rounded cost ranges for production, marked as indicative and requiring an individual quote. Do not enter amounts that have not been confirmed by an offer.
Checklist
Video
Frequently asked questions
When should the decision documentation be started?
From the first day of the pilot. Collecting data as it happens is easier than reconstructing it after the end.
Which data convince the board most?
The plant's own results: stage times, patrol completeness, response time and a few described events. Numbers from other projects are only context.
Should the document contain amounts?
Only rounded ranges, marked as indicative, with an individual quote. Do not enter amounts that the offer does not confirm.
Prepare the pilot report
We will help set the measures before the start and build the decision document for the board. Book a short call about the pilot scope.
Let's talk