> For the complete documentation index, see [llms.txt](https://lewe.gitbook.io/teamcal-neo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lewe.gitbook.io/teamcal-neo/user-guide/calendar-month.md).

# Calendar (Month)

## Layout

The primary calendar layout in TeamCal Neo is a month. You view and edit calendars per month. The only exception is the year calendar. It is provided for overview purposes only though and cannot be edited.

## TeamCal Neo is Day-Based

As TeamCal Pro, TeamCal Neo is also a day-based calendar. This concept is one of the main success factors of the application. A day is the smallest unit you can plan in TeamCal Neo. It is not a meeting calendar in which you can schedule absences from 9 to 10 in the morning or something like that. There are several good calendar applications out there that you can use for that.

In TeamCal Neo you mark days. Nothing more, nothing less. I am emphasizing on this because I have received several change requests to offer smaller units of a day. I have always denied that because I believe in the value of a simple day-based calendar. And I think the popularity of TeamCal Pro confirms that.

## Absence Factor

Of course you can create absence types like “Half-day Vacation”. In order to get your counts right, just set the factor of that absence type to 0.5.


---

# 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://lewe.gitbook.io/teamcal-neo/user-guide/calendar-month.md?ask=<question>&goal=<endgoal>
```

`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.