CONTRACTOR SYSTEMSINDEX

The operating record for construction systems and project controls.

Coverage desk

Estimating & bid control

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

Procore visual comparisons need action-authority lineage

Procore's September 9 acquisition announcement says DroneDeploy can capture jobsites with drones, robots, and cameras while Procore AI compares visual data with BIM and schedule records and surfaces action. Project teams still need the exact capture, comparison method, exception, reviewer, contract role, authorized action, and later result.

ALICE scenario selection needs objective-and-constraint lineage

ALICE describes importing a P6 or Microsoft Project schedule or a BIM model, setting optimization goals and constraints, generating alternatives on a time-cost graph, and selecting or exporting a solution. The chosen scenario still needs a record that explains its inputs, trade-off, authority, schedule promotion, and later variance.

Sequence Enterprise EVM needs a baseline-change ledger

Octave presents Sequence Enterprise, formerly EcoSys, across project controls, planning, scheduling, estimating, earned value, budgeting, and forecasting. An earned-value view still needs a controlled performance baseline and a separate ledger for approved changes before a variance can support a project decision.

Knowify inventory moves need quantity-and-custody proof

Knowify describes tracking materials from purchase through storage, transfers, project or service allocation, job cost, and final use. A system movement does not establish the counted quantity, physical custodian, installed location, contract entitlement, cost treatment, or condition. Reconcile each event to evidence at both ends.

A Dalux handover item needs asset-tag and acceptance lineage

Dalux presents Handover as a way to collect and deliver information to a client and connects it with field, BIM, documentation, facilities, assets, and operations. A completed item becomes useful handover evidence only when it resolves to the installed asset, approved information requirement, inspection and commissioning records, authorized acceptance, and downstream operations receipt.

PMWeb portfolio roll-ups need a comparison contract

PMWeb presents detailed portfolio roll-ups and granular project-level insights for owner-operators. A cross-project total is decision-ready only when its population, purpose, status date, scope, baseline, currency, record states, forecast version, units, formulas, and exclusions are explicit.

A Sage lease option needs an exercise-and-receipt record

Sage says Sage 300 Construction and Real Estate serves property managers and can turn static lease documents into dynamic information while accommodating flexible lease options. A value changed in software does not prove that a party exercised an option through the required channel or that the required recipient received it. Preserve the option, election, delivery, receipt, disposition, and resulting lease version as one reconstructable chain.

Siteline waiver tracking needs execution-and-condition proof

Siteline says it can generate, send, collect, remind on, and track lien waivers alongside subcontractor billing. A tracked status still needs the correct party, form, signature, payment condition, amount, period, and delivery evidence before anyone relies on the waiver.

Sequence 10 document management needs release-and-custody proof

Octave's product preview describes Sequence Enterprise 10 as an upcoming release, slated for summer 2026, with embedded document management for versioned files connected to project work. That announcement is not evidence of general availability or a reason to retire an existing common data environment without custody, migration, workflow, and export tests.

An Aurigo capital-plan rank is not appropriation authority

Aurigo presents Masterworks for capital planning, portfolio prioritization, funding, grants, estimation, construction control, and reporting. Owners still need to connect every project rank to approved criteria, current evidence, funding restrictions, governing decisions, and the specific authorization to commit money.

Acumatica can release change costs before revenue approval—preserve the split

Acumatica's current construction page says its 2026 R1 workflow can release costs before formal approval of the revenue portion. That can represent real field exposure without inventing contract entitlement, but only if directed work, cost commitment, pricing, approval, forecast, billing, and cash states remain separate and reconcilable.

A SYNCHRO 4D sequence is not the controlling project schedule

Bentley describes SYNCHRO 4D as linking schedule and model information to visualize construction sequences; project teams still need baseline, data-date, logic, update, approval, and work-authorization lineage.

A Kahua submittal approval is not authorization to install

Kahua presents a construction project-management platform for owners and delivery teams, and its official support record depicts a routed submittal workflow with review, response, completion, and closure states. An approved or completed submittal status can preserve a review record, but it does not by itself authorize field installation under a project's contract, current documents, role assignments, and release controls.

A Contruent cost forecast is not an approved project budget

Contruent documents construction cost-management software for budgets, work and cost breakdowns, earned value, forecasting, schedules, contracts, invoices, progress claims, change orders, and approvals. A forecast can project an outcome, but it does not change the authorized budget baseline or approve additional spend.

A CMiC commitment record is not an executed subcontract

CMiC documents construction ERP workflows spanning financials, project management, procurement, commitments, subcontracts, purchase orders, changes, and cost control. A commitment entered in the system can support forecasting and administration, but it does not by itself prove contract formation, signatures, notice, scope agreement, or authorization to proceed.

ProjectSight revision management requires evidence of field use

Trimble presents ProjectSight for drawings, revisions, RFIs, submittals, photos, and mobile field access. A platform can identify the current drawing record, but the project still needs evidence that the right field audience received, understood, and worked from that revision before affected work proceeded.

A HeavyBid estimate is not an accepted contract price

HCSS presents HeavyBid as estimating and bid-management software for heavy construction. A resource-based estimate can support a governed bid, but the contract price still depends on the submitted offer, clarifications, negotiations, award, and executed agreement.

AACE’s TCM Framework makes cost control a lifecycle system—not a project module

AACE defines Total Cost Management as a systematic approach to cost across the life cycle of an enterprise, program, facility, project, product, or service. Estimating, planning, scheduling, forecasting, performance measurement, risk, and control are connected practices, so a cost dashboard is only one part of the management chain.

GAO's cost guide keeps estimates reproducible

Scope, assumptions, data, methods, sensitivity, risk, documentation, update, and reconciliation matter more than an estimating interface.

Production planning is not the master schedule

Touchplan and Last Planner workflows operate at different decision horizons from contract and CPM schedules, even when activities and commitments are connected.