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 testing whether a remote sensing model transfers around active construction sites. The immediate decision is to prioritise sites requiring progress review. Useful reference evidence includes dated site records and consistently located surface observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.
The setting: Construction site change
A construction site can progress through clearing, ground works, temporary storage, structural development and surface finishing. A satellite image may reveal some visible changes without establishing whether the project has reached a contractual or operational milestone. Define the monitoring objective in terms of observable surfaces and the decisions the information should support. Site boundaries and a reliable sequence of dated records provide the context needed to distinguish project activity from changes in neighbouring land.
The size and arrangement of features determine what the image can resolve. Stockpiles, temporary access routes and partly completed structures may be mixed with other surfaces within an observation. Shadows and acquisition geometry can also change the appearance of buildings. Compare quality-screened observations and retain the dates supporting each mapped change. A map should not imply that every visible feature was measured independently or that its physical dimensions are known more precisely than the data allow.
Validation should use dated site observations that describe the same area and feature definition as the analysis. Record temporary works and other context that might explain an apparent change. A remote observation can help select a site for review, while more specific statements about project progress need relevant project records. Evaluate whether the product provides useful and timely evidence for that review, including examples where a conspicuous image change had an ordinary or temporary explanation.
Identify what changes between domains
A model trained on one region or season learns relationships present in its development data. Applying it elsewhere assumes those relationships remain useful. New crop varieties, forest types, soil colours, management practices, illumination, or sensor characteristics can violate that assumption. Define the intended transfer explicitly: a new district, another year, another sensor, or a different class distribution. Each change creates a different test. A model that transfers across nearby fields has not thereby demonstrated reliable performance across climates or observation systems.
Keep the measurement pipeline consistent before attributing differences to the model. Reflectance scaling, band order, cloud masking, spatial resolution, composite windows, and missing value handling can all change predictions. Sensors with similarly named bands may have different spectral responses. Harmonization can reduce some differences but does not establish equivalence for every target. Examine predictor distributions, missing data rates, and examples from the new setting. Flag inputs outside the conditions represented during training so that extrapolation remains visible.
Test the destination, then adapt carefully
Design evaluation splits around the intended deployment. Hold out geographic regions to test spatial transfer and later years to test temporal transfer, keeping neighboring samples or repeated observations of the same site together when needed. Report performance for meaningful destination groups rather than only a pooled score. Class prevalence affects some metrics, so interpret changes alongside the underlying confusion matrix or residual distributions. A random pixel split can look excellent while providing little evidence about performance in an unseen region.
If local labels are available, reserve a destination assessment set before fine tuning or recalibration. Use the remaining observations to compare straightforward baselines with more complex adaptation methods. Check whether improvement comes from genuine transfer or simply from adding representative local data. Retain an option to withhold predictions when input quality or novelty makes them unreliable. Document the training domain, destination evidence, preprocessing versions, and conditions where use is unsupported. Continue monitoring once new observations arrive, since seasonal and environmental shifts can emerge after an initial evaluation. Transferability is a measured property of a particular model, workflow, target, and destination; it should not be inferred from architecture name or strong performance on the original test set.
Budget the complete processing workflow
A processing budget should cover the complete path from source observations to a maintained product. Data access and computing are only part of that path. Include preparation, geographic updates, reference collection, expert review, delivery, and support where those activities belong to the service. A calculation that runs cheaply on a small demonstration can still require substantial effort when the surrounding work is repeated across many locations.
Measure representative tasks rather than assuming that every observation costs the same amount to process. Record data volume, processing time, retry frequency, manual interventions, and the conditions that create unusually demanding cases. Separate fixed setup work from work that grows with the number of observations or users. These records support decisions about batching, caching, storage policy, and the point at which a different processing design becomes worthwhile.
Connect the budget to a defined level of service. Faster delivery, more frequent observation, broader coverage, or more detailed review can each change the resources required. Describe these trade-offs before promising a delivery pattern that the workflow has not demonstrated. Review the budget using operational evidence and preserve enough detail to understand changes between processing versions. The aim is a sustainable service whose resource choices remain aligned with the information that users value.
Preserve a reproducible processing history
A result should be linked to the inputs and processing choices that produced it. Record source identifiers, software versions, configuration values, reference data versions, and the time of processing. The record does not need to expose every internal implementation detail to the end user. It must preserve enough information for the producing team to investigate a result, reproduce a comparison, and explain why a revised product differs from an earlier version.
Version changes that can affect the meaning of the output. Updated boundaries, a new quality mask, revised calibration, different model parameters, or altered aggregation rules can all change results even when the source imagery is unchanged. Avoid overwriting an earlier product without retaining a suitable history. A clear relationship between versions helps users distinguish an improvement in processing from a real change in the observed surface.
Use representative regression cases when modifying the workflow. Select cases that cover ordinary conditions and known failure modes, then compare meaningful outputs before and after the change. Investigate differences against the intended purpose of the revision rather than assuming that a closer visual match is always preferable. Preserve the review decision with the version record. Reproducibility becomes practical when the team can trace a result through a documented sequence of inputs, transformations, tests, and delivery decisions.
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.



