A project may reach handover before the tank can be filled to its normal upper level or before the intended product is available. Conditional radar acceptance records exactly what has and has not been demonstrated. It must not turn an unfinished test into an unrestricted acceptance simply because the plant has started.
Separate missing evidence from an unacceptable installation
An unavailable test condition and a failed requirement need different treatment. A planned observation during the first production batch may be open for practical reasons. An unsupported pressure rating, unsuitable hazardous-area approval or a known critical measurement failure is not just another item to close later.
The authorised project and operating representatives decide whether a limited release is permissible. The supplier can explain instrument evidence but cannot grant permission to operate the site's process. Record that distinction wherever commercial delivery and operating approval occur at different times.
Make conditional radar acceptance specific enough to close
| Open item | Evidence needed for disposition |
|---|---|
| Untested upper level | The required measurement and system response at an approved representative condition. |
| Product unavailable | An observation with the actual product and the operating state that was not represented by the substitute. |
| Missing document | The exact document, revision and equipment identity required by the purchase specification. |
| Failed critical test | Corrective work and an approved repeat test; a promise to investigate does not close the failure. |
For each permissible open item, specify the temporary restriction, responsible owner, due date or operating trigger, and who can accept the evidence. "Monitor closely" is incomplete unless it states what will be observed and what action follows an unacceptable result.

The MV-RD12 liquid radar has published model data, but a product-page measuring range is not a site test record. Identify the ordered assembly and its local installation when asking which observations are needed. A successful output simulation verifies a different part of the system from a physical liquid-level comparison.
Keep the restriction visible to operations
Link the open item to the instrument tag and the relevant operating instruction. Shift changes should not hide the limitation. If the authorised condition or date expires, use the agreed escalation process; do not silently roll the deadline forward in a spreadsheet.
When the missing process state becomes available, retain the test values and configuration used. Compare them with the original acceptance criterion, not a revised limit chosen after seeing the result. A changed product, nozzle or output assignment may require a different review rather than closure against the old test.
Q1. Can payment or delivery acceptance close a technical restriction?
No. Commercial milestones and operating approval have different evidence and authorities. The contract should state both, so a delivery signature is not mistaken for technical release.
Q2. What if the planned test can never be performed?
Return the requirement to the responsible engineer for an approved alternative, a revised duty or rejection. Do not leave an indefinite condition attached to equipment used as though it had passed.
Summary
Close a condition with identifiable evidence, not elapsed time. Send the MV-RD12 test gap, configuration and proposed operating limitation for an instrument-level review.
