The Client Called Every Day. We Have Counted.

ORC DISPATCH · MISSION REPORT · ORC-2024-177 · CLEARED FOR EXTERNAL PUBLICATION · CLIENT CONTACT LOG: INCLUDED IN FULL
MISSION REF / ORC-2024-177 · FILED 22 AUG 2024 · PUBLISHED 22 MAY 2026
The Client Called Every Day. We Have Counted.
LEO Standard Retrieval · S-01 · ORC-V1 “Maud” · Jul–Aug 2024
Outcome
SUCCESS
Duration
29 days
Client calls
29
Filed by
A. Kowalski
APPROVED BY M. HARGREAVES, OPS DIR · LEGAL: L. SANDHU · NOTE: THE CONTACT LOG IS ACCURATE. WE KEPT RECORDS.
CLIENT CONTACT LOG · DAYS 1–29 CLICK ANY ROW TO EXPAND
DAY
NATURE OF CONTACT
ORIGIN
01
Mission launch confirmed. Client acknowledges briefing pack.
ORC
A. Kowalski issued the standard launch confirmation. The briefing pack contains the update schedule. The update schedule states that ORC will call at mission milestones. Day 1 is a milestone. Days 2 through 7 are not milestones.
02
“Just checking in.” No new information requested or provided.
CLIENT
The client called at 09:14 to check in. A. Kowalski confirmed the mission was proceeding normally. The client asked if there was “anything to report.” There was not. The call lasted four minutes. Three of those minutes were silence.
03
“Anything yet?” No.
CLIENT
The client called at 08:52. A. Kowalski confirmed the mission was proceeding normally. The client asked the same question as day 2. The answer was the same as day 2. The call lasted two minutes. A. Kowalski has noted that this was an improvement.
07
Transit phase complete. ORC scheduled update issued.
ORC
A. Kowalski issued the planned Day 7 transit update. This call was in the briefing pack. The client seemed surprised that ORC had called without being called first. We noted this.
09
Rendezvous achieved. ORC scheduled update issued.
ORC
Rendezvous with the object achieved on schedule. Update issued per the briefing pack. The client asked how we knew where the object was. We explained that this is what we do. The client said “right, yes, of course.” This is a common response.
09
Client calls back 40 minutes later “to ask a follow-up.”
CLIENT
The follow-up question was whether we could “speed things up.” The answer was no. Orbital mechanics do not accommodate urgency as a parameter. A. Kowalski explained this. The client said “understood.” The client called again on day 10.
17
Capture confirmed. ORC scheduled update issued.
ORC
Object captured on day 17, within the planned window. A. Kowalski issued the update. The client asked if the mission was “basically done.” A. Kowalski explained that capture is the midpoint, not the conclusion. The client had read the briefing pack. The client had not retained this information.
29
Re-entry confirmed. Mission complete. ORC final report issued.
ORC
Controlled deorbit confirmed over South Pacific uninhabited zone. Final report issued. The client asked if there would be any more updates. There would not. The mission was complete. The client said they would “miss the calls.” A. Kowalski has noted this in the file without further comment.
FULL LOG: 29 ENTRIES · CLIENT-INITIATED: 22 · ORC-INITIATED: 7 · CALLS WITH NEW INFORMATION: 7
01 / THE OFFICIAL ACCOUNTCLEARED

ORC-V1 “Maud” completed a standard LEO retrieval at 584 km for a European commercial operator. The mission proceeded within normal parameters. Rendezvous was achieved on day 9. Capture was completed on day 17. Controlled deorbit was confirmed on day 29 over the South Pacific uninhabited zone. Documentation was issued within 14 working days. The mission is considered complete and successful.

The mission itself was routine. Maud performed well. The object was where it was supposed to be. The capture was clean. The deorbit was clean. From an operational standpoint, this report should be one paragraph.

From a client-management standpoint, this report requires a dedicated section, a contact log, and [REDACTED].

The client was provided with a briefing pack at mission commencement. The briefing pack contained the update schedule. The update schedule listed seven planned ORC communications across the 29-day mission. The client interpreted this schedule as [REDACTED].

A. Kowalski managed all client communications personally. A. Kowalski’s mission log, which is normally a technical document, contains the following entry on day 14: [REDACTED].

The client called on day 29, one hour before the ORC scheduled re-entry confirmation call, to ask if there was “any news.” There was. A. Kowalski asked if they could call back in an hour. They could not wait an hour. A. Kowalski told them the re-entry had been confirmed. The client asked how we knew so quickly. We explained that we had been watching. [REDACTED].

The client sent a thank-you letter after mission completion. The letter was warm and appreciative. The letter noted that they had “felt very informed throughout.” We have filed it. The client has been offered a pre-mission briefing call for future engagements, during which we will discuss the update schedule in more detail. They have accepted.

03 / MISSION STATISTICSVERIFIED
Service tierS-01 Standard Retrieval
VehicleORC-V1 “Maud”
AltitudeLEO · 584 km
Mission duration29 days
Planned client updates7
Actual client contacts29 (one per mission day)
Client-initiated calls22
Calls containing new information7 (all ORC-initiated)
Times A. Kowalski explained the update schedule4
Times client acknowledged the update schedule4
Times client then called anyway22
Re-entry confirmedDay 29 · South Pacific uninhabited zone
Client satisfactionHigh. Very high. They felt “very informed.”
  • The briefing pack update schedule will be amended to include a note explaining that the listed updates are the complete planned communication schedule, and that additional calls are welcome at mission milestones but may not result in additional information. We are aware this note will not work. We are adding it anyway.
  • A. Kowalski’s handling of 29 days of daily client contact, while maintaining full mission controller responsibilities for an active GEO operation running in parallel, is noted. A. Kowalski was nominated for Employee of the Quarter. T. Davies won Employee of the Quarter. A. Kowalski has been informed that the nomination was made. A. Kowalski has not responded.
  • The client’s comment that they “felt very informed throughout” is the intended outcome of our client communications policy, achieved here at approximately three times the planned resource cost. We are reviewing whether this is a communications policy problem or a briefing pack problem. It may be neither. It may simply be this client.
  • The client has booked a second mission. A. Kowalski has been assigned a different account for that period. This was a scheduling decision. It was also, we acknowledge, slightly more than a scheduling decision.
CLIENT NOTE ORC provides named operations leads and direct contact during active missions. We remain available throughout. We also have an update schedule. Both things are true. Contact us to discuss communication preferences before mission commencement. We recommend this.
END OF REPORT · ORC-2024-177 · ORS/L/2011/0042 · A. KOWALSKI: NOMINATED · MISSION: COMPLETE · CLIENT: SATISFIED

Similar Posts