Spaces

Hand-over notes for space organisation staff: press, security, contracts

These hand-over notes show what an AI agent should write for staff when it passes a space organisation chat to a person. They give the who, what and how urgent, in a few lines.

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

Before you start

When your agent passes a chat to a person, the person should be able to act in ten seconds. The press office should know who wrote, what they want and when. The security team should know whether it is urgent. A good note makes the difference between a quick, calm reply and a scramble through a long thread.

Fill in the three boxes with a real example, then copy the note that matches the team. Use the same shape every time, so staff learn where to look. Notes should be factual, short and free of opinion. They should also say what the agent has and has not told the sender.

To the press office

Press request for [business]: [sender] asked for [request]. Their deadline is [deadline]. I told them the press office would reply and I did not comment on the matter itself.

To the security team

Security matter for [business]: [sender] reported or asked about [request]. Timing: [deadline]. I gave the urgent contact and said nothing about site arrangements. Please act on this first.

To the contracts team

Procurement query for [business]: [sender] asked about [request]. They need an answer by [deadline]. I explained the registration steps only and did not discuss any award or terms.

To the education team

Education request for [business]: [sender] asked about [request]. They would like a reply by [deadline]. I have not promised a visit, a speaker or a place. Please confirm details with them.

Technical information request

Technical request for [business]: [sender] asked for [request]. Timing: [deadline]. I shared nothing and said a colleague would reply. Please check access rules before sending anything.

What every note should say

Four things belong in every note: who wrote and how to reach them, what they asked in one line, how urgent it is, and what the agent already said. The last one matters most. Staff must know whether the sender has been promised anything.

Keep the sender's own words for anything sensitive, so nothing is lost in summary. Do not copy private details into a general channel. Send the note only to the team that needs it.

  • Start with the team and the type of request.
  • State the deadline in plain words.
  • Say what the agent did not say.
  • Link or attach the full chat for context.

FAQ

How long should a hand-over note be?

Three to five lines is enough. If the staff member must scroll, the note is too long. The full chat is always available if they want more detail.

Who should receive the note?

Only the team that owns the topic, with a back-up person named. Sending sensitive notes to a wide group risks leaks and leaves nobody feeling responsible for the reply.

What if a chat touches two teams?

Send one note to the team with the more urgent or sensitive part, and mention the second team in it. They can pass it on once they have a plan, and the sender is not repeated twice.

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.