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

# Files, Dates & Locations

> Entities that handle uploads, date selection, and location-based inputs

These entities cover inputs that go beyond simple text and numbers. Use them to collect documents, schedule dates, and capture addresses or property details. They are especially useful for financial services where validated data is critical.

***

## File Upload

<CardGroup cols={2}>
  <Card title="File Upload" icon="upload">
    **When to use:** Collect documents, photos, or ID scans\
    **What users see:** A secure upload field with size and type checks
  </Card>
</CardGroup>

**Tips:**

* Tell users what file types you accept (e.g. PDF, JPG)
* Keep size limits clear up front
* Allow users to remove and replace files easily

***

## Date Picker

<CardGroup cols={2}>
  <Card title="Date Picker" icon="calendar-days">
    **When to use:** Birth dates, policy start dates, appointments\
    **What users see:** A calendar interface with optional restrictions
  </Card>
</CardGroup>

**Tips:**

* Use for clear, single dates — avoid long multi-date selections
* Add limits if needed (e.g. minimum age, max booking window)
* Keep formats consistent across your flows

***

## Address & Location

<CardGroup cols={2}>
  <Card title="Address" icon="map-pin">
    **When to use:** Collecting validated Danish addresses\
    **What users see:** Real-time suggestions as they type, powered by RTB
  </Card>

  <Card title="Household House" icon="house">
    **When to use:** Mortgage, insurance, or property flows\
    **What users see:** A structured form for property value, ownership, and loans
  </Card>
</CardGroup>

**Tips:**

* RTB-powered lookups ensure addresses are accurate and reduce manual typing
* Use Household House only when you need detailed property data
* Combine with Choice or Amount entities for financial scenarios

***

## Best Practices

* **Be clear:** Tell users exactly what you need (file type, date range, address format)
* **Validate gently:** Prevent obvious errors but don’t overwhelm with restrictions
* **Keep it relevant:** Only show these fields when they’re truly needed
* **Mobile friendly:** Make sure uploads, calendars, and address inputs work well on small screens

***

## Example Recipes

**Insurance application**\
Message → Date Picker (Birth date) → Address → File Upload (Documents)

**Mortgage application**\
Message → Household House (Property details) → Amount (Loan) → File Upload (Supporting docs)

***

## Related Pages

* [Collecting Information](/features/collecting-information)
* [Choices & Decisions](/features/choices-decisions)
* [Communication & Display](/features/communication-display)