# DateStatus

> [!NOTE]
> **Note:** This enumeration is the same for the pre-election data and election results feed types. It isn't used with officeholder feeds. In pre-election feeds, this is a required field. If the date is known and not likely to change/cancel, use `confirmed` instead of leaving blank. See the definitions for each enum value.

The following table lists the enumerations for date status in the
[`Contest`](https://developers.google.com/civics-data/reference/contest) and
[`Election`](https://developers.google.com/civics-data/reference/election) entities:

| Value | Description |
|---|---|
| `confirmed` | Used when an election is confirmed. |
| `canceled` | Used when an election is canceled. |
| `postponed` | Used when an election is postponed and no new date is set. If an election is postponed and no new date has been set, set the `ElectionDateStatus` to postponed and leave the original `StartDate` and `EndDate` in place. When a new date is confirmed, update the dates and set the `ElectionDateStatus` back to `confirmed`. |
| `tentative` | Used when an election is tentatively scheduled but at risk of being canceled. This is used to reflect that the election itself is at risk of not happening and not its date specifically. For example, a second round election contest where the date is known but it may or may not happen depending on the results of the first round, or a low probability snap election where the date may or may not be known. |
| `changing` | Used when an election is likely to happen, but the date is highly likely to change. For example, a high probability snap election whose date is being speculated or an election with other regional factors that could lead to a change in its date. |

> [!NOTE]
> **Note:** Both `tentative` and `changing` are used for elections with some level of risk of becoming `canceled`, but a `tentative` election is more likely to become `canceled` and a `changing` one is more likely to become `confirmed` once a date is finalized.