Every observation and interpretation contains uncertainty, but the sources and consequences of that uncertainty differ between applications. Some arise from acquisition conditions, others from reference measurements, processing choices, or the transfer of a model to a new setting. This perspective examines how those sources affect the decision a user is considering. It encourages teams to describe uncertainty in a form that can influence action, rather than adding a generic qualification at the end of a report. The objective is to support proportionate decisions while keeping the limits of the available evidence understandable.
This working guide considers writing requirements from an earth observation need within ground-station data delivery. The immediate decision is to test delivery of usable observation products. Useful reference evidence includes transfer records, acquisition metadata and complete product checks. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Ground-station data delivery
A ground-station workflow connects acquired observations with the data products a user eventually receives. Successful communication is one part of that chain, while completeness, timing, processing and interpretation determine whether the observation is useful. Define what the delivery system must preserve, including acquisition identifiers, instrument settings, timing and the metadata needed for later calibration or geolocation. A received file should not automatically be treated as a complete and ready-to-use image product.
A test sequence should follow data from a known input through transfer, storage, processing and delivery. Record missing segments, failed attempts and changes in processing state instead of hiding them behind a simple success label. The operational question may concern when an agricultural user receives a current observation or whether a researcher can reproduce a product. These uses require traceable timestamps and a clear distinction between preliminary material and the version accepted for analysis.
Validation can use controlled test data and documented end-to-end checks before any independent satellite service becomes operational. Assess whether the delivered product retains its expected content and whether failures are represented clearly enough for a user to respond appropriately. A concept timetable cannot establish actual service availability. The practical output is evidence about the delivery workflow, its measured constraints and the information users need to judge the age, completeness and processing status of an observation.
Translate a user decision into measurable behavior
A mission requirement should connect to a decision that someone needs to make with the observations. Begin by defining the target phenomenon, geographic area, relevant season and consequence of delay or error. A request to monitor crops is too broad to guide a spacecraft design. The useful question is which crop condition must be distinguished, at what field scale, how often, and with what confidence.
Translate these needs into product requirements before allocating spacecraft specifications. Consider spatial detail, spectral information, radiometric performance, location accuracy, usable revisit and delivery latency. Geometric revisit describes observation opportunities; clouds and acquisition constraints can make usable observations much less frequent. Define terms carefully so that a requirement for delivered, cloud screened coverage cannot be satisfied merely by showing an orbit access calculation.
Keep traceability through design and verification
Write individual requirements that can be checked using a stated method and acceptance criterion. Identify the conditions under which each applies, such as target brightness, viewing angle or operating temperature. Avoid combining several unrelated promises in one sentence. Retain a rationale and a link to the higher level need, allowing reviewers to understand why the requirement exists and what would change if it were relaxed.
Allocate performance across the payload, spacecraft, ground segment and processing chain. Image sharpness may depend on optics, detector sampling, motion and resampling. Delivery time may depend on acquisition planning, onboard storage, ground contacts and processing queues. Budgets make these contributions visible and expose conflicts between objectives. Preserve margin where uncertainty remains, and record assumptions rather than hiding them inside an optimistic headline specification.
Plan verification while writing the requirement. Inspection, analysis, demonstration and testing each provide different kinds of evidence. Define the test configuration, reference measurement, uncertainty and pass criterion early enough to influence the design. Verification asks whether the implemented system meets its requirements; validation asks whether that system serves the intended use. Representative users and realistic application examples can reveal an inadequate requirement even when every hardware test passes. Manage revisions through a controlled record that describes their consequences for dependent requirements, budgets and tests. This turns requirements into a working design tool rather than a document assembled only before a review.
Translate the decision into observation requirements
Start with the decision that the information is intended to support. Describe the geographic unit, the time available for acting, and the consequence of an incorrect interpretation. A requirement such as detecting an unusual pattern across management blocks is different from identifying its cause. Keeping that distinction explicit helps a team select measurements that are relevant to the application and prevents later evaluation from drifting towards whatever result happens to be easiest to demonstrate.
Build a compact requirements matrix linking each decision to the evidence needed, the proposed observation source, and an acceptance condition. Include geographic accuracy, temporal relevance, quality screening, and the context required for interpretation. The matrix should also identify the evidence used to justify each requirement. An engineering preference or a convenient data source can inform a study, but neither should silently replace a documented information need.
Review the matrix with the people who will use the result. Ask how their response would change when information is delayed, incomplete, or uncertain. Record unresolved requirements as questions for a pilot rather than converting them into confident specifications. This produces a practical framework for comparing technical options, designing tests, and explaining why an observation is useful to the intended workflow.
Design an evaluation that reflects deployment
A model evaluation should resemble the conditions in which the model will be used. Start by identifying which relationships the development data share: nearby locations, repeated observations of the same unit, common collection teams, or measurements from a single period. These relationships can make records less independent than they appear. An evaluation that ignores them may test the ability to recognise familiar conditions rather than the ability to operate in a new setting.
Choose a split strategy that matches the intended transfer. Holding out locations, seasons, operational units, or acquisition conditions can answer different questions. Document which question each split is designed to address, and keep the held-out evidence separate while selecting features and tuning the method. Repeatedly inspecting the same evaluation set to improve a model gradually makes that set part of development, even if it retains its original label.
Report results at a scale that is meaningful to the user. A strong average can hide poor performance for important subgroups or unusual conditions. Examine error patterns and retain examples of both successful and unsuccessful predictions. Where the evidence covers only a limited range of conditions, describe that range explicitly. The evaluation then becomes a practical guide to suitable use, further testing, and the collection of additional reference observations.
Bring the evidence back to the decision
Useful uncertainty communication identifies the limitation, explains how it could affect the result, and connects it to a practical response. Some decisions can proceed with a qualified estimate; others require another observation or an independent check. Preserve uncertainty information through processing and delivery so that it is available at the point of use. This makes the analysis more accountable and gives the team a clearer basis for deciding which additional evidence would most improve the outcome.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



