> 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/forecast-close-date.md).
# Forecast Close Date
The Forecast Close Date field is used to indicate the **anticipated** date when an Opportunity is expected to be won. It may be set by either you or the client. This might be the date when:
* Your client is expected to agree to the terms of a quotation.
* A purchase order is issued.
* A tender decision will be made.
* The client needs your product or services.
{% hint style="info" %}
**Did you know?**
You can always update the Forecast Close Date as your Opportunity progresses along its Pipeline, to reflect when you think the Opportunity will reach a successful outcome.
{% endhint %}
The Forecast Close Date can be helpful when reviewing multiple Opportunities during sales forecasting. It provides a sense of urgency for each open Opportunity to ensure they are closed on time.\
The Forecast Close Date should not be confused with an Opportunity's Create Date, Start Date or End Date. When reviewing multiple Opportunities over time, it can be helpful to compare the anticipated Forecast Close Date with the actual End Date.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.daylite.app/help/sales-guide/opportunities/forecast-close-date.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.