A recent image acquisition date does not, by itself, tell a reviewer the epoch associated with its supporting coordinates. For a UG21 mapping inquiry, request three separate records: when observations were collected, which coordinate reference and applicable epoch the deliverable uses, and when the output was processed. Have the responsible survey professional explain their relationship. Do not resolve a mismatch by changing a date label or applying an undocumented shift.

This distinction matters when a project combines new site imagery with an earlier control record, a design drawing or a previous survey. The immediate purchasing question is not whether the newest file looks sharper. It is whether the supplier can identify the reference information behind that file and show who reviewed its suitability for the intended comparison.

Give each date a specific job

Start the brief with the decision the mapping will support. A visual progress update, a repeat-site comparison and a deliverable intended for engineering use do not necessarily require the same review. Avoid writing a blanket accuracy requirement before the people responsible for the downstream work have described what they need to compare and what evidence they will accept.

Then separate the date fields in the requested handover. An acquisition record tells the buyer about collection timing. A processing record identifies when a particular output was produced. A coordinate-reference record describes the basis on which coordinates are supplied, including an epoch where applicable. The buyer should not assume that one field can replace the others simply because each contains a year.

These are proposed procurement distinctions, not a substitute for geodetic judgment. Some projects may have a straightforward, well-established reference requirement. Others need specialist interpretation. In either case, the useful outcome is a documented answer from the responsible person, not a buyer choosing an epoch from a calendar because it matches the site visit.

Read the source within its limits

The NOAA National Geodetic Survey's NA2011 FAQ, question 11, explains an epoch date as a date associated with station coordinates and discusses coordinates changing with time. That page was last updated in April 2012. It is useful here for the underlying concept, not as a current processing instruction.

NGS also distinguishes survey-epoch and reference-epoch coordinates in its modernization FAQ. The explanation concerns the modernized system and must not be read as proof that every planned service has already been adopted. Neither source establishes a positioning capability for UG21. This article does not prescribe a transformation, select a datum for your project or estimate a coordinate change.

Build a reference record that survives handover

For a practical review, ask for a small, explicit record alongside the delivered files. Its purpose is to stop essential explanations being stranded in a meeting or a private message. The record should be understandable to the next analyst without requiring that analyst to reconstruct the supplier's intentions from filenames.

• Identify the deliverable and its revision, including the exact files to which the record applies.
• List acquisition dates or date ranges separately from the processing date.
• State the coordinate reference, realization and applicable epoch as confirmed by the responsible professional.
• Identify the source control information and the version of the supporting record.
• Describe any reference changes made during processing and point to the retained explanation.
• Name the reviewer, the intended use and any unresolved limitations.

Do not turn this list into a demand for confidential project information in an initial sales email. A redacted example can establish the expected format. Actual control details should follow the project's access rules. The buyer needs enough information to evaluate the proposed process before ordering, while keeping sensitive site records within an appropriate review channel.

A field marked unknown is more useful than a plausible value inserted without evidence. Make unresolved items visible in the quote review. Assign an owner and a decision date to each item. If the supplier cannot establish the reference basis of an inherited dataset, the response may be a limited comparison, an additional investigation or a revised deliverable, rather than a confident compatibility statement.

A repeat-site review without an invented success story

Consider a hypothetical facilities team comparing a new mapping delivery with an earlier site plan. Both packages use familiar coordinate terminology, but the new report lists only an image capture date. The team sees a discrepancy and asks whether the ground has changed. At this point, the available information does not justify that conclusion, nor does it justify blaming the aircraft.

The first action is documentary: preserve both received packages and request the missing reference explanation. Ask the survey lead to identify which records are directly comparable and which require further treatment. Record the question against the specific deliverable revision. Avoid asking an analyst to move one dataset until it looks aligned, since that would obscure the basis of the comparison.

The next action is contractual: determine whether investigating inherited reference information was included in the supplier's scope. If it was excluded, request a separately described task with an owner and an output. If it was included, ask for the missing evidence. This approach keeps a technical uncertainty from becoming an argument about who should have guessed the customer's expectations.

The example is original editorial buyer analysis, not a reported customer incident. Its transferable lesson is narrow: a date column should have a declared meaning. Good handover discipline makes uncertainty easier to resolve; it does not guarantee that every historical file can be reconciled or that a particular comparison will meet a professional acceptance standard.

Define acceptance before the final delivery

Ask the intended recipient to review the proposed reference-record format early. A procurement manager may care that a document exists, while the GIS or survey reviewer needs particular fields and supporting evidence. Those are different checks. Naming both reviewers helps avoid a completed commercial delivery that remains unusable for its intended technical purpose.

Use a limited, authorized example to test the handover process. The reviewer should be able to identify the file revision, locate its acquisition information and follow the reference explanation without contacting an unnamed operator. Any remaining question should have a documented disposition. This is an evidence-navigation exercise, not a substitute for independent positional validation.

Also decide what happens when a corrected package arrives. Keep the earlier revision identifiable, document the reason for replacement and notify downstream recipients. Do not silently replace an output that has already entered another team's analysis. Your acceptance record should distinguish a corrected label from reprocessed data and should state which downstream conclusions need review.

For hosted outputs, acceptance also has a delivery-path dimension. The companion UG73 guide to Cloud Optimized GeoTIFF delivery separates the file from the way the recipient accesses it. A readable web map does not replace the coordinate-reference record, just as a complete record does not prove that the hosted file works in the recipient's software.

Keep hardware selection separate from survey responsibility

The UG21 product page is a starting point for a VTOL and fixed-wing platform inquiry. Its product identity is not evidence that a particular positioning system, processing service, coordinate transformation or professional survey review is included. Those details need a configuration-specific answer and, where appropriate, a separately defined service agreement.

When discussing a proposed package, separate the aircraft, payload, positioning components, processing workflow and final professional review. Ask which organization owns each part. A single commercial quotation may bring several elements together, but the responsibilities should still be visible. This is especially important when the person delivering imagery is not the person approving its use in engineering work.

A calibration claim is another example of evidence that needs a precise scope. The UIV2200 guide to laboratory accreditation scope addresses a different procurement check: whether a quoted measurement activity falls within a laboratory's stated coverage. Neither a calibration document nor an aircraft product name automatically settles the coordinate-reference question discussed here.

Send a focused inquiry

Retain the supplier's answer with the accepted specification rather than only in the email thread. If a different subcontractor later supplies the mapping output, repeat the responsibility check against that arrangement. A previous answer about one package should not silently become an assurance about a different team, dataset or configuration.

Before contacting a supplier, write one paragraph describing the intended comparison, the existing data you expect to use and the person who will approve the result. Add the proposed handover fields, but do not send sensitive site coordinates through an unapproved channel. Ask the supplier to identify missing information and distinguish included work from optional specialist support.

Use the VTOL and fixed-wing drone collection to review available platform identities, then contact UNITED UAV about the proposed UG21 configuration. Request an explicit answer about reference documentation and responsibility before comparing package totals. A useful reply should tell you what can be quoted now, what requires technical review and what remains outside the offered scope.

The buying decision becomes clearer when a date no longer has to do several jobs. Preserve the collection timeline, identify the coordinate basis and retain the processing history as separate evidence. That gives the responsible reviewer a defensible starting point without inventing precision, rewriting old records or treating a recent photograph as proof of a current coordinate epoch.