> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/efr-faq/revit-model-and-workflow/does-enercalc-for-revit-require-manipulation-and-management.md).

# Analytical Model Management

Does ENERCALC for Revit© require manipulation and management of the Revit analytical model?

No. One of the driving philosophies behind ensuring ease of use is our belief that most engineers do not wish to break from their standard workflow in order to manage Revit analytical elements. Although certain aspects of the program do require that analytical elements be enabled for data storage purposes, the user does not need to manipulate geometry, intersection points, or any other aspect of the “stick model” analytical data as would be required in other Revit-connected structural software packages.


---

# 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://enercalc.com/docs/efr-faq/revit-model-and-workflow/does-enercalc-for-revit-require-manipulation-and-management.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.
