---
title: "Set up timesheet periods and maintain related settings"
url: "https://help.altus.pro/nl/article/set-up-timesheet-periods-and-maintain-related-settings"
language: "nl"
last_updated: "2026-05-28T05:12:30.944Z"
---

# Set up timesheet periods and maintain related settings

**Timesheet Periods** define the time intervals in which users can enter and submit timesheets (e.g. weekly periods).

They are critical for controlling **time entry, approvals, and reporting**, ensuring consistency across resource and project tracking.

* * *

## Important: Permissions Required

This task is available to users with **administrative access to Settings in Altus**.

-   If you do not see the required options, you may not have sufficient permissions
-   Contact your system administrator to request access or support

* * *

## Accessing Timesheet Periods

1.  Navigate to **Settings**
2.  Locate the **Resources** section
3.  Select **Timesheet Periods**

This view displays all configured timesheet periods, including:

-   Period Name
-   Start Date
-   Finish Date
-   Timesheet Period Status (Open / Closed)

* * *

## Creating Timesheet Periods

### Create Individual Timesheet Period

1.  Select **New**
2.  Enter required details:
3.  -   **Name** (e.g. FY 2025–26 Week 1)
    -   **Start Date**
    -   **Finish Date**
4.  Set the **Timesheet Period Status**
5.  Select **Save** or **Save & Close**

* * *

### Bulk Create Timesheet Periods

Use **Bulk Create** to efficiently generate a full sequence of timesheet periods.

1.  Select **Bulk Create**
2.  Complete the required fields:

**Start Date**

-   Defines when the first timesheet period begins

**Period Duration**

-   Defines the length of each period
-   Commonly set to **1 Week(s)** for weekly timesheets

**Number of Periods**

-   Defines how many periods to generate (e.g. 52 for a full year of weekly periods)

**Sequence Seed**

-   Defines the starting number for the period sequence (e.g. 1 = Week 1)

**Name Template**

-   Defines how periods are named
-   Supports tokens such as:
-   -   `{sequence}`
    -   `{start}`
    -   `{finish}`
-   Example: `FY 2025–26 Week {sequence}`

1.  Select **Bulk Create**

This will generate a structured set of timesheet periods covering the defined timeframe.

* * *

## Opening and Closing Timesheet Periods

Timesheet periods are controlled using the **Timesheet Period Status** field.

### Closed Period

-   Prevents users from entering or submitting timesheets
-   Prevents updates to previously submitted time entries
-   **Prevents users from recalling submitted timesheets**
-   Typically used after timesheets have been reviewed and approved
-   Ensures time data is **finalised for reporting and compliance**

### Open Period

-   Allows users to enter and submit timesheets
-   Allows submitted timesheets to be **recalled (if required and permitted)**
-   Used for current and active reporting periods

* * *

## Important: Managing Period Continuity

Timesheet periods should form a **continuous, gap-free sequence**:

-   Periods must align sequentially (end date → next start date)
-   Avoid gaps or overlaps between periods
-   Deleting a period that creates a gap **may not be supported by the system**

This ensures:

-   Accurate time tracking
-   Consistent approval cycles
-   Reliable reporting and utilisation metrics

* * *

## How Timesheet Periods Are Used

Timesheet periods support:

-   **Time entry and submission cycles**
-   **Manager approvals**
-   **Resource utilisation and reporting**

Each timesheet entry is recorded against a defined period, enabling structured tracking of effort.

* * *

## Key Considerations

-   Align timesheet periods with organisational reporting cycles (e.g. weekly)
-   Ensure periods are created in advance to avoid disruption to users
-   Close periods only once approvals and corrections are complete
-   Only reopen periods under controlled governance

* * *

## Tips

-   Use **Bulk Create (e.g. 52 periods)** to establish a full year upfront
-   Apply consistent naming conventions (e.g. FY + Week number)
-   Keep at least one future period open for continuous time entry
-   Regularly review period status to align with reporting timelines