# Data Readiness

> Data readiness is how complete, consistent, and accessible a construction company's project, pipeline, cost, and staffing records are. It determines whether AI tools can produce useful forecasts and comparisons or confident answers built on gaps.

- Stages: Preconstruction, Forecasting, Workforce
- Concepts: Data
- Published: 2026-08-28
- Canonical: https://buildr.com/library/data-readiness

## Why it matters in construction

AI in precon uses two kinds of data: the documents it reads today and the history it uses for comparisons and forecasts. Document features can work from day one. Historical data is where most GCs find gaps. Win rates cannot be computed if losses were never logged. Staffing forecasts cannot be calibrated if nobody knows how many superintendent hours the last hospital job consumed. Sub matching breaks down when the same sub is entered four different ways.

A model given thin or inconsistent history does not refuse to answer. It answers anyway, with the same confidence, and the errors look like insight. Data readiness is the work of making sure the answers rest on something real.

## How it works

Ask four questions of each data source:

1. **Is it captured?** Pursuits, including the ones the firm lost or declined. Actual staffing hours by project. Final cost by CSI division as well as contract value. Sub performance history, not only contact info.
2. **Is it consistent?** One project type list. One sub master with deduplicated names. One definition of "start date." The model cannot tell that "TI" and "tenant improvement" and "interiors" are the same thing unless someone decides they are.
3. **Is it connected?** A pursuit in the CRM should link to the estimate, which links to the awarded project, which links to actual cost and staffing. Each link is a place where a forecast can learn from an outcome.
4. **Is it accessible?** A model cannot use a spreadsheet on someone's desktop. Data in a system with an API can be connected to the tool.

Most firms should pick the AI use case first, then fix only the data that use case needs. Projects often stall when teams try to clean everything before they start.

## Example in practice

Imagine a $90M/year commercial GC wanting to use AI pipeline forecasting. The CRM has 600 opportunities over five years. On inspection, 410 are wins or active; the 190 losses mostly sit in a "closed" status with no reason, and 80 pursuits were never entered because the BD lead tracked them in a notebook.

The precon director spends three weeks with the BD team backfilling outcomes and reasons for the last three years, standardizing eight project types down from 23 free-text values, and merging 140 duplicate owner records. The resulting dataset covers roughly 350 completed pursuits with outcomes. That is enough for the forecasting model to produce win-rate estimates by project type and delivery method that the team can check against their own memory, and the tool goes live with numbers people trust.

## Go deeper

- [The Real Cost of Disconnected Preconstruction Software](/blog/cost-of-disconnected-preconstruction-software.md)
- [CRM for General Contractors: How to Actually Get Your Team to Use It](/blog/crm-adoption.md)
- [How to Build a Subcontractor Database That Actually Gets Used Across Your Team](/blog/how-to-build-subcontractor-database.md)

## Related terms

- [AI Pipeline Forecasting](/library/ai-pipeline-forecasting.md): AI pipeline forecasting estimates how much construction revenue may convert from active pursuits. It uses historical outcomes to score each opportunity's win probability and timing alongside the BD team's judgment.
- [AI Workforce Forecasting](/library/ai-workforce-forecasting.md): AI workforce forecasting uses pipeline, backlog, and historical staffing data to estimate how many superintendents, PMs, and field crews a construction company will need each month. It gives leadership time to plan for staffing gaps.
- [Structured Data Extraction](/library/structured-data-extraction.md): Structured data extraction uses AI to turn unstructured construction documents, such as sub proposals, RFPs, and specs, into typed fields like line items, prices, exclusions, and dates that can be sorted, compared, and loaded into an estimate or CRM.
- [Hallucination](/library/hallucination.md): A hallucination occurs when an AI language model states something confidently that is untrue or unsupported by the source. For example, it might invent a unit price or an exclusion that does not appear in a subcontractor's proposal.
- [AI-Native vs. AI Bolted-On Software](/library/ai-native-vs-bolted-on.md): AI-native software puts AI models inside its core workflows and data model. Bolted-on AI is usually a separate feature added to an existing product. For a construction firm, the difference affects whether the AI can work with pipeline, estimate, and staffing data or only discuss it.

## Referenced by

- [Activity Capture](/library/activity-capture.md): Activity capture uses AI to log emails, meetings, calls, and site visits against the right contacts and opportunities in a construction CRM. It gives business development teams a usable relationship history without manual data entry.
- [AI Cash Flow Forecasting](/library/ai-cash-flow-forecasting.md): AI cash flow forecasting projects a construction company's monthly cash position from backlog billing schedules, weighted pipeline, historical pay-app timing, and retainage patterns. It can show leadership a potential cash shortfall before it arrives.
- [AI Go/No-Go Scoring](/library/ai-go-no-go-scoring.md): AI go/no-go scoring uses language models and a general contractor's historical pursuit data to rate a construction opportunity against fit, capacity, competition, and margin. It gives the team a consistent basis for deciding which bids to chase.
- [AI Labor Allocation](/library/ai-labor-allocation.md): AI labor allocation matches construction staff to active and upcoming projects using each person's role, experience, location, and availability. It recommends assignments that meet project needs without overloading people.
- [AI Subcontractor Matching](/library/ai-subcontractor-matching.md): AI subcontractor matching uses a general contractor's sub database and bid history to recommend which subcontractors to invite for each trade package on a construction project, based on trade, location, capacity, past performance, and qualification status.
- [Embeddings and Semantic Search](/library/embeddings-and-semantic-search.md): Embeddings are numeric representations of text that place similar ideas near each other even when the wording differs. Semantic search uses them to find construction documents, subs, or past projects by meaning rather than exact keywords, so acoustical ceiling can match ACT and lay-in tile.
- [Fine-Tuning](/library/fine-tuning.md): Fine-tuning further trains an existing AI model on a specific set of examples so it learns a particular style, format, or task. A construction firm might use it to teach a model its conventions for classifying subcontractor scope items.

## FAQ

### Do I need clean data before buying AI software?

Not perfect data, but usable data. Document-reading features work on day one because the documents are the data. Forecasting and benchmarking features need history, and if your history is in personal spreadsheets, that is the first project.

### What is the most common data readiness problem at GCs?

Lost pursuits that were never recorded. A CRM full of wins and no losses cannot teach a model anything about win rates. Second is inconsistent naming: the same sub entered four ways, project types that mean different things to different people.

### How long does it take to get ready?

Weeks, not years, if the goal is usable rather than perfect. Standardize project types and sub names, backfill outcomes on the last two or three years of pursuits, and get actual staffing hours by project from payroll. That covers most of what forecasting tools need.