Resource Planning Template: Match Capacity to Work

How to plan capacity without turning a proposal into a staffing decision

Build the model from stable records and explicit human decisions. Keep workforce-policy and sensitive employment data in their approved systems, then expose only the minimum planning inputs required for a qualified owner to compare capacity with demand.

1. Version the plan, periods, unit, and calendar rules

   Choose one plan version, one capacity unit, one IANA time zone, and non-overlapping periods with exclusive end dates. Name the plan owner and update cycle. Stable IDs and versioned calendar assumptions let reviewers distinguish a changed plan from a changed workforce fact.

   Sources: [resource-pack], [pmi-scheduling]

2. Record capacity and demand independently

   Create minimum fictional resource records with available units, skills, calendar, and accountable owner. Record work-item demand separately with required units, period, skills, project owner, priority, and assumptions. Do not use proposed allocation to rewrite either input.

   Sources: [resource-pack], [pmi-scheduling], [nist-privacy]

3. Propose allocations and expose overcommit

   Link each proposed allocation to stable resource, demand, and period IDs. A proposal may temporarily exceed effective capacity only when the group is visibly marked needs review. The template must flag the difference and leave the resolution to named people.

   Sources: [resource-pack]

4. Separate proposal, approval, and assignment

   Require a current proposal before approval and a current approval before assignment. Store approver, assignment owner, reason, and plan version. Never infer assignment from a tentative status, available hours, skill label, utilization target, or algorithmic score.

   Sources: [resource-pack], [nist-access], [eeoc-responsibilities]

5. Review exceptions and publish a bounded version

   Resolve every approved or assigned over-capacity group, record calendar overrides with an owner and reason, and publish only the reviewed version. Communicate assumptions and changes, but keep project scheduling, staffing authority, delivery commitments, and individual evaluation in their distinct owner processes.

   Sources: [resource-pack], [pmi-scheduling], [nist-privacy]

The capacity and allocation boundary

This template owns an aggregate project or team view of demand, effective capacity, periods, calendars, proposed, approved, and assigned allocations, overcommit, and named human decisions. It does not own the broader workforce, project schedule, or employee record.

Three fictional resource-planning patterns

Each pattern changes the resource unit and decision owner, but keeps demand, capacity, proposal, approval, and assignment distinct. Replace fictional records only after validating source ownership and workforce policy.

Decide whether the resource plan is ready for review

The plan is reviewable when its inputs, exceptions, and human decisions can be traced to the current version. Structural validation does not make the plan accurate or authorized.

1. Capacity, demand, and allocation use different units or calendars

   Choose: Stop and normalize the plan version before comparing totals or proposing assignments.

   Tradeoff: The review waits, but avoids a precise-looking overcommit result built from incomparable inputs.

2. A tentative proposal exceeds effective capacity

   Choose: Mark the group needs review and have the named owner change demand, timing, capacity assumptions, or the proposed allocation.

   Tradeoff: The plan exposes unresolved contention instead of auto-balancing it into an unreviewed staffing decision.

3. An approved or assigned total exceeds effective capacity

   Choose: Reject the version and resolve the allocation before publishing or sending it to a downstream system.

   Tradeoff: A human must revisit the decision, but an overbooked proposal cannot silently become an assignment.

4. A field contains protected, medical, leave-reason, pay, or performance data

   Choose: Remove it, document the minimum planning purpose, and use a separately authorized system and qualified owner for the source record.

   Tradeoff: The planning view has less personal context, but it avoids becoming an employee-evaluation or sensitive-record repository.

What a resource plan cannot decide

The template makes planning assumptions and conflicts visible. It does not create trustworthy source data, authority, consent, a project schedule, or a fair staffing outcome.

• Available units are a versioned planning input, not proof of real-time availability, consent, qualification, authorization, cost, productivity, utilization, performance, or an outcome.
• Proposed, approved, and assigned allocations do not establish task dependencies, start dates, shift coverage, bookings, payroll time, delivery dates, budgets, or project success.
• The pack does not implement authentication, authorization, privacy controls, workforce-system integration, concurrency, notifications, audit storage, retention, export, or recovery.
• A human owner must review source accuracy, access, employment policy, potential discriminatory effects, accommodation boundaries, and every approval or assignment.
• This ordinary informational article does not grant AI signup credits. The linked commercial page follows its own current eligibility rules.

Sources and verification record

The same-release artifact is the direct source for file structure, example counts, and validation. Current primary professional, NIST, and U.S. agency references support versioned scheduling inputs, privacy minimization, access boundaries, and human employment responsibility.

1. [resource-pack] Playcode:Resource planning fictional example

   Checked August 1, 2026. Supports: The locally reviewed two periods, three resources, four demand records, four allocations, calendar adjustments, manual decision states, and deterministic checks. Public availability remains unverified until deployment.

2. [pmi-scheduling] Project Management Institute:Practice Standard for Scheduling, Second Edition

   Checked August 1, 2026. Supports: Schedule-model concepts including model IDs and versions, calendars and work periods, update cycles, resource planning, approval, baselines, approved changes, communication, and maintained records. It does not prescribe this template.

3. [nist-privacy] National Institute of Standards and Technology:NIST Privacy Framework

   Checked August 1, 2026. Supports: Voluntary privacy-risk framing for minimum-purpose workforce inputs, assigned responsibilities, access, retention, disclosure, and disposal without claiming legal compliance.

4. [nist-access] National Institute of Standards and Technology:NIST SP 800-53 Rev. 5 Update 1

   Checked August 1, 2026. Supports: Security and privacy control reference for authorization, least privilege, account management, audit, and information handling. The planning pack does not implement these controls.

5. [eeoc-responsibilities] U.S. Equal Employment Opportunity Commission:Responsibilities under federal employment discrimination laws

   Checked August 1, 2026. Supports: The human employment boundary: employment actions must not discriminate on protected bases, and employees who complain need protection from retaliation. A template cannot determine compliance or fairness.

Resource planning template questions