Working time and calendars#

This guide shows how to tell Planning Engine when work can happen: working hours, weekdays, holidays and short days. It also covers how tasks and resources pick a calendar and how to turn calendars off.

How calendars work#

A task's Duration is working time. A 16-hour task doesn't end 16 hours after it starts. It ends once it has used 16 hours of its calendar's working time, so nights, weekends and holidays stretch it. Lags work the same way. LevelingDelay and Pauses are the exception: they're elapsed wall-clock time.

A calendar is a CalendarData: an Id plus an optional Worktime with three parts:

Hours: the working ranges of a day, as TimeRange values in minutes since midnight. Default: 08:00-12:00 and 13:00-17:00.
Days: a bool[] of exactly seven flags, index 0 is Sunday. Default: Monday to Friday.
Dates: exceptions keyed by the date's midnight Moment. A DayRule makes a date Off, On (working with the calendar's Hours) or working with its own Hours(...) ranges.

Every project has a calendar named "global". If you don't define one, the engine uses the built-in Monday-Friday, 08:00-12:00 and 13:00-17:00. A calendar in ProjectData.Calendars with the id "global" replaces it.

Which calendar a piece of work uses depends on SchedulingConfig.CalendarMode (CalendarMode):

Mode	A task works on
`Resource` (default)	each assignment's calendar: the resource's calendar, intersected with the task's own calendar when both are set
`Task`	the task's `CalendarId`, else `"global"`; resource calendars are ignored
`TaskInherited`	the task's `CalendarId`, else the nearest ancestor's, else `"global"`

SchedulingConfig.UseCalendars overrides all of this. It's true by default. Set it to false and every calendar becomes flat 24/7 time.

The engine validates calendars when you pass the data to Project.Solve(data, …) or Engine.Schedule. These cases throw an InputException with the field path in Path:

a duplicate calendar id
a calendar with no working time
an hour range outside 00:00-24:00
Days with a length other than 7
a task or resource CalendarId that names no calendar (for resources, only in Resource mode)
in Resource mode, a task calendar and a resource calendar that share no weekly working time (reported at assignments[i])

Calendars are part of the snapshot only. SchedulingChanges can't add or edit a calendar. To change one, send the full data again with Solve(data, …). Edits can still point tasks and resources at existing calendars through CalendarId.

Defining calendars#

Replace "global" to change the working week for the whole project. The calendar below works Monday to Friday, 09:00-17:00. Thursday the 13th is a short day and Friday the 14th is a holiday:

using Plen;

static Moment At(int day, int hour) =>
    Moment.FromYmdHm(2026, 8, day, hour, 0) ?? throw new InvalidOperationException("invalid date");

var global = new CalendarData
{
    Id = "global",
    Worktime = new Worktime
    {
        Hours = [new TimeRange(9 * 60, 17 * 60)],
        Days = [false, true, true, true, true, true, false], // Sun..Sat
        Dates =
        {
            // Thursday: a short day, 09:00-13:00.
            [At(13, 0)] = new DayRule.Hours([new TimeRange(9 * 60, 13 * 60)]),
            // Friday: a public holiday.
            [At(14, 0)] = new DayRule.Off(),
        },
    },
};

var data = new ProjectData
{
    Config = new SchedulingConfig { DurationUnit = TimeUnit.Hour },
    Calendars = [global],
    Tasks = [new TaskData("build") { StartDate = At(10, 9), Duration = 36 }], // Monday
};

var result = Engine.Schedule(data, new SolveOptions { IncludeUnchanged = true });
foreach (var update in result.Updates)
{
    Console.WriteLine($"{update.Id}: {update.StartDate} -> {update.EndDate}");
}

Output:

build: 2026-08-10 09:00 -> 2026-08-17 17:00

The 36 hours are Monday to Wednesday (24 h), the short Thursday (4 h) and the next Monday (8 h). The holiday and the weekend hold no work.

A property you leave as null keeps its default. new Worktime { Days = [...] } changes the weekdays and keeps the 08:00-12:00, 13:00-17:00 hours.

Date exception keys#

Worktime.Dates is a SortedDictionary<Moment, DayRule>, so each exception's key is a full Moment. Only the date part counts. Use the date's midnight as the key, as the example does with At(13, 0).

