HubSpot Strategy, CRM Architecture & Marketing Automation Blog | Campaign Creators

What to Record When Leveling Bids and How to Keep It in HubSpot

Written by Campaign Creators | 11/20/26

Bid leveling compares bids on equal scope, so every price reflects the same work before anyone picks a winner. The record should capture each bid's inclusions, exclusions, alternates, qualifications, the adjustments made to level it, and the award decision, stored on the job record next to the awarded party.

That record does three jobs after the spreadsheet closes. It protects the award when a bidder asks why they lost, it answers scope questions during construction, and it shows estimators what to watch for on the next construction bid. This guide covers what general contractors and subcontractors should capture and where each piece lives in HubSpot.

Key Takeaways

  • Record three layers for every scope: each bid as received, the leveling adjustments, and the award decision with its reasons.
  • Keep the leveling math in your estimating tool or spreadsheet, and keep the summary, evidence, decision, and relationships in HubSpot.
  • Store summary values on the deal, attach the leveling sheet, label each bidder's company association, and use a custom object on Enterprise for bid lines.
  • HubSpot Work tables, in public beta, can hold a leveling grid per job with linked CRM records.
  • After award, compare the awarded scope to the leveled scope, and tie change orders back to the original leveling record.

Table of Contents

  1. What Should You Record When Leveling Bids?
  2. What Is Bid Leveling, and Why Keep a Record of It?
  3. What to Capture for Each Bid
  4. What to Capture About the Leveling
  5. What to Capture About the Award Decision
  6. How Does Bid Leveling Differ for GCs and Subs?
  7. Where Does the Leveling Record Live in HubSpot?
  8. Set Up Tasks and Approvals Around Leveling
  9. Keep the Record Useful After the Award
  10. Reports Built From Leveling Data
  11. Frequently Asked Questions

What Should You Record When Leveling Bids?

Record three layers when leveling bids: what each bidder submitted, how your team adjusted each bid to a common scope, and who won and why. Each layer has a different owner and a different home in HubSpot.

Layer What it answers Typical owner
Each bid What did this bidder price, include, and exclude? Estimator who received the bid
The leveling What did we add or deduct to compare bids fairly? Estimator or preconstruction manager who leveled
The decision Who got the work, at what amount, and why? Project executive or procurement lead who approved

The rest of this guide breaks down each layer, shows how the record differs for GCs and subs, and maps every field to a place in HubSpot.

What Is Bid Leveling, and Why Keep a Record of It?

Bid leveling is the process of adjusting several bids for the same scope to one common baseline, so prices compare fairly. It sits between receiving bids and awarding the work.

Leveling is different from the bid itself and from negotiation. The bid is what a bidder submits. Leveling is your internal comparison, where you add the cost of anything a bidder excluded and remove anything extra, so the numbers line up. Negotiation comes after, when you talk to bidders about price or terms.

The invitation to bid and the bid list set the baseline that leveling checks against. The invitation to bid defines the scope, drawings, specs, and addenda each bidder should price, and the bid list records who was invited. A clear invitation makes leveling faster, since every gap shows up against the same scope.

A record helps because the decision outlives the spreadsheet. Months later, a project manager needs to know if firestopping was in the drywall contract, an unsuccessful bidder asks for feedback, or an estimator wants to know which supplier usually excludes freight. A durable record answers each of those in minutes.

What to Capture for Each Bid

Capture every bid as received, before anyone adjusts it: the price, the scope, the terms, and the date. This layer belongs to the estimator who received the bid.

Field What to capture
Bidder and contact Company, estimator name, email, and phone
Date received Date and time the bid arrived
Base bid amount The lump sum for the defined scope
Alternates Each alternate with its add or deduct price
Unit prices Prices per unit for quantities that may change
Allowances Amounts carried for items not yet defined
Inclusions Scope items the bidder confirmed
Exclusions Scope items the bidder left out
Clarifications and qualifications Conditions, assumptions, and limits the bidder attached
Addenda acknowledged Which addenda the bid covers
Bid validity period How long the price holds
Bond and insurance status Bonding capacity and insurance confirmation
Schedule and lead time Start availability, duration, and material lead times

