An analytical result becomes operational information only when the receiving team can understand it and use it within existing responsibilities. Handoffs often fail because assumptions that were obvious to the analyst are absent from the delivered product. This perspective considers the information needed at that boundary: acquisition time, processing status, geographic scope, quality qualifications, and the action expected from the recipient. It also asks how corrections and feedback should return to the producing team. A dependable handoff creates a shared understanding of the result, rather than merely transferring a file.
This working guide considers writing requirements from an earth observation need in potato growing fields. The immediate decision is to focus scouting within potato fields. Useful reference evidence includes emergence records, canopy stage and representative plot observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Potato growing fields
Potato monitoring begins with the distinction between the canopy visible from above and the crop component ultimately harvested below ground. Establishment timing, variety, row structure and management can create different canopy patterns across fields. An image service should specify whether it is supporting crop-stage assessment, identifying areas for inspection or estimating a defined production variable. These objectives require different reference measurements and should not be combined into one unqualified vegetation score.
Maintain a field timeline that includes planting, emergence and the operations that can affect canopy appearance. Early observations may contain a large soil contribution, while later observations may show a more continuous canopy. Cloud and shadow contamination, field edges and neighbouring land cover can alter summaries at either stage. Compare observations using suitable quality rules and retain the acquisition dates so that a recent-looking map does not conceal an old measurement.
A field team should collect consistent crop-stage and canopy observations across both flagged and typical areas. Record management context and sampling support rather than relying on an isolated photograph. A vegetation change cannot establish the presence of a specific disease, and a canopy index is not a direct measurement of tuber yield. Evaluate any production model with appropriate harvest data and independent assessment, while keeping the simpler inspection-priority product transparent about what it actually observes.
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.
Deliver quality flags that users can interpret
Quality information should describe the condition of an observation in terms that remain useful through the workflow. A single valid or invalid label may be sufficient for some calculations, but operational users often need to know why an observation was qualified. Distinguish acquisition limitations, processing failures, uncertain reference matches, and conditions that make interpretation ambiguous. These categories point towards different responses and should not be merged without a clear purpose.
Define a small, documented set of flags with stable meanings. Record whether a flag applies to a complete scene, a geographic unit, an individual measurement, or a derived result. A unit containing a mixture of qualified and unqualified observations may also require a coverage measure. Include the rule used to combine flags when summarising data so that a favourable average does not conceal a substantial fraction of unusable input.
Test the flags with the people receiving the product. Ask what they would do differently for each state and whether the terminology supports that choice. Keep the original flags available even if the interface presents a simpler summary. When flag definitions change, version the rules and review their effects on historical comparisons. Useful quality communication makes the condition of the evidence visible at the moment when a user decides how much confidence to place in the result.
Check readiness before an acquisition
An acquisition plan should consider the complete sequence needed to obtain a usable observation. Define the target, the required configuration, the timing opportunity, and the conditions under which the observation should proceed. For a spacecraft study, this includes the relationships between pointing, instrument operation, available resources, and data handling. For other observation platforms, the same principle applies: a valid measurement depends on more than the presence of a suitable sensor.
Use a readiness checklist tied to the intended acquisition rather than a generic declaration that the system is available. Confirm the relevant configuration, geographic information, time references, storage capacity, and expected data products. Identify conditions that require postponement or a revised plan. Where resource estimates are uncertain, state the assumption and test its consequences before treating it as an operational margin.
Review the acquisition after it occurs or after a representative simulation. Compare the planned sequence with the evidence actually produced, including metadata, coverage, and quality information. Record incomplete acquisitions as useful evidence about the workflow rather than silently excluding them from the record. Repeated reviews can reveal whether a limitation arises from planning, platform behaviour, instrument operation, or processing. This creates a disciplined route from an observation opportunity to a dependable measurement capability.
Bring the evidence back to the decision
A successful handoff leaves the recipient with a clear result, sufficient context, and a practical route for raising questions. Test the delivery with the people who will use it, including how they respond when observations are missing or qualified. Capture their feedback as evidence for improving the product. The most useful delivery format is the one that preserves the relevant technical meaning while fitting the decisions, time constraints, and responsibilities of its intended audience.
Sources & further reading
Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.


