> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/sales-guide/opportunities/start-date-and-end-date.md).
# Start Date and End Date
The Start Date is the date that the Opportunity is first worked on. When used, it is automatically populated with the **creation date** of the Opportunity.
{% hint style="info" %}
**Pro Tip:**
The Start Date is is different than the Create Date.
The Start Date can be edited at any time, whereas the Create Date cannot be changed.
{% endhint %}
The Start Date and the End Date are helpful because they let you compare multiple Opportunities, so you can gauge the average period of time it takes to close those Opportunities. This is often referred to as the **Sales Cycle**.
The End Date field is auto-populated when the status of an Opportunity is changed from **Open** to **Won**. It is not auto-populated when the status is changed to Lost, Abandoned or Suspended.
The End Date can be added manually, or changed at any time thereafter.
The Start and End Date fields are not automatically shown in a New Opportunity card. You will need to select them as standard fields by navigating to **Settings > Edit Cards > Opportunities** and checking the Start Date and End Date boxes. Once you have done this it is possible to see the Start Date and the End Date on every Opportunity card.
---
# 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.daylite.app/help/sales-guide/opportunities/start-date-and-end-date.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.
