Skip to content
Field notes / Estimating and bid coverage

Construction bid/no-bid checklist: qualify the job before estimating

Screen scope fit, capacity, documents and the decision path before a full estimate. Includes a weighted fictional pursuit example and free qualification worksheet CSV.

By Buildalytic editorial team10 min readUpdated

Download the qualification worksheetFree blank worksheet. No signup required.
Construction managers review unlettered project cards and a capacity planner at a meeting table.
AI-generated fictional pursuit-planning scene. The scorecard, weights and company decisions below are invented examples, not a validated prediction model or customer result.
The short answer

A construction bid/no-bid checklist records whether an opportunity fits your work, whether the team can pursue and perform it, which requirements remain unresolved and who authorizes the decision. Use hard constraints before a weighted preference score. A promising project score should not override an unavailable resource or an unmet requirement that your company treats as a condition of pursuing the work.

What to take away

  • Screen mandatory constraints separately from preferences that can be weighted.
  • Keep confirmed capacity, assumed availability and unresolved questions distinguishable.
  • Give each material unknown an owner, evidence source and decision checkpoint.
  • Record the authorized bid, hold or no-bid decision and its basis before releasing full estimating effort.

Define the decision before opening a full takeoff

An invitation can look attractive because the project is large, close to home or issued by a buyer you want to work with. Those facts do not answer whether your company should spend the next week estimating it. A short qualification review should establish the work involved, the information available, the resources needed and the person responsible for the pursuit decision.

Use the checklist to make that review repeatable, not to replace judgment. A small contractor may discuss the items in one meeting; a larger team may require several approvals. In either case, retain a concise record of the evidence, unresolved questions and decision. The next estimator should not have to reconstruct why a job entered the pipeline.

Procore's bid/no-bid guidance discusses project fit, location, resources and the risks of overcommitting. This article uses those broad considerations as context for an original worked worksheet. The sample weights and thresholds are not research-backed win probabilities. Your company should choose its own criteria and approval process based on its work and actual constraints.

Sources: Procore: Bid or No Bid? How Contractors Should Choose Their Project Bids

Check hard constraints before adding a score

A hard constraint is a condition your company requires before pursuing this opportunity. Examples to investigate include the ability to meet required qualifications, an achievable submission process, essential delivery resources and any project-specific commercial approvals. Identify the actual requirement and decision authority. Do not turn a generic checklist label into an unsupported claim about legal eligibility.

Use pass, unresolved and fail with a source reference. Unresolved means the team still needs evidence or a decision; it is not a soft pass. A failed condition should lead to the action your company has defined, such as no-bid or escalation for a documented change. The scorecard should not average it away with strong marks for project location or buyer interest.

Confirm who can clear each constraint. The operations lead may review crew capacity, the appropriate commercial owner may review contract questions, and the responsible bonding contact may confirm available support where required. The qualification coordinator records those responses. The worksheet does not certify eligibility, issue a bond or interpret the agreement.

Define the work you would actually price

Identify the project, location, trade scope, size and delivery approach using the current invitation and package. Separate your intended scope from the whole project description. A hospital expansion can contain a familiar small package or an unfamiliar specialist system. Fit should describe the work your company would undertake, not simply the building type in the invitation heading.

Record relevant experience with comparable work and the differences that require review. A similar project completed several years ago may be informative, but it does not prove that the same team, equipment or supplier relationships are available now. Ask the responsible people to explain the current delivery approach and any new requirements that change the pursuit effort.

Also identify the estimator and time needed to prepare a responsible submission. If the team can only price the work by abandoning an already approved priority, that tradeoff belongs in the decision. A busy pipeline can hide this cost because every opportunity has a due date, while none records which existing estimate will lose attention.

Compare the proposed work with current commitments

Review the expected work period against actual commitments, using the operations team's current information. Distinguish a tentative window from a confirmed schedule. If the new opportunity overlaps a crew peak, identify the affected resources and ask who can resolve the conflict. Do not enter available merely because the bid has not yet been awarded.

Consider dependencies such as project management bandwidth, specialist suppliers, equipment and any required commercial capacity. Record the source and time of the check. A confirmation can become stale when another project is awarded or a start date moves. Set a recheck trigger where a changed assumption would alter the pursuit decision.

Keep possible mitigations separate from confirmed solutions. Hiring, resequencing, subcontracting or obtaining additional support may be options for the appropriate owner to evaluate. The worksheet should say proposed mitigation until there is evidence for it. A positive scenario should not be reported as the company's committed delivery plan.

Check the package and the route to a decision

List the current drawings, specifications, addenda, required forms and key submission instructions. Identify missing information and the question deadline or clarification route where applicable. A large quantity of documents does not necessarily mean the scope is ready to estimate. Record the specific ambiguity that affects quantities, inclusions, timing or effort.

Autodesk's submission checklist calls for collecting project files, checking instructions and addressing requested information. Those are submission considerations, but they also help frame an early qualification question: can the team obtain and review the necessary inputs in time? Use the actual solicitation to determine what is required; the published checklist is not a universal substitute.

Understand the decision path without inventing a win probability. Identify the buyer, procurement stage, known next checkpoint and your source for that information. A relationship can help the team ask useful questions, but it does not establish an award. If the project status or decision date is unknown, record the uncertainty and assign a fact-finding action.

Sources: Autodesk: Bid Submission Checklist

Use a weighted score to compare preferences