Two keys on the same day collide. A second key for a date, say 12:00 after 00:00, silently replaces the first rule, and you get no error. Build keys from dates only and you can't hit this.

Task calendars#

Set TaskData.CalendarId to run one task on a different calendar. Here the migrate task runs on a night shift, while review stays on the default "global" calendar:

using Plen;

static Moment At(int day, int hour) =>
    Moment.FromYmdHm(2026, 8, day, hour, 0) ?? throw new InvalidOperationException("invalid date");

// 22:00-06:00: the range ends before it starts, so it crosses midnight
// and belongs to the day it starts on.
var night = new CalendarData
{
    Id = "night",
    Worktime = new Worktime { Hours = [new TimeRange(22 * 60, 6 * 60)] },
};

var data = new ProjectData
{
    Config = new SchedulingConfig { DurationUnit = TimeUnit.Hour },
    Calendars = [night],
    Tasks =
    [
        new TaskData("review") { StartDate = At(10, 8), Duration = 16 },
        new TaskData("migrate") { StartDate = At(10, 22), Duration = 16, CalendarId = "night" },
    ],
};

var result = Engine.Schedule(data, new SolveOptions { IncludeUnchanged = true });
foreach (var update in result.Updates)
{
    Console.WriteLine($"{update.Id}: {update.StartDate} -> {update.EndDate}");
}

Output:

review: 2026-08-10 08:00 -> 2026-08-11 17:00
migrate: 2026-08-10 22:00 -> 2026-08-12 06:00

The night shift's days are the default Monday to Friday. Monday's shift runs until Tuesday 06:00, because a range that crosses midnight belongs to the day it starts on.

A task's own calendar (else "global") also matters in Resource mode. Milestones, lag without a link calendar and slack always use it.

Inheriting a calendar from a summary#

In Task and Resource modes a child doesn't look at its parent's calendar. Switch to CalendarMode.TaskInherited to make a task without a CalendarId use the nearest ancestor's:

using Plen;

static Moment At(int day, int hour) =>
    Moment.FromYmdHm(2026, 8, day, hour, 0) ?? throw new InvalidOperationException("invalid date");

var sixDayWeek = new CalendarData
{
    Id = "six-day",
    Worktime = new Worktime { Days = [false, true, true, true, true, true, true] },
};

var data = new ProjectData
{
    Config = new SchedulingConfig
    {
        DurationUnit = TimeUnit.Hour,
        CalendarMode = CalendarMode.TaskInherited,
    },
    Calendars = [sixDayWeek],
    Tasks =
    [
        new TaskData("phase") { TaskType = TaskType.Summary, CalendarId = "six-day" },
        new TaskData("pour") { Parent = "phase", StartDate = At(14, 8), Duration = 16 }, // Friday
    ],
};

var result = Engine.Schedule(data, new SolveOptions { IncludeUnchanged = true });
foreach (var update in result.Updates)
{
    Console.WriteLine($"{update.Id}: {update.StartDate} -> {update.EndDate}");
}

Output:

pour: 2026-08-14 08:00 -> 2026-08-15 17:00
phase: 2026-08-14 08:00 -> 2026-08-15 17:00

pour works Friday and Saturday on the summary's six-day week. With the default mode it would wait for Monday.

Resource calendars#

In the default Resource mode each assignment works on its resource's calendar, and the task's dates follow its assignments. Give a resource a calendar through ResourceData.CalendarId. The example below runs the same project in Resource and Task mode:

using Plen;

static Moment At(int day, int hour) =>
    Moment.FromYmdHm(2026, 8, day, hour, 0) ?? throw new InvalidOperationException("invalid date");

ProjectData Build(CalendarMode mode) => new()
{
    Config = new SchedulingConfig { DurationUnit = TimeUnit.Hour, CalendarMode = mode },
    Calendars =
    [
        new CalendarData
        {
            Id = "tue-sat",
            Worktime = new Worktime { Days = [false, false, true, true, true, true, true] },
        },
    ],
    Tasks =
    [
        // `prepare` has no resources, so it runs on the global calendar
        // and ends Friday 17:00.
        new TaskData("prepare") { StartDate = At(14, 8), Duration = 8 },
        new TaskData("inspect") { StartDate = At(14, 8), Duration = 16 },
    ],
    Links = [new LinkData { Id = "l1", Source = "prepare", Target = "inspect" }],
    Resources = [new ResourceData { Id = "dana", CalendarId = "tue-sat" }],
    Assignments =
    [
        new AssignmentData { Id = "inspect:dana", Task = "inspect", Resource = "dana", Value = 1 },
    ],
};

