March 2026 update

Task schedule update

We’ve revised and updated the Task schedule. Here’s what’s new:

Design

We’ve aligned the Task schedule with the VOLAGIC design. The font used in the tool is now also used in the Task schedule. As the font is quite narrow, more information can fit into less space.

Display of Helper names

To minimise the risk of individual rows becoming too tall, Helper names that no longer fit within the Task time slot are now displayed before or after it.

“Timeless” Tasks

In VOLAGIC, you can create Tasks without a specified duration. One example would be a time for dropping off cakes or similar items. These Tasks are now also displayed correctly in the Task schedule.

Extended hour display

The hour columns are no longer limited to 10 hours. They now have a minimum width, allowing you to display longer Shifts clearly. If the duration is still too long, hours are grouped into blocks of two and, for even longer periods, into blocks of three. 

Task comments

Task comments are now included for every Task. They appear below the Shift view, identified by the corresponding number shown on the Task.

Helper data

For each person listed, their phone number and date of birth are now included, provided these fields have been enabled and filled in by the organisation. These are the system-defined fields under “Helper data”. If you collect this information using custom fields, it cannot be displayed.

Different options

Wherever you can export the Task schedule, you can now choose how to export it: portrait or landscape orientation, with or without Helpers’ contact details.

Eventimport

The Event import feature has also been updated.

Import template

The import template is still available in the same place as before. The following columns have now been added to the template:

• ID
• Start date

• End date

ID

The ID groups Events together. If you want to create an Event with multiple Shifts via import, you must now identify them using an ID. The value you enter for the ID does not matter, as long as it is the same for all Shifts belonging to that Event. The ID is not displayed anywhere afterwards; it is only used during import.

Rows without an ID or with different IDs are always imported as separate Events.

Start date / End date

Enter the Shift’s start and end dates here. For an Event without Shifts, these correspond to the Event’s start and end dates. Important: if a Shift runs into the following day, make sure to set the end date accordingly. Shifts spanning multiple days CANNOT be imported. Instead, as when creating Events directly in the system, use multiple Shifts on different days.

Multi-day Events

As mentioned above, you can also import multi-day Events. To do so, create the Shifts for the required days and group them all together using the ID.