What Are Resource Calendars?

Resource Calendars document the working days and hours, availability, and capacity of individual resources assigned to a project. In PMBOK 8, resource calendars are a key input to both schedule development and resource management — they tell the scheduling tool when each specific person, piece of equipment, or facility is available to perform work. Resource calendars go beyond project calendars (which define organizational working days) by capturing individual availability constraints: part-time allocations, vacation, training commitments, and known blackout periods for each named resource. Without accurate resource calendars, the schedule model produces dates that are impossible to achieve with the actual people assigned.

What's Inside This Resource Calendars Example

This Resource Calendars example covers the six-person Project Phoenix team for MCG's website launch ($72,250, March 17 to June 13, 2025). The spreadsheet contains a dedicated tab for each resource:

• Alex Morgan (PM): 100% availability, Mon–Fri, no vacation. Travel to Austin client on April 22 (1 day, handled remotely).
• UX Designer: 80% allocation to Project Phoenix. Non-project time: Mondays reserved for another client. Vacation: April 28–29 (2 days).
• Lead Developer: 100% allocation. Vacation: May 19–21 (3 days, Week 9). MCG development training: June 2 (1 day, Week 11).
• Content Specialist: 75% allocation. Non-project time: Friday afternoons reserved for MCG internal content. Sick leave: May 5–9 (5 days, Week 7 — ISS-004).
• QA Analyst: 60% allocation. Non-project time: other QA commitments Tues/Thurs mornings.
• Data Migration Specialist: 50% allocation, available only Weeks 6–11 for peak migration work (confirmed via resource manager agreement).

How Alex Morgan Used These Resource Calendars

Alex Morgan collected all resource calendar information during Week 1 by asking each team member to complete a standard availability form. The calendars were loaded into the scheduling tool before any activity sequencing began — this is the correct sequence; loading calendars after building the schedule means the schedule is built on fictional availability.

Three resource calendar entries had direct execution impact:

• UX Designer's Monday constraint: Knowing Mondays were unavailable, Alex scheduled all UX Designer tasks with Tuesday start dates. This prevented Monday "start tomorrow" assignments that would have created artificial one-day delays throughout the design phase.
• Lead Developer vacation (May 19–21): Pre-loaded at Week 1. Alex scheduled the integration testing documentation and architecture review tasks for those three days — work the Lead Developer could do asynchronously or that other team members could advance. Zero critical-path impact.
• Content Specialist sick leave (ISS-004): The sick leave in Week 7 was not pre-planned, but because the resource calendar for the Content Specialist had been built with a 75% buffer, the team already understood this resource was not fully dedicated. Alex redistributed the missed week's tasks within the existing calendar constraints without needing to revise the schedule baseline.

Download and Customize

This Resource Calendars example is available as a free download. Use it as a reference to build your own resource calendars, or start with the blank template and populate it for each assigned team member.

• Download the Resource Calendars Template — PMBOK 8 (blank, ready to use)
• Read the article: Resource Calendars in PMBOK 8 — Guide and Best Practices

Resource Calendars Example: Key Takeaways

Resource Calendars and Project Calendars are often confused — and that confusion costs schedule accuracy. The Project Calendar tells the tool when the organization works; the Resource Calendar tells it when each specific person works. For Project Phoenix, the UX Designer's Monday constraint was invisible to the Project Calendar (which showed Monday as a working day) but captured in the Resource Calendar. Without that individual calendar, the scheduling tool would have routinely placed UX tasks with Monday starts — and the team would have lost approximately 10 person-days of schedule efficiency across the project's duration to one-day artificial delays. Collect individual resource availability information before building the schedule. Always.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.