Assess delivery capacity, not headcount alone

A staffing list describes positions and people. It does not establish whether the administration can deliver its commitments. Capacity also depends on available time, relevant capability, authority, processes, information, tools and the continuity of critical work.

Two departments with the same number of employees can have very different capacity because their service demand, responsibilities and operating conditions differ. A national staffing ratio or another Nation’s organization chart may provide a question to explore, but it cannot answer the local resource decision by itself.

Arcus recommends starting with the services, obligations and priority initiatives the Nation expects the administration to deliver. Then assess the evidence for current demand, delivery performance and the resources needed to sustain it.

The assessment should examine the work system rather than rank individual employees. Where individual performance concerns arise, handle them through the appropriate employment process instead of allowing an organizational assessment to become an informal personnel judgment.

Set boundaries around the decision

Define the departments, services, time horizon and questions included. An assessment intended to support next year’s staffing budget differs from one preparing for a major new service responsibility or diagnosing repeated delivery failures.

Agree what the assessment can recommend and who will decide. Clarify whether it can examine service priorities, role design, shared support, technology and processes as well as staffing. A mandate restricted to headcount may miss the cause of the problem.

Identify the evidence available and its limitations. Useful records may include work volumes, service commitments, budgets, vacancies, job descriptions, schedules, backlogs, overtime, training and recurring exceptions. Data quality should be assessed rather than assumed.

Explain the purpose and process to employees. Invite factual input and protect employment information through appropriate access and reporting practices. In a small team, apparently anonymous comments may still identify a person, so avoid promising anonymity that cannot be delivered.

Use existing plans and assessments where they remain relevant. Confirm what has changed instead of requiring staff to repeat information already documented.

Establish the demand the workforce must meet

Describe recurring services, required outputs, deadlines and major initiatives. Distinguish committed work from proposed additions and discretionary activities. Identify the authority responsible for setting priorities when demand exceeds available capacity.

Use workload evidence at an appropriate level. Transaction volumes may help assess routine processing, while complex casework or policy development may require categories of effort and professional judgment. Avoid pretending that every activity has a stable average processing time.

Consider variation and peaks. Annual averages can hide periods when reporting, budgeting, community events and projects occur together. Examine the timing of demand and the consequences of delay.

Include work that is often invisible: coordination, preparation, rework, supervision, travel, relationship maintenance and responding to unexpected needs. Do not add these as separate categories if they are already included in an estimate of task effort.

Record uncertainty as a range or confidence statement. If the estimate rests on a small sample or staff recollection, say so and identify what additional evidence would materially change the decision.

Measure usable capacity and capability

Begin with available positions and actual staffing, then account for vacancies, planned absences, part-time arrangements and recurring responsibilities. Paid hours are not all available for a single service activity.

For a hypothetical two-person team, assume 300 paid hours in a month. Deduct 40 hours of planned absence and 60 hours of meetings, supervision and other work outside the service being assessed. That leaves 200 hours for the defined service scope. If evidenced demand is 230 hours, the estimated gap is 30 hours.

This is an assessment scenario, not a universal productivity ratio. Check that the demand estimate excludes the 60 hours already removed from capacity, and test how much the result changes under different workload assumptions.

Assess capability separately from time. A team may have available hours but lack a required skill, decision authority or access to information. Another team may have strong expertise but too little time to use it reliably.

Review continuity. A process dependent on one person may appear adequately staffed under normal conditions but fail during an absence. Identify backup capability, authorized access and the time needed for another person to take over.

Test explanations using more than one source

Interview staff and managers, review relevant records and trace representative workflows. Each source reveals different things. Interviews provide context; records show patterns; workflow review can locate delays and rework.

If a backlog is attributed to understaffing, examine whether work is waiting for approvals, missing information or specialist review. More processing capacity may not resolve a decision bottleneck. Conversely, a process improvement should not be used to deny a sustained workload gap supported by evidence.

If inconsistent output is attributed to a skills gap, check whether expectations, tools and supervision are adequate. Training may help, but it will not create authority or repair an unreliable information system.

