AI-assisted construction estimate workbook import: review before commit

A spreadsheet is a calculation system, not just a table

Construction estimate workbooks contain headings, hidden rows, formulas, subtotals, units and notes that may not fit a standard import. AI can help identify structure and propose line mappings, but it must not turn every visible number into a sellable item. The safe workflow separates file review from the final import.

This is one of seven practical workflows in our guide to AI features in construction management software: AI prepares a traceable proposal, while the estimator controls what becomes part of the calculation.

Store the original workbook and record uploader, project, version and intended destination. Scan each relevant sheet and show which ranges were read. Flag hidden sheets, merged cells, formula errors, external links and unsupported units. Do not evaluate macros or follow instructions embedded in the document as if they were trusted commands.

Build a reviewable proposal

Extract code, description, quantity, unit, material cost, labour, margin or selling price only when those columns are supported by the source. Preserve the row and sheet reference for every proposed line. Reconstruct heading and subtotal hierarchy separately from billable items.

Compare calculated totals with workbook totals, but explain differences caused by rounding, excluded rows or formulas. A matching grand total does not prove every mapping is correct. Highlight duplicate codes, zero quantities, text in numeric fields and prices without currency or effective date.

Confirm the calculation version

Let an estimator correct units, hierarchy, tax-independent pricing assumptions and item-library matches. Keep unmapped rows in an exception list. The reviewer chooses whether to create new items, link existing ones or leave a source row out. Record those decisions so a repeated import does not silently make different choices.

The current Alfie registry contains review_calculation_workbook_import and import_calculation_from_workbook. Source tests keep these flows web-only, where the workbook and proposed structure can be inspected. Do not claim that this import is available through WhatsApp or that Alfie approves the estimate autonomously.

Commit once and retain the source

Import the confirmed proposal as a named calculation version. Use an idempotency or file fingerprint check to prevent accidental repeats. After commit, show created and skipped records and keep a route back to the source row. Further estimator edits belong to the calculation history rather than changing the original import record.

When external AI services process a workbook, assess the exact product, endpoint, contract and retention configuration. OpenAI and Anthropic both document product-specific commercial-data controls; a provider name alone does not establish zero retention or suitability.

Read the guide to migrating from Excel, construction estimating software and Alfie.

Sources: current Alfie actions and tests; OpenAI API data controls; Anthropic commercial retention, checked 1 August 2026.