Help

Help›Demand›Events

Events

Reviewed Oct 29, 2026

View as Markdown
Words
TierEvery tier
SeatAny seat reads it
WhereUnder Demand, the Events room

The question this page answers ​

Which promotions, launches and closures are moving my forecast, when do they land, and is each one moving demand yet?

What you see ​

Events on Table, marked 1 and 2.
  1. New event, the page's one act.
  2. Table or Calendar, the status and channel filters, and search.

An event is a dated adjustment to the forecast on a set of variants across chosen channels: a percentage up or down, custom values typed per period, or a launch planned in units per product per week. Published, it moves the forecast from its start date; unpublished, it moves nothing. A variant can sit in only one event on a channel over any given days. Events is under Demand on the rail of every plan.

The head has New event. On Table, Events on this page plots the current filtered page’s dated events above its rows. Shapes and labels distinguish promotions, launches and custom events; hover or focus reads the native window, status, channels and adjustment. Select an event to open its record. This is the current page of up to 25 events, not the whole calendar.

Table | Calendar switches the view, beside the filters Any status and Any sales channel, a search on the event name in the table, and Clear filters once any is set. The table: Event, Status, Runs, Channels and Adjustment, with Variants in the column chooser, 25 rows a page, with a footer such as 1 to 14 of 14. The Status cell is a badge, and its hover or keyboard focus carries the one thing more there is to say: expired on an Unpublished draft whose dates have passed, day {n} of {m} on an Ongoing run, not learned from on a window marked as a one-off. Adjustment reads the figure, such as +20% or −18%, with the words on hover ({n}% increase or decrease, with edits where a figure was typed over it); Custom values; {N} units on a launch; No values yet where a custom event has nothing typed; No launch units yet on a launch nobody has typed units into; or Not set. A launch prints units and never a percentage, because a launch adds its own line to the plan rather than scaling the baseline, and its window is never learnt from. The calendar is one month, seven columns, a chip per event per day it covers, in the order Ongoing, Scheduled, Completed, Unpublished, Suggested, then by name; a day with more than three chips folds the rest into +N more, a list where each row opens that chip's details beside it. A chip opens a popover with the event's status and facts and Open the event; on a suggestion, Create event is the main button and the window and event day read as two rows.

Suggested by Tightly, a second table drawn only when a live suggestion exists: Suggestion, with its event day beneath, Suggested window, Starts and Your lift last year, which reads your own measured lift on the variants that sold in those weeks, the industry range where you have no history there, or Not measured. A suggestion names two dates on purpose, the day itself and the window Tightly suggests running an event around it. Its calendar chip says:

Tightly suggests running an event {window} around {name} ({day}).

What to do ​

New event opens the page that creates one. A row opens the event. A row's menu offers Open the event on every known status; Publish on an Unpublished draft; Unpublish on Ongoing and Scheduled; and Delete on every status. Each write says its consequence before its one button:

Publishes {name}: the forecast moves from {date} on its {N} variants. Unpublishing reverts the forecast to Tightly's own figures, keeps the {n}% increase so it can be reapplied later, and discards custom values typed over it. Deletes {name} and reverts every demand change made during it. Deletes {name}. This cannot be undone.

On a draft whose dates have passed, Publish carries its reason in ink instead:

Expired events can't be published.

The writes need a seat that can write. A refused write renders the server's sentence in the same popover, such as Cannot reactivate past events, Event is already active or Event is already cancelled; after any write the counts move, and nothing redirects. On a suggestion, Create event opens New event with the name, the window, your lift and the variants it measured filled; Ignore removes the row. An expired suggestion cannot be created:

Expired events can't be created.

When it is empty or failed ​

No events on your calendar. No events match these filters. Events could not be read. Suggestions could not be read. Tightly could not reach the server.

A failed read offers Try again. Neither empty state draws an act of its own: New event is the head's and Clear filters is in the row above. A month with nothing draws an empty grid and no sentence. Until the first sync lands, the page is one sentence and a door to Home.