The scarce resource may be the owner’s attention

A Nation can have a funded road project, a facility renovation and a servicing extension, each with a competent external team, and still struggle to move them together. Each team needs scope decisions, payment verification, access arrangements, community communication and acceptance of completed work. Hiring another technical consultant does not automatically create more time for these owner responsibilities.

Arcus’s central insight is that a small administration should authorize the next stage of each project against shared decision capacity, rather than manage concurrency by project count or total construction value. Two complex approvals in the same week can be harder to support than several projects in relatively stable phases. The appropriate limit is therefore specific to the work, role and period. There is no defensible universal number of projects per administrator.

This article concerns coordination across a portfolio. For a single stalled investment, see pre-construction delay diagnosis. For choosing which projects enter the funded program, see the fundable capital plan.

What the evidence supports—and what remains uncertain

The First Nations Infrastructure Institute’s August 2026 lessons identify unclear responsibility for funding, people and decisions, and recommend charters for work involving multiple entities. They also describe maintaining continuity through staff and leadership transitions. These are practice-based findings, not a controlled evaluation of a staffing ratio.[1]

A November 2025 ISC audit found inconsistent information-sharing and insufficiently formalized coordination between education programming and education facilities. That is evidence about departmental interfaces, not a finding that First Nations administrations lack competence. It supports checking whether a delay originates outside the Nation before assigning a local staffing remedy.[2]

ISC’s current construction-management business-plan guidance also distinguishes the project owner’s role, team qualifications, implementation and resourcing. It applies to a specified delivery arrangement; it is not a universal staffing standard.[3] Together, these sources justify explicit capacity and responsibility tests. They do not establish how much a particular Nation would save by adopting the approach below. The framework and worked example are Arcus analytical synthesis, not original empirical research.

Distinguish four causes of a crowded project queue

Insufficient capacity: complete, decision-ready requests accumulate with the same person across unrelated projects. Compare the actual time available after payroll, community services and other standing duties with the upcoming workload. A full calendar alone is not enough: establish which tasks require that person’s authority or expertise.

Unclear authority or repeated rework: requests circulate between staff, committees and Council, or return because the question, options or recommendation are incomplete. Additional staff may simply produce more material for the same unresolved decision route. Trace a small sample of recent decisions from first submission to resolution; record missing information and each return.

External dependency: a complete submission awaits a funder, utility, regulator, land arrangement or contractor. Check dates, the recipient’s outstanding questions and the agreed next action. Escalating the external dependency or resequencing unaffected work may help; adding an internal coordinator does not itself secure an approval.

Unstable scope: demand, site conditions or service requirements change after work has begun. Check whether changes respond to new evidence or reopen already agreed preferences. The remedy may be a revised scope decision and cost forecast, rather than pressure to work faster. More than one cause can operate at once.

Build a role-based capacity picture for the next eight weeks

Start with the next consequential decision on every active project: approve design, issue a tender, authorize a change, verify a payment or accept commissioning. Record the due date, evidence required, preparer, decision-maker, finance reviewer and operating owner. Include the decision’s consequence if late. Do not replace an existing project schedule; expose the internal commitments those schedules collectively create.

Estimate hours or days by role with the people who perform the work. Subtract normal services, known absences and unavoidable obligations from available time. Keep explicit room for uncertain work rather than treating every paid hour as available for projects. Distinguish a task that can be supported by an external specialist from a decision that must remain with the Nation under its own authorities.

Use a rolling period that reflects the portfolio. Eight weeks is a practical starting point, not a researched optimum. A remote seasonal construction program may require a longer view, while an immediate incident needs a separate response process. Preserve essential-service risk mitigation even when a permanent project cannot yet advance.

A worked capacity example

Consider a fictional four-week period. After ordinary duties and a contingency allowance, finance has 48 hours available for capital work; the executive sponsor has 24. Three projects require finance review of 20, 18 and 22 hours, and sponsor decisions of 6, 8 and 7 hours. Finance demand totals 60 hours, exceeding capacity by 12; sponsor demand totals 21 hours and fits within the available time. These are invented assumptions for explanation, not benchmarks or observations of a client.

