Organizational Capacity Assessment Template – Free Word Download

Introduction

In the portfolio management process, one of the most frequent and fatal errors organizations make is overestimating their ability to deliver. They approve projects based on strategic desire rather than logistical reality. The result is a “traffic jam” of initiatives where resources are spread so thin that nothing gets finished, quality suffers, and employee burnout skyrockets. The Organizational Capacity Assessment is the project management governance tool designed to prevent this scenario.

Unlike the Change Readiness Assessment (which asks “Are we willing to do this?”), the Organizational Capacity Assessment asks “Are we able to do this?” It is a quantitative and qualitative audit of the resources required to execute the project successfully. This includes human resources (bodies in seats), intellectual resources (skills and competencies), financial resources (cash flow and budget), and physical/technical resources (equipment, environments, and licenses).

This document should be completed during the Portfolio Planning phase or the Project Initiation phase. It serves as a reality check for the Project Sponsor and the Steering Committee. If this assessment reveals that the organization is already operating at 110% capacity, adding a new project without pausing an existing one is a recipe for failure.

This template guides you through a rigorous analysis of your constraints. It forces the project team to look at the “supply side” of project management. You will need input from Department Heads, Resource Managers, and IT Operations to complete this accurately. By identifying bottlenecks before the project begins, you can make informed decisions about hiring, outsourcing, phasing, or delaying the project to ensure a smoother path to delivery.

Section 1: Project Scope and Demand Profile

1.1 Project Overview

Instructions:

Define the demand this project places on the organization. This sets the stage for the capacity analysis.

• Project Name: [Enter Name]
• Project Priority: [e.g., Critical/Strategic, Regulatory/Mandatory, Discretionary/Nice-to-have]
• Proposed Timeline: [Start Date] to [End Date]
• Project Type: [e.g., Software Development, Construction, Process Re-engineering]

Guidance:

The “Project Priority” is crucial. If the organization is at full capacity, a “Regulatory” project might force a “Discretionary” project to be paused. Be clear about where this project sits in the pecking order.

1.2 Peak Demand Windows

Instructions:

Projects rarely need the same level of resources throughout their lifecycle. Identify when the “crunch times” will occur.

• Phase 1 (Planning): [Low Demand]
• Phase 2 (Execution/Build): [High Demand – Expected Dates: Jan-Mar]
• Phase 3 (Testing/QA): [Peak Demand – Expected Dates: Apr-May]
• Phase 4 (Deployment): [Medium Demand]

Tips for Success:

Identifying the timing of the peak demand is essential. You might have capacity in January but zero capacity in April. Mapping this helps in “resource smoothing” across the portfolio.

Section 2: Human Resource Capacity (Quantitative)

Instructions:

This is typically the most constrained resource in any organization. You must calculate the Full-Time Equivalent (FTE) requirement and compare it against availability.

2.1 The “80% Rule” Calculation

Note: A common mistake is assuming an employee is available for 40 hours of project work per week. Between administrative tasks, team meetings, email, and breaks, the effective project availability is usually 80% (approx. 32 hours) or less. Use the 80% figure for all calculations below to ensure realism.

2.2 Functional Team Capacity Analysis

Instructions:

Break down the requirements by team or role. Do not just look at the total number of people; look at specific departments.

Table 2.2: Resource Availability Matrix

Role / Team	Total FTE Required	Current Staff Count	% Already Allocated	Net Available Capacity	Deficit/Surplus
Example: Java Developers	3.5 FTE	10	90% (Busy on other projects)	1.0 FTE	DEFICIT (-2.5 FTE)
Example: QA Testers	2.0 FTE	5	50%	2.5 FTE	SURPLUS (+0.5 FTE)
[Insert Role]	[Number]	[Number]	[%]	[Number]	[+/-]
[Insert Role]	[Number]	[Number]	[%]	[Number]	[+/-]

Step-by-Step Calculation Guide:

1. Total FTE Required: How many people do you need full-time for this project?
2. Current Staff Count: How many people exist in that role total?
3. % Already Allocated: Look at the resource forecast. Are they booked on other initiatives?
4. Net Available: (Count * (100% – % Allocated)).
5. Deficit/Surplus: (Net Available – Required).

Interpretation:

If you show a deficit in a critical role (like “Java Developers” in the example above), you physically cannot do the project with internal staff. You have three options: Hire, Outsource, or Delay.

2.3 Subject Matter Expert (SME) Bottlenecks

Instructions:

