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