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 open-field tomato production. The immediate decision is to select tomato rows for crop review. Useful reference evidence includes transplanting dates, canopy observations and field management notes. 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: Open-field tomato production
Open-field tomato production can involve short management cycles, staggered planting and repeated operations within neighbouring parcels. The field calendar is therefore central to interpreting a satellite observation. Newly transplanted plants, established rows and areas nearing the end of production can show different responses for ordinary reasons. Record the planted area and the relevant management unit carefully, particularly where a commercial holding contains several crops or planting stages at the same time.
The image footprint may mix plants with soil, mulch, access routes and irrigation infrastructure. Determine whether the spatial resolution supports the intended row-level interpretation or whether a broader field summary is more appropriate. Examine the quality and age of observations before proposing a management use that depends on rapid response. A monitoring workflow should communicate when cloud gaps or the acquisition schedule leave insufficient current evidence for that decision.
Validation should document crop stage, canopy continuity, recent operations and the area represented by each sample. Field staff may use a mapped anomaly to choose an inspection location, but the subsequent diagnosis requires suitable observations and expertise. If production or quality is the target, collect reference information for those outcomes rather than assuming that greener vegetation implies more marketable fruit. The evaluation should measure whether the product improves a defined scouting or management process.
Maintain the geographic units of analysis
Many observation services summarise measurements within a field, management block, catchment, forest unit, or other mapped boundary. The meaning of that summary depends on whether the boundary accurately represents the unit being discussed. Start with a clear source for the geometry and record its date, coordinate reference, and intended use. A boundary drawn for visual orientation may require additional checking before it becomes a measurement unit.
Inspect overlaps, gaps, narrow fragments, and features that may have changed since mapping. A geometrically valid polygon can still describe an outdated operational unit. Ask the responsible team how divisions, mergers, new infrastructure, and management changes are recorded. Where pixels or reference measurements cross a boundary, define how they are assigned or excluded so that results remain comparable between analysts and processing runs.
Version the boundaries alongside the observations. If a unit changes, preserve a relationship between the previous and revised geometry rather than replacing the history without explanation. Comparisons through time should identify whether they use a constant spatial unit or the operational units valid at each date. This makes it easier to distinguish a change in the measured surface from a change introduced by the geography used to summarise it.
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
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.