Clarifications, qualifications, and scope notes arrive as free text, and our guide to structured vs. unstructured CRM data covers how to keep that text useful for reporting and HubSpot AI.

Who owns it: the estimator who received the bid.
Sign it's working: every bid on the job has a complete row before leveling starts.

What to Capture About the Leveling

Capture what your team changed to compare bids fairly: the scope gaps, the adders and deducts applied, the resulting level bid, and the open questions. This layer shows how you reached the numbers you compared.

Field What to capture
Scope gaps Items one bidder priced and another left out
Adders and deducts The amount added or removed to level each bid, with the basis for each
Level bid Each bidder's adjusted total after adders and deducts
Assumptions Quantities, pricing sources, or scope interpretations you used
Open questions Clarification requests sent to bidders, with dates and answers
Leveled by and date Who leveled and when

Here's an illustrative leveling sheet for one drywall scope, with sample numbers:

Item Bidder A Bidder B Bidder C
Base bid $412,000 $389,500 $398,000
Exclusions None Level 5 finish at lobby Firestopping
Adder to level $0 $14,200 $9,800
Level bid $412,000 $403,700 $407,800
Alternate 1, deduct ($6,000) ($5,500) Not priced
Lead time to start 3 weeks 6 weeks 2 weeks

Bidder B has the lowest base bid and the lowest level bid. The record shows the $4,100 spread to Bidder C and the reason the decision layer needs to capture next.

Who owns it: the estimator or preconstruction manager who leveled.
Sign it's working: anyone can see why each level bid differs from its base bid without opening the spreadsheet.

What to Capture About the Award Decision

Capture who won, at what amount, and why, plus the reasons other bidders didn't win and who approved the award. This layer protects the decision when anyone asks about it later.

Field What to capture
Low level bid The lowest leveled amount and its bidder
Selected bidder The bidder awarded the work
Award amount The amount in the subcontract or purchase order
Award reason Price, scope fit, schedule, relationship, or capacity, with a short note
Non-award reasons One reason per unsuccessful bidder
Approvals Who approved the award and when

In the illustrative example, the team selects Bidder C at $407,800 because a two-week start fits the schedule and Bidder B's six-week lead time doesn't. The record shows the $4,100 premium and the schedule reason in one place.

Who owns it: the project executive or procurement lead who approved the award.
Sign it's working: the award reason and approval sit on the job record before the subcontract goes out.

How Does Bid Leveling Differ for GCs and Subs?

GCs level several subcontractor bids for each scope on a job, and subs level supplier quotes and their own alternates before submitting a construction bid to a GC. Both need the same three layers, applied to different decisions.

Topic GC leveling subcontractor bids Sub leveling supplier quotes
What gets leveled Subcontractor bids for each scope, such as drywall, electrical, or roofing Supplier and vendor quotes for materials, plus the sub's own alternates
What each side records Base bids, inclusions, exclusions, alternates, bonds, schedule, and level bids per scope Quote amounts, freight and lead time, substitutions, quote validity, and the alternates the sub will offer
Decision Which subcontractor gets each scope Which supplier to carry in the bid, and which alternates to submit
Follow-up Subcontract, scope review meeting, and feedback to unsuccessful bidders Bid submission to the GC, then purchase order to the supplier after award
Where it connects in HubSpot The GC's job deal, with subcontractor companies labeled by role The sub's job deal, with supplier companies labeled by role

Subs often skip the record for supplier leveling, since it happens fast and close to the bid due date. Capturing it pays off when a quote expires before award or a GC asks about an alternate weeks later.

Where Does the Leveling Record Live in HubSpot?

Store summary values as deal properties, the leveling sheet and bid documents as attachments, each bidder as a labeled company association, and line-level detail in a HubSpot Work table or a custom object. Estimating tools and spreadsheets keep the leveling math.

