> This is the Markdown of a Backed Help Centre page, https://admin.backed.giving/help/administrator/applications/field-tags-and-field-events.md. Every page is listed at https://admin.backed.giving/help/llms.txt.

> This page uses Backed's default terms, such as Funding Round and Application Template. An organisation may rename them, so read each as your organisation's own term if you've renamed it.

Field Tags and Field Events are set on a field's `Properties` in the Form Builder.

## Field tags

A Field Tag names a field so its answer can be used elsewhere. The tag's name is the personalisation
token in letters and emails and the column name in reports.

1. Open the template in the Form Builder and select the field.
2. Under its tag, choose `Select a Tag` to reuse a tag already used on other fields, or
   `Create new Tag`. A tag name uses lower-case letters, digits and underscores.
3. The field shows `Tagged as …`. Select `Remove tag` to take it off.

Save the template before you tag a new field. Table columns can carry a tag too.

A tag on an Assessment template or a Decision form template appears under `Assessment` in the
`Personalisations` menu of the emails about an Assessment (`Communicate > Email templates`). When the email is
about one Assessment, the tag fills with the Assessor's answer.

`Settings > Tags` lists every tag in use, where you can rename or delete them or write what each
one means in its `Definition`. See
[Categories and tags](../organisation/categories-and-tags.md).

A standard field's tag, such as `std_abn`, is set by Backed: it cannot be renamed, deleted, put on
another field or taken off its own, and a tag you create cannot start with `std_`.

## Field events

A Field Event shows or requires another part of the form depending on the answer given to this
field. For example, a `Yes` to "Do you have a partner organisation?" can show a section about the
partner.

1. Select the field whose answer decides, and select `Create new Event`.
2. Under `Condition`, choose `The answer equals` and the `Value`.
3. Under `Action`, choose `Show element` or `Require element`.
4. Choose the `Target`: a field, a whole section or a whole page. Only a field can be required.
5. Select `Save event`.

Each event is listed as `When the answer equals "…": … — …`. A field that depends on an event is
marked `Conditional`.

Backed refuses an event that would make a field decide, through other fields, whether it is itself
shown or required, and an exact duplicate of an existing event. Save the template before you add an
event to a new field.

### An eligibility question on the first page

Field events can turn the first page of an Application template into an eligibility check. When
the answer on the first page hides every field that asks for an answer on all the later pages, the
applicant sees only the first page: no other page in the page list, no `Next` and no `Submit`. The
answer that shows those fields again gives the pages and `Submit` back, and anything already typed
on them is kept.

1. On the first page, add a Yes/No field, for example "Is your organisation a registered charity?".
2. Add a Free Text field on the first page with your ineligibility message, and an event that shows
   it when the answer equals `No`.
3. Add events that show each later page (or each field on it) when the answer equals `Yes`.

Until the question is answered, the later pages and `Submit` stay hidden too. Backed also refuses
the submission itself while the form is in this state, so an application cannot be submitted around
it. A form with only one page never hides `Submit` this way, and the check applies to Application
templates only.

## See also

- [Form builder](form-builder.md)