Resource Calendar

A resource calendar defines the individual working schedule of a single resource — a person, a piece of equipment, or a shift-based machine — as opposed to the default project calendar that applies to the project as a whole. When a resource calendar is set, it overrides the project calendar for any task assigned to that resource: the scheduling engine computes the task's finish date from the resource's own available hours, not from the generic project default.

Same Task, Four Resource Calendars, Four Finish Dates

Resource	Calendar	5-Day Task Starts	Finishes
Full-time employee	Mon–Fri, 8 hrs/day	Mon, Jun 1	Fri, Jun 5
Part-time employee	Tue & Thu only	Tue, Jun 2	Thu, Jun 18
Single-shift machine	8 hrs/day, 7 days/week	Mon, Jun 1	Fri, Jun 5
Dual-shift machine	16 hrs/day, 7 days/week	Mon, Jun 1	Wed, Jun 3

Resource Calendar vs. Project Calendar

The project calendar is the default assumption — the working days and hours that apply unless a resource's own calendar says otherwise. The resource calendar is the exception that governs reality for that specific person or machine. A task assigned to a resource with a different calendar than the project default can have a finish date that looks surprising until the assigned resource's actual availability is checked. When a resource is unassigned, the project calendar is what determines the task's dates instead.

Why Resource Calendars Matter for Realistic Schedules

A schedule built entirely from the project calendar, ignoring individual resource availability, looks achievable on paper but often isn't. A task assigned to a part-time resource or a single-shift machine takes longer in calendar time than the same duration assigned to a full-time resource or a round-the-clock machine — even though the task's duration in working time is identical. Resource calendars are what let a scheduling engine tell the difference, and they are the same underlying data that resource leveling and resource allocation checks rely on to detect over-allocation.

Resource Calendars in Maverick

Maverick calls this an availability schedule rather than a calendar, but the function is the same: every resource — employee, machine, or equipment — has its own schedule of working days and hours. When a resource is assigned to a task, Maverick computes the finish date from that resource's individual schedule, automatically skipping non-working days and adjusting for multi-shift machines or part-time employees. For the full mechanics, including time segments and how schedules drive downstream dates, see the guide: Resource Schedules and Working Hours.

Related Terms

Project Calendar  ·  Task Duration  ·  Resource Allocation  ·  Resource Leveling  ·  Resource Utilization