Satellite Operators Editing and Proofreading Services

A conjunction alert shows a 1-in-8,000 chance of collision between an active satellite and a piece of debris, closing to within 200 metres in eleven hours. The operator decides to manoeuvre. The notification sent to customers who depend on that satellite's service says only that a planned manoeuvre will cause a brief service interruption, with no explanation of why a satellite that was not scheduled for any manoeuvre is suddenly having an unscheduled one, and no indication of whether this is routine or the kind of event a customer might want to understand better before it happens again next month.

We edit what satellite operators produce around collision avoidance and spacecraft operations — conjunction assessment and manoeuvre decision communications, spacecraft anomaly reports and their resolution, customer service interruption notifications, orbital debris and space situational awareness reporting, license and regulatory filing correspondence, and the internal criteria documents that state when a manoeuvre is triggered. Our editors work on the message that has to explain an invisible decision to people who only experience its consequence.

The decision criteria stated plainly is what turns a conjunction-driven manoeuvre notification from an unexplained inconvenience into an understood event, and its failure is a notice that reports the consequence — a service interruption — without any of the reasoning that produced it. A brief service interruption tells a customer nothing about whether this is routine risk management or something they should be worried is becoming more frequent. We work through these so the actual trigger for the decision is stated in terms a customer can evaluate, since "a planned manoeuvre" obscures that this was actually a probability threshold being crossed, which is a very different kind of event from routine stationkeeping; so the frequency and normality of this kind of event is given context, given that a customer experiencing their first conjunction-driven manoeuvre has no way to know whether this happens monthly across the fleet or is a rare escalation; so the timeline and duration of the service interruption is stated specifically rather than as "brief," because a customer planning around an outage needs a window, not an adjective; so anomaly reports distinguish a resolved issue from one being monitored, as these require very different customer expectations about recurrence; so regulatory and licensing correspondence about debris mitigation states compliance status specifically rather than in general terms of commitment to best practices, since a regulator reading a filing needs a status, not an intention; and so internal criteria for triggering a manoeuvre are documented precisely enough that a decision can be reviewed afterward against the stated threshold, rather than justified after the fact by whoever made the call. Communications written this way keep customer trust through an event that, explained badly, looks like something going wrong rather than something working correctly.

Everything you send is treated in confidence, including operational data, customer information and technical findings. We are editors rather than satellite operators, orbital mechanics specialists or regulatory advisors, and we offer no view on collision risk, operational decisions or compliance. What we can do is make sure the explanation matches what the customer actually needs to know.