> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/t4r/list-of-features/data-from-schedule.md).
# Data from Schedule
**Icon:** 
**Location:** ribbon Be.Smart T4R, panel Legends
**Packages:** Be.Smart T4R Silver
### **Overview**
The Data from Schedule feature is used to automatically generate legend components for items of a schedule.
After selecting an existing schedule, it creates a set of sheets with the schedule itself and a legend for each of its items placed and organized on them.
The legends contain legend components of selected type, their basic dimensions and a Type Mark or Mark tag as a reference to the schedule.
The user can choose the types of generated legend components, their scale as well as the types of created dimensions and text annotations. It is a useful tool especially for fast creation graphical window and door schedules.
---
# 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.besmart.software/3d-modeling-and-design/t4r/list-of-features/data-from-schedule.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.