Agency Resource Planning Template: Balance Skills, Capacity and Delivery Risk

An agency resource planning template connects uncertain client demand to the real availability and skills of the people expected to deliver it. The goal is not to fill every hour. It is to expose where commitments, capability, timing and commercial assumptions cannot all be true at once.

Use the plan as a decision surface, not a surveillance tool. People are not interchangeable units, and a spreadsheet cannot determine sustainable workload, fair allocation or client priority by itself.

Set the planning horizon and decision cadence

Choose periods that match the work: weeks for near-term delivery, months for pipeline and hiring scenarios. Keep the immediate horizon detailed and confirmed; reduce precision farther out. A named resource owner should publish cutoffs and coordinate changes.

Define the decisions the plan supports: staffing committed projects, reserving specialist time, resolving conflicts, evaluating new work, using partners or adjusting scope. Identify who can commit named people and who approves commercial or employment changes.

Review often enough to catch material movement without forcing constant reshuffling. Maintain event-driven updates for signed work, delay, scope change, leave or a critical dependency.

Build a trustworthy demand register

Represent each project with client, workstream, phase, period, required skill, effort range, delivery owner, contractual state and evidence link. Decompose only to the level needed for allocation. False task-level detail adds maintenance without improving decisions.

Separate committed, likely and exploratory demand. Record probability as a planning assumption with source and date, not as truth. Keep weighted pipeline totals distinct from actual booked capacity; a fractional forecast cannot be assigned to a fractional person.

Use an agency client discovery interview guide to clarify outcomes and constraints before translating an early conversation into demand. Discovery is evidence, not a signed commitment.

Model usable capacity honestly

Start with contracted or otherwise approved availability for the period. Apply known leave, holidays, internal responsibilities, management, learning, business development and realistic delivery overhead. Qualified owners determine which assumptions are appropriate.

Avoid a universal utilization percentage applied to every role. A creative director, account lead and specialist contributor may have different non-project responsibilities. Show both total availability and usable delivery capacity with the assumptions visible.

Represent units consistently. If demand is estimated in days and capacity in hours, document the conversion and whether a day means contracted time, focused delivery time or a commercial billing unit. Round only for presentation after calculations are complete. Include a planning allowance for rework and coordination only when evidence and policy support it; hidden buffers make both margin and availability difficult to explain.

Do not publish sensitive personal details broadly. A capacity constraint can often be represented as reduced availability without exposing health, family or other private information.

Match skills, continuity and development

Create a controlled skill taxonomy suited to actual work, with proficiency evidence and an owner for updates. Self-assessment, manager judgment and project history each have limitations; do not convert them into a definitive ranking of human value.

Match critical skills first, then account for client context, team continuity, timezone, language, accessibility, development goals and conflicts. Protect review and mentoring capacity when a less experienced team member takes on stretch work.

Avoid concentrating every difficult project on the same expert. Track single points of failure and succession options. Capacity that exists only if one person works across five simultaneous contexts is not resilient capacity.

Copy this agency resource planning template

AGENCY RESOURCE PLAN

Planning horizon / period:
Plan owner / decision authority:
Demand cutoff / capacity cutoff:
Approved assumptions and source links:

DEMAND
Project | Status: COMMITTED / LIKELY / EXPLORATORY
Period | Outcome / phase | Skill needed | Effort range
Delivery owner | Confidence | Contract / brief evidence

CAPACITY
Person or role ID | Period | Skill / proficiency evidence
Approved availability | Internal / leave allowance
Usable delivery capacity | Data access class

ASSIGNMENT
Project | Person / role | Allocation | Confidence
Continuity / development rationale | Approver | Evidence

RISK / DECISION
Gap or overload | Trigger | Client / people impact
Options | Recommended owner | Decision by
Fallback | Approval / communication evidence

Implement separate demand, capacity and assignment tables joined by stable IDs. Protect formulas, define units consistently and preserve snapshots at each approved planning cycle.

Allocate with explicit constraints

Sequence allocation according to authorized priorities, contractual obligations and delivery dependencies. Record why a person or role is proposed, then validate with delivery and people owners. A name in a planner is not confirmation until the relevant commitment process is complete.

Check period totals, overlapping deadlines, review bottlenecks and context switching. Include onboarding and handover effort when moving people. Use ranges where discovery is incomplete, and reserve only through an explicit policy rather than informal ownership of someone’s future time.

