How to Track Engineer Spec History
Building and maintaining a record of which engineers spec which products, and using that data to prioritize your territory.
Engineer spec history is a structured record of which engineers specify which products, on which projects, over time.
It tells you who specs your products, who specs competitors, and how those patterns shift. Most reps keep this in their heads. The good ones keep it in a CRM. The problem is it walks out the door when they leave.
What engineer spec history actually looks like
For each engineer or firm, you want to track: which products they spec as basis of design, which they list as alternates, which projects they've worked on recently, whether their preferences have shifted.
The specificity matters. "Smith Engineering specs our chillers" is useless. "Smith Engineering specs Trane chillers on 7 of their last 10 projects. They switched to Carrier on the last 2. That's a signal." — that tells you where to allocate spec support effort.
A typical engineer record contains:
- Engineer or firm name. The individual (John Smith, PE at Smith Engineering) or the firm (Smith Engineering PC).
- Product category. Chillers, boilers, switchgear, pumps, fans, etc.
- BOD manufacturer. What they spec as basis of design for that equipment type.
- Alternate products. What they list as acceptable equals.
- Recent projects. Project name, date, whether your product was BOD, alternate, or none.
- Preference trend. Stable, shifting, or new firm.
Without this structure, you're working from memory, incomplete notes, or tribal knowledge that doesn't transfer when someone leaves.
Why this data matters for territory strategy
Basis of design position is the strongest competitive position on a project. When your product is BOD, the contractor's path of least resistance is to buy what the engineer already approved. Substitution adds friction, schedule risk, and potential rejection.
Knowing which engineers favor your products tells you where your spec support team is winning. Knowing which engineers are drifting toward competitors tells you where to intervene.
This is the difference between territory management based on gut feel and territory management based on data. Instead of "I think Jones & Associates might be worth a call," you know "Jones & Associates specs Trane 60% of the time. They switched to Carrier on 3 of the last 4 projects. We need spec support time there."
Territory intelligence also reveals competitive gaps. If a competitor is consistently winning BOD position with particular engineering firms, that's where you should target spec support visits and product education. If you're getting listed as alternate but not BOD, you know the relationship isn't strong enough yet.
How reps track this today
Most reps track engineer preferences in their heads. Some keep messy CRM notes. A few maintain spreadsheets. The problem is this approach is inconsistent, incomplete, not searchable, and disappears with turnover.
A new rep inheriting a territory with zero engineer history spends 2–3 years rebuilding what the previous rep knew intuitively. Meanwhile, relationships that were strong atrophy because no one documented them. Specifications that were shifting toward a competitor go unnoticed until it's too late.
Manual tracking also creates silos. One rep might know Engineer A prefers your brand, but that knowledge doesn't propagate to other reps covering adjacent territory. When Engineer A moves firms or gets promoted, the institutional memory disappears.
The reps who do keep organized records often maintain spreadsheets with rows for each engineer and columns for product categories, BOD preference, recent projects, and notes. But these spreadsheets are static. They require manual entry after every project. Most reps don't maintain them consistently.
Building a structured spec history
To track engineer preferences systematically, you need a minimum dataset for each engineer or firm:
- Engineer name. First and last name, credentials (PE, FAIA, etc.), current firm.
- Firm name. The design firm where they work.
- Equipment category. Chillers, boilers, cooling towers, switchgear, etc.
- BOD manufacturer. What they spec for that category.
- Project name. The specific project where you observed this spec.
- Date. When the project was designed (or when you observed the spec).
- Outcome. Won (we were BOD or alternate and got the order), lost (competitor was BOD or alternate), or no participation.
Over time, this builds a map of your territory's competitive position. You can see which firms consistently spec your products, which prefer competitors, and where the relationship is vulnerable.
The data also reveals patterns: "Engineers at design firms in the northeast corridor spec Trane 70% of the time. Engineers in the southeast favor Carrier." Or: "Hospitals consistently spec York. K–12 schools split between Trane and Carrier." These patterns guide where to place spec support effort.
What changes with automated tracking
When bid triage software automatically extracts basis of design designations from every bid your team handles, the spec history builds itself. You don't need reps to manually enter data. You don't need a spreadsheet updated quarterly.
Each project that goes through your system adds to the dataset. Over 100 projects, you have a reliable record of which engineers specify which products. Over 500 projects, you have a competitive map of your entire territory.
New reps inherit the full specification memory layer on day one. They can search for all projects where Smith Engineering was the design firm. They can see that Smith specs Trane 80% of the time but has drifted to Carrier on the last 2 projects. They can identify which engineering firms are worth a spec support visit based on frequency and shift patterns.
Automated tracking also catches shifts that manual tracking misses. A rep might notice that Firm A stopped specifying your products entirely. But if the rep left, or the data was in a spreadsheet that wasn't updated, no one notices until the pattern is entrenched. With continuous tracking, trend shifts appear in real time.
Using spec history for targeting
With a structured spec history, territory targeting becomes systematic:
- Sort engineers by frequency. Identify which firms are the largest BOD specifiers of equipment your company manufactures. The engineers and firms that specify your category most often are your highest-value relationships.
- Look for shifts in BOD patterns. Identify firms that were strong BOD specifiers but have drifted toward competitors. These are intervention points. A spec support visit might re-establish the relationship before it erodes further.
- Identify new entrants. Some projects bring in engineers who haven't been in your database before. These represent new relationship opportunities.
- Assess relationship health. An engineer that was BOD for 10 straight projects but isn't BOD on the last 2 might indicate a relationship problem, or might reflect project requirements. The data flags it for follow-up.
- Identify alternate-only positions. When you're consistently listed as alternate but not BOD, you know the relationship is weaker. You need more spec support or a different positioning strategy.
The reps who manage territory effectively use this data to prioritize. They identify the 10–15 engineering firms in their territory that specify the most equipment in their category. They focus spec support on those firms. They track shifts and respond when a firm starts drifting to a competitor.
This is the data that turns territory management from gut feel into repeatable decisions.
Frequently Asked Questions
What is engineer spec history?
Engineer spec history is a structured record of which engineers specify which products, on which projects, over time. It tracks the basis of design manufacturer, alternate products, and project details for each engineer or firm. The record reveals patterns: which engineers favor your products, which prefer competitors, and how those preferences shift.
Why does engineer spec tracking matter for reps?
Basis of design position is the strongest competitive advantage on a project. Knowing which engineers spec your products as BOD tells you where your spec support effort is working. Knowing which engineers are drifting toward competitors tells you where to intervene. This data turns territory management from gut feel into repeatable decisions.
How do most reps track engineer preferences?
Most reps track engineer preferences mentally. Some keep CRM notes. A few maintain spreadsheets. The problem is this is inconsistent, incomplete, not searchable, and walks out the door when the rep leaves. A new rep inheriting the territory starts from zero and spends 2–3 years rebuilding institutional knowledge.
Can spec history tracking be automated?
Yes. When bid triage software extracts basis of design designations from every bid automatically, the spec history builds itself. Every project adds to the dataset. New reps inherit the full history on day one. The result is a searchable, permanent record that grows with every bid.
Related guides
- Construction agent memory layer
- Bid triage automation
- What is basis of design?
- AI agent for manufacturer reps
- Manufacturer rep bid management
BuildVision tracks engineer spec patterns across your projects and surfaces the insights your reps need for territory prioritization. Start free or see how it works.