Post-Deployment Verification: The Service Nobody Sells

Why UV-C performance should be proven in the crop, not assumed after installation

Most technology projects in horticulture have a clear commercial ending. The system is sold, the robot is delivered, the installation is completed, and the handover is signed.

But with UV-C crop protection, that is not the end of the story.

It is the beginning of the real test.

A UV-C robot can be installed correctly, drive through the greenhouse, switch on at the right time, and still leave the grower with one critical question:

Is the treatment actually working in my crop?

That question is often left unanswered. If mildew pressure goes down, everyone assumes the system works. If disease comes back, everyone starts guessing. Was it the lamp? The robot? The treatment frequency? The crop density? The climate? The timing?

In reality, UV-C performance is not proven by installation. It has to be verified after deployment, under real crop conditions.

In Dutch culture there is a saying: Meten is weten (to measure is to know)

For UV-C crop protection, that could not be more true. If the dose is not measured in the crop, if the biological response is not followed, and if the business case is not checked against reality, then everyone is still working with assumptions.

This is a major gap in the market. The industry sells robots, lamps, software, treatment schedules, and maintenance plans. Very few people sell proof after deployment.

Post-deployment verification is the missing layer between promise and performance. It is also what makes the business case honest.

Step One: Dose Measurement in the Real Crop

The first step is UV dosage measurement at canopy level. Not only at the lamp. Not only at a clean calibration distance. Not only at the easiest point in the row.

The dose needs to be measured where the crop actually is: on exposed leaves, inside the canopy, around shaded zones, near fruit clusters, and in the places where mildew pressure is most likely to survive.

We have written separately about why the canopy is not one surface and why dose distribution varies through a real crop. That is the technical foundation. Verification is the operational answer.

Step Two: Biological Effect Assessment

Dose measurement tells us what the system is delivering. It does not tell us whether the system is working.

That answer lives in the crop, and it is the part of verification that almost nobody else in the market is set up to do.

A UV-C programme is working when mildew development is being interrupted in the places where pressure normally builds. That means watching specific things over time. Are new mildew spots slowing down? Is pressure stabilising in the upper canopy while the lower canopy still shows activity? Are symptoms returning in the same shaded zones week after week? Is disease moving from inner or lower canopy areas into the visible crop? Is the rate of new infection changing in line with the treatment schedule, or independently of it?

These questions connect the dose to the disease. Without them, verification remains technical. The grower knows what the lamp delivered, but not whether the biology responded.

With them, dose, crop structure, disease pressure, and treatment result become one connected picture rather than four separate data streams.

This is the bridge that suppliers struggle to build. A supplier can measure dose. Interpreting biological response in a commercial crop, honestly, is a different kind of work. It requires somebody whose role is not tied to defending the sale.

Step Three: ROI Reconciliation

The third step is the honest financial check.

Before purchase, UV-C is justified with expected savings: fewer chemical applications, lower labour demand, better crop quality, less disease loss, and stronger residue management. After deployment, those expectations should be checked against reality.

Did chemical use actually reduce? Did labour really decrease, or was it moved elsewhere? Did the robot run often enough during the required treatment windows? Did the system protect enough yield to justify the investment?

This is not about blaming the technology. It is about closing the loop between the business case that was sold and the result that was delivered.

What Verification Changes

Post-deployment verification turns assumptions into decisions. It helps identify whether the issue is dose, crop geometry, timing, disease pressure, operation discipline, or ROI expectations.

Each of those has a different fix.

Without verification, the diagnosis is a guess, and the conversation tends to default to the loudest voice in the room.

With verification, the grower owns the answer.

The real question is not whether the robot was installed.

The real question is whether the result has been measured, understood, and verified in the crop.