> 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/onboarding/program-overview/interface-navigation/typical-worksession.md).

# Typical Worksession

How a typical work session flows from the Project Assistant through calculation modules to printing and saving.

A Typical Worksession

In order of occurrence, here are the steps in using the software:

1. Start the program.
2. The Project Assistant is displayed where you can choose to use the last calculation, the last project, a recent project, or create a new project.
3. A project is selected and you view the Project Manager. Here you can add new calculations, edit existing calculations, insert non-calculation items into the project (such as Excel files, Adobe Acrobat PDF files, or scanned images), and initiate project printing capabilities.
4. Editing or adding a calculation takes you to one of the calculation modules.
5. Using the calculation sheet, you enter data on the input tabs while reviewing results and graphics on the output tabs.
6. When the structural calculation is complete, you can print it and/or save it.
7. You can always return to the Project Manager where you can add/edit/delete/print other items within the current project, or save the current project and open a new one.


---

# 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/onboarding/program-overview/interface-navigation/typical-worksession.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.