The Waiting-For List: A Quiet Career Skill in Spaceflight Work

Ask people who work around launch vehicles, satellites and ground stations why some colleagues stay calm while others scramble, and the reply is seldom raw brilliance. It is bookkeeping. The steady ones know exactly what they have asked of other people and what has not come back yet. In other words, they keep a waiting-for list, and in a field where one missing sign-off can hold a whole campaign, that habit is a genuine career skill.

Why spaceflight work stalls in the gaps

Almost nothing in this industry is done by one person. A payload engineer waits on a thermal analysis. A mission planner waits on a range slot. A technician waits on a part from a supplier, and a student applicant waits on a reply from a lab. Each handoff is small, and each is invisible once you have sent the message. That is how work stalls without anyone deciding to stall it: the request leaves your hands, you move on, and three weeks later you discover nobody ever picked it up.

A waiting-for list is the cure. It is nothing more than a short running record of requests you made that someone else must answer. It is different from your own to-do list, which holds actions only you can take. The two lists answer different questions. The to-do list asks what you should do next. The waiting-for list asks what is quietly out of your hands and whether it is still moving.

What each entry needs

An entry that just says “thermal report” is useless a fortnight later. Useful entries carry four small facts, and you can fit them on one line.

  • The thing you are owed, described so a stranger could understand it.
  • Who owes it, by role or team rather than a vague “them”.
  • When you asked, so you can see how long it has really been.
  • When to nudge, a date you pick on the day you ask, based on how long the request reasonably deserves.

The nudge date does the heavy lifting. Without it the list is a graveyard of good intentions. With it, you have a daily or weekly prompt telling you which item has gone quiet long enough to deserve a polite follow-up.

A worked example from a ground-segment team

Picture a small team preparing antenna time for a satellite pass. The lead engineer needs a frequency coordination confirmation from an outside body, a firmware sign-off from the software group, and a rental quote for a mobile dish from a vendor. On Monday she writes three lines in a notebook. Each notes the owner, the date she asked, and a nudge date. The coordination reply gets a longer fuse because such approvals are slow. The vendor quote gets a short one, because it should take a day.

On Thursday the vendor line comes due. She sends a two-sentence reminder. The vendor replies within the hour, apologising for a missed email. Had she relied on memory, that quote would have drifted into the following week and the pass would have gone ahead on the wrong equipment, or not at all. The cost of the list was five minutes. The cost of not having one would have been a lost window.

Where it fits into a space career

If you are early in this field, the waiting-for list costs almost nothing and makes you look dependable. Hiring managers in aerospace talk constantly about people who “close loops”. Closing a loop simply means you noticed a request was still open and did something about it. When you are the junior person coordinating test schedules, parts and approvals, the list makes you the one who always knows where things stand.

It also trains a habit that scales. A technician who tracks six requests will later be able to track sixty as a programme coordinator. The notation barely changes; only the volume does. If you are still deciding which orbital regimes to study, read a plain walkthrough such as this beginner introduction to low Earth orbit and notice how many separate parties a single mission depends upon. Every one of those dependencies is a potential line on someone’s waiting-for list.

Setting up your own list in ten minutes

Software is optional here: a paper notebook, a plain text file or a spreadsheet all work. What matters is that it lives in one place you look at daily. Try this setup.

  1. Create two columns of headings: Owed to me and Nudge on. Add the owner and the date asked beside each item.
  2. Every time you send a request that you cannot finish yourself, add a line before you close the message window.
  3. Check the list when the morning inbox opens, or right before the team stand-up.
  4. When something arrives, strike the line and note the date. Do not delete it straight away; a week of struck lines is useful evidence of how long certain groups take.
  5. When a nudge date passes with no reply, send a short, friendly follow-up and set a new date.

Choosing sensible nudge dates

The right nudge interval depends on the request and the culture of the group you are asking. A same-team question might deserve a reminder after a day. A cross-organisation approval might sensibly wait a week. A procurement request that involves a purchasing office could take longer still, and chasing it daily would only irritate people. Over a few months your struck-through lines teach you how long different parties really need, and your nudge dates become more accurate.

For orbital work, where timing windows are rigid, work backwards from the hard date. If a test slot opens on a Friday, an approval you need cannot realistically arrive on Thursday. Set the nudge for early in the week before and treat anything later as a risk to raise with your supervisor. A concrete look at how orbit choice shapes schedules, like an easy explainer on geostationary orbit, shows why missed handoffs on the ground often cost more than the engineering itself.

Keep it polite and keep it human

A reminder is not an accusation. The most effective follow-ups restate the request in one line, mention the date it matters, and offer to help if something is blocking the reply. “Just checking whether the calibration data is on its way, since we integrate on Thursday; happy to chase the lab myself if that is easier” reads far better than “Why haven’t I heard back?” People respond to clarity and generosity, and your list gives you the facts to be clear.

It also protects relationships. When you track requests carefully you stop resenting colleagues for silences you cannot see, because you know precisely how long a reply has been outstanding and whether it has actually crossed the point of concern.

A short word on side interests

Many people who enjoy this field also wander into other planning topics. One example is a website called Propraahi, which describes itself as a property research resource for home buyers in India. It is a reminder that any long, multi-party project, whether a launch campaign or a big household purchase, depends on someone keeping track of who still owes what.

Mistakes that make the list useless

  • Recording only the big items. The small unanswered email is the one that bites you.
  • Writing “them” instead of a role. When you return later, you will not remember who you meant.
  • Skipping the date asked. Without it you cannot judge how overdue anything is.
  • Never reviewing it. A list you do not read is just a diary.
  • Letting it swell. Retire items that no longer matter and say so openly to whoever owed them.

Making it visible to your team

Think of the shared board as a courtesy to future you. When a colleague is on leave or rotates to another programme, the people covering for them can read the open requests and carry on without a long briefing.

Once your own list works, consider sharing the relevant lines. In a small crew, a shared sheet of cross-team requests with owners and nudge dates turns hallway reminders into something everyone can see. Supervisors tend to notice who maintains such a sheet, and it often becomes the quiet foundation of a coordinator role. Keep the shared version short, factual and free of blame; it should read as a status board rather than a scoreboard.

If you want a one-line version of the whole idea, it is this: whenever you hand a request to someone else, write down who has it, when you gave it to them, and when you will look again. That small ritual, repeated across a career, is what keeps launches, tests and applications moving while others wonder why things went quiet.