foreach (var mode in new[] { CalendarMode.Resource, CalendarMode.Task })
{
    var result = Engine.Schedule(Build(mode), new SolveOptions { IncludeUnchanged = true });
    foreach (var update in result.Updates)
    {
        Console.WriteLine($"{mode} {update.Id}: {update.StartDate} -> {update.EndDate}");
    }
}

Output:

Resource prepare: 2026-08-14 08:00 -> 2026-08-14 17:00
Resource inspect: 2026-08-15 08:00 -> 2026-08-18 17:00
Task prepare: 2026-08-14 08:00 -> 2026-08-14 17:00
Task inspect: 2026-08-17 08:00 -> 2026-08-18 17:00

In Resource mode Dana works Saturday, so inspect starts right after prepare and runs Saturday and Tuesday. In Task mode her calendar is ignored and inspect waits for Monday on "global".

The rules for picking an assignment's calendar:

The resource has a calendar and the task doesn't: the resource's calendar.
Both have one: their intersection. Give a task a mornings calendar and assign it to Dana, and the work runs Tuesday to Friday mornings only.
The resource has none: the task's calendar.
Summaries and milestones always use the task's calendar.

A task with several assignments on different calendars spans the envelope of its assignments. Each assignment starts at the first working time of its own calendar and runs the full duration there. The task ends when the last one ends. The reported Duration stays the working time of each assignment, not the length of the envelope. Results don't include per-assignment dates.

Resource calendars also shape resource load: each assignment books work only on its own calendar. See Resource load.

Flat time#

Set SchedulingConfig.UseCalendars to false to schedule without working hours. Every calendar becomes 24/7, so a day of duration is 24 hours:

using Plen;

var friday = Moment.FromYmdHm(2026, 8, 14, 8, 0)
    ?? throw new InvalidOperationException("invalid date");

var data = new ProjectData
{
    Config = new SchedulingConfig { UseCalendars = false },
    Tasks = [new TaskData("burn-in") { StartDate = friday, Duration = 2 }], // days
};

var result = Engine.Schedule(data, new SolveOptions { IncludeUnchanged = true });
foreach (var update in result.Updates)
{
    Console.WriteLine($"{update.Id}: {update.StartDate} -> {update.EndDate}");
}

Output:

burn-in: 2026-08-14 08:00 -> 2026-08-16 08:00

With calendars on, the same task skips the weekend and ends on Tuesday at 08:00. The engine still validates calendar ids, but they all resolve to the same flat time, so you can toggle UseCalendars without touching the rest of the data. In flat mode resource and assignment edits never move dates.

Explicit starts on non-working time#

When an edit sets a start that falls on non-working time, the engine doesn't always snap it. A task with no predecessor keeps the exact start you gave it. Its end is computed forward on the working calendar, so the duration is still right. A task with a predecessor gets its start from the link instead.

using Plen;

static Moment At(int day, int hour) =>
    Moment.FromYmdHm(2026, 8, day, hour, 0) ?? throw new InvalidOperationException("invalid date");

var data = new ProjectData
{
    Config = new SchedulingConfig { DurationUnit = TimeUnit.Hour },
    Tasks = [new TaskData("deploy") { StartDate = At(13, 8), Duration = 4 }], // Thursday
};

var project = new Project();
project.Solve(data, new SolveOptions());

// The user drags the task onto Saturday 10:00.
var changes = new SchedulingChanges();
changes.Tasks.Update.Add(new TaskUpdate("deploy") { StartDate = At(15, 10) });
project.Apply(changes);

var result = project.Solve(null, new SolveOptions());
foreach (var update in result.Updates)
{
    Console.WriteLine($"{update.Id}: {update.StartDate} -> {update.EndDate}");
}

Output:

deploy: 2026-08-15 10:00 -> 2026-08-17 12:00

The start stays on Saturday 10:00. The four hours of work run Monday 08:00-12:00. This applies to Project.Apply and Project.Preview, the calls behind drags in an editor.

This is by design: the UI layer owns snapping. If your editor should only allow working-time starts, snap the date before you send the TaskUpdate.