A bid pipeline is the list of every job you have been invited to bid, are pricing, have submitted, or are waiting to hear back on, sorted by stage and due date. For an electrical, plumbing, HVAC, masonry or drywall sub, it is the difference between choosing which bids to chase and scrambling to price whatever landed in the inbox this morning. This guide shows how to set one up, what to record on each bid, and how to review it every week.
TL;DR
- Give every invitation one row with a stage, a due date, an owner and a next action. Nothing lives only in an inbox or someone's head.
- Use five to seven stages that match how your shop works, from invited to won or lost.
- Review the pipeline weekly to decide where estimating hours go. Review win rates by GC and job type every quarter.
- Forecast from your own win rate, not from the total dollar value of open bids.
- Spreadsheets work at first. Once invitations come in faster than one person can log them, automated tracking pays for itself.
Table of Contents
- What a bid pipeline means for a trade contractor
- Set up your pipeline stages
- What to record on every bid
- Track due dates so nothing slips
- Decide which bids to chase
- Run a weekly pipeline review
- Forecast workload and revenue from your own numbers
- Keep the pipeline accurate across the team
- Spreadsheet, CRM or purpose-built software
- Where Subascent fits
- Our perspective
- FAQ
- Sources
What a bid pipeline means for a trade contractor
General contractors talk about a pipeline of projects they want to win as prime. You are one level down. Your pipeline is made of invitations to bid from GCs, each one a scope of your trade on someone else's job. You do not control when those arrive, and you often get them from a dozen GCs at once.
That changes the problem. You are not hunting for leads so much as triaging a flow. A masonry sub might get 30 invitations in a week and have time to price eight. The pipeline is how you decide which eight, and how you remember the other 22 exist if a GC calls back.
A working pipeline answers four questions at any moment:
- What is due this week, and who is pricing it?
- What have we submitted and not heard back on?
- What did we say no to, and why?
- How much estimating work is coming that we have not started?
If you cannot answer those in under a minute, you do not have a pipeline yet. You have an inbox.
Set up your pipeline stages
Keep the stages few and clear. Every extra stage is one more thing the team will forget to update. Here is a set that fits most specialty trades:
| Stage | What it means | Who moves it |
|---|---|---|
| Invited | Invitation received, logged, not yet reviewed | Office admin or estimator |
| Reviewing | Plans and scope being checked for bid or no-bid | Estimator and owner |
| Pricing | Takeoff and estimate in progress | Estimator |
| Submitted | Proposal sent to the GC | Estimator |
| Follow-up | Waiting on a decision, with a next contact date | Estimator or PM |
| Won | Awarded, ready to hand to the PM | Owner |
| Lost or passed | Closed, with a reason recorded | Estimator |
Two habits matter more than the stage names. First, every bid has exactly one stage at a time. Second, moving a bid forward is part of finishing the task, not a separate admin chore. When the proposal goes out, the stage changes in the same five minutes.
If you want more on what arrives at the first stage, our guide to what a bid invitation is covers how to read one, and what a bid package is explains what should come with it.
What to record on every bid
The more you record, the more useful the pipeline is at review time. But you also have to keep it up. This is the practical minimum:
- Project name and location. Travel time changes your price and your interest.
- GC and contact. You will want to see win rates by GC later.
- Bid due date and time. Record the time, not just the date. A 2 p.m. deadline is not a 5 p.m. deadline.
- Your trade scope. For example, electrical rough-in and finish, or CMU and brick veneer only.
- Estimated bid value. A rough range at the invitation stage is fine. Replace it with the real number once priced.
- Estimator assigned. One name.
- Addenda received. A missed addendum is a common cause of bad bids.
- Next action and its date. This one field keeps bids from going quiet.
- Outcome and reason. Won, lost on price, lost to a GC's preferred sub, no-bid because of schedule. Be honest.
The documents themselves matter too. Scope and spec requirements drive what you can and cannot price, and trades outside yours show the same pattern: a contractor in underground utilities, for example, publishes how bid documents and specifications should be written so that bidders price the same work. As a sub, read the spec sections for your trade before you commit estimating hours, and note in the pipeline anything that makes the job a stretch.
Track due dates so nothing slips
Missing a bid date rarely happens because someone forgot the job. It happens because the invitation sat in an inbox, the due date moved in an addendum, or two people each assumed the other was handling it.
A few controls fix most of that:
- One intake point. Ask estimators to forward invitations, or route them from a shared address, so the office logs them in one place.
- Log within a day. An invitation not logged by tomorrow morning is a risk.
- Calendar the real deadline and an earlier internal one. Set the internal date a day ahead so there is time to level quotes from your suppliers and review.
- Update when addenda change dates. Change the date in the pipeline first, then tell the estimator.
- Sort by due date. The default view should be "what is due soonest," not "what came in last."
We go deeper on this in how bid due date tracking works for trade subs and in our write-up on bid invitation tracking, which looks at the weekly hours that go into manual logging.
Decide which bids to chase
A pipeline is only useful if it lets you say no. Most trade firms lose money not on bids they lose, but on estimating hours spent on bids they never had a real shot at.
Before a bid moves from Reviewing to Pricing, ask five quick questions:
- Do we know this GC, and have they paid on time?
- Does the scope fit what our crews do well?
- Can we start when the schedule says, or are we already full?
- Is the bid list crowded? Ten subs on a scope usually means thin margins.
- Do we have the estimator hours this week, given what is already in Pricing?
Write the answer in the pipeline. A pass with a one-line reason is useful data. Three months later, you may notice you never win bids from a certain GC, or that your plumbing no-bids all share a travel radius. That is where the pipeline starts to guide strategy instead of just tracking it.
Pass decisions also protect your relationships. Telling a GC early that you cannot bid is better than going silent. Most will invite you again.
Run a weekly pipeline review
Thirty minutes, same time each week, owner and estimator at the table. Walk the pipeline in this order:
- Due in the next seven days. Is each one on track? Does anything need help or a quote chase?
- Pricing. Who has too much? Move work or drop a bid.
- Submitted and waiting. Which ones are more than two weeks past the bid date? Assign a follow-up call.
- Newly invited. Decide bid or pass on each.
- Recently closed. Record outcome and reason, if not already done.
Guidance from construction business consultants lines up with this: review open bids on a weekly cadence to allocate estimating capacity, and revisit your probability assumptions less often, such as quarterly, against what actually happened. That split is practical. Weekly is for workload. Quarterly is for learning.
A worked example
Say a drywall sub has an estimator who can price roughly six mid-sized bids a week. On Monday the pipeline shows:
- 4 bids in Pricing, due Thursday and Friday
- 7 new invitations, due next Tuesday to Thursday
- 9 submitted bids waiting
The owner sees 11 bids competing for six slots of capacity. Three of the new invitations come from a GC who has never awarded the firm anything, and two are across the state. Those five get a pass email. Two of the nine waiting bids are from a GC who usually decides within ten days, so they get a call. The week now has a plan.
Without the pipeline, those 11 bids sit in email, and the estimator starts with whichever one feels loudest.
Forecast workload and revenue from your own numbers
Owners often look at the total dollar value of open bids and feel good. Do not treat that number as revenue. It is a sum of things you might not win.
A more honest forecast uses your own history:
- Calculate win rate by bid type. For example, hit rate on electrical tenant improvements versus new-build ground-up work, or by GC. Use at least a year of outcomes if you have it.
- Weight the open pipeline. If you win about one in five bids on a type, a $400,000 submitted bid counts as roughly $80,000 of expected work.
- Add what is already awarded. Backlog not yet billed is the base. Pipeline is the addition.
- Shift by expected start dates. A job awarded now may not start for four months, so it does not fill your crews this quarter.
This is the same approach construction business advisers describe: combine remaining backlog with probability-weighted new work, rather than using raw bid totals. It will not be exact. It will be far closer than a gut feeling, and it tells you early when you need more bids in the door or more crews on the payroll.
The estimating side of this matters too. Our seven-step subcontractor estimating workflow shows how a bid travels from invitation to job, and how to cut the rework that eats estimator hours.
Keep the pipeline accurate across the team
A pipeline that only one person updates is a single point of failure. A pipeline that five people update loosely is a mess. Fix both with a few rules:
- Estimators own the stage. They know where a bid really stands.
- Office admins own intake and follow-up dates. They are best placed to log invitations and chase answers.
- The PM gets a clean handoff on award. Scope, exclusions, quotes and the GC contact should travel with the job. Our guide to bid proposal exclusions explains why the written exclusions matter when the job starts.
- Foremen feed back what they see. If a foreman visits a site and finds access, phasing or conditions that differ from the drawings, that note belongs on the job and informs the next bid on a similar scope.
- Close the loop. Every submitted bid ends as won, lost or passed. Open items older than a few months are noise.
One trade-specific tip: if you price in different divisions, such as a mechanical sub with HVAC and plumbing under one roof, keep one pipeline with a trade field rather than two separate sheets. You want a single view of estimator capacity. Likewise, bid leveling for masonry and HVAC estimating workflows both feed a shared pipeline so the numbers show up where the owner looks.
Spreadsheet, CRM or purpose-built software
There are three common ways to run a pipeline.
A shared spreadsheet. Free, flexible, and fine when you handle a few bids a week. It breaks when two people edit at once, when nobody sorts by due date, or when invitations pile up faster than anyone types them in.
A general sales CRM. Better for tracking contacts and stages, but built around a sales funnel, not a bid calendar. You end up bending fields to fit due dates, addenda and scopes.
Software built for trade subs. It treats the invitation, due date, scope and estimate as one record, and it connects to the rest of the job: takeoff, estimate, submittals, change orders and billing. That connection is the point. When a bid is won, it becomes a job without retyping it.
The tipping point for most shops is when someone has missed a deadline, or when logging invitations takes a chunk of the office week. If you are there, it is worth a look.
Where Subascent fits
Subascent is job and bid management software built for specialty trade subcontractors. Its bid management tools handle invitation and due-date tracking, and they connect to estimating, PDF takeoff, submittals, RFIs, change orders, daily reports and QuickBooks sync, so a won bid carries into the job without double entry. You can see how it works on the bid management features page and the estimating and takeoff page.
Plans are published on our site: Starter is $49 per month or $490 per year, Scale is $99 per month or $990 per year, and Pro is $179 per month or $1,790 per year. PDF takeoff is available as a separate Takeoff plan at $99 per month. The free CrewTrack mobile app for foremen comes with the subscription. See the current details on the Subascent plans page or start from the Subascent home page.
There is a free trial, so you can load your open bids and see whether your weekly review gets shorter.
Our perspective
We built Subascent because the software on offer assumed everyone was a GC. A sub does not manage a project from the top. A sub gets invited, prices fast, waits, and then runs a scope for someone else.
Most owners we talk to track bids in a mix of email flags, a spreadsheet and memory. It works until it does not. The failure is rarely dramatic. It is a bid that did not get priced because the invitation was buried, or an estimator who spent two days on a job the owner would have passed in two minutes.
Our view is that the pipeline should be the front door to the whole business. The same record that holds the due date should hold the takeoff, the estimate, the exclusions, and then the job budget. When that chain is unbroken, you can see which kinds of bids make money, not just which ones you win.
That is what we designed Subascent to do: keep the bid pipeline simple enough that estimators will use it, and connected enough that the office, the PM and the foreman benefit from it too.
Dave
FAQ
What is the difference between a bid pipeline and a bid log?
A bid log records what happened: who you bid, when, and the result. A pipeline is forward-looking. It shows stage, due dates and next actions for open bids so you can plan workload. Most firms need both, and a good pipeline becomes the log once bids close.
How many stages should a trade contractor's pipeline have?
Five to seven is usually enough: invited, reviewing, pricing, submitted, follow-up, won, and lost or passed. More stages tend to go stale because nobody updates them. Add one only if you will act differently when a bid reaches it.
How often should we follow up on submitted bids?
Set a next-contact date when you submit, based on how fast that GC usually decides. A call one to two weeks after the bid date is common. Record each contact and its answer so the next review does not start from scratch.
Can I run a bid pipeline in a spreadsheet?
Yes, if invitations are few and one person owns the sheet. Include due date and time, GC, scope, estimator, stage and next action, and sort by due date. Move to dedicated software when logging takes real office time or a deadline has slipped.