> 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/sample-session/setting-up-a-project/setting-up-your-title-block.md).
# Setting up your Title Block
How to set the title block lines that print on a calculation's reports, and why they are set per module rather than once for everything.
The title block is the area at the top of a report where your own company information appears, above the Project Information block.
{% hint style="info" %}
**NOTE:** The title block here is not a single program-wide setting you configure once. You set it where you print, and it applies to reports for that module type. Setting it up for one kind of calculation does not set it for the others.
{% endhint %}
Open **Print Document** from a calculation, then expand **Project Information** in the **Sections to Include** list.
The title block fields in the Print Document window
Three toggles control what appears:
* **Show Printed Date**
* **Show Logo**
* **Show Title Block**
With **Show Title Block** on, you get six lines to customize the report with your own company information, **Title Block 1** through **Title Block 6**. The preview on the right updates as you type, so you can see exactly what will print.
At this time, please enter some information in the first few lines so you can see it printed later in this sample session.
As the panel itself says, these settings control the module you are in and automatically apply to all reports for that module 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 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/sample-session/setting-up-a-project/setting-up-your-title-block.md?ask=&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.
