Satellite Operators Editing and Proofreading Services

Eleven hours before closest approach, a conjunction data message puts the chance of collision between an active satellite and a piece of debris at 1 in 8,000, with a predicted miss distance of 200 meters. The operator decides to maneuver. The notice that goes out to customers says a planned maneuver will cause a brief service interruption, and nothing further. It does not say why a satellite with no maneuver on its schedule is suddenly making one, or whether this is ordinary or the start of something. The customers who read it will feel the interruption without ever learning what it was for.

Conjunction assessment and maneuver decision communications, customer service interruption notices, and spacecraft anomaly reports with their resolutions come to us most often. The work also covers orbital debris and space situational awareness reporting, license and regulatory filing correspondence, and the internal criteria documents that state when a maneuver is triggered. Our editors attend to the message that has to account for a decision no customer can see.

These notices fail by reporting a consequence and withholding the reasoning that produced it. The phrase "a planned maneuver" covers routine stationkeeping and a collision avoidance burn equally well, though the first is a calendar entry and the second is a threshold being crossed. A line reading "a tracked debris object was predicted to pass within 200 meters at a collision probability of 1 in 8,000, and the satellite was moved out of its path" tells a reader what kind of event this was. The word "brief" fails in the same way, because a customer arranging work around an outage needs a start time and a duration in minutes rather than an adjective.

Frequency is the other thing a customer cannot supply. Someone seeing a first conjunction-driven maneuver has no way to know whether the fleet does this most months or whether the event is a rare escalation, and one sentence of context settles the question. Anomaly reports need the same discrimination between a fault that has been resolved and one that is still under observation, because the two carry different expectations about recurrence. A filing that says the operator "remains committed to responsible debris mitigation" gives a regulator nothing to check, while a filing naming the requirement, the disposal orbit, and the date the maneuver was completed states a status.

Internal criteria deserve the same treatment, since a maneuver reviewed six months later can only be judged against a threshold written down beforehand. Criteria recorded as a numerical probability, an object class, and the person authorized to order the burn allow that review to happen. Criteria recorded as "operator judgment" leave the decision to be defended after the fact by whoever made it. Communications written this way hold customer trust through an event that, described badly, looks like a failure rather than a system working correctly.

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