Spaces

Launch and open-day checklist for space organisation chats

This checklist prepares a space research or technology organisation for its busiest message days, such as launches, open days and application deadlines. It keeps replies consistent and sensitive matters with people.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Space work runs on dates the public can see. A launch window, an eclipse, an anniversary or an open day sends questions pouring in about timing, tickets, travel and viewing spots. The same questions arrive again and again, often within hours, which is exactly when a ready answer is worth the most.

Use this list two weeks before the date. Write the plan for a delay as well as the plan for success, because launches slip and weather closes sites. Make sure someone can change the written reference in minutes, and tell your hand-over teams the date.

Tick each one as you go. 0 of 9 done.

[ ] Write the event facts in one place: times, locations, tickets, viewing advice.
[ ] Prepare a delay or scrub message and agree who may send it.
[ ] Add accessibility, parking and public transport details.
[ ] Confirm which questions go to the press office on the day.
[ ] Set safety advice for crowds, weather and restricted viewing areas.
[ ] Brief the on-duty staff and name a back-up.
[ ] Check supplier and delivery messages for the same dates.
[ ] Plan a quiet message for after the event.
[ ] Review the chats the next morning and update the reference.

Plan for the delay

The most common problem on a launch day is not too many messages but the wrong message. When a launch moves, people who are already travelling need a short, calm note that points to the live notice. Avoid explaining the cause. Technical reasons are for the mission team to state.

Prepare two or three versions in advance and keep them where the person on duty can find them. Speed matters more than detail.

Other dates to mark

Not every busy day is a launch.

  • School term starts, when visit requests arrive.
  • Placement and internship closing dates.
  • Funding call deadlines for researchers and small companies.
  • Tender notice dates for suppliers.

FAQ

How early should we brief the agent for an event?

Two weeks is a good aim for a big date, so staff can test it. For a short-notice event, even a single page with times and the delay plan helps a great deal.

Should the agent say whether a launch will go ahead?

No. It should point to your live notice and repeat only what you have published. Decisions about a launch belong to the mission team, and guesses can mislead travellers.

Can we message everyone who asked last time?

Only people who asked to be told, such as someone who requested an alert about the next open day. Messaging past enquirers who did not ask for updates is unsolicited and not allowed.

More free tools for space research and technology programs

Read the guide: Answer visitor, student and supplier questions in chat, and keep technical and security matters with your people.