SMEs are often the hidden constraint. These are the one or two people in the company who “know how everything works.” They are usually required for every single project.

• identified Key SMEs: [List names, e.g., The Chief Architect, The Head of Compliance]
• Current Load: [Are they already double-booked?]
• Impact of Unavailability: [High/Medium/Low]

Risk Warning:

If your project relies 100% on a specific individual (e.g., “Jane must approve all designs”), and Jane is booked on three other critical projects, Jane is a single point of failure. You must negotiate for her time specifically.

Section 3: Skills and Competency Capability (Qualitative)

Instructions:

Having available bodies is not enough; they must be the right bodies. This section assesses if the available resources possess the specific skills required for this unique project.

3.1 Competency Gap Analysis

Instructions:

List the specific technologies, methodologies, or domain knowledge required.

Table 3.1: Skills Matrix

Required Skill / Competency	Internal Proficiency Level	Gap Description	Resolution Strategy
Example: React Native Mobile Dev	Low (Most staff know standard React web)	Team lacks mobile-specific nuances.	Hire 1 Senior Contractor to lead/mentor.
Example: Agile/Scrum Methodology	Medium	Staff is used to Waterfall.	Conduct 2-day Scrum Bootcamp.
Example: GDPR Regulatory Knowledge	High	Legal team is well-versed.	None required.
[Insert Skill]	[Low/Med/High]	[Describe Gap]	[Strategy]

Guidance for Completing Section 3:

Be honest about proficiency. “Low” means they have heard of it but never used it. “Medium” means they can work with supervision. “High” means they can lead/teach others. If the gap is critical (e.g., building an AI tool with no AI engineers), this is a “Red Flag” capacity issue.

3.2 Learning Curve Impact

Instructions:

If you plan to train internal staff to close the gap, you must account for the “Learning Curve.” Productivity will be lower in the first few months.

• Estimated Productivity Loss: [e.g., “Team will operate at 50% velocity for the first 4 sprints while learning React.”]
• Schedule Adjustment: [Has the project timeline been extended to account for this learning phase? Yes/No]

Section 4: Infrastructure and Technical Capacity

Instructions:

Do you have the tools to do the job? This includes hardware, software environments, and licenses.

4.1 Environment Availability

• Development Environment: [Is there a sandbox ready? Yes/No]
• Testing/QA Environment: [Is there a dedicated QA server? Or will we conflict with other testing teams?]
• Staging/Pre-Prod: [Is there a staging environment that mirrors production?]

Common Pitfall:

A frequent capacity bottleneck in IT projects is the “Environment Contention.” If three projects are trying to test on the same QA server simultaneously, data gets corrupted and schedules slip. Ensure you have a dedicated or reserved environment.

4.2 Licensing and Tooling

• Software Licenses: [Do we have enough licenses for the new software (e.g., Salesforce seats, Jira licenses)?]
• Hardware: [Does the team have the necessary laptops/servers/mobile devices for testing?]
• Physical Space: [If this is an on-site project, do we have desk space/war rooms for the team?]

Section 5: Financial and Budgetary Capacity

Instructions:

This goes beyond the simple project budget. It assesses the organization’s cash flow and financial flexibility.

5.1 Funding Liquidity

• Budget Status: [Approved / Pending / Not Allocated]
• Cash Flow Constraints: [Are there quarterly spending caps? e.g., “We cannot spend more than $50k in Q1 due to cash flow restrictions.”]

5.2 Contingency Reserves

• Management Reserve: [Does the organization have a central pool of money for emergencies?]
• Cost of Capital: [Is the organization currently in a cost-cutting mode (hiring freeze/travel ban) that might impact our ability to spend the budget even if we have it?]

Guidance:

Sometimes a project has a theoretical budget of $1M, but the company enforces a hiring freeze. This is a “Capacity” issue. The money is there, but the capacity to use it (by hiring) is blocked.

Section 6: Operational Business Capacity

Instructions:

Projects change the business. Can the “Business as Usual” (BAU) operations handle the disruption this project will cause during implementation?

6.1 Operational Bandwidth

• Seasonality Impacts: [Does the project go-live overlap with a peak business period? e.g., Retail Black Friday, Finance Year-End Close]
• Impact on Customer Service: [Will the project temporarily slow down response times? Can the support team handle the increased volume of tickets during launch?]

Table 6.1: Operational Stress Test

