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

# Smart Fields

> How EventPilot tracks the value, confidence, and origin of every planning field — and what you can do with each one.

Every field in your event plan is a Smart Field. A Smart Field doesn't just store a value — it also tracks how confident the system is in that value and where the value came from. This gives you a clear picture of what's been decided, what's been suggested, and what still needs attention.

## Confidence levels

Each Smart Field has one of five confidence levels. The level determines how the field looks and how it behaves.

| Level                 | What it means                                | Visual appearance            |
| --------------------- | -------------------------------------------- | ---------------------------- |
| **Empty**             | No value has been set yet                    | Blank, muted placeholder     |
| **Inferred — low**    | AI extracted a value, but with low certainty | Gray chip indicator          |
| **Inferred — medium** | AI extracted a value with moderate certainty | Amber/yellow chip indicator  |
| **Inferred — high**   | AI extracted a value with high certainty     | Stronger amber indicator     |
| **Confirmed**         | You have explicitly accepted this value      | Solid green display, no chip |

<Note>
  Only you can move a field to `confirmed`. The AI never marks fields as confirmed, regardless of how certain it is.
</Note>

Inferred fields — at any confidence level — are proposals. They show up in your form so you can review them, but they don't carry the same weight as a confirmed decision until you say so.

## Provenance: where values come from

Every Smart Field shows where its current value originated. You can see this by hovering over the field. Provenance sources include:

* **AI extraction** — the value was pulled from something you said in the chat
* **User edit** — you typed the value directly into the field
* **User confirmation** — you confirmed an AI-suggested value as-is
* **Re-opened** — a previously confirmed field was re-opened for re-evaluation

Provenance helps you quickly audit your event plan and understand which values reflect deliberate decisions versus AI inferences still awaiting review.

## Actions on each field

Every Smart Field with a value shows a set of action buttons. The available actions depend on the field's current state.

<AccordionGroup>
  <Accordion title="Confirm">
    Marks the value as your accepted decision. The field moves to confirmed status, your decision is saved permanently, and the value becomes protected from AI overwrites going forward.

    Use **Confirm** when the value is correct and you're ready to lock it in.
  </Accordion>

  <Accordion title="Reject">
    Clears the field entirely, removing the current value and resetting it to `empty`. The AI may re-suggest a value in a later turn if relevant information comes up in conversation.

    Use **Reject** when the value is wrong and you don't yet know the correct answer.
  </Accordion>

  <Accordion title="Decide Later">
    Moves the field to your **Open Decisions** list without clearing the suggested value. The field is flagged as postponed so you can come back to it.

    Use **Decide Later** when the value needs more thought, a stakeholder decision, or external information before you can confirm it.
  </Accordion>

  <Accordion title="Re-open">
    Available on confirmed fields. Converts the field back to an inferred state so you can revise the value. The previous confirmation remains in the audit trail, but the field is no longer locked.

    Use **Re-open** when circumstances change and a confirmed decision needs to be revisited.
  </Accordion>
</AccordionGroup>

## Conflict detection

If the AI extracts new information that would change a field you've already confirmed, it does not overwrite your answer. Instead, the new suggestion appears as an **alternative value** on the field, alongside your confirmed value.

You'll see a conflict indicator on the field with two choices:

* **Keep** — dismiss the alternative and retain your confirmed value
* **Switch** — replace your confirmed value with the AI's suggestion, which then becomes the new confirmed value

This means your confirmed decisions are never silently replaced. The AI surfaces new information for you to evaluate; you decide what to do with it.

<Warning>
  Alternatives on confirmed fields require an explicit action from you. They don't resolve on their own and remain visible until you keep or switch.
</Warning>

## Confirmation history

Every time you confirm a field, EventPilot permanently records that decision. This history is cumulative — past confirmations are never deleted, and you can always see the full sequence of decisions made on an event.

Key properties:

* **Permanent records** — confirmations are stored and cannot be altered after the fact
* **Most recent wins** — if you re-open and re-confirm a field, the new confirmation is the effective value; previous confirmations remain in the history
* **Human-only** — only your explicit actions create confirmation records; the AI never writes to this history

You can view the full confirmation history for any event, giving you a complete record of every decision made and when it was made.

<Tip>
  Confirmation history is especially useful for events with multiple stakeholders or long planning timelines, where it's important to know who decided what and when.
</Tip>