A repair handover checklist illustrates how explicit status, evidence and receiving-owner confirmation reduce continuity risk; adapt those principles to agency delivery rather than copying domain-specific controls.

Ask proposed assignees and their accountable managers to validate the plan before it becomes a client promise. They may know about review load, specialist dependencies or sequence constraints that a central planner cannot see. Record disagreement as a planning issue, not as resistance to be overwritten. If two projects need the same person, identify the authorized priority decision and customer consequence instead of asking the individual to absorb both.

Expose delivery risk and scenarios

Flag missing critical skill, sustained overload, undercovered review, external dependency, uncertain start, single-person reliance and impossible sequencing. Define thresholds and owners rather than using unexplained red cells.

Model discrete scenarios: deal starts on time, delayed start, reduced scope, partner support or internal redeployment. Show client outcome, capacity effect, cost, lead time and reversibility for each. Do not merge scenario averages into a supposedly precise plan.

Stress-test the chosen scenario against one or two plausible disruptions, such as a delayed dependency or unavailable reviewer. The purpose is not to predict every incident but to discover brittle commitments. A credible contingency names the substitute capability, activation trigger, authority, lead time and impact; “freelancer if needed” is not a plan unless sourcing, confidentiality, onboarding and commercial controls are feasible.

Track linked assumptions and issues with a RAID log template. Every accepted risk needs an owner, review date and trigger for escalation.

Connect resource and commercial decisions

Translate proposed staffing into the costing basis approved by finance and commercial owners. Consider role mix, partner cost, non-billable review, travel, currency and contract constraints where applicable. Do not assume that utilization alone predicts margin or quality.

When capacity is insufficient, present choices: change timing, narrow scope, renegotiate service levels, use an approved partner, hire, develop capability or decline work. Show consequences for existing clients and staff.

Qualified owners must apply applicable employment law, contracts, procurement rules, financial policy, privacy controls and professional judgment. This template is not authorization to hire, schedule overtime, share employee data or commit client delivery.

Run the weekly resource review

Prepare changes since the prior snapshot, conflicts needing authority and scenarios with a recommendation. Invite only owners needed for decisions. Confirm facts asynchronously; use meeting time for tradeoffs.

Read back assignments, unresolved gaps, decisions, owners, effective dates and client communication. A meeting governance framework can clarify who recommends, decides and records.

Kuno can assist with drafting an authorized resource-review readback for human verification. Explore Kuno for reviewed planning notes with notice, consent where applicable, access controls and appropriate retention.

Protect people and planning data

Resource plans may include client confidentiality, rates, performance inferences, leave and sensitive staffing intentions. Minimize fields, separate access levels and avoid recording reasons for absence when availability is sufficient. Do not use assistive tools to infer health, commitment or future performance.

Confirm recording purpose and participants, obtain consent where applicable and keep private side conversations outside the capture. Human reviewers must correct assignments and remove inappropriate personal information before distributing notes.

Use Kuno for an authorized allocation recap, not as the source of truth. The approved resource system and accountable owners control assignments.

Audit quality and learn from variance

Before publishing, check duplicate assignments, unit consistency, period boundaries, stale pipeline probability, leave treatment, unsupported skill labels, formula overrides and access permissions. Sample source links and confirm approvals.

Compare planned with actual demand and allocation without using timesheets as a simplistic measure of individual worth. Investigate forecast error, scope volatility, rework, dependency delay and context switching. A client status report template can support transparent client communication where an authorized owner approves it.

Update assumptions and taxonomy from evidence. Preserve prior snapshots so improvements are measurable and changes cannot rewrite history.

FAQ

What should an agency resource planning template include?

Include demand, skills, usable capacity, assignments, confidence, dependencies, risks, assumptions, evidence and owners.

How do agencies calculate usable capacity?

Start with approved availability and subtract realistic leave, internal work, development and delivery overhead assumptions.

How far ahead should an agency plan resources?

Plan the near term in detail and use increasingly scenario-based views farther into the future.

How should tentative client work be represented?

Keep it separate from committed demand, record confidence and evidence, and model discrete scenarios.

What signals indicate agency delivery risk?

Look for missing skills, overload, key-person dependency, context switching, unresolved dependencies and weak contingencies.

Can Kuno allocate agency staff automatically?

No. Kuno can assist with reviewed notes; accountable managers must verify constraints and decide allocations.