A fourth project requires another 10 finance hours and 4 sponsor hours. Accepting it immediately raises the finance shortfall to 22 hours and the sponsor shortfall to one hour. Calling the fourth project “small” does not resolve either constraint. Nor would adding ten hours of engineering support address the finance queue.

Three responses merit comparison. First, move a genuinely deferrable review into the next period after checking contract dates and service consequences. Second, have qualified support prepare reconciliations and evidence packs, while retaining authorized verification and approval. Third, postpone the fourth project’s next stage. The decision depends on which work is substitutable, the costs of delay and the consequences of losing a funding or seasonal window.

If external support needs six hours of internal onboarding and review, buying 22 hours of support does not necessarily release 22 internal hours. Estimate the net relief on the constrained role and confirm it from the first completed work cycle. Also check the next period: shifting all reviews to the same later week merely relocates the bottleneck.

Choose an operating arrangement that fits the duration of demand

Protected internal coordination suits a manageable, continuing pipeline where experienced staff can receive genuine relief from other duties. Its cost includes the displaced work and backfill, not just an amended job description. It fails if the coordinator remains accountable for the same full operational workload.

Time-limited owner support can suit a concentrated design, procurement or commissioning peak. Specify deliverables such as decision packs, dependency tracking, consolidated forecasts and handover records. Include supervision, mobilization, travel and knowledge transfer in the cost. Make clear which decisions remain with the Nation and avoid overlapping consultant responsibilities.

Shared capacity across Nations or a regional organization can support specialist expertise that one administration does not need full time. Compare access to that expertise with scheduling conflicts, travel, confidentiality, governance and exit arrangements. A shared resource is useful only if its availability fits the actual peaks across participating portfolios.

Staggered delivery may be the soundest option when qualified support is unavailable or cannot be supervised effectively. Compare reduced concurrency with escalation, remobilization, temporary service measures and delayed benefits. Funding conditions and contract obligations need confirmation before dates change. None of these options is automatically cheapest.

Cost the coordination model without hiding the administration’s work

Build a capacity budget alongside the capital budget: internal time and backfill; external support; procurement and contract administration; travel and community engagement; reporting; commissioning; and transition into operations. Separate incremental cash expenditure from the opportunity cost of existing staff time. Do not count the same salary twice simply because a person works on several projects.

Allocate shared support using a defensible basis such as the work performed or time required, consistent with the relevant funding agreements. A percentage of project value may obscure the burden of a small but complicated investment. Confirm eligible costs with each funder; the presence of a coordination budget does not establish reimbursement entitlement.

Compare the cost of support with identified consequences of delay or poor oversight, using ranges where uncertain. Avoid promising that a coordinator “pays for itself” unless the evidence supports the claimed avoided cost. Some support is justified by service continuity and decision reliability even when a cash return cannot be calculated.

Implement a small coordination routine that changes decisions

First two weeks: the administrator and project leads compile the next decisions, reconcile dates and examine a small sample of delayed items. Finance validates capacity and payment obligations; the operating owners identify handover requirements. The sponsor resolves conflicting priorities using the Nation’s existing delegation arrangements.

Next four weeks: test the release framework on the actual pipeline. Hold one short cross-project review of exceptions, dependencies and capacity collisions. Maintain one decision log with an owner and due date for each action. Bring Council the choices requiring its authority, rather than every operational status detail.

After the first cycle: compare estimated and actual review effort, adjust sequencing and decide whether permanent or temporary support is warranted. Preserve a concise handover pack covering scope, decisions, funding conditions, contacts and unresolved risks. The purpose is continuity when a person changes, not an additional report nobody uses.

Measure overdue decision-ready items, rework, missed contractual dates, unapproved scope changes and commissioning acceptance. Pair those indicators with service outcomes and staff workload. A falling count of active projects is not success if essential needs are simply deferred; a green dashboard is not credible if it excludes known blocked dependencies.

When this approach is insufficient

Capacity planning cannot cure an unsafe asset, an unresolved rights or land issue, or a structural funding shortfall. A highly specialized project may require technical assurance beyond what a small generalist team can provide. Emergency action follows the applicable emergency authorities and safety advice. Use the framework to expose these dependencies and secure the appropriate response, not to relabel them as ordinary scheduling problems.