> 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/common-for-several-products/smart-assemblies/shop-drawing-configurations/schedules.md).

# Schedules

You can create any number of schedules for each Assembly.

![](/files/nCESFZPYhIanse7Wa8K6)

To add a new schedule or delete an existing one, use these buttons:

![](/files/cPtSEFyf4R5tXbVBQOle)

**Create View** - If ticked ON, the schedule will be created.

**View Number** - In Smart Assemblies it's not possible to have the same Views with the same Schedule Templates. If you try to make two same Views (schedules) have the same Schedule Templates, you get an error message like this:

![](/files/N87x9Ni3UOkzU4zgCuVk)

But if you set different View Number values for those views, then it will be OK:

![](/files/7hDgM260qpgiSqnDnt7u)

**View** - Select from three possible Schedule Types:

* **Schedule** - schedule for one Category element
* **Part List** - schedule for Multiple Categories
* **Material Takeoff** - material takeoff for Multiple Categories

**View Name** - Enter the name for the selected 

**Template Type:**

* **Schedule Instance** - Schedule from the Project Browser will be used as Schedule Template

![](/files/9ghf7JOBRG7nFPPJWJwY)

* **Schedule View Template** - ***Recommended option*** - Schedule View Template will be applied as Schedule Template.

![](/files/oCNpzI3ycaG5tNZrp2vX)

**Count Field Type** - Select if the Count parameter should show values *By Assembly Instance* or *By Assembly Type*.


---

# 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/common-for-several-products/smart-assemblies/shop-drawing-configurations/schedules.md?ask=<question>&goal=<endgoal>
```

`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.