How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

Resource calendars

A resource calendar shows when specific people, equipment, or facilities are available or unavailable for project work. It lists working time, non-working time, shifts, and other constraints that affect scheduling and assignments.

Key Points

  • Lists availability and non-working time for people, equipment, and facilities.
  • Includes working days, shifts, holidays, time-off, and time-zone or location details.
  • Used to estimate durations, assign resources, and validate schedule feasibility.
  • Highlights resource conflicts and supports resource leveling and smoothing.
  • Maintained collaboratively by the project manager, resource managers, and often PMO or HR.
  • Typically implemented in scheduling tools and linked to enterprise or organizational calendars.

Purpose

Ensure that activities are planned and assigned only when required resources are actually available. Resource calendars reduce scheduling conflicts, support realistic duration estimates, and enable effective allocation of people and critical assets.

Source & Ownership

  • Primary sources: HR systems, PMO standards, functional managers, and enterprise calendars.
  • Ownership: The project manager uses it for planning; functional/resource managers provide and approve availability data.
  • Updates: Adjusted as team members join/leave, shifts change, or new constraints (training, maintenance) arise.
  • Tooling: Commonly maintained in PPM or scheduling tools (e.g., resource pools, team calendars) integrated with corporate calendars.

How to Use

  • Collect base calendars: organization-wide working days, holidays, and standard shifts.
  • Add resource-specific details: individual time-off, training, part-time status, locations, and time zones.
  • Record equipment/facility windows: maintenance shutdowns, booking rules, and capacity limits.
  • Link the calendars to activities in the schedule so estimates reflect real availability.
  • Run resource analysis (leveling/smoothing) to resolve over-allocations or gaps.
  • Review and update regularly; communicate changes to the team and stakeholders.

Example Usage

During schedule development, the project manager sees that two key analysts are on leave the first week of July. The team defers a requirements workshop to the following week and assigns preparatory tasks to available staff. For testing, the lab calendar shows one test rig down for maintenance, so the plan staggers test execution to avoid idle time.

Caveats

  • Outdated calendars lead to unrealistic dates and resource conflicts.
  • Respect privacy: store only necessary availability details, not sensitive personal data.
  • Consider time-zone and location differences when planning cross-regional work.
  • Contractor availability may change quickly; confirm frequently and include contingency.
  • Do not assume full-day availability; account for partial allocations and shared roles.

PMP Example Question

While finalizing the schedule, the project manager needs to verify whether a specialized technician can support an activity next month. Which document should the manager consult first?

  1. Resource calendars
  2. Risk register
  3. RACI matrix
  4. Work performance data

Correct Answer: A — Resource calendars

Explanation: Resource calendars show individual and asset availability and constraints. They are the primary input to confirm whether a specific resource can be assigned at a given time.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across seven sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management, not on Udemy.

See What Is Included