Balerion LogoBalerion
Get started
← ManualTeam

Betriebsrat and Plan Approval

For companies with codetermination: the monthly plan is sent out only after Scheduling and the Betriebsrat have approved it.

Requirements

  • The "Plan approval with Betriebsrat" switch is on, it is off by default
  • At least two people, the dual control principle is enforced

The Betriebsrat role

Betriebsrat is a supplied role with exactly three permissions: read plans, read reports, and sign the second approval stage. Everything else is denied.

The Betriebsrat does not see payroll data. Payroll, Controlling, and Expenses deny access. What the role can see in reports is time data only, without any amounts: planned time, actual time, counted time, check-in, and check-out.

The role also cannot see employee master data, customers, inventory, invoicing, or communications to security officers.

A note that saves searching: The menu bar is not reduced for this role. The Betriebsrat sees menu items that cannot be opened. The plan view in Scheduling and Shifts, the hours report, the Analysis, and the Audit Log work for this role.

Balerion Security, Betriebsrat and Plan Approval: The Betriebsrat role
The company decides whether approval is required.

Approve in two stages

Approval always applies to a full calendar month, not an individual shift or a freely selected period. The approval status is shown as a row above the plan in Scheduling and Shifts, with one field for each visible month. There is no separate page for it.

A month moves through: open, stage 1, approved. Scheduling signs stage 1, and the Betriebsrat signs stage 2.

The same person cannot sign both stages. This is strictly enforced. The button then disappears and "Second person required" is shown. Even someone with both permissions cannot countersign their own approval.

Balerion Security, Betriebsrat and Plan Approval: Approve in two stages
The schedule is sent only after approval.

What is blocked without approval

Exactly one thing: publishing draft shifts. Planning, creating, assigning, and changing remain permitted. Security officers simply do not learn about them.

An attempt to publish without full approval is rejected and lists the affected months. Partial approval is not enough. Stage 1 alone does not release anything.

Changes after approval

Once a month has been signed, every plan change in that month requires a reason of 10 to 500 characters. The dialog appears automatically as soon as the server pauses the change, and the exact wording is logged.

The month then reverts to "changed" and must be signed again. The number of times this happens is counted.

If a change fails for technical reasons, the approval remains in place. Only a change that is actually written reverts the month.

Do not confuse it with the period close

Both operate on calendar months and both apply restrictions, but they do opposite things:

  • Plan approval acts beforehand and opens: it enables publishing. It is off by default and requires two people.
  • Period close acts afterward and closes: it seals the settled month against changes. It is always available and one person is sufficient.

They also depend on different permissions. The Betriebsrat cannot close or reopen a month and cannot see the corresponding setting at all.

Related

Updated on: 03.09.2026