Reports and publishing
One saved analysis. The right evidence for each reader.
Publishing freezes the available analysis artifacts and report inputs into a version. The report can then present an appropriate scope and level of technical detail without silently recomputing live project data.
Customer
Decision, outcome, major risk and recommended action.
Field worker
Installation-facing checks, site inputs and operational cautions.
Engineer
Technical inputs, models, detailed evidence and open risks.
Regulator
Scope-appropriate technical basis and cited evidence.
Published map, heatmap and profile artifacts retain the version’s available evidence.
Full, terrestrial, satellite, HaLow, node-link and comparison reports can narrow what they expose.
Technical provenance appears where it is useful and is withheld where it would distract a field or customer reader.