> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/adding-questions-and-content/question-reference/date-and-time.md). # Date & time A date picker with the option of specifying time. The **Date and Time** component is used when specifying time is important as well as the date. Setting meeting times or otherwise establishing timeframes for availability are common use cases. The answer to a date question is stored as [Formsort subtype](/response-data-collection-and-management/variable-schema.md#subtypes) *datetime* and are always formatted as [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601). ## **Limiting answers to a specific timeframe** You can force the responder to pick dates in the future or in the past by enabling the **Only allow times in the past?** or **Only allow times in the future?** options. This way, you can ensure that responders do not accidentally schedule a meeting for a time in the past, or specify a past event as some time in the future. Additionally, you can set a range of dates and times by enabling **Min date** and **Max date**, which can help ensure users set meetings during available hours. ## Date picker styling options The date and time menu is rendered from the native date time input of the responder's browser. Currently, there is no dropdown version. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.formsort.com/adding-questions-and-content/question-reference/date-and-time.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.