When a preview is overtaken by the result, how should FTC show it? Tell us what helps you most

FTC publishes previews before big events and reports after them. This week is a good example: previews for the Federal Reserve, the Bank of England and the Bank of Japan went up before their decisions, and the results were published as separate reports afterwards (Fed, Bank of England, Bank of Japan).

When a preview is overtaken by the result, how should FTC show it? Tell us what helps you most — central bank rate path diagram
A central bank's policy rate path across recent meetings

The old previews are still useful as a record of what was expected, but a reader who lands on one from a search engine after the decision can be confused. Today we handle it in a few ways: an "Update" note at the very top of the preview with a link to the result, and a title and short description that now say what happened instead of what was about to happen. We would like to know if that is enough.

Some ideas, and we would like your opinion on each:

  • a coloured banner at the top of the preview that says "This event has happened" and links to the result
  • moving the result summary above the preview text
  • marking outdated previews in the news list, or moving them out of the main list
  • leaving previews exactly as they were written, and only linking forward to the result
  • something else that you would like to see
When a preview is overtaken by the result, how should FTC show it? Tell us what helps you most — risk-reward diagram
A risk-reward ratio of 1 to 2

It would also help to know how you use previews. Do you read them after the event to compare them with what happened, or do you skip them once the decision is out? Do they help you check your own plan against what you expected?

Feedback here goes to the whole team. Please keep it about the site, and remember that posts that promise returns or sell signals will be removed.

Comments

Log in to join the discussion. Comments follow the community guidelines.

Log in to comment

Loading comments…