A method that produces a plausible result has not automatically demonstrated that it works for its intended users. Validation requires a defined question, suitable reference evidence, and an evaluation design that reflects how the method will be used. This perspective examines which observations should be compared, how they should be sampled, and which errors matter in practice. It also considers the difference between evidence used to develop a method and evidence reserved for evaluating it. The objective is a test that can reveal weaknesses as well as confirm useful performance.
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.
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.
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.
Define a representative reference sample
A reference sample should represent the situations in which a method will be used. Begin by defining the target population: locations, time periods, management conditions, surface types, or instrument states that belong within the intended application. A collection of convenient observations may be valuable for exploration, but it does not automatically support conclusions about that wider population. Make the scope of the sample visible before calculating a summary of performance.
Consider a stratified design when important conditions are unevenly represented. Relevant strata might include different landscape types, developmental stages, observation quality levels, or ranges of the variable being estimated. Choose sample locations within those groups using a documented rule, and retain the information needed to understand their selection. Where access restrictions affect the sample, record the excluded conditions so that the limits of the resulting evaluation remain clear.
Keep development and evaluation evidence separate where the purpose of the study requires an independent test. Nearby observations or repeated measurements can share information, so a random split of individual records may overstate independence. A split organised by location, period, or operational unit can provide a more demanding comparison. The appropriate design follows the intended deployment, the structure of the observations, and the errors that matter to the user.
Keep an auditable review record
A review record should explain how a result moved from an analytical output to an accepted interpretation or operational decision. Preserve the product identifier, the evidence considered, the reviewer role, and the outcome of the review. A short, consistent record is often more useful than an extensive free-text note that cannot be compared between cases. The objective is to make important decisions traceable without turning routine review into unnecessary administrative work.
Separate observations from conclusions within the record. Describe the evidence visible to the reviewer, the alternative explanations considered where relevant, and the reason for accepting, qualifying, or rejecting the result. If a correction is required, identify what should change and how the revised product relates to the earlier version. Keep unresolved questions visible so that they can be addressed by another observation or by the person responsible for the next action.
Use the accumulated record to improve the workflow. Recurring review reasons can reveal unclear requirements, missing contextual information, unstable processing steps, or an evaluation gap. Examine whether similar cases receive similar decisions across reviewers and over time. Preserve the relationship between feedback and subsequent revisions so that improvements can be assessed against the evidence that motivated them. An auditable record supports learning, accountability, and consistent delivery while allowing the technical process to evolve.
Bring the evidence back to the decision
The validation record should explain the population represented by the test, the reference observations used, and the limitations of the comparison. Report meaningful errors alongside useful successes, and retain examples that challenge the method. Treat wider deployment as a new opportunity to evaluate transfer across relevant conditions. A well-designed validation programme gives users a defensible basis for deciding where the method is useful, where additional evidence is needed, and where another approach may be appropriate.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.



