> ## 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.

# Confirm Fields

> Understand how to lock in planning decisions, defer open questions, and resolve conflicts when the AI suggests a different value.

## Why confirmation matters

Every field in the EventPilot smart form exists in one of three states:

| State         | Meaning                                                    |
| ------------- | ---------------------------------------------------------- |
| **Empty**     | No data has been provided yet                              |
| **Inferred**  | The AI has suggested a value, but you haven't validated it |
| **Confirmed** | You have approved the value — it is locked and protected   |

**Confirmed fields cannot be overwritten by the AI.** This is a core principle of EventPilot: the AI proposes, you decide. Once you confirm a value, it remains exactly as you set it unless you explicitly reopen it.

<Note>
  Inferred fields are color-coded to show confidence level: green for high confidence, amber for medium, and gray for low. Confirmed fields display with a solid, stable style.
</Note>

***

## How to confirm a field

<Steps>
  <Step title="Review the inferred value">
    When the AI fills in a field from your conversation, the field displays the suggested value with a confidence indicator and a provenance note (e.g., "Extracted from message").
  </Step>

  <Step title="Click Confirm">
    Click the **Confirm** button on the field. The field status changes to confirmed, the value is locked, and your decision is saved to your confirmation history.
  </Step>
</Steps>

You can also confirm a value you typed manually. Edit the field, then click Confirm to lock it.

***

## How to reject a field value

If the AI inferred the wrong value, click **Reject** on the field. This clears the value entirely and returns the field to an empty state — ready for you to provide the correct information, either by telling the AI in chat or editing the field directly.

***

## How to defer a decision

If you're not ready to commit to a value, click **Decide Later**. This moves the field to the **Open Decisions** list in the smart form's Open Decisions section.

<Tip>
  Use Decide Later to keep your planning moving without getting blocked on uncertain details. You can review and resolve all deferred items at once when you're ready.
</Tip>

Deferred items appear in the Open Decisions section with the field name and the last suggested value (if any). To resolve a deferred decision, navigate to Open Decisions, review the item, and confirm or reject the value.

***

## How to re-open a confirmed field

Circumstances change. If you need to revise a decision you've already confirmed:

<Steps>
  <Step title="Find the confirmed field">
    Locate the field in the smart form. Confirmed fields have a distinct visual treatment that sets them apart from inferred fields.
  </Step>

  <Step title="Click Re-open">
    Click the **Re-open** button on the confirmed field. The field reverts to an inferred state, making it editable and allowing the AI to propose updates again.
  </Step>

  <Step title="Update and re-confirm">
    Edit the value or let the AI suggest a new one, then confirm again when ready.
  </Step>
</Steps>

***

## Conflict resolution

If you've confirmed a field and the AI later receives information that contradicts it, EventPilot **does not silently overwrite your decision**. Instead, you see a **conflict warning** on that field.

The conflict warning shows:

* Your confirmed (locked) value
* The AI's new suggested alternative

You then choose one of two actions:

<CardGroup cols={2}>
  <Card title="Keep" icon="shield" href="#keep">
    Dismiss the AI's suggestion and retain your original confirmed value. The conflict is resolved in your favor.
  </Card>

  <Card title="Switch" icon="rotate" href="#switch">
    Accept the AI's new suggestion. The field is updated to the new value and re-confirmed with a new confirmation record.
  </Card>
</CardGroup>

***

## Confirmation history

Every confirmation action is stored permanently. This means:

* Every confirm, re-open, and conflict resolution is recorded with a timestamp
* The full history of a field's decisions is always available
* No confirmation can be retroactively deleted or altered

<Note>
  EventPilot's confirmation history is designed for accountability in professional event planning — you always have a complete record of who decided what and when.
</Note>
