Check the displayed temperature scale before interpreting a color difference between thermal report panels. More red in a second image is not, on its own, a defensible finding that a condition has worsened. For a UVH2 inspection inquiry, define the comparison question and ask what supporting records a qualified reviewer needs. Do not infer sensor compatibility, measurement capability or a diagnostic result from the appearance of an aircraft or a thermal image.

A reviewer opens two panels side by side. One appears muted, while the other contains a bright patch. It is tempting to turn that contrast into a conclusion before reading the legends. This is a hypothetical reporting scenario, not an account of a UVH2 inspection. The useful question is whether the presentation supports the intended comparison and whether the evidence behind the panels has been reviewed.

Read the scale before the color patch

A report panel should give its recipient enough context to understand the display. Ask the proposed provider how the legend will be shown, which labels belong to each image and how the reviewer can find the supporting record. A picture separated from its explanation may be useful as an illustration while being inadequate for the comparison the buyer has in mind.

FLIR's technical note The secret to a good thermal image, written by Christiane Buchgeister in July 2017, explains that the displayed temperature interval affects brightness and contrast. It also describes automatic limits based on the apparent minimum and maximum in the scene. This dated note supports a general display principle. It does not establish that UVH2 includes FLIR hardware, that a particular export is available, or that a pictured object has a fault.

The procurement implication is to ask how the proposed report will prevent a reader from mistaking display appearance for a reviewed finding. That is our editorial recommendation. The provider should explain the chosen presentation, and the qualified reviewer should determine what conclusions the available evidence can support. A familiar palette does not remove either responsibility.

Define the comparison before requesting the panels

Write the intended question in plain language. Is the recipient comparing two observations of an identified object, reviewing different areas in one visit, or simply locating material for further assessment? The report should be designed around that purpose. A generic request for before-and-after pictures can leave the provider guessing which differences matter and the recipient guessing which similarities were controlled.

Ask what would make the comparison inconclusive. The responsible specialist should identify the conditions, records and limitations relevant to the actual application. The buyer should preserve that explanation in the scope rather than inventing a universal checklist for every object and environment. This guide is about commissioning a clear report, not performing thermography or diagnosing equipment.

Keep the intended audience in view. A specialist may need access to supporting data and method information, while a manager may need a concise conclusion with visible limitations. Those are different communication needs. Ask for a package that connects the summary to its evidence so that a short presentation does not become detached from the review that gives it meaning.

Specify a report-panel contract

Our suggested starting point is a small panel specification agreed by the provider and recipient. It should identify the observation, the role of the image, the display explanation and the location of supporting records. Let the specialist determine the technical fields required for the project. The buyer's job is to ensure that the fields are understandable and will actually be delivered.

Ask whether the display scale will be fixed for a defined comparison or adjusted for another purpose, and how that choice will be explained. Do not direct the provider to use one setting for every circumstance merely to make the panels look uniform. A qualified reviewer should decide what presentation is appropriate and explain any tradeoff between revealing detail and supporting the intended comparison.

If a panel is adjusted for presentation, request a clear relationship to the reviewed source material. The report should not leave a later reader unsure whether two versions represent different observations or different views of the same observation. A simple version and purpose statement can help, provided it is part of the actual package rather than a convention known only to the original author.

Test the explanation with a representative sample

Before requesting a large report, ask for a sample layout that the intended recipient can review. The review question is whether the layout communicates the comparison and its limits clearly. It should not be treated as acceptance of unprovided project data. If the example is illustrative or comes from a different context, have the provider state that context plainly.

During the review, ask someone to explain what the legend means for each panel before discussing the conclusion. Then ask where they would find the supporting record. If those questions cannot be answered, clarify the layout or documentation request. Do not respond by choosing a more vivid palette to make the intended story easier to see.

Keep a distinction between an identified reporting problem and a confirmed technical problem. A missing legend is a reason to request the missing information. It does not automatically prove that the underlying observation is wrong. Conversely, a complete legend does not prove that every relevant measurement or interpretation requirement has been met. The specialist review still has its own scope.

A practical lesson for report handover

Ask the reviewer to describe the comparison without relying on the phrase more red. This is a proposed review exercise, not a quote from a customer or an expert interview. It prompts the team to use the scale, observation identity and supporting evidence in its explanation. If the conclusion cannot survive that discussion, it needs clarification before being presented as an actionable finding.

Make the lesson a habit in the handover meeting. Assign one person to verify that each panel carries its own explanation and another to confirm that the summary points to the correct records. Have the responsible specialist state the limits of the conclusion. These are documentation roles, not a substitute for the qualifications or methods required by the actual inspection.

Do matching scales settle the whole question?

No. Matching scales can address a display-comparison issue, but this article does not treat that as sufficient evidence of a valid measurement comparison or a diagnosis. Ask the qualified reviewer what else must be established for the particular question. The buyer should not turn one useful presentation check into a blanket approval of the full inspection chain.

Likewise, different display scales are not automatically evidence of misconduct or a failed inspection. They may serve a stated presentation purpose. The problem for the buyer is an unexplained difference that a reader can easily misinterpret. Request the explanation, keep it near the panels and make sure the conclusion does not depend on an assumption that the report never discloses.

Where UVH2 fits

The UVH2 dual-sensor fixed-wing VTOL drone product page is the starting point for a configuration inquiry. Its category does not by itself answer which report formats, radiometric files, software functions or third-party integrations are available in a proposed package. Ask UNITED UAV for configuration details and identify which questions belong to the proposed inspection and reporting provider.

Carry the reporting requirement into any comparison across the VTOL and fixed-wing drone collection. State the intended deliverable and the review responsibility consistently. Avoid treating an aircraft image or a broad application description as evidence that a complete inspection service has been supplied, tested or approved for your particular use.

The cost of producing and reviewing a package also depends on its scope. Our UG82 guide to estimate assumptions helps organize that discussion without inventing project totals. For another example of separating appearance from data meaning, see the UG32 raster-handover guide. These are related procurement habits, not claims of shared sensor capabilities between the products.

Send a comparison question, not just an image request

Keep the acceptance note linked to the reviewed report version. Record whether the team checked layout clarity, supporting documentation or the specialist's conclusion; those are not identical reviews. When a panel is revised, identify the reason and ask which part of the review must be repeated. A tidy revision history is useful only when it explains the meaning of the change, not merely that a new file was created.

• Which identified observations are to be compared?
• Who will determine whether the comparison is technically appropriate?
• How will each panel disclose its display scale and purpose?
• Where will supporting records and limitations be available?
• What would make the requested conclusion inconclusive?

A clear response can lead to a narrower, more useful scope, including a decision that additional specialist evidence is required. That is a legitimate outcome of the inquiry. The goal is not to force every proposed comparison into a confident conclusion. It is to make the report's presentation and the evidence behind it understandable to the people who must use it.

To begin, send UNITED UAV your UVH2 configuration inquiry with the comparison question and the recipient's report-panel requirements. Mark unconfirmed sensor and processing needs explicitly. This keeps the discussion grounded in what can be supplied and reviewed, without turning a color difference into a diagnosis or a product category into an unsupported capability claim.