> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/toolkits/daily-profiles-tm.md).

# Daily Profiles™

ICT Daily Profiles

The ICT Daily Profiles by CandelaCharts rooted on the ICT teachings represent a pattern-based approach to trading that focuses on identifying and analyzing the key highs and lows of various intraday trading sessions.

These profiles provide a structured framework to understand how price action evolves across distinct periods, such as the 00:00–06:00 (Session I - Tokyo), 06:01–12:00 (Session II - London), 12:01–18:00 (Session III - NY), and 18:01–23:59 (Session IV - Syndey) sessions.

The day is divided into four main sessions to accurately identify potential highs and lows, ensuring precise probability detection.

By pinpointing the critical turning points in these sessions, traders gain insights into potential areas of liquidity, support, and resistance.


---

# 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.candelacharts.com/toolkits/daily-profiles-tm.md?ask=<question>&goal=<user_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.
