Spaces

Delay and change notices for exchange members and data users

These notices help an exchange tell members, issuers and data users about a delay, a schedule change or an unavailable service. They share what is known, point to the status page and avoid guessing at causes.

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

Before you start

Delays at an exchange are noticed fast and talked about. A late statement, a moved cut-off or a data feed that is down will bring a wave of messages. The best response is calm, accurate and consistent, with one place people can check for updates.

Fill in what has changed, the new time if you have one, and where updates are posted. Copy the notice that fits. Send these only to people who have written to you about the matter or who asked to be told. Public announcements go through your normal channel.

Delay with a new time

A short note from [business]: [what] is delayed and is now expected [new time]. We are sorry for the change. Any further update will be posted on [status page].

Delay with no time yet

Hello from [business]. [what] is delayed, and we do not yet have a new time. A colleague will write to you as soon as we do. The latest public information is on [status page].

Schedule change

Please note that [what] at [business] has changed and is now [new time]. We apologise for any inconvenience. The full notice is on [status page].

Service unavailable

Hello, [what] is currently unavailable. [business] staff are working on it. We will not guess at a cause. Updates are posted on [status page], and a colleague will reply here.

Say what you know, and only that

A good notice states what is affected, what the new time is or that it is not yet known, and where to look. It does not explain the cause unless that has been cleared by the right person.

Speculation in chat can be read as fact, and it can be wrong. If the cause is under review, say that a colleague will share what can be shared, and stop there.

  • Name what is affected, plainly.
  • Give a time only when it is confirmed.
  • Point to one place for updates.

Keeping updates in step

Make sure the status page and the chat say the same thing. If they differ, people lose trust in both. Update them together.

FAQ

Should the agent explain why something is delayed?

Not unless a named person has cleared a statement for it to use. The agent should say what is affected and where updates are posted, and leave causes to staff.

Who sends these notices?

Usually your agent replies to people who wrote in, while a named person decides what the wording should be. Public announcements should go through your normal communications route.

What if the new time changes again?

Update the status page first, then the chat. A person should write to anyone who was given the earlier time, so nobody acts on out-of-date information.

More free tools for stock and commodity exchanges

Read the guide: Answer member and listing questions at an exchange.