HubSpot Work Tables

HubSpot Work organizes workspaces into projects, and each project holds tables, documents, forms, and AI agents. Per HubSpot's guide to setting up HubSpot Work, it's in public beta, a Super Admin must enroll the account, and each user needs a Core, Sales, or Service seat. HubSpot's guide to collaborating in HubSpot Work notes that teams can update fields, add files, and link CRM records within a table. A table per job, with one row per bidder and a column linking each row to the bidder's company, keeps the grid next to the CRM. Our overview of HubSpot Work tables walks through setup, and our guide to how HubSpot Work uses your CRM data covers what to clean up first.

  • Best for: A leveling grid per job, with rows linked to CRM records

  • Limits: Public beta, so features can change
  • Tier: Starter, Professional, or Enterprise hubs, Smart CRM Professional or Enterprise

Custom Objects for Bid Lines

A custom Bid object gives each bid its own record with base bid, level bid, exclusions, and status, associated to the deal and the bidder's company. HubSpot's guide to creating custom objects notes they need an Enterprise subscription and can carry their own properties, pipelines, and association labels. This option fits GCs leveling many scopes per job who want to report across every bid, and our technology consulting team can help you decide if a custom object is worth the setup.

  • Best for: One record per bid with its own properties, associated to the deal and bidder

  • Limits: More setup, and each bid becomes a record to maintain
  • Tier: Enterprise

Division of Labor

Your estimating tool or spreadsheet does the math: takeoffs, line-item comparisons, and adders. HubSpot holds the summary, the evidence, the decision, and the relationships. Link the two with a Leveling sheet link property on the deal, and confirm any estimating tool connection on the HubSpot App Marketplace and in the vendor's documentation before you plan around it. Our HubSpot integration library lists the connections we've built, and HubSpot integration development covers tools without a listed app.


Associations

Connect each bidder to the deal with a company association and a label: Bidder, Selected bidder, or Supplier. Connect contacts the same way: the bidder's estimator and your project manager. Per HubSpot's guide to creating and using association labels, custom labels need a Professional or Enterprise subscription, and each object pair holds up to 50 labels. Our bid tracker article covers the job data model these associations attach to.


When a Leveling Application Fits

Deal properties, attachments, Work tables, and custom objects cover leveling for most teams. Our team configures them as part of HubSpot CRM architecture work. When a firm needs a leveling application with its own interface, scope-specific rules, permissions, and testing, Brainstem Ventures by Campaign Creators adds custom capabilities that connect to your existing systems. It's a specialized software engineering capability within Campaign Creators, built to keep the systems that work and engineer what's missing.

Bid Leveling Record Table

Every field in the record has one home in HubSpot and one reason to exist. Use this table to set up properties, labels, and attachments before your next leveling round, and give each property a named owner, following our approach to property governance with data contracts.

Field What to capture Where it lives in HubSpot Why you need it
Bidders Every company invited and every company that bid Company associations labeled Bidder Shows the full bid list on the job
Bid documents Each bid as received Attachments on the deal, or files in a Work table row Proves what each bidder submitted
Base bids Each bidder's lump sum Custom Bid object or Work table, plus Low bid and High bid deal properties Shows the starting spread
Inclusions and exclusions Scope items confirmed or left out Custom Bid object, Work table, or the attached leveling sheet Explains each adder
Alternates and unit prices Add or deduct pricing per alternate Custom Bid object, Work table, or the attached leveling sheet Supports later scope changes
Scope gaps and adders What was added or removed to level each bid Leveling notes on the deal, plus the leveling sheet Shows how the level bids were built
Level bids Each bidder's adjusted total Custom Bid object or Work table, plus a Low level bid deal property Compares bids on equal scope
Bid validity Date each price expires Bid validity date property Triggers reminders before prices lapse
Selected bidder The awarded party Company association labeled Selected bidder Keeps the award next to the job
Award amount and reason Amount and the reason it won Award amount and Award reason deal properties Protects the decision
Non-award reasons Why each other bidder didn't win Custom Bid object, Work table, or a deal note Supports feedback and future bids
Approval Who approved and when Pipeline approval history, or an Approved by property Shows the award followed your process

Want a second look at your leveling record? The Architecture Blueprint maps your current HubSpot setup against where it needs to be, including the properties, labels, and objects behind a durable award record.

Set Up Tasks and Approvals Around Leveling

Use tasks for missing clarifications, workflow reminders for expiring bid prices, and an approval step before award. Each one keeps leveling moving without anyone tracking dates by hand.

Tasks for Scope Clarifications

When leveling turns up a scope gap, create a task for the estimator to request a clarification from that bidder, with a due date before the award meeting. Close the task when the answer is logged on the deal.

Reminders for Bid Validity

Store each bid's validity date, and let a workflow create a task a week before the earliest date passes. Per HubSpot's guide to creating workflows, workflows need a Professional or Enterprise subscription.

An Approval Step Before Award

HubSpot's pipeline approvals add an approval stage to a deal pipeline, so a deal can't move past it until designated approvers sign off. Per HubSpot's guide to requiring approvals for deals, the feature needs Sales Hub Enterprise and supports up to 30 approvers per pipeline, and a rejected deal can only move to a closed lost stage. An approval history card on the deal shows who approved and when. On other tiers, record the approver and date in deal properties and require them before the award stage. Short HubSpot training helps estimators and approvers follow the same steps.

Keep the Record Useful After the Award

After the award, compare the awarded scope to the leveled scope, tie change orders back to the leveling record, and share feedback with unsuccessful bidders. The record keeps paying off through construction and into the next bid.

  • Awarded scope versus leveled scope: Confirm the subcontract or purchase order includes every adder you assumed during leveling. A gap here usually shows up later as a change order.
  • Change orders: Link each change order to the original leveling record, so the team can see if the item was excluded, included, or never discussed.
  • Feedback to unsuccessful bidders: Use the non-award reasons to give short, consistent feedback, which keeps good bidders coming back.
  • Win and loss reasons: For subs, log the GC's award result and reason on the job deal. Our article on how bid management software and HubSpot track hit ratio covers how to count those results.

Reports Built From Leveling Data

Leveling data supports four reports: the spread between the low and selected bid, awards by trade, repeat award rate by company, and clarifications per bid. Each one improves the next round of leveling.

Report Built from What it answers
Spread between low and selected level bid Low level bid and Award amount properties How much do non-price factors cost, and how often?
Awards by trade Trade or scope property and Selected bidder labels Which trades see the most competition?
Repeat award rate by company Selected bidder labels across jobs Which bidders win repeat work, and which never do?
Clarifications per bid Clarification tasks or a count property Which bidders submit complete bids?
Supplier quote spread (subs) Supplier quote and selected quote values Where does supplier pricing vary most?

For subs, these reports pair with the job-level win rate, which our article on connecting construction bidding software to HubSpot ties to every GC invitation. When your team wants help keeping these reports current, ongoing HubSpot support covers report fixes and new views.

Recap

Bid leveling compares bids on equal scope, and the record captures each bid as received, the adjustments made to level it, and the award decision with its reasons. In HubSpot, summary values live on the deal, documents attach to it, bidders connect through labeled company associations, and line-level detail sits in a Work table or a custom object on Enterprise. Tasks, reminders, and an approval step keep leveling on schedule, and the record stays useful after award for change orders, feedback, and the next bid.

How Can Campaign Creators Help You Design a Bid Leveling Record in HubSpot?

Campaign Creators designs the properties, labels, objects, and workflows that keep your leveling record next to the job and the awarded party. As a HubSpot Elite Solutions Partner, we apply CRM architecture expertise to the way GCs and subcontractors compare bids and make awards.

We map your leveling process, implement the record in HubSpot with deal properties and association labels, build Work tables or a custom Bid object, and add the tasks, reminders, and approvals around each award.

Ready to design your bid leveling record? Book a consultation with our team.