An inspection image and a condition assessment are different purchases. A useful satellite-inspection report connects observations, coverage limits and interpretation to the customer's defined asset-management question.
A satellite-inspection image can be striking while leaving a customer unsure what decision it supports. A visible surface, a suspected change and an assessed asset condition are different information products. A commercial customer should decide which one it needs before comparing image counts, presentation quality or a supplier's broader servicing ambitions.
The purchasing problem is familiar from other inspection markets: define the question, obtain evidence relevant to that question and preserve the limits of what the evidence can establish. In space, where another inspection may be difficult to arrange, the completeness and interpretability of the delivered record deserve particular attention.
A customer might want a record of external condition, a comparison with earlier documentation or evidence to inform a later lifecycle review. Each purpose changes the useful deliverable. A collection of photographs may satisfy an archive requirement while being inadequate for a reasoned assessment of a suspected change.
The customer should write the question in language that can be assessed after delivery. For example, an authorised asset owner might ask whether the supplied observations support a documented account of the visible condition of a named external area. That question is narrower and more defensible than asking the supplier to prove the complete health of the spacecraft.
The purchase should also identify the decision-maker. An engineering team, asset manager and commercial partner can need different explanations of the same observation. A good report gives them a common evidence base while making clear which conclusions require specialist judgement or information outside the purchased inspection.
JAXA's 14 June 2024 account of ADRAS-J observations described a defined service with image-quality and data-volume requirements intended to reveal aspects of long-orbiting debris condition. The release also distinguished observation from interpretation: it described visible material while treating its identification as a presumption informed by earlier imagery. That historical example illustrates the value of an information requirement and qualified analysis, rather than a generic promise to deliver impressive pictures.
Astroscale's inspection offering positions characterisation as relevant to subsequent lifecycle services and identifies commercial operators among its intended customers. That is evidence of the company's market positioning. It does not establish that a particular inspection scope, timetable or result is available to every prospective customer.
Together, these sources point to a commercial distinction. Inspection can be purchased as a useful information service in its own right, even when the eventual action informed by that service remains separate. The customer should evaluate the delivered evidence without assuming that a later servicing or disposal outcome has already been demonstrated.
The report should identify what was observed and what was outside the accepted scope. A clear statement of coverage helps a reader interpret both positive findings and apparent absences. Without it, a reader can mistake an unobserved area for an inspected area where nothing unusual was found.
There are at least three meaningful outcomes for a requested observation: relevant evidence was obtained, evidence was obtained but was insufficient for the question, or the relevant area was not observed. These states should remain distinct in the delivery summary. Collapsing them into a single completed status makes the report easier to read superficially and harder to use responsibly.
The customer should agree how partial coverage affects acceptance. It may accept a bounded report that answers most of its questions, request additional interpretation or hold a particular conclusion open. The price and completion condition should reflect that arrangement. Acceptance need not mean the evidence supports every conclusion the customer originally hoped to draw.
A representative sample report is useful before purchase. It should show how the supplier describes a limitation, rather than only displaying its best image. The missing-data section is often where a customer learns whether the service will support a serious review.
A statement in the report should lead back to identifiable evidence. Readers need to know which image or other delivered record supports the statement, when that evidence was obtained and whether any processing affects its interpretation. This need not make the executive summary difficult to read; detailed references can sit alongside the relevant finding.
The record should distinguish the original observation from an annotated or otherwise transformed version. An annotation can help a reader find a feature, but it should not replace the source object or hide the analyst's contribution. Retaining both versions allows a later reviewer to understand how the conclusion was presented.
For a comparison with historic material, identify the origin and applicability of the earlier record. A pre-launch photograph, an engineering illustration and an earlier inspection are not interchangeable baselines. If the earlier material does not show the same subject clearly enough, that limitation belongs in the comparison.
BDI's guide to derived-data lineage addresses the broader principle: a downstream claim should retain its relationship to the evidence and transformations that produced it. In an inspection report, that relationship makes disagreement inspectable rather than leaving the customer with an unexplained conclusion.
Consider an illustrative commercial asset review. A delivered image shows an external feature that looks different from the customer's earlier documentation. The supplier records the difference but cannot establish from the available material whether it reflects a physical change, the earlier record's limitations or a difference in presentation.
That finding can still be valuable. It identifies an uncertainty the customer can examine against its own records or other evidence. It becomes less useful if the report jumps directly from a visible difference to a confident explanation of the cause. The customer's next decision depends on knowing which part was observed and which part remains an interpretation.
The assessment should explain its confidence in ordinary language tied to the evidence. A numerical score without a defined basis may create false precision. A concise description of the supporting observations, competing interpretations and missing information can be more informative to the person deciding whether further assessment is justified.
A negative finding needs the same discipline. Saying that the delivered observations do not show a specified feature is narrower than certifying that the feature does not exist anywhere on the asset. The wording should follow the coverage and information quality actually achieved.
A customer may receive preliminary images before the assessed report is complete. The service should label these stages clearly and identify which delivery starts the acceptance review. Otherwise a preliminary preview can be mistaken for the final evidence package or trigger a commercial deadline prematurely.
The final package should connect the delivered objects, findings, limitations and revision history. If the supplier corrects an interpretation, the customer needs to know which earlier statement it replaces and whether the underlying observations changed. BDI's ground-service handover guide provides a related framework for distinguishing transfer completion from acceptance of an information product.
Agree who can raise a question and how the supplier will respond during review. An explanation of an existing finding is different from a request for new acquisition or an expanded analytical scope. Keeping that distinction clear avoids an open-ended support expectation while preserving a reasonable opportunity to understand the purchased report.
The customer should establish which evidence it can retain, share with an authorised adviser and use in a later asset review. A portal view that expires can be inadequate if the report's purpose includes explaining a decision months afterwards. The available export should preserve the context needed to interpret the findings.
A useful acceptance decision ultimately asks whether the supplier delivered evidence that answers the agreed question within stated limits. It does not reward visual drama or require unsupported certainty. The commercial value lies in reducing a defined uncertainty while leaving a durable record of what remains unknown.
JAXA's June 2024 release is a historical buyer account of a defined observation service. Astroscale's inspection page establishes its stated commercial positioning. The article addresses information-product acceptance and authorised asset assessment, without inspection manoeuvres or operational methods.
Suggest a correction