Keep a finding record with the observation, supporting evidence, competing explanations, confidence and decision implication. Where sources disagree, investigate the difference rather than averaging opinions into a score that appears more certain than the evidence allows.

Validate findings with the people who understand the work. Validation should correct facts and test interpretation while preserving the assessment’s ability to identify difficult issues.

Prioritize gaps by consequence and timing

A long list of weaknesses is not an implementation plan. Prioritize the gaps that most affect essential services, important decisions, control, continuity or approved strategic commitments.

Consider likelihood, consequence, urgency and dependency. A modest gap in a critical process may deserve attention before a larger but less consequential inconvenience. A capability required before a new program begins may need development months in advance.

Avoid reducing the whole administration to one average capacity score. Strong results in several areas can conceal a serious weakness in one essential function. Present the evidence at the level needed for a decision.

Separate immediate stabilization from structural improvement. Temporary coverage may protect a deadline while role redesign, development or recruitment is prepared. Make the temporary arrangement and its review date explicit.

Identify decisions leadership must make about service scope. If resources cannot support all commitments, the assessment should reveal that choice rather than assume staff will absorb the difference indefinitely.

Compare actions and their operating implications

Reducing or deferring lower-priority work can close a capacity gap quickly, but changes service commitments. Process redesign may reduce rework or waiting, but requires implementation effort and should be tested before promised savings are treated as available capacity.

Training can address a defined capability gap when employees have time and opportunities to apply it. Recruitment can add capacity or expertise, but involves continuing cost, orientation and a realistic labour-market proposition.

Shared or external support can provide specialist access or continuity. It still requires internal ownership, reliable inputs and coordination. A new system may help when information or workflow is the constraint, but introduces configuration, support and adoption work.

Compare the options against the same gap and service requirement. For each, identify cost, time to benefit, implementation owner, dependencies, risks and evidence that would confirm improvement.

Use a combination where justified. In the hypothetical 30-hour monthly gap, simplifying work by an evidenced ten hours and adding twenty hours of usable support could be a candidate response. It remains a hypothesis until coordination effort, actual demand and the proposed improvement are tested.

Budget the assessment and the changes separately

The assessment itself uses staff, manager and analyst time. Its recommendations may require a much larger recurring investment. Keep these budgets distinct so approval of the assessment is not mistaken for approval of every proposed change.

For a narrow hypothetical diagnostic, eight one-hour interviews use eight analyst hours and eight participant hours. Add eight analyst hours for record review and analysis, plus a one-hour validation meeting involving six people in total. The illustrative effort is 30 person-hours.

This is a limited exercise, not an estimate for a complete multi-department assessment. A broader scope, poor records or complex service demand may require substantially more work. Define deliverables and evidence needs before committing to a schedule or fee.

Present implementation costs separately: recurring staffing, one-time system changes, training, backfill and ongoing support. Identify funding, authority and sequencing for each recommendation.

Include the capacity needed to implement. A department already unable to meet current demand may need temporary support or reduced commitments to carry out the improvement plan.

Make the findings usable after the report

Present a concise decision record for each priority gap: the service affected, evidence, explanation, options, recommendation, cost and accountable owner. Preserve the supporting detail so assumptions can be reviewed later.

Agree the first implementation actions and the measures that will show whether they work. These might include backlog age, timely decisions, reliable coverage, fewer errors or a demonstrated capability. Choose measures connected to the problem.

Review results after a meaningful operating period. If performance does not improve, revisit the explanation and implementation conditions rather than assuming the assessment was correct because its recommendations were approved.

Maintain the assessment as the Nation’s services and priorities change. Its value is the ability to make better resource and operating decisions with current evidence, not the permanence of its original conclusions.

Evidence and source notes

1. Indigenous Services Canada, Governance Capacity Planning Tool Instructions, inventory, needs identification, prioritization and development planning.
2. Government of Yukon, Capacity Assessment Tool, 2014, background and departmental assessment sections. A historical method developed with First Nation input; no worksheets are reproduced here.

Research reviewed October 18, 2026. Workload and resource calculations are hypothetical. The six stages are original Arcus analysis, not a standardized staffing ratio or individual performance assessment.