Department	Anticipated Disruption	Capacity to Absorb	Mitigation
Example: Customer Support	Launch will generate +20% call volume.	Low (Current wait times are high).	Hire temporary support agents for launch month.
Example: Warehouse	Inventory freeze for 2 days during migration.	Medium (Can be managed on weekend).	Schedule migration for Sunday night.

Section 7: Management and Governance Capacity

Instructions:

Do we have enough leaders to oversee this? A project without a focused Manager or an engaged Sponsor is a ship without a rudder.

7.1 Project Management Bandwidth

• Assigned Project Manager: [Name]
• Current Project Load: [How many other projects are they running?]
• Capacity Assessment: [Green (Dedicated) / Yellow (2-3 Projects) / Red (Overloaded >3 Projects)]

Guidance:

If the PM is managing 5 complex projects, they are not managing any of them; they are just reporting status. Effective project management requires “thinking time.” If the PM is Red, request a dedicated resource.

7.2 Steering Committee Bandwidth

• Sponsor Availability: [Does the sponsor have time to meet bi-weekly to resolve blockers?]
• Decision Velocity: [Based on past experience, how fast can this group make decisions? Slow/Fast]

Section 8: Vendor and Partner Capacity

Instructions:

If you are outsourcing, you are renting capacity. Is that external capacity reliable?

• Primary Vendor: [Name]
• Vendor Team Stability: [Do they have a stable team, or high turnover?]
• Concurrent Engagements: [Is the vendor prioritizing us, or are we a small fish in their pond?]
• Supply Chain Risks: [For hardware projects, are there lead-time issues? e.g., Chip shortages]

Section 9: Capacity Summary and Scoring

Instructions:

Summarize the findings to present a clear picture to leadership. Rate each dimension as Low Risk (High Capacity), Medium Risk, or High Risk (Low Capacity).

Table 9.1: Capacity Scorecard

Dimension	Rating (R/A/G)	Summary of Issues
Human Resources	[RED]	Critical deficit in Developer roles.
Skills/Competency	[AMBER]	Need training on new tech stack.
Infrastructure	[GREEN]	Environments are ready.
Financial	[GREEN]	Budget approved and available.
Operational	[AMBER]	Launch overlaps with busy season.
Management	[RED]	PM is currently overloaded.

Overall Capacity Assessment:

• [ ] Full Capacity: Proceed as planned.
• [ ] Constrained Capacity: Proceed with risks; requires aggressive prioritization or resource leveling.
• [ ] Over Capacity: DO NOT PROCEED. The project is not viable without acquiring new resources or canceling other work.

Section 10: Recommendations and Balancing Strategy

Instructions:

If the scorecard above shows Red or Amber, propose a solution. You cannot just state the problem; you must offer the “Path to Green.”

10.1 Strategic Options

Select the recommended strategy:

1. [ ] Resource Leveling (Smoothing): Extend the timeline. Instead of needing 5 developers for 3 months, use 2 developers for 8 months. This reduces peak demand.
2. [ ] Descoping: Reduce the work. Cut features to match the available team size.
3. [ ] Staff Augmentation: Buy capacity. Use the budget to hire contractors or a vendor agency to fill the skill/body gap.
4. [ ] Portfolio Re-prioritization: Pause a lower-priority project to free up the internal staff for this one.

10.2 Action Plan

1. Action: [e.g., “Request $50k budget increase to hire 2 contractors.”] | Owner: [PM]
2. Action: [e.g., “Shift project start date by 4 weeks to await availability of the QA Lead.”] | Owner: [Sponsor]
3. Action: [e.g., “Secure dedicated testing environment from IT Ops.”] | Owner: [Tech Lead]

Conclusion – Organizational Capacity Assessment Template – Free Word Download

The Organizational Capacity Assessment is a mechanism for truth. It moves the conversation from “We hope we can do this” to “The math says we can (or cannot) do this.”

Presenting a “Red” capacity assessment to executives can be intimidating, but it is the professional responsibility of the Project Manager. It is far better to have a difficult conversation now about resource constraints than to report a project failure six months from now due to foreseeable burnout and shortages.

By completing this assessment, you provide the Steering Committee with the data they need to make governance decisions. They can either provide the missing capacity (money/people) or adjust their expectations (scope/time). This transparency fosters a culture of realistic planning and sustainable delivery, ensuring that the organization uses its finite resources on the most valuable initiatives without breaking the teams that deliver them.

---

Meta Description:

An Organizational Capacity Assessment template to evaluate resource availability, skills, infrastructure, and financial readiness before committing to a project.

Discover More great insights at www.pmresourcehub.com