# The event page

Source: https://docs.tightly.io/help/demand/event
Reviewed: 2026-10-29

## The question this page answers

What does this event do to my forecast, on which variants and channels, when, is it moving demand yet, and did what sold match what I said it would?

## What you see

::: shot page
:::

Events, at the top, returns to the list. The head is the event's name with its status word as a badge, Ongoing, Scheduled, Completed or Unpublished, and From a suggestion beside it where Tightly proposed it. Under it the figure row: Runs; Day of the run on an Ongoing event, or Starts in (Starts Today on the day) on a Scheduled one; the channels it runs on, with more than two names folded into "and {n} more" and the rest on hover; Adjustment, such as 20% increase, with edits, Custom values, Custom values, none set yet, or Not set; and Baseline reading Does not learn from these days only on a window marked as a one-off. Units | Revenue switches the run chart between units and revenue.

The page is one scroll, with no tabs. A launch shows its allocation editor first: pick a product's week, split its units across variants (the SKU column) and channels with **Add allocation**, then choose **Save allocations**.

**The event's run** is one chart with Baseline forecast, Event target and Actual, the last drawn only on an event that is Ongoing or Completed, with today's seam inside the run. A day nobody recorded reads not recorded on hover, and a period still running reads not closed yet. Its head states what landed against what was targeted, or the target before anything has landed.

**Event impact** shows three compact panels: Revenue, Profit and Units. Each compares the baseline with the event target and highlights the change. Ongoing events also show Target so far and Actual so far; completed events show Actual. Return on cost is available on hover. Missing readings remain unmeasured, and an unchanged target reads No change.

**The variants** are the Demand forecasting grid scoped to this event's dates and variants, with the same period stacks, the Columns menu (where Velocity 30d and Review are switched on), Group by products, Add variants, Export CSV in the More menu, and a footer counting its lines. Each line shows its variant and channel under the name. A cell typed over reads edited by hand on hover; a cell under another event reads Locked by {name}, with Open the event on its menu. The grid is read-only while the event is Unpublished or Completed, or grouped by products.

## What to do

A launch with daily allocations is edited through the dated account-launch editor. The event’s weekly allocation controls do not overwrite that saved daily profile. Review the exact account, dates and quantities there, save, then return to the event to read the result.

1. On an Unpublished draft, press **Publish**; on a draft whose dates have passed, press **Edit and publish** instead.
2. Press **Unpublish** on an Ongoing or Scheduled event, from the head's menu.
3. Press **Edit** to open the drawer; on a published event only the name, the one-off mark and a percentage move are open, and on an unpublished one the whole form is open.
4. Tick **Do not learn from this window** on a marked one-off, then **Save**, or **Save and publish** where Edit and publish opened the drawer.
5. In the grid, type a planned figure into an open period, then **Save** to write the changed cells.
6. Press **Add variants** to open the drawer of variants free for these dates, or select rows and press **Remove from event** on the bulk bar.
7. Select a variant row and choose **Review forecast** to open its forecast with the event dates and channels carried through. Save or discard any unsaved event or grid changes first. Grouped rows do not open an unrelated variant.
8. Press **Delete**, from the head's menu, on any status.

Each of these prints its consequence before the button, the same sentences Events prints, such as Removes {N} variants from {name}; their forecast returns to Tightly's own figures. A moved range is checked as you type: Some variants are unavailable for these dates..., or These days have passed. Tick "Do not learn from this window" to record them. A refusal renders in the popover, verbatim, such as Cannot reactivate past events, Event is already active or Event is already cancelled. Neither Add variants nor Remove from event is offered on a Completed event, and while any write is in flight the others wait. After a write the record refetches and the head moves; nothing redirects. Delete returns you to Events, where the counts have moved.

## When it is empty or failed

> This event no longer exists.
> The event could not be read.
> The forecast series could not be read.
> The event's money could not be read.
> The lines this event touches could not be read.
> The variants free for these dates could not be read.
> No available variants for these dates.
> No variant is in this event yet.

While the record is read, the head says Reading the event. A not-found keeps you on the page with the door Events and no redirect; each read fails alone, and the rest of the page still renders from what answered.
