An Aurigo capital-plan rank is not appropriation authority

Make the rank a reproducible recommendation

Aurigo's official page establishes current positioning across capital planning, prioritization, program delivery, and financial control. A ranked list can organize a portfolio, but it should remain a recommendation until the authorized body acts. Preserve the candidate population, eligibility rules, scoring criteria and weights, input values and sources, scenario assumptions, dependencies, constraints, model or formula version, run time, analyst, reviewer, and reasons for overrides or exclusions.

Test how the rank changes when cost, schedule, asset condition, risk, demand, regulatory need, community impact, grant timing, or delivery capacity changes. Missing and disputed evidence should remain visible rather than defaulting to a neutral score. Ties, mutually dependent projects, mandatory work, sunk commitments, geographic or program constraints, and projects that cannot be split need explicit treatment outside a simple ordered list.

Separate planning capacity from funding authority

A high rank does not create budget, appropriation, grant eligibility, debt capacity, or authority to contract. For each candidate, map the funding source, fiscal period, legal entity, eligible costs, matching requirements, restrictions, expiration, reimbursement conditions, prior commitments, contingencies, and accountable finance owner. Distinguish planning estimates from an adopted capital plan, appropriated amount, encumbrance, executed contract, notice to proceed, and paid cost.

The approval record should identify the governing agenda or workflow, decision-maker, date, approved amount and scope, conditions, dissent or deferral where relevant, and source document. If a project moves up or down after approval, retain both the earlier decision and the new evidence. A user changing a dashboard status should not silently rewrite the legislative, board, executive, or delegated action that actually controls spending.

Carry the plan into delivery without losing the boundary

Once authorized, link the selected project to its baseline scope, estimate, funding, schedule, procurement strategy, contract, change authority, forecasts, payment, and benefit or service measures. Reconcile portfolio totals to approved funding and commitments by source and period. A planning rank should not become the project identifier, and a later cost forecast should not automatically change the authorized budget or the comparative evidence used to select the project.

Test an estimate increase after ranking, a grant award below the assumed amount, an ineligible cost, a delayed appropriation, a project split across fiscal years, a dependency that fails, and an emergency project inserted outside the normal cycle. The control should show the affected portfolio, require the right approval, preserve the former scenario, and identify which downstream commitments may proceed. Measure decision latency, evidence gaps, overrides, funding shortfalls, and variances separately from the platform's workflow completion.

Read Aurigo's claims within the evidence boundary

Aurigo's official record supports the provider's positioning for capital planning, portfolio management, funding and reimbursement workflows, grants, estimating, construction management, asset condition, analytics, documents, workflow, integration, and security. It does not establish a customer's data completeness, ranking validity, legal authority, appropriation, grant eligibility, estimate accuracy, procurement compliance, project delivery, financial result, or public value.

Contractor Systems Index reviewed the official page on September 2, 2026. No dated material development after the September 1 publication cutoff was established, so this is durable capital-control analysis rather than a current-intelligence event. A buyer test should reconstruct one project from candidate evidence through score, scenario, override, governing approval, appropriation, funding conditions, procurement, commitment, delivery variance, and later portfolio reforecast.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Contractor Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.