---
title: The event timeline
description: What you can do before the start, during play, and after the freeze, and why it works that way.
---

An Athena event moves through three phases: **before the start**, **live play**, and **after the freeze**. Each phase opens some doors and closes others; knowing which is which saves you from staring at a countdown wondering if something is broken.

## Before the start

The event site goes up before the competition does, and that head start is deliberate: everything *administrative* is open early so that when the clock hits zero, you're solving challenges instead of filling in forms.

Open before the start:

- **Registration and login**: create your account, verify your email, set up your [profile and avatar](/players/how-to/manage-your-account).
- **Teams**: on team events, create your team or join with a handle and password. Doing this early still matters: rosters [can change](/players/reference/teams#leaving-removals-and-disbanding), but solves and points always stay with the team they were earned on, and you don't want to negotiate rosters while the clock runs.
- The **event page** itself, counting down under **Starting In**.

Gated until the start: the challenge list, individual challenges, the scoreboard, and your dashboard. Opening any of them shows the same thing, with a live countdown: *"The event hasn't started yet"* / *"This page unlocks automatically when the countdown reaches zero."* And it means it: the page unlocks itself the moment the event begins, no refresh needed. There's no early peek at challenges, which keeps the start fair. Nobody gets a reading head start on the problems.

## Live play

At zero, the gates open and everything competitive runs at once: challenges, flag submission, instances, hints, and the live standings. A few timeline-flavored things to expect while the event runs:

- **Not everything appears at once.** Organizers can release challenges in waves, so the catalog can grow mid-event and is worth re-checking even if you've "seen everything".
- **Standings move in near-real-time.** The scoreboard and leaderboard refresh themselves every few seconds.
- The event page flips to **Time Remaining**, but read it carefully: it counts down to the event's *end*, which falls some hours after the freeze. When the remaining time is down to that closing window, scoring has already stopped.

## The freeze

At the freeze time, competition ends. Submissions close for good (*"Submissions are closed."*), instances can no longer be started, and the scoreboard stops where it is: *"Standings are frozen: final rankings as of the freeze."* Because nothing can score after that moment, the frozen board **is** the final result; there's no hidden backlog of late solves waiting to be revealed.

Why a hard cutoff instead of letting things trail off? Two reasons:

1. **It makes the result trustworthy.** A single, published freeze time means every team competed against the same deadline, and the final board can't shift afterward, so there are no disputes about a solve that landed "just after".
2. **It cleanly separates competing from wrapping up.** The site stays online past the freeze, and three things open the moment it hits: **feedback**, **writeups**, and **certificates**. Writeups in particular only make sense after the freeze; you can finally show your work without handing rivals a solution.

So the freeze isn't the site shutting down; it's the event changing modes, from competition to retrospective. What to do in that phase is covered in [After the freeze](/players/how-to/after-the-freeze).

One nuance: the freeze, not the advertised end time, is when scoring stops. The end falls **after the freeze**, by however long the organizers set the wind-down, so there is a gap between the buzzer and the site going away. Treat the freeze time as the real deadline your solves must beat, and the end time as when you lose access.
