> For the complete documentation index, see [llms.txt](https://docs.ai.insly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.insly.com/nora/onboarding/fields-+-required-optional.md).

# Fields + required/optional

## What it is

The fields Nora extracts, selected from your Ledger product. We send you the full list prefilled in a field sheet (sent separately); you mark each field.

## What you decide

* Per field: **keep** or **discard** in Nora.
* Per kept field: **required** or **optional**.
* Optional: an **extraction hint** per field, e.g. “Use the year of manufacture, not the registration year.”

## What to send us

* The completed field sheet (sent separately).

## When

🔴 **ASAP** This is the core of the setup. Testing starts once it is applied.

## Why discard fields

* **Higher accuracy:** the AI keeps track of fewer fields per submission, so it confuses similar fields less often. Fewer failures on larger files.
* **Faster processing:** less to consider in extraction.
* **Less to review:** reviewers only see what matters.
* Discarded fields can still be completed in Ledger.

## What “required” does

* A missing required field blocks export.
* For emailed submissions, Nora asks the sender for it by email.

| Nora can require                                | Nora can’t require                                                                                                                       |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| A field that must always be filled              | A field that applies only when another answer is X (e.g. “bankruptcy details”, needed only when the “has been bankrupt” answer is “Yes”) |
| A value from a fixed list (dropdown)            | One of two fields where only one ever applies (e.g. Property Owners vs Project Public Liability)                                         |
| A number of list items (e.g. at least 1 driver) |                                                                                                                                          |
| A valid format (date, number, email)            |                                                                                                                                          |

A couple of examples that illustrate the issues with marking conditional fields as mandatory (also referenced in the table):

* The **“Bankruptcy details”** field under **“Has been declared bankrupt?”** will only need to be populated when that question is answered **“Yes”**. Answer **“No”** and those details will not be needed. Made mandatory, every submission would get an email asking the sender to describe a bankruptcy even if that never happened.
* Two fields where only one can ever apply. For example, if you answer **“Yes”** to **“Are you appointing a main contractor who will be in full control of the site?”** then **“Property Owners Liability”** becomes relevant, but if you answer **“No”** then **“Project Public Liability”** becomes relevant. Never both. Marking both mandatory would mean not being able to create the quote due to wrong fields blocking the export.

Conditional fields therefore stay optional. We add hints so the AI fills them whenever the source contains the answer, and your team completes the rest in review.

## Before making a field required, check where the answer comes from

| Situation                        | Recommendation                                                                                              |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| On the form and usually answered | Require it: follow-up catches anything the AI missed.                                                       |
| On the form but often left blank | Require it: follow-up collects the answer.                                                                  |
| Not on the form at all           | Usually keep it optional or discard field from Nora: otherwise every submission triggers a follow-up email. |