A non-detect result should travel with its qualifier, applicable reporting limit, and method context, not be silently converted to zero during a handover. The responsible analyst must decide how it is treated in a particular report. In a UG62 monitoring inquiry, define that information requirement separately from any proposed sensor or sampling capability, which still needs written feasibility confirmation.

Start with the report the program needs

An environmental program manager may receive a proposal describing aircraft supply, data collection, and a final spreadsheet as one package. Before comparing the package price, ask what decision the spreadsheet is expected to support. A screening review, a trend assessment, and a submission under a specific reporting requirement may call for different evidence and different professional review.

This article uses chemical analysis reporting as a bounded example. It does not claim that UG62 collects samples, carries a particular environmental sensor, or produces laboratory measurements. An aircraft inquiry and an analytical reporting requirement can belong to the same project without either proving that the other is technically feasible.

A completed analysis can still leave a bounded result

The US EPA's Data Quality Assessment: A Reviewer's Guide, EPA QA/G-9R discusses non-detects as results whose values are not established above the relevant detection limit, rather than known zeros. It also explains that analytical treatment depends on the data and purpose. This 2006 guidance provides background, not a current permit determination or a universal rule for every reporting program.

The buyer's immediate concern is preservation of meaning. If the laboratory supplies a qualified result, the next system should not erase the qualification without an authorized, documented analytical decision. Some reporting requirements may prescribe a particular treatment or surrogate. The contract should identify the qualified reviewer who decides which rule applies, rather than embedding an unexplained replacement in a spreadsheet template.

Keep a non-detect distinct from a location that was never observed, an analysis that failed, or a result withheld pending review. Those records may all lack an ordinary numeric result, but their reasons differ. Ask the program specialist to define the categories required for this project and the evidence that distinguishes them.

Separate the number from the result status

Our editorial recommendation is to design the delivery table around the information the reviewer needs, not around the convenience of a single numeric column. A numeric-only export may be easy to chart, yet leave the recipient unable to tell whether a blank means no result, a qualified result, or an import problem. That ambiguity should be resolved in the specification.

These are proposed procurement fields, not a replacement for a laboratory's reporting standard. Ask the laboratory or analyst which terms it uses and retain those definitions. Detection limit and reporting limit should not be treated as interchangeable labels merely because a template provides one column called limit.

Test the transfer, not just the first spreadsheet

Use a representative, de-identified sample of records in the agreed export path. Include the result categories the program expects to encounter and let the specialist choose appropriate examples. The recipient should be able to trace each sample record back to its source evidence and explain its status after the transfer.

A practical field-oriented lesson is to check that a less-than qualifier and its associated limit survive a spreadsheet import. An empty numeric cell should not automatically become zero simply to make a chart render. This is an editorial acceptance recommendation, not a report of a particular customer failure or a prescribed statistical method.

Ask the software owner to demonstrate how the receiving system represents qualified results. If it cannot retain the required fields, document the gap and agree a supported alternative before acceptance. Do not quietly move the qualification into a free-text note that downstream users never receive. The buyer needs an explicit decision about how the evidence remains available.

Keep original evidence and derived reporting distinct

A reporting analyst may need a derived dataset for a particular calculation or submission. The procurement question is not whether derivation is always wrong; it is whether the method, authorization, and relationship to the original evidence are recorded. Ask for a clear distinction between the supplied analytical result and a value prepared for a later purpose.

The scope should identify who chooses the treatment, who checks it, and who can answer questions after delivery. A software integrator should not become the analytical decision maker by default merely because it writes the export routine. Likewise, an aircraft supplier should not be assumed to own laboratory interpretation unless that responsibility is explicitly accepted and appropriately supported.

When a requirement changes, ask whether previously derived reports need review. Preserve the original result context so the responsible specialist can make that decision. This is a governance question for the project, not an instruction to recalculate historical reports using a method selected by a general content article.

Compare offers using the same reporting boundary

Imagine one quotation ends at delivery of source laboratory reports, while another includes structured data import and a reviewed summary. Their prices cannot be compared fairly as though both promise the same outcome. List the delivery boundary for each bidder, then identify the customer work that remains after that boundary.

Ask how exceptions are handled. A qualified result with an unclear limit, a missing source report, or an unresolved record identity should reach a named reviewer rather than disappear into a generic successful-import count. The quotation can specify an exception log and a resolution process without pretending that every possible analytical issue can be automated.

For a United States project, determine the actual program or permit requirements with the responsible professional. For a New Zealand project, establish the receiving organization's requirements independently; an EPA background guide is not evidence of local compliance. Keep jurisdictional decisions out of the aircraft marketing claim.

Two related questions for the broader data package

A proposed remote-sensing project may also contain attributes whose interpretation depends on processing context. The lidar intensity evidence checklist addresses one such issue. It is not a substitute for chemical analysis expertise, but it illustrates why an attribute's name should not carry more meaning than the supplied evidence supports.

If the proposal includes a separately engineered measurement interface, review the differential-input and common-mode questions with a qualified integrator. Electrical compatibility and analytical reporting are different acceptance boundaries. A well-defined report cannot rescue an unverified measurement chain, and a compatible interface does not establish the validity of an environmental conclusion.

Define the UG62 scope honestly

The UG62 product listing identifies the aircraft being considered within the VTOL and fixed-wing collection. It does not establish sampling hardware, analyte detection, laboratory services, environmental certification, or suitability for a particular monitoring mission. Each proposed capability requires current written evidence for the exact configuration.

Ask the offer to distinguish aircraft supply, any proposed payload integration, data handling, laboratory work, and professional interpretation. Identify which parties are involved and where their responsibilities meet. If a feasibility review rejects the proposed collection method, the reporting specification can still be useful for another collection route; it should not pressure the team to claim an unsupported aircraft capability.

Before requesting a bundled price, assemble a short requirement note: the medium under investigation, the analyte or observation of interest, the intended reporting decision, the receiving system, and the professional responsible for the interpretation. Leave unknown technical choices open. A specific problem statement is more useful than requesting an all-purpose environmental drone package.

What the buyer should ask next

Make the exception owner visible in the handover record. For example, a missing qualification can be assigned to the source-report provider, while an import that drops a supplied qualification belongs with the data-transfer owner. The analyst then reviews any effect on the intended conclusion. This proposed division is not a universal organizational chart; it is a way to prevent every discrepancy from being passed between contractors without a decision. Agree the actual responsibilities with the parties named in the quotation.

Should every non-detect be left out of calculations? This article does not prescribe that. The responsible analyst must select a justified treatment for the data, purpose, and applicable requirements, and document the decision.

Can the report use a prescribed surrogate? Where a relevant requirement or justified method calls for one, preserve its status as a reporting choice and retain the original evidence. Do not present it as an independently measured value.

How should a configuration discussion begin? Send the analyte or observation, medium, reporting purpose, and responsible analyst's requirements through the UNITED UAV inquiry page. Ask first whether any proposed payload and workflow are appropriate, then request separate scope and evidence for the parts that can actually be supported.

EPA background source checked 13 October 2026. Examples are editorial procurement analysis, not environmental, legal, statistical, or flight advice.