Replace “waiting for approval” with a decision that can be acted on

A project can accumulate drawings, meetings and revised estimates while its construction start remains uncertain. The activity is visible; the controlling condition may not be. Additional design work might be essential to answer a technical question. It might also be advancing a solution whose site, service capacity, operating resources or funding has not been resolved.

Arcus’s central analytical proposition is that pre-construction recovery should be organized around the binding unresolved decision, rather than the percentage of documentation completed. A binding condition is one whose absence prevents the next authorized step. Removing it must change what can happen next. If it does not, the team has either identified a secondary constraint or omitted another prerequisite.

This does not mean there is always one bottleneck. Several conditions may jointly prevent progress. Nor should legitimate community deliberation, environmental review or professional assurance be treated as administrative waste. The task is to distinguish necessary work from avoidable rework and unexplained waiting, with the Nation retaining authority over its priorities.

For a community-wide investment sequence, use the related ten-year infrastructure planning framework. This article focuses on recovering one project before a construction commitment.

What the evidence says—and what it cannot establish

ISC’s evaluation of the Other Community Infrastructure and Activities program covered April 2016 to March 2021, with most data collected in 2022. Among 83 survey respondents, 40% disagreed that funding was allocated in a timely manner. The evaluation also identified disruption from staff turnover and loss of institutional knowledge. Its sampling and administrative-data limitations mean these findings cannot identify the cause or likely delay of a particular project today. They do show why “the local team needs to work faster” is an insufficient starting diagnosis.¹

A November 2025 ISC internal audit of education and education facilities found that time-limited funding sometimes pushed prioritization toward projects considered ready to proceed. It also found disconnected information systems requiring manual data sharing. The audit focused on departmental controls and funding activity from April 2020 to March 2023; it is not a study measuring project-level delay causes across all First Nations infrastructure.²

FNII’s May 2023 guidance describes project readiness through strategic, technical, commercial, financial and management cases. This is useful professional guidance, not a comparative evaluation proving that one preparation method reduces delays.³ Taken together, these sources support investigating several dimensions of readiness. They do not validate a universal timetable or a claim that a new tracking tool can overcome an external funding shortage.

Test four competing explanations before choosing a remedy

The evidence needed for a decision is incomplete. Ask the intended reviewer to identify the unresolved question, the required evidence and the acceptance criteria. Compare that request with the latest submission. If there is a specific unanswered technical question, commission work that answers it. If the same question has already been answered and accepted, another study may only duplicate effort.

The evidence is complete, but authority or sequencing is unclear. A file may be moving between parties without anyone accepting responsibility for the next decision. Build a dated history of submission, acknowledgment, requests for clarification and decisions. Identify who has authority and whether their decision depends on another party’s action. Escalation should carry a complete decision request, its consequences and the unresolved dependency—not a general demand for urgency.

The project is ready in principle but financially incomplete. Distinguish an expression of support, a conditional contribution, a signed funding arrangement and money available when invoices fall due. Test the whole project budget, eligibility of proposed costs, timing of receipts and operating commitments. A financing gap requires an authorized funding or scope decision; it cannot be solved by relabelling the project as ready.

The proposed delivery route does not match the market or season. Review documented contractor availability, procurement feedback, long-lead items, access windows and the owner’s capacity to administer the proposed package. A weak market response may reflect scarce capacity, an unclear scope, unsuitable packaging or unrealistic risk allocation. Compare the evidence before deciding to retender, repackage or change the timing. A procurement adviser should assess applicable rules and fairness when the approach changes.

These explanations can coexist. An apparently complete funding request may depend on a design estimate that no longer reflects the intended scope. A contractor’s proposed start may depend on an access arrangement outside the contractor’s control. Record the dependency explicitly so that solving one problem does not produce a premature green status.

A worked example: acceleration that does not advance the start

Consider a fictional community facility. Assume design completion will take six weeks, funding confirmation eight weeks, and a necessary access arrangement twelve weeks. Assume these activities can proceed in parallel, all three must finish before a four-week procurement stage, and no other constraint or seasonal cutoff applies. These durations are illustrative assumptions, not service standards or forecasts.

The earliest construction commitment is therefore after sixteen weeks: the longest prerequisite takes twelve weeks, followed by four weeks of procurement. Paying to reduce design from six weeks to three changes neither the twelve-week prerequisite nor the sixteen-week result. Resolving the access arrangement in seven weeks would move the controlling prerequisite to funding at eight weeks and the possible commitment to week twelve.

The practical lesson is not that design should slow down. Its six-week completion may protect the schedule if another condition resolves sooner, and unfinished design may itself create costly rework. The lesson is to distinguish productive preparation from expenditure advertised as schedule acceleration. Ask which dependency changes and how much of the resulting time is usable.

Suppose an authorized recovery option costs an additional $30,000 and genuinely avoids four weeks of temporary accommodation at $10,000 a week. On those fictional assumptions, the narrowly defined cash benefit is $40,000 and the net benefit is $10,000. If it avoids only two weeks, the net effect becomes a $10,000 additional cost. These calculations exclude other effects, financing, taxes, escalation and non-financial benefits; no probabilities are assumed. They are a sensitivity test, not a business case.

