InnerWeb
Skip to main content

Final pilot report: checklist

The final pilot report has one job: to let management decide on deployment, extension or closure. To do this it must contain the goal and scope, the indicator results from system data, user feedback, costs and a transition plan. The checklist below helps you verify that the report is complete before the board meeting.

What the final report is for

The final report closes the pilot and opens the decision. It is not a summary of activity but a decision document: it should show whether the pilot goal was achieved, what it cost and what must be done next. In decision documentation for moving to production, pilot data such as stage times and routes per warehouse are shown as justification.

The report should be understandable to people who did not take part in the pilot: board members, purchasing and finance. For this reason every item in the list below should be backed by a figure from the system or an explicit assumption, not a general impression.

Goal, scope and indicators

The first part of the report restates the goal recorded before the start and describes the scope: the area, the number of beacons, the number of users and devices, and the duration. The pilot could start at one facility under live traffic from external contractors, and extension to further plants is planned only after the results are assessed, so the report should clearly state what the conclusions apply to and what they do not.

The second part contains the indicator results. The route-patrol pilot measures the completeness of patrols and the time to respond to a fault, and the morning report shows the manager the effect from the first day. Set out the baseline value, the target value and the value achieved; without a baseline, improvement cannot be shown.

Sample layout of the final report: number of mandatory sections

Sample layout of the final report: number of mandatory sectionsBar chart: number of checklist items in the four parts of the report: 3, 3, 4 and 3.01234pcsGoal and scope: 3 pcs3 pcsGoal and scopeIndicators and results: 3 pcs3 pcsIndicators andresultsCosts and transition: 4 pcs4 pcsCosts and transitionRisks and next steps: 3 pcs3 pcsRisks and next steps
Source: Illustrative calculation: layout of the checklist from this page

Costs and transition to production

The third part covers costs and the options for the next steps. Show the pilot cost broken down by item and compare it with the cost of production deployment. After the pilot, devices used in it can be transferred to ownership on a one-to-one basis, to avoid buying twice, so the report should state whether this option is planned and how it affects the budget.

Also describe the three possible decisions: moving to production deployment, extending the pilot or closing it. In past InnerWeb projects, the move from pilot to production deployment reached 100%. This is a result from the past that does not replace your data, so do not present it as an argument without your own pilot results.

Risks, limitations and next steps

The report is not complete if it does not state limitations. List what the pilot covered and what it did not: for example, the absence of the voice assistant, which is a pilot on a single server, or modules that require additional BLE hardware. Extending with further modules needs no new licence or installation, only possibly hardware, and this fact simplifies the plan for the next stage.

Close the report with a plan of next steps, with the people responsible and dates. Management decides faster when it sees who does what in the first weeks after the decision.

Checklist

Video

Frequently asked questions

What is most important in the final report?

Indicator results read from the system, compared with the baseline and target values, and a clearly described decision to be taken.

Should the report include costs?

Yes. Show the pilot cost broken down by item and compare it with the cost of production deployment, including the option of transferring devices to ownership 1:1.

Which decisions can management take?

Moving to production deployment, extending the pilot to another area, or closing it. The report should describe the consequences of each.

Is the 100% move from pilot to deployment an argument?

It is a fact about past InnerWeb projects, not a promise for your site. The decision should rest on your own pilot indicators.

Let's plan a pilot for your site

Book a conversation with InnerWeb: we will help you select the scope, the number of users and the pilot success criteria for your hall or route.

Let's talk