---
title: The event lifecycle
description: How an event moves from provisioning through the pre-start gate, live play, and the freeze.
---

An Athena event passes through four phases: **provisioning**, the **pre-start** window, **live play**, and the **freeze**. Each phase changes what players can do on the event site, and each transition happens on its own, driven by the schedule you set at creation. Once the event is provisioned, you never have to flip a switch.

## Provisioning

Creating an event kicks off setup of its dedicated site. You can watch this from the provisioning screen's live updates, which run from *Request received* to *Finished*, but you don't have to keep the page open; setup continues regardless. When it completes, your event has a public URL players can visit. From this moment the site is real and reachable, even though the event hasn't started.

## Before the start: onboarding is open, play is gated

The pre-start window exists so that the start of your event is playable from minute one. Players can already:

- visit the landing page, which shows a live **"Starting In"** countdown,
- register an account (and verify their email, if you required it),
- create or join teams, in team mode, including saving their team's join credentials.

What they can't do is play. The challenge list, dashboard, and scoreboard show a full-screen gate with a days/hours/minutes/seconds countdown, reading *"The event hasn't started yet"* / *"This page unlocks automatically when the countdown reaches zero."* The gate is not just cosmetic: the platform also refuses early flag submissions and instance launches outright.

Encourage players to finish account and team setup during this window; when the countdown hits zero, the gated pages unlock on their own, with no refresh needed.

## Live play

Between start and freeze, the event runs itself: challenges are visible (except those with a later [scheduled release](/organizers/how-to/release-challenges-in-waves) or unmet prerequisites), submissions flow, and the scoreboard updates live. Your job shifts to [monitoring](/organizers/how-to/monitor-a-live-event), [announcements](/organizers/how-to/announce-to-players), and [player reports](/organizers/how-to/triage-player-reports).

## The freeze

At start + duration comes the **scoreboard freeze**, the moment competition actually stops. It is terminal, with no unfreeze and no action on your side. In one stroke:

- **Submissions close.** Flag attempts are rejected with *"Submissions are closed."*
- **Instances stop launching.** Players see *"The competition is frozen; instances cannot be started."*
- **The scoreboard freezes.** It stops updating and its subtitle switches to *"Standings are frozen: final rankings as of the freeze."*

And in the same stroke, the post-event surface opens:

- **Feedback**: players rate the event 1–5 stars with optional comments; until the freeze that page says *"Feedback opens when the scoreboard freezes"*. Responses land on your dashboard's Feedback page.
- **Writeups**: each challenge page gains a **Submit writeup** button. There is one writeup per team, and uploading again replaces it. They arrive on your Writeups page.
- **Certificates**: when provided for a team, its certificate becomes available for download on the team's page.

The event's **end** time, shown to players on the landing page, falls after the wind-down you chose when creating the event (24 hours by default). Think of the freeze as when the competition ends and the wind-down as the closing window: players exchange writeups and leave feedback while the results stand still. Reviewing what came in is covered in [Export event data](/organizers/how-to/export-event-data).

## After the event ends

When the clock reaches the event's **end** (the wind-down after the freeze), the platform tears the event down on its own. Teardown follows the End time currently saved in [Event settings](/organizers/reference/event-settings), so editing **End** on a running event moves teardown with it. The check runs on a timer rather than to the second, so teardown typically begins within about ten minutes of the end time. Until it starts, the event shows as **Finished**; while it runs, **Tearing down**; afterwards, **Ended**.

:::warning[Teardown destroys the event's data, so download your files before it starts]
Teardown is not just the site going offline. It deletes the event's database and its uploaded-file storage, and the per-event dashboard becomes unreachable the moment teardown begins. Analytics, Leaderboard, and Certificates are all gone from that point.

One thing survives on your behalf: early in teardown, before the site comes down, the platform builds this event's [data export](/organizers/how-to/export-event-data), and that archive stays on **Data exports** in your organization dashboard for as long as your plan's retention allows. It carries the participants, teams, scoreboard, solves, submissions, hints, reports, certificates, integrity findings, and audit trail as data.

What it does not carry is files: challenge attachments and player writeups. Download those from the **Files** and **Writeups** pages, plus any Analytics reports you want in report form, **while the event is still running**.
:::

Once teardown finishes, the event stays in your workspace events list marked **Ended**. What remains is the workspace-level record of the event, not its contents.

## Ending an event early

To stop an event before its scheduled end, open its **Settings** page and use the **Danger zone** section at the bottom. As the panel states, ending is permanent: players lose access immediately and every hosted resource for the event is removed.

The confirmation asks you to **type the event's name** before it will proceed. This is the platform's most destructive action, and it can't be undone. During provisioning the same control reads **Stop provisioning** and cancels the setup that's in flight.

Ending is also what returns credits, and it settles them on the spot. For an event that went live, the runtime you paid for and did not use comes back to your wallet the moment you end it, counted in whole hours against the end date your reservation covers, with any part-hour dropped. End an event a day into a three-day booking and roughly two days of runtime come back; let it run to its end date and nothing does, because there is no unused runtime left to return. Stop an event during provisioning and the whole reservation is released, since none of it was ever used. Either way the confirmation dialog shows the amount before you commit.

Closing an event out is two steps, and the panel says so:

1. **End the event** and wait for teardown to finish.
2. **Delete** the record from the events list once teardown has completed.

## Deleting an event

Deletion is the second step, and it only becomes available once an event has reached **Ended** or **Failed**. Trying to delete a live or provisioning event is refused with *"End this event before deleting it. Deleting now would leave its infrastructure running."*, so there is no single-click path from "running" to "gone".

Open your **workspace dashboard**, find the event in the events table, and click the **trash** button on its row. (Deletion lives here on the events list, not on the event's own dashboard pages.) Confirm the dialog, and the record is removed for good. Any [custom domains](/organizers/how-to/connect-a-custom-domain) attached to the event are freed for reuse elsewhere.

Credits are normally already settled by this point, since ending the event is what returns them, so deleting adds nothing. If anything was still outstanding (an event that reached **Failed** on its own, say), it is settled now instead, for whatever runtime is still unused by then. The entry shows up in your credit activity as *CTF credits released* or *Cancelled CTF credits returned*; see [Manage billing and credits](/organizers/how-to/manage-billing).
