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 optical payload choices for small satellites across forest restoration sites. The immediate decision is to track areas requiring restoration follow-up. Useful reference evidence includes planting records, survival assessments and vegetation composition. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Forest restoration sites
A forest restoration site can contain planted seedlings, natural regrowth, grasses, shrubs and remaining mature trees. An increase in remotely observed vegetation does not by itself establish that the intended restoration objectives have been achieved. The monitoring plan should identify which outcomes matter, such as vegetation establishment, survival of planted trees or recovery of a particular structure. Each outcome needs reference observations that distinguish the desired change from other ways a site can become greener.
Maintain the boundaries of treatment areas and record planting, maintenance and disturbance events. Compare image sequences at suitable seasonal stages and examine how exposed soil or rapidly growing ground vegetation contributes to the signal. Small planting patches may be difficult to separate from their surroundings at satellite scale. A broader observation can still be useful, provided its interpretation remains consistent with the surfaces and spatial support actually measured.
Field assessments should document survival, composition and structural development according to the restoration objective. Include locations with apparently favourable image responses as well as areas that look unusual, since both can reveal important errors in interpretation. A satellite-derived pattern may help organise follow-up work without replacing field evidence of ecological recovery. Reports should explain which changes were observed remotely, which outcomes were confirmed on the ground and which questions remain unresolved at the current monitoring scale.
Connect the optical design to the measurement
An optical Earth observation payload turns incoming radiance into sampled measurements. Its usefulness depends on more than the ground size represented by a pixel. The aperture, focal length, detector characteristics, spectral response and operating environment all influence the information that survives into the image. A mission should choose these features around a target measurement and its expected brightness, rather than treating pixel spacing as a complete performance specification.
Ground sampling distance describes the spacing of samples on the surface for a specified viewing geometry. Optical blur, detector response, motion and processing can reduce the detail that is actually resolved. The modulation transfer function expresses how contrast is retained across spatial frequencies and helps connect component performance with final image sharpness. Smaller pixels alone cannot recover detail removed by the optical system or excessive image motion.
Balance signal, packaging and calibration
A larger entrance aperture can collect more light, but it also creates demands on mass, volume, alignment and thermal control. Narrow spectral bands collect less energy than broader bands under otherwise comparable conditions. Longer integration can improve signal collection until motion, saturation or other constraints become limiting. The resulting trade must be evaluated for dark targets as well as bright land, and for the expected range of illumination and atmospheric conditions.
Small spacecraft packaging makes mechanical and thermal interfaces particularly consequential. Focus and alignment can shift as temperatures change, while launch loads and contamination can affect performance. Stray light from outside the intended field can bias measurements even when an image appears visually acceptable. Baffles, suitable materials, cleanliness procedures and representative testing help control these effects. Detector defects, nonuniform response and electronic noise also require characterization.
Plan radiometric, geometric and spectral calibration with the payload design. Establish how ground tests connect to measurements after launch, and how changes in response will be monitored. The calibration record should describe uncertainties and conditions, rather than just providing a correction file. Evaluate the complete imaging chain using representative scenes and realistic motion assumptions. A credible specification states where performance is expected, how it will be measured and which tradeoffs were accepted. It should not turn a detector data sheet into an unsupported claim about an entire spacecraft.
Prioritise alerts using evidence and consequence
An alert is a request for attention, so its design should consider both the evidence available and the cost of responding. Begin by distinguishing a measured change, a proposed interpretation, and the action expected from the recipient. A large numerical difference is not automatically the most urgent case. The significance of the location, the age of the observation, the confidence in the interpretation, and the consequences of delay can all influence priority.
Create a review queue with enough context to support consistent decisions. Useful information can include the supporting dates, quality qualifications, previous observations, geographic unit, and the reason the case entered the queue. Define when an alert can be closed, escalated, or held for another observation. A documented rule is easier to improve than an informal practice that depends entirely on the memory of the operator reviewing the result.
Collect feedback from inspections and operational responses. Record alerts that led to a useful finding, alerts that required no action, and important conditions that the system failed to flag. Review these outcomes across different settings rather than relying only on a total count of alerts. The objective is a queue that directs limited attention towards meaningful decisions, while generating evidence for adjusting thresholds, improving context, and reducing repeated sources of unnecessary work.
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.