If a seasonal access window is missed, a small change in approval timing could have a much larger consequence. Replace the simple parallel model with a dated schedule reflecting actual access, procurement and mobilization requirements. Ask the relevant professionals to verify those dependencies before using the model to authorize spending.

Compare recovery options by the constraint they remove

Complete a targeted evidence package. This is appropriate when an identified reviewer needs a bounded answer. Authorize a defined scope, cost ceiling and acceptance test. The risk is scope expansion without agreement that the new work will enable the decision. Protect the administration’s time for supplying local information and reviewing the result.

Run independent preparation in parallel. This can shorten elapsed time when work genuinely does not depend on unresolved choices. It also creates expenditure at risk. Identify which designs, investigations or procurement materials remain useful if the preferred site or funding route changes, and which would have to be repeated. Record the maximum exposure leadership is prepared to accept.

Repackage or stage the project. This may help when a smaller deliverable has independent utility and a credible operating arrangement. Compare extra mobilization, interfaces, contract administration and future disruption against earlier service benefits. A stage that cannot function without an unfunded second stage is not an independent solution.

Defer the construction commitment while preserving readiness. This may be appropriate when funding, authority or a necessary prerequisite cannot be resolved on a credible timetable. Maintain evidence that will remain useful, identify information that will expire, and fund essential interim services. Report the unmet need and the reason for deferral openly. Deferral should not quietly become cancellation through loss of records or staff turnover.

Do not assume an alternative delivery method transfers all risk to a contractor. Specify who controls scope, approves changes, manages interfaces and pays when assumptions change. Compare the owner’s recurring oversight workload as well as the professional fees charged at the start.

Keep management readiness separate from required approvals

ISC’s tendering policy effective April 1, 2026 applies to capital projects funded wholly or partly through CFMP and FNIF, with specified exclusions including housing and Health Facilities Program projects. Section 7.8 requires project owners to confirm the contract cost is within budget before entering a contract. Do not apply this policy indiscriminately to every project in the housing and infrastructure portfolio.⁴

The July 2021 Protocol for ISC-Funded Infrastructure requires appropriately qualified professionals for CFMP infrastructure work and explicitly cautions that referenced requirements may change. Confirm the applicable current requirements and funding agreement with the relevant professionals and program office.⁵ A management readiness review coordinates those determinations; it does not replace them.

Before contract award or mobilization, the project owner should receive a concise statement of what has been accepted, what remains conditional, who can authorize the next commitment and the consequences of proceeding. A request to preserve momentum is not evidence that a condition has been satisfied.

Implement recovery without creating another reporting burden

The administrator should appoint a project sponsor with sufficient authority to coordinate the decision record. The project manager maintains the dependency schedule and evidence versions. Technical advisers specify and assess technical evidence; finance confirms affordability, cash timing and exposure; the Nation’s authorized decision-makers approve material scope, funding and commitment changes.

First, reconstruct the current position from existing records and agree the next commitment under consideration. Second, hold a focused review with the people who can resolve the critical conditions. Third, authorize only the necessary recovery work, with owners and acceptance criteria. Finally, review progress at a frequency proportionate to the next decision and actual risk. Preserve a handover record so staff changes do not restart the same discussion.

Useful indicators include time since a complete decision request was acknowledged, unresolved conditions affecting the next commitment, rework caused by changed assumptions, expenditure committed before conditions close, and changes to the earliest credible start. Report why a date changed. The number of meetings held and documents produced are workload measures, not evidence that a construction start is becoming more achievable.

Where the binding issue is a shortage of external funding, the honest result may be a defensible escalation and interim-service decision rather than a faster construction date. That clarity still protects leadership from spending scarce resources on the wrong remedy.

Evidence and source notes

1. ISC, Evaluation of the Other Community Infrastructure and Activities Program, 2016–2021 evaluation period; principally 2022 data collection; page modified September 15, 2025. Sections 3.2–3.3, 5.2 and 6.3. Historical respondent and program evidence with sampling and data limitations.
2. ISC, Audit of Elementary and Secondary Education and Education Facilities, November 2025; page modified June 9, 2026. Sections 2.3 and 3.2. Departmental controls audit; not an independent project-delay comparison.
3. FNII, Shovel Ready: The Steps To Break Ground on an Infrastructure Project, May 10, 2023. Indigenous institutional professional guidance on business-case dimensions.
4. ISC, Policy on tendering for First Nations’ federally funded capital projects, effective April 1, 2026. Sections 4 and 7.8; scope and exclusions matter.
5. ISC, Protocol for ISC-Funded Infrastructure, version dated July 1, 2021. Section 1.1; professional responsibilities and need to monitor updated requirements.

Research reviewed October 19, 2026. The diagnostic, decision record, recovery comparisons and fictional schedule and cost example are Arcus analytical synthesis, not original empirical findings. Evidence does not establish a universal distribution of delay causes or validate forecast savings.