After checking the constraints, score the preference factors using a documented scale. For illustration, use zero to five, where zero means poor fit or no supporting basis and five means strong fit supported by current evidence. Leave a material unknown marked unresolved rather than assigning an optimistic middle score solely to complete the table.

Choose weights that total 100. Multiply each score by its weight and divide by five to obtain weighted points on a 100-point scale. This arithmetic can make preferences easier to compare across opportunities, but the weights are company judgments. A result of 64 does not mean a 64 percent chance of winning or a guaranteed level of profitability.

Keep a short evidence note beside each score. If the team cannot explain why a factor received three rather than four, the number may add little value. Use the discussion to identify the question that matters. The score is a summary of that reasoning, not a way to avoid recording the unresolved decision.

Worked example: a good trade fit with two failed gates

The following pursuit and company policy are fictional. Opportunity C-31 is a familiar trade package near the contractor's normal market. The team assigns the preference scores below. At the same time, the responsible operations lead confirms that the required crew is committed during the proposed peak, and the company's bonding contact reports that the needed support is not available for this pursuit as currently structured.

Under the example company's policy, both are hard constraints. The preference score totals 64 points: 24 for scope fit, 15 for buyer and decision-path information, eight for package clarity, nine for location and logistics, and eight for estimating capacity. That result summarizes preferences but does not clear either failed gate.

The authorized manager records no-bid on the current basis. The record includes the two sources and a condition for reopening: documented resolution of both constraints before the internal decision checkpoint, followed by a fresh approval. Nobody is instructed to begin a full estimate merely because the score is above an invented pass line. No real company's eligibility or capacity is being assessed here.

Worked example: a good trade fit with two failed gates
Preference factorWeightScore / 5Weighted points
Scope and experience fit30424
Buyer / decision-path information25315
Package clarity2028
Location / logistics fit1539
Estimating capacity1048
Total100Not a win probability64

Give unresolved items a bounded next step

For an opportunity that remains on hold, define what information could change the decision and who will obtain it. A scope question should identify the disputed boundary and the required response. A capacity question should identify the period and resource. A commercial question should go to the authorized reviewer rather than wait in a general estimating inbox.

Set an internal checkpoint that leaves enough time for a responsible pursuit decision. Do not create an open-ended investigation with no owner or limit. If the needed answer cannot be obtained before the company's decision point, apply the defined process and record the outcome. The checklist should make the cost of waiting visible alongside the potential opportunity.

Any limited estimating authorized during a hold should have a clear purpose and effort limit. For example, a manager may approve a small scope review to formulate a clarification question. That does not imply approval for the full takeoff. Record what was authorized so the team does not confuse fact-finding with a decision to bid.

Use the qualification worksheet and decision record

The free CSV above includes project, opportunity ID, current package, constraint or preference, requirement source, current evidence, status, score, weight, weighted points, owner, next action, checkpoint, decision and reopening condition. Use separate rows for the hard constraints and preference factors, and mark their type clearly.

Begin with one recently reviewed pursuit and reconstruct only the evidence you actually had at the time. Avoid backfilling a prediction from the eventual result. Ask whether the worksheet would have exposed the most important uncertainty before the estimate started. Then test the C-31 example: the 64-point score should remain visible while the two failed constraints prevent an automatic go decision.

Keep the accepted decision with the opportunity record and communicate it to the people assigning estimating work. If the company declines, notify the appropriate external contact through its approved process when required or appropriate. This guide supplies a planning record; it does not itself authorize messages, commitments or representations to a buyer.

Learn from pursuits without rewriting the evidence

Review the decision process after the outcome is known. Compare the assumptions with actual information, identify which checks were useful and decide whether criteria need adjustment. A lost bid does not automatically prove that the pursuit decision was wrong. A won job does not prove that every capacity assumption was sound. Separate the quality of the original decision from later events.

Track estimating effort and the reason for bid, hold or no-bid with consistent definitions. If the same information gap repeatedly consumes time, improve the intake or question process. If a hard constraint is repeatedly waived, review the policy with its owner. Do not silently weaken the checklist by treating every exception as a new normal.

Buildalytic advertises custom workflows for information requests, response logging, waits and named approvals. A qualification demo can use an unresolved capacity question or missing package record to show how the next response reaches the right person. Keep the pursuit decision and commercial judgment with your authorized team. Do not present the workflow as an automatic bid predictor or eligibility determination.

Sources: Buildalytic custom construction workflows

Common questions

What is the difference between a hard gate and a weighted score?

A hard gate represents a condition your company requires before pursuit. A weighted score summarizes preferences among opportunities. In the fictional example, strong preference factors cannot override failed capacity conditions.

What does a 64-point score mean?

It is the total of the example scores multiplied by their weights and divided by five. It is a company-defined comparison measure, not a 64 percent win probability, return forecast or validated industry threshold.

Can a no-bid decision be reopened?

Define the condition, evidence and approving owner in the original record. If the relevant facts change before the internal checkpoint, conduct the required review and retain both the earlier decision and the new approval.

Sources and editorial notes

Prepared with AI assistance. Reference date: 2026-10-29. Worked examples are illustrative and are not customer results. Product details can change; confirm the current scope and terms before rollout.

How we prepare and update field notes
See it on your workflow

Bring one pursuit with an unresolved decision

Bring a redacted opportunity record and a missing scope, capacity or package response. We will map the information request, responsible owner, checkpoint and named approval while your team retains the pursuit decision.

Start with the call, text or record your team already handles. Review the expected outcome and the human handoff before choosing a rollout.

Request a qualification workflow demo Explore the relevant capability