Spaceflight looks like a story about rockets, but anyone who has spent time around a flight control room will tell you it is mostly a story about people staying awake. A spacecraft does not pause at night. Somebody has to watch the telemetry at the quietest hour, somebody has to make the call nobody wants to make, and somebody has to explain it all to the next person coming in. The way space programmes spread that burden, through rotating mission control shifts, is one of the most useful and least glamorous ideas in the whole field.
This explainer follows a made-up junior controller, Ines, through her first season on a small satellite operations team. Her story is invented, but anybody who has stood a watch will recognise the pattern.
The night shift nobody asked for
When Ines joined, the team had an unwritten arrangement. Two veterans, Tomas and Wen, covered the overnight passes because they had always done it. Nobody had voted on it. The newcomers were happy to keep their evenings, and the veterans were too proud, or too tired, to complain. For a while it worked, which is exactly why it was dangerous.
Spaceflight history is full of examples where crews and controllers were organised in named teams that took turns at the console. During the Apollo era, flight directors led colour-coded shifts that handed the mission to each other around the clock. The arrangement was not a courtesy. It existed because tired people make poor decisions, and because a mission that depends on one exhausted expert is a mission with a quiet crack running through it.
On Ines’s team the crack showed up as a small thing. Wen stopped logging the odd behaviour of one ground station because he assumed everyone knew. Tomas stopped explaining why he preferred a certain antenna for a certain pass. The knowledge was real, but it lived in two heads, and both heads were running on too little sleep.
Why the hard shifts matter more than they look
Think about how orbits shape a day of work. A satellite in low orbit sweeps past a ground station in a short window and then disappears over the horizon, so the team must be sharp during each contact and then wait for the following contact. For a plain refresher on that rhythm, the newcomer guide to low Earth orbit here covers how quickly those passes come and go. A geostationary satellite, by contrast, hangs above the same patch of Earth, and the simple geostationary orbit primer explains why its operators live with a very different, slower kind of vigilance.
Both patterns have one thing in common. The hardest moments are rarely the busy ones. They are the odd-hour anomalies, the ambiguous reading at the end of a long watch, the decision that must be made before the next person arrives. When the same two people always carry those moments, three things happen at once.
- They tire. Fatigue is not a character flaw, and it is the single most predictable cause of avoidable mistakes in any watch-keeping job.
- They become indispensable. The team starts to route every difficult question to them, which makes the rest of the team slower to learn.
- They become a risk. If either one moves on, falls ill or simply takes a holiday, the team discovers how much it never wrote down.
What a fair rotation actually looks like
Ines raised the issue gently, in the way a newcomer does. She asked whether she could shadow an overnight pass. Tomas shrugged and said yes. Within days she had asked the follow-up question that changed the team: why was she shadowing instead of running it?
The team’s lead, Rohan, took the question seriously. Over the next few weeks they built a rotation, and the details are worth copying because they are simple.
- Everyone takes every slot. The overnight pass, the weekend contact and the end-of-month reconfiguration all go into the same pool. Seniority earns you a say in how the pool is run, not an exemption from it.
- Pair first, then solo. A newcomer takes a slot beside someone experienced, then runs it with the veteran reachable, then runs it alone. Nobody is thrown into the dark console without a lantern.
- Write the handover while it is fresh. At the end of each watch the controller leaves a short note on what happened, what looked strange and what they would check first next time. The note is for the person who takes the console next, so it is written in plain words.
- Make the schedule public. A rota pinned where everyone can see it removes the quiet resentment that builds when favours are hidden. People can swap, but swaps are visible.
- Protect recovery. After a hard slot, the next day is lighter. A rotation that ignores rest simply moves the burnout around.
The first month was untidy. Ines fumbled a pass, a swap request landed on the wrong week, and Wen admitted he missed the quiet of owning the night. But something else started to appear in the notes. Ines described a ground-station quirk in language a beginner could follow, and Wen, reading it, realised he had never actually explained it to anyone. The rotation was spreading load, and it was also pulling hidden knowledge out into the open.
The same pattern on the ground, in the cloud
Everything above applies to the people who keep software services alive, which is why it is worth a short detour. Teams that run websites, data platforms and cloud infrastructure use the same idea and call it an on-call rotation. The pager is passed around so that the unpleasant hours, and the learning that comes with them, do not settle on one or two shoulders. A DevOps and cloud operations consulting and support company such as DevOpsSupport, which offers consulting, support and training for startups and larger teams, helps organisations set up that kind of fair rotation so the knowledge stays spread out.
Back in the control room, the principle stays put. A rota also gives a team something to point at when a new hire asks how things are done: the answer is on the wall, not in somebody’s memory. It gives managers an honest picture of who is stretched and who has capacity, and it gives quieter people a legitimate way to ask for the harder slots without having to argue for them. Whether the machine is a satellite or a service, the person on watch is only as good as the notes left by the last one and the practice they have had before tonight.
Common objections, answered plainly
“Our veterans are simply better at it.” Probably true today, and a rotation is how that stops being true tomorrow. You are not asking veterans to be worse for a night. You are asking them to coach while the newcomer drives.
“It will slow us down.” For a few weeks, yes. After that, the team has more people who can act confidently at three in the morning, and the veterans finally get uninterrupted sleep, which pays for itself in better judgement.
“Some people prefer nights.” Fine. Let them volunteer for extra slots, but keep the rota open to everyone, so the preference is a choice instead of a default.
A starter plan for a small team
If you run, or are about to join, a small operations team of any kind, here is a plain way to start. List every duty that people quietly avoid. Put each on a shared sheet with a name and a date. Agree a rule for swaps. Add a short handover note to every slot. Review after a month and ask one question: who learned something this month who would not have learned it otherwise?
Ines is now the person who trains the next newcomer. Tomas sleeps through most nights and, to his own surprise, enjoys the weekend shifts he once resented. Rohan’s rota is still pinned by the door. Nothing in it is clever, and the plainness is what makes it hold. The best defence against exhaustion in space, as on the ground, is a team that shares its hardest hours on purpose.