> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/configuration/report-time-zone.md).

# Report time zone

Choose the time zone used for the times printed in reports and exports

Reports and exports are generated by the server, not by your browser, so their times cannot follow your screen. They are printed in the instance's **report time zone**, which is **UTC** by default. If a time in a report looks one or two hours off from the same time on screen, the report time zone is most likely still UTC.

## Change the report time zone

Changing it requires the permission to change global settings.

1. Go to **Extra → Settings** and open the **General** tab.
2. Open the **Date format** section.
3. Under **Report time zone**, pick your region, for example `Europe/Paris`. Regions are listed from west to east, each with its current UTC offset.
4. Save.

The new zone applies to every report generated afterwards. A report already downloaded keeps the times and the zone printed in it.

## How times are printed

Every time carries its own UTC offset:

| Report time zone   | A time printed in a report        |
| ------------------ | --------------------------------- |
| `UTC` (default)    | `2026-07-14 06:30:00 (UTC)`       |
| `Europe/Paris`     | `2026-07-14 08:30:00 (UTC+02:00)` |
| `Asia/Kolkata`     | `2026-07-14 12:00:00 (UTC+05:30)` |
| `America/New_York` | `2026-07-14 02:30:00 (UTC-04:00)` |

Each report also states its zone at the top:

```
Generated at   2026-10-23 09:58:11 (UTC+02:00)
Time zone      Europe/Paris - each time shows its UTC offset
```

{% hint style="info" %}
The offset is worked out for each time, because it changes with daylight saving time: in Paris, a time in July shows `(UTC+02:00)` and a time in December shows `(UTC+01:00)`. On the night clocks go back, the same local time can appear twice with two different offsets, for example `02:30:00 (UTC+02:00)` then `02:30:00 (UTC+01:00)`. Both are correct and one hour apart.
{% endhint %}

## What follows the report time zone

* The PDF reports: audit report, attestation, action plan, findings report, incident report and risk report.
* The Markdown exports of incidents and findings assessments.
* The Word audit report.
* The publication and generation dates of policy document PDFs.
* The creation time of each finding in the findings Excel export.

## What does not change

* **Times on screen** keep following your browser.
* **Calendar dates** such as due dates and ETAs are printed as they are, without any conversion.
* **The API and the CSV exports** keep their times in UTC.
* **Your personal date format** only controls how dates are laid out on screen. See [Date format](/ciso-assistant/configuration/date-format.md).

{% hint style="warning" %}
**Custom Word templates.** In a [custom template](/ciso-assistant/configuration/settings/custom-templates.md), `{{ date }}` is the report date in the report time zone, and `{{ generated_at }}` now reads `2026-10-23 09:58:11 (UTC+02:00)` instead of ending with `UTC`. Check templates that display it.
{% endhint %}

## Renamed regions

Only current region names are offered. If your instance already stores a region that has since been renamed, such as `Europe/Kiev` (now `Europe/Kyiv`), it is kept, still shown in the list and still used; pick the new name whenever convenient.


---

# 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://intuitem.gitbook.io/ciso-assistant/configuration/report-time-zone.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.