> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-5.43/voyage-management-system/step-by-step-guides/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/timesheet.md).
# Timesheet
Time Not To Count List
The cargo port panel contains a list of all periods not to be counted.
Time to count can also be viewed in the table and are calculated after each new not to count period is added. They are not editable.
**Adding a new *****not to count***** period**
1. Click the create icon 
on top of the list.
2. Fill in all required fields listed below in the Add Time Not to Count window.
3. Click **Create**.
| Fields | Description |
| --------- | ---------------------------- |
| From Date | Start of not to count period |
| To Date | End of not to count period |
**Editing a *****not to count***** period**
1. Click the edit icon 
on the right side of the not to count row.
2. Change the fields in the Edit Time Not to Count window.
3. Click **Save**.
---
# 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://docs.dataloy.com/release-5.43/voyage-management-system/step-by-step-guides/laytime-calculations/maintain-laytime-calculation/manage-cargo-ports/timesheet.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.