A weak subcontractor list doesn't just slow you down — it costs you bids, margin, and sometimes the project itself. When you're assembling a bid and realize your go-to mechanical sub retired, your backup is maxed out on another job, and you've never prequalified the third name on your list, you're not estimating anymore. You're gambling.
Knowing how to build a subcontractor database that actually functions is one of the highest-leverage things a GC can do for their business. Not because it's glamorous admin work, but because it directly determines who you can call, how fast you can bid, and how much default risk you're carrying on any given project. The contractors who win consistently don't have better instincts — they have better systems.
This guide walks you through seven steps to build that system from scratch, or fix the one that's already broken.
Step 1: Define What Your Database Actually Needs to Do
Many GCs fail at this step before even opening a spreadsheet. They build a contact list — names, phone numbers, maybe a trade category — and call it a database. Then nobody uses it because it doesn't answer the questions people actually ask: *Can this sub bond a $4M scope? Did they perform on the last job? Are they licensed in this county?*
Before you pick a tool or design a field, decide what jobs this database has to do.
Bidding vs. prequalification vs. performance: three different jobs
A database you use to pull bid invite lists needs fast filtering by trade, geography, and capacity. A prequalification database needs financial documents, EMR ratings, bonding limits, and license verification. A performance database needs project-level scores tied to specific subs and specific supers.
These aren't the same tool. Conflating them creates a bloated record that estimators ignore and PMs never update. You don't need three separate systems — but you do need to design your records with all three use cases in mind from the start.
Who on your team will actually use it — and how often
The estimator-PM-super handoff is where most sub databases die. The estimator builds the list, the PM uses it to award contracts, and the super never sees it — which means the field-level intel about which subs actually show up, which ones fight every RFI, and which ones clean up after themselves never makes it back into the record.
If your super has been framing for 20 years, he can tell you in 30 seconds which concrete sub you should never call again. The problem is nobody asks him until after the bid goes out. Build your database workflow to capture that knowledge, not just the estimator's contact list.
Step 2: Source Your Subcontractors Before You Build Anything
Data quality is everything. If you populate your database with whoever emailed you a flyer last month, you've built a liability, not an asset. Knowing how to find subcontractors across multiple channels — and filtering for quality before they go in — is what separates a working database from a bloated contact dump.
Mining your own project history first
Your fastest and richest source of sub data is already sitting in your email, your accounting software, or your old bid files. Most GCs have three to five years of awarded subcontracts with real performance signal attached — who finished on time, who submitted change orders on everything, who you'd call again tomorrow.
Start there. Pull every sub you've paid in the last three years, cross-reference with your project managers on who performed, and you've got a pre-filtered starting list that already has implicit quality screening baked in.
Finding new subs: plan rooms, trade associations, and bid platforms
When you're expanding into a new trade or geography, you need external sources. AGC chapters are useful for mechanical and electrical subs in most metro markets. SMACNA and NECA maintain contractor directories by region that are worth bookmarking. For civil and specialty trades, state licensing boards often have searchable databases.
On the digital side, iSqFt and BuildingConnected both maintain sub networks you can search by trade and zip code. BuildingConnected is particularly strong for GCs already using it for bid management — the network data and your invite history live in the same place. For smaller regional markets, local plan rooms and supplier referrals still outperform any platform.
Step 3: Run a Subcontractor Prequalification Process — Not Just a Form
Prequalification isn't just about collecting paperwork. If you're filing forms without reviewing them, you're performing 'risk theater' rather than actual vetting.
A real prequalification process uses the data to make a decision: approved, conditional, or not approved. And it has a workflow that flags when that decision needs to be revisited.
What a prequalification form should actually ask
The core fields that actually predict default risk are: Experience Modification Rate (EMR), bonding capacity relative to your typical scope size, current backlog as a percentage of annual revenue, active license and insurance verification, and references from at least two projects of similar type and dollar value.
EMR is the single most predictive safety metric available to GCs without a full audit. An EMR above 1.2 should trigger a conversation before approval, not a rubber stamp. OSHA's data consistently shows that contractors with elevated EMRs have higher incident rates — and incidents mean schedule disruption, which means your project absorbs the cost.
Free prequalification form templates vs. building your own
You don't need to build a prequalification form from scratch. The AGC publishes a standard prequalification questionnaire, and ConsensusDocs offers template language that's been vetted by industry legal counsel. Both are reasonable starting points.
What you customize is the threshold logic — the point at which a sub's answers trigger a conditional approval or a rejection. A $500K electrical scope has different risk tolerance than a $4M mechanical scope. Your form should reflect that, which means the thresholds, not the fields, are what you're really designing.
When to re-prequalify and how to flag stale records
Prequalifying a sub once in 2019 and treating that as current is one of the most common failure modes in subcontractor management. A company's financial position, bonding capacity, and EMR can change dramatically in 12 months — especially after a bad project or a key person departure.
Set a re-prequalification trigger tied to two conditions: time (annual for any sub you've used in the last 24 months) and project size (any scope over your defined threshold requires fresh financials regardless of when they last prequalified). Flag stale records automatically if your tool supports it, or build a quarterly audit into someone's calendar if it doesn't.
Step 4: Structure Your Subcontractor Database Fields So It's Actually Searchable
A database you have to scroll through manually is just a slow spreadsheet. The whole point of structure is that you can pull a targeted list in under five minutes — every licensed plumber in a 50-mile radius with a bonding capacity over $2M and a performance score above 3.5 — without touching a filter more than twice.
Core fields every subcontractor record needs
At minimum, every sub record should carry: company name, primary contact and direct line, trade category using CSI Spec Sections Construction codes, state license number and expiration, insurance certificate expiration, bonding limit, prequalification status and date, and last-used date with project reference.
The last-used date is underrated. It tells you immediately whether a sub is active in your market or whether the contact is two years stale. A record with no project activity in 36 months should be flagged for re-verification before you invite them to bid.
Tagging for bid invites: geography, project type, and capacity tier
Beyond the core fields, you need tags that let you filter for bid invite purposes. Geography tags should go down to the county or metro level — a sub licensed in your state but based four hours away is a different risk profile than a local crew. Project type tags (healthcare, multifamily, industrial, ground-up vs. renovation) help you match subs to scope complexity. Capacity tier tags (small, mid, large relative to your typical project sizes) keep you from inviting a two-man shop to bid a $6M scope.
This tagging structure is what turns a database into a decision-support tool. Without it, you're back to scrolling.
Step 5: Attach a Subcontractor Agreement Template to Every Approved Record
Your database shouldn't stop at contact and prequalification data. Once a sub is approved, their record should link directly to the subcontractor agreement template that applies to their trade and scope size. This closes the gap between "approved to bid" and "ready to execute" — and it's a gap where a lot of GCs lose time and expose themselves to risk.
What your subcontractor contract template must cover to limit default exposure
Subcontractor default in construction is more common than most GCs want to admit. According to Surety & Fidelity Association of America data, subcontractor defaults account for a significant share of construction bond claims — and the contracts that hold up best in default scenarios are the ones that defined scope, schedule, and payment terms with precision before work started.
Your subcontractor contract template language should address at minimum: a detailed scope of work with exclusions explicitly listed, schedule milestones with liquidated damages tied to specific dates, your payment terms (pay-when-paid vs. pay-if-paid, and your state's enforceability rules for each), termination for convenience and termination for cause clauses, and insurance and indemnification requirements that match your owner contract upstream.
The scope definition clause is where most subcontractor defaults actually begin — not at the payment dispute, but six weeks earlier when two parties realized they had different assumptions about what was included.
Keeping templates current without a legal review every time
Contract law changes. Lien rights, pay-if-paid enforceability, and indemnification limits shift at the state level more often than most GCs track. Running a 2021 subcontractor agreement template on a 2025 project isn't just sloppy — it can void clauses you're counting on.
Build a versioning system: date-stamp every template, assign ownership to one person (usually your ops manager or in-house counsel if you have one), and schedule an annual legal review. The review doesn't need to be a full redraft — a one-hour call with your construction attorney to flag any state-level changes is enough to keep your templates defensible.
Step 6: Build a Subcontractor Performance Scorecard Into the Workflow
The database only compounds in value if information flows back into it after every project. A subcontractor performance scorecard is how you close that loop — and how you manage subcontractors over time rather than just at the point of hire.
One GC we spoke with on a $14M school renovation put it plainly: "We had a framing sub we'd used for years. Great price, always competitive. But our supers had been complaining about their punch list performance for two years. Nobody had written it down anywhere. We re-invited them, same problems, and it cost us three weeks at the end of the job." The scorecard exists to make that institutional knowledge durable.
What to score and who scores it
Keep the scorecard simple enough that it actually gets filled out. Five categories work well: schedule adherence, quality of work, communication and responsiveness, safety compliance, and change order behavior. Rate each on a 1–5 scale, weight them based on your priorities, and require sign-off from both the PM and the super within 30 days of substantial completion.
The 30-day window matters. After 60 days, the details blur and scores drift toward the middle. You want the score completed while the project is still fresh.
Using scores to tier your invite list — not just to punish bad subs
Reframe the scorecard as a bidding tool, not a complaint log. Subs with scores above 4.0 get first-round invites on your most competitive bids — the ones where you need reliable coverage and can't afford a scope gap. Subs scoring between 2.5 and 4.0 get invited when you need additional coverage or a second price. Subs below 2.5 get flagged for PM review before any re-invite goes out.
This tiering system means your best subs know they're getting consistent work from you, which improves your relationship and your pricing. Subs who perform get rewarded with access. That's how you manage subcontractors over time rather than starting from scratch on every bid.
Step 7: Choose the Right Tool to House It All
The best database structure in the world fails if it lives in a tool your team won't open. The right tool depends on your bid volume, team size, and how integrated you need the sub database to be with your estimating and project management workflow.
Spreadsheets: still viable under a certain volume
A well-structured Google Sheet or Excel file is genuinely sufficient for GCs running fewer than 20 bids per year. You can implement all the fields and tagging logic described above in a spreadsheet — it just requires discipline on data entry and a clear owner.
The breakdown happens at scale. Version control becomes a problem the moment two estimators are editing the same file. Search gets slow when you're filtering across 400 records. And there's no automated flag for expired insurance certificates or stale prequalification dates. If you're growing, plan your migration before the spreadsheet breaks, not after.
Dedicated platforms: Procore, Buildertrend, BuildingConnected, and Bidi
Procore's vendor management module handles sub records, insurance tracking, and document storage reasonably well, but it's priced for mid-to-large GCs and the learning curve is real. If you're already on Procore for project management, it's worth using — if you're not, it's a heavy lift just for sub database purposes.
Buildertrend's subcontractor portal is better suited to residential and light commercial GCs. It handles communication and document sharing cleanly, but the prequalification and performance scoring functionality is thin compared to what a purpose-built tool offers.
BuildingConnected's strength is the network — it's the largest digital bid network in North America, and if you're inviting subs to bid at volume, the pre-populated sub profiles save real time. The gap is on the performance tracking and contract management side.
Bidi approaches the problem differently. Rather than bolting a sub database onto a project management platform, it's built around the bid management workflow — so the sub records, bid invites, and leveling all live in the same place. If your primary pain point is running faster, more organized bids with better sub coverage, see how Bidi handles subcontractor management before you commit to a heavier platform.
Frequently Asked Questions
What fields should I include in a subcontractor database?
At minimum, every record needs company name, primary contact and direct phone, trade category (CSI MasterFormat code), state license number and expiration date, insurance certificate expiration, bonding limit, prequalification status and date, and last project date with a reference. Beyond that baseline, add geography and project type tags for bid invite filtering, and a performance score field that updates after each project. The fields you skip are usually the ones you wish you had when a sub defaults or a bid goes sideways.
How often should I update subcontractor prequalification?
Annual re-prequalification is the right cadence for any sub you've used in the last 24 months. For subs you haven't used recently, re-prequalify before any new invite goes out. You should also trigger a fresh prequalification any time a sub is being considered for a scope that exceeds your standard project size threshold — a sub that was financially solid on a $500K scope may not have the capacity or bonding for a $3M one. Stale prequalification data is one of the most common contributors to subcontractor default risk.
What should a subcontractor prequalification form include?
A solid prequalification form covers five core areas: safety record (EMR for the last three years), financial capacity (bonding limit, current backlog as a percentage of annual revenue), licensing and insurance verification, references from two or more projects of similar type and dollar value, and any active litigation or claims history. Free starting templates are available from the AGC and ConsensusDocs — customize the approval thresholds based on your project size and trade risk profile rather than rebuilding the form from scratch.
How do I find subcontractors when entering a new market?
Start with the local AGC chapter — most maintain contractor directories by trade and geography. State licensing board databases are publicly searchable in most states and give you a verified list of licensed contractors by trade. Digital platforms like BuildingConnected and iSqFt have sub networks you can filter by zip code and trade. Supplier referrals are underrated: the local lumber yard, electrical distributor, or mechanical supplier knows who the active, creditworthy contractors in their market are. Combine two or three of these channels before you start inviting anyone to bid.
What causes subcontractor default in construction, and how do I prevent it?
Subcontractor default typically traces back to one of three root causes: underbidding the scope (the sub priced the job wrong and runs out of money mid-project), capacity overextension (the sub took on more backlog than their team and cash flow can support), and scope ambiguity (the contract didn't define who was responsible for what, and the dispute escalates into a work stoppage). Prevention starts at prequalification — checking backlog-to-revenue ratios and bonding capacity — and continues into the contract, where tight scope definition and clear milestone language reduce the ambiguity that fuels disputes. A performance scorecard that tracks early warning signs like communication breakdowns and missed submittals can also flag a struggling sub before they're in default.
Is a spreadsheet good enough for a small GC's subcontractor database?
Yes, with conditions. If you're running fewer than 20 bids per year and your team is two or three people, a well-structured Google Sheet with consistent data entry discipline is a legitimate tool. The problems start when you scale: multiple editors create version control issues, manual filtering across hundreds of records gets slow, and there's no automated alert when an insurance certificate expires. Build the spreadsheet with the same field structure you'd use in a dedicated platform — that makes migration easier when the volume justifies it.
Build the Asset, Then Let It Compound
Learning how to build a subcontractor database is really learning how to turn every project into future leverage. Every sub you score, every prequalification you update, every contract template you version — it all feeds the next bid. The database doesn't just organize your contacts. It sharpens your pricing, reduces your default exposure, and tells you in five minutes who to call when a scope hits your desk at 7 AM.
The GCs who build this right don't start over on every bid. They pull a filtered list, send targeted invites, and spend their time leveling bids instead of tracking down certificates of insurance.
If you want to see how this works in practice without building it in a spreadsheet, explore how Bidi helps GCs manage subcontractor bids and build a searchable sub database — from invite to award, in one place.
*Reviewed by Baylor Jeppsen, Construction Estimating Expert and Founder of Bidi Contracting.*
