# Date Range Fields

Date Range fields are configured to hold start and end dates, defining the duration of an event with values like '2023-09-25 to 2023-09-30'. It's a combination of two [Date Fields](/data/collections/field-types/date.md).

They can be used with the [calendar](/views/display/calendar.md) or timeline view as the start and end dates for the events.

## Components

A Date Range field stores:

* **Start Date**: When the event or period begins
* **End Date**: When the event or period ends

Both dates can include time information depending on your configuration.

## Use Cases

Date Range fields are perfect for:

* Event scheduling (conferences, meetings, workshops)
* Project timelines and milestones
* Vacation and leave tracking
* Booking and reservation systems
* Campaign durations
* Rental periods
* Contract terms

## Integration with Views

Date Range fields work excellently with:

* [Calendar views](/views/display/calendar.md) to show events with proper start and end times
* [Timeline views](/views/display/timeline.md) for project management, scheduling and Gantt-style planning with dependencies
* Filtering to find overlapping periods or events within date ranges

## Best Practices

* Ensure end dates are after start dates through validation rules
* Consider timezone handling for multi-day events
* Use Date Range fields instead of separate start/end date fields for better data integrity
* Date ranges display more intuitively in calendar and timeline views than separate date fields
* Consider default durations for common event types (1 hour meetings, full-day events, etc.)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.noloco.io/data/collections/field-types/date-range.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.