> ## Documentation Index
> Fetch the complete documentation index at: https://docs.terminus.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Part 3: Static picklists

> Build the Goals picklist with its three options and the Goal dropdown field that uses it.

In this part you build the `Goals` picklist, with the codes `awareness`, `consideration`, and `conversion`, and the `Goal` dropdown field that offers them. It takes four short steps. The code you set here is what Part 6 puts into the UTM Campaign.

You need the `Marketing` governance model from [Part 2: Fields basics](/tutorial/02-fields-basics).

## How it works

A picklist is a named list of options. You define it once on the governance model, then point any number of dropdown fields at it. Every dropdown field needs a picklist. Later parts add four more dropdowns: `Country`, `Region`, `UTM Medium`, and `UTM Source`.

Each option has two parts:

* **Code**: the value stored in records and read by computed fields. It is 1 to 100 characters. Use lowercase with no spaces.
* **Label**: the text people read next to the code.

For `Goals`, the code `awareness` has the label `Awareness`. Form and Grid mode list options by label, Quick mode shows each option's code on a button, and the record always stores the code. The order you enter the options is the order they appear.

A static picklist is one you fill in by hand. This part uses only static picklists. For options that come from another taxonomy's records, see the [automated picklist recipe](/recipes/automated-picklist).

## Steps

<Steps>
  <Step title="Open the new-picklist flow">
    With `Marketing` open, click **Picklists** in the sidebar. Click **Create new**, then choose **Static Picklist**.

    The editor opens as a grid with **Code** and **Label** columns. A single column header above them reads `Name`.
  </Step>

  <Step title="Name it Goals">
    The column header is the picklist's name. Hover `Name` to see its tooltip, **Rename level**. Click it, type `Goals`, and press Enter.

    Leave the picklist as a single level. You add levels in Part 4.

    Picklist names are unique within a governance model, so you cannot have two `Goals` on `Marketing`.
  </Step>

  <Step title="Add the three options">
    Type each option into its own row, the code first and then the label. The grid always keeps an empty row at the bottom for the next option.

    | Code | Label |
    | - | - |
    | `awareness` | Awareness |
    | `consideration` | Consideration |
    | `conversion` | Conversion |

    Click **Save**. `Goals` now appears in the **Picklists** list, marked `3 options`.

    A code can appear only once in a list, and a list needs at least one option before it will save.

    <Warning>
      Choose codes carefully, because records store them. If you later change `awareness` to `awareness_v2`, records created earlier still hold the old code, which no longer exists in the list. Labels are safe to edit. Codes are not.
    </Warning>
  </Step>

  <Step title="Create the Goal Dropdown field">
    Click **Fields** in the sidebar, then **Create new**, and pick **Dropdown**. Set **Name** to `Goal`. In **Picklist**, select `Goals`. Click **Save to draft**.

    The `Goal` field appears in the field list next to the three fields from Part 2.

    Once records exist, do not point `Goal` at a different picklist. Records can end up holding options the new list does not contain. To change the choices, add options to `Goals` instead.
  </Step>
</Steps>

## Check your work

* The `Goals` picklist exists on `Marketing` with three options: `awareness` / Awareness, `consideration` / Consideration, `conversion` / Conversion.
* The `Goal` field exists, is a Dropdown, and uses the `Goals` picklist.
* `Marketing` now has four fields: `Campaign Name`, `Launch Date`, `Destination URL`, and `Goal`.

## Next up

You have the `Goals` picklist and the `Goal` dropdown. In [Part 4: Hierarchical picklists](/tutorial/04-hierarchical-picklists), you build `Countries` and `Regions`, so that picking a country narrows the region dropdown. For more on picklists, see the [picklists reference](/reference/picklists) and the [static picklist reference](/reference/picklists/static).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.