Construction bid solicitation: a practical guide for GCs

Construction bid solicitation is the controlled process a general contractor uses to identify qualified trade partners, distribute bid packages, communicate requirements, track participation, manage revisions, and collect proposals in a form that can be evaluated reliably.

It is not emailing drawings to a long bidder list.

The distinction matters because a poor solicitation cannot be repaired during leveling. When trade boundaries are unclear, documents go out inconsistently, questions get answered privately, or bidders use incompatible pricing structures, the estimating team spends bid day reconstructing information that should have been controlled weeks earlier. Leveling then becomes archaeology.

A solicitation process that works produces five outcomes:

1. The right subcontractors and suppliers receive the right packages.
2. Bidders understand the work, the commercial requirements, the schedule, and the submission rules.
3. Every bidder prices from the same current information.
4. The GC knows where coverage is strong, weak, or uncertain before bid day.
5. Proposals arrive in a format that supports efficient leveling and a defensible award.

The practical rule for getting there is short:

Standardize the controls. Configure the package, bidder strategy, timing, questions, and pricing form for the project in front of you.

What solicitation actually covers

Solicitation sits between scope and procurement planning on one side, and bid leveling and subcontract award on the other. It begins well before the invitation is sent and it includes defining the work packages, identifying trade boundaries and interfaces, deciding which firms are qualified and appropriate, preparing package-specific invitation materials, setting the pricing and submission requirements, securing credible intent, managing bidder questions and project changes, receiving and validating proposals, and preserving an audit trail through award.

AIA A701 and the federal sealed-bidding framework both treat bidder instructions, submission requirements, bonding, amendments, evaluation factors, and deadlines as formal parts of the solicitation, not administrative details bolted on at the end. That is the right mental model even on private negotiated work.

The full loop, in order:

1. Project and procurement strategy.
2. Package and scope planning.
3. Bidder qualification and list development.
4. Issue the invitation to bid.
5. Confirm intent and coverage.
6. Manage questions, addenda, and revisions.
7. Receive controlled bid submissions.
8. Compliance review.
9. Bid leveling.
10. Clarification, recommendation, and award.
11. Capture bidder and project lessons, which feed step 1 on the next project.

Most teams run steps 4 and 7 well and treat everything around them as overhead. The results show up in leveling.

Solicitation is not estimating

The estimate establishes what the GC believes the work should cost. Solicitation asks the market what qualified trade partners will actually provide, under stated assumptions, at a specific moment in time.

Those two numbers diverge for legitimate reasons: the estimator and the bidder read the scope differently, the bidder has a different labor plan or supplier relationship, the bidder priced risk the estimate did not carry, the bidder excluded design or temporary work or testing or supervision, the documents changed after the estimate was prepared, or market capacity moved.

The goal of solicitation is not to force every bidder to think identically. It is to create enough common structure that you can explain why the prices differ.

It starts before the package goes out

The bidder list should not be assembled for the first time on issue day. For critical trades, market engagement belongs in package planning, where early conversations reveal whether qualified firms have capacity, whether the proposed bid date collides with a major market deadline, which manufacturers or systems force early decisions, whether the package is too large or too fragmented for the market to absorb, which scope questions will produce inconsistent assumptions, and whether bonding, union labor, certified payroll, controlled insurance, participation goals, clearances, or project-specific safety requirements will disqualify part of the list.

Prequalification is a risk-control process, not a form. ConsensusDocs' standard subcontractor qualification form covers project experience, financial information, and safety records; AGC's default-prevention guidance emphasizes financial condition, liquidity, past performance, and changes in ownership or business strategy. Both point the same direction: look at whether the firm can carry the work, not only whether it can price it.

Delivery method and procurement method are separate decisions

A recurring source of confusion is treating design-bid-build, CM-at-risk, design-build, IPD, negotiated, competitive, lump sum, and best value as one vocabulary describing one thing.

They describe three different things. The delivery method assigns contractual responsibility for design, construction, coordination, and risk. The procurement method determines how a party gets selected. The commercial model determines how compensation and price risk are structured. CMAA is explicit that price-based, qualifications-based, and combined procurement can each be applied across different delivery systems, and that lump sum, GMP, and reimbursable compensation are separate from the delivery structure.

So a project can use competitive, negotiated, qualifications-based, or hybrid procurement inside several delivery structures. Your solicitation has to match the combination you are actually in.

That matrix is an operating framework, not a substitute for contract review or local procurement law. Public requirements vary across federal, state, municipal, education, and transportation authorities.

Design-bid-build

Design-bid-build gives the cleanest solicitation event, because drawings and specifications are developed before the bid is requested. The apparent simplicity is misleading: a complete drawing set does not guarantee coordinated scope. You still have to define package boundaries, identify alternates, confirm who carries permits and temporary services, and resolve conflicts between drawings, specifications, schedules, and the bid form.

For hard-bid solicitation: freeze and identify the document set, publish an exact list of drawings and specifications and reports and addenda, write a package scope that supplements the contract documents without silently contradicting them, state whether the bidder must flag conflicts or price the more stringent requirement, require separate prices for owner alternates and GC options and unit prices and allowances and taxes, and permit no private clarification that could move another bidder's price.

On bid duration, the FAR is worth borrowing from even when it does not apply to you. Federal construction invitations must allow enough preparation time considering site inspection, subcontract quotations, review of project data, and estimate preparation, at least 30 calendar days where a synopsis is required. The principle transfers: the bid period should reflect the work required, not the date your estimate schedule prefers.

CM-at-risk

In CM-at-risk the construction manager is involved during design, then assumes construction performance risk and usually holds the trade contracts. CMAA notes that CMAR pricing is commonly established somewhere around 50% to 90% design development, though the real timing varies widely.

Solicitation here is rarely one event. It spans conceptual market checks, schematic budgets, design-development trade input, early procurement for demolition or foundations or structure or utilities or long-lead equipment, final GMP bidding, and post-GMP buyout for whatever was not awarded earlier.

The invitation has to state the design status honestly. A 60% package presented as a complete lump-sum scope produces prices padded with invisible, inconsistent contingency. Each CM-at-risk invitation should separate defined work, inferred work, design assumptions, allowances, pending owner decisions, quantities that will be reconciled, the escalation basis and quote validity, the design contingency the GC carries versus the trade contingency you are asking bidders to carry, and the scope expected during preconstruction, design assist, coordination, fabrication, and construction.

Run all of it off a rolling procurement log showing design readiness, issue date, bidder status, pricing date, recommendation, owner approval, contract release, long-lead release, and unresolved scope.

Design-build

Design-build puts design and construction under one contract. DBIA's best-practice framework treats procurement, contracting, and execution as related disciplines and emphasizes demonstrated competence, clear risk allocation, and collaboration. DBIA and FMI project design-build at more than 47% of assessed US construction spending by 2028, which makes this capability increasingly hard to opt out of.

The central question is no longer only "what will you build it for?" It is also "what will you help design, validate, coordinate, and deliver?"

For the relevant trades, the invitation should define whether design assist is required, whether delegated design is included, who retains the engineer of record for the system, which calculations and models and shop drawings and professional seals are expected, the design-meeting and coordination obligations, the expected value-engineering participation, the pricing milestones and open-book requirements, ownership and permitted use of design ideas if the bidder is not selected, compensation for substantial pre-award design effort, the performance criteria where prescriptive design is incomplete, and responsibility for code, authorities, commissioning, and manufacturer coordination.

A low number from a trade partner that excluded engineering, coordination, mockups, controls integration, and commissioning is not a low total cost.

Integrated project delivery

IPD uses contractual and commercial structures intended to align owner, designer, builder, and often key trade partners around shared outcomes. CMAA describes it as collectively managing or sharing risk, responsibility, and liability among the primary parties. AIA's guidance notes that conventional bidding is limited for participants already integrated into design, while remaining subcontractors and suppliers may still be competitively procured.

For core partners, solicitation looks more like team selection and commercial alignment than bid collection. Evaluation weights technical capability, collaborative behavior, reliability of cost forecasting, leadership availability, production-system maturity, BIM and coordination capability, transparency of labor and material and overhead and profit, capacity to participate in target-value design, willingness to put profit or incentive compensation at risk, and the ability to make qualified people available early.

Negotiated versus competitive

Competitive solicitation earns its place when scope is defined, several capable bidders exist, and market pricing genuinely matters to the decision. Negotiated procurement earns its place when continuity, qualifications, early involvement, specialization, schedule, or prior performance carries more weight.

The strongest teams hybridize: negotiate with a preferred partner, obtain independent supplier or material validation, benchmark production rates and unit costs, competitively solicit the high-risk or uncertain portions, require transparent assumptions with open-book support, and reserve the right to compete the package if cost or performance expectations are not met.

Negotiation does not mean accepting an unstructured proposal. Competitive bidding does not mean sending the package to every firm in the database.

The solicitation workflow, step by step

Establish the procurement plan

Before any invitation exists, answer: what must be bought, at what level should it be packaged, when does each package need market input and pricing and recommendation and release, which packages need design assist or early procurement, which are critical to the schedule or the GMP, which require owner approval or public process, how much competition is appropriate, and which risks must stay visible all the way through leveling and award.

The plan should connect the estimate work breakdown structure, the specification divisions, the schedule activities, the design milestones, and the contract strategy. None of those five systems substitutes for the others, and assuming otherwise is how packages end up with no owner.

Build the package

A bid package should be large enough to create clear accountability and small enough that more than a handful of firms can perform it. Both failure directions are real: an oversized package shrinks the bidder pool, and an over-fragmented one multiplies interfaces.

Review every boundary for demolition and patching, temporary protection and utilities, layout and surveying, hoisting and scaffolding and access and material handling, cutting and coring and sleeves and embeds and penetrations, firestopping and waterproofing at interfaces, controls and power and communications and integration, testing and inspections and commissioning and closeout, permits and fees and bonds and insurance and taxes, design and engineering and detailing and modeling and coordination, and cleaning and waste handling and attic stock and training and warranties.

For trades with repeated interfaces, build a boundary matrix that names four parties per task: who furnishes, who installs, who coordinates, who verifies.

Prepare the ITB

Within the first screen, the invitation should tell a bidder what the project is, where it is, which package is being solicited, who the GC contact is, when questions are due, whether a site visit is required, when and how the bid must be submitted, which documents control, and which commercial or qualification conditions are mandatory.

Prequalify in proportion to risk

A $100,000 finish package and a $25 million electrical package should not get the same review.

Prequalification is not permanent approval. Refresh financial and capacity information before a major award, especially when market conditions, ownership, backlog, or leadership have moved.

Build a classified bidder list

Stop maintaining one undifferentiated directory. Classify firms as preferred and proven, qualified but untested with your company, project-specific specialist, developing trade partner, geographic expansion candidate, supplier-only, design-assist capable, bondable for this package, approved with restrictions, or do not invite.

For each, track relevant project types, typical package size, geographic reach, labor model, key contacts, past response behavior, bid accuracy, post-award performance, safety, financial status, and relationship notes.

The objective is not the largest invitation count. It is enough credible coverage to make a real decision.

Contact bidders yourself

An automated invitation is the start of outreach, not the end of it. Critical packages need personal contact from someone the bidder recognizes, confirming that the invitation reached the right person, that the firm understands the package, that it has capacity, that the bid date is realistic, that the estimator has actually opened the documents, and that no immediate concern will keep the firm out.

Do not confuse "opened the invitation" with "will submit a usable bid." Track behavior, not system status.

Track intent and coverage honestly

Use real states, not a binary: invited, invitation viewed, contacted, undecided, intends to bid, declined, no response, proposal received, proposal incomplete, withdrawn, carried for leveling, shortlisted, awarded, not selected.

Capture a reason for every decline where the relationship allows: capacity, schedule conflict, package size, location, labor constraints, bond requirements, incomplete design, unacceptable contract terms, insufficient bid time, no supplier coverage, poor project fit. Decline reasons are the cheapest market intelligence available to a precon team, and almost nobody files them.

Weight coverage by credibility. Four unresponsive names are not better coverage than two firms that downloaded the documents, attended the site walk, asked package-specific questions, and reconfirmed intent.

Manage questions and addenda as one controlled channel

Every material question enters one Q and A process. Any response that changes scope, quantity, quality, schedule, commercial terms, or bidder assumptions goes to every affected bidder.

The federal sealed-bidding standard states the governing principle cleanly: material information given to one prospective bidder should be furnished promptly to the others, and an amendment must allow enough time for bidders to consider it. Oral explanations should never become the hidden basis of a bid.

Never replace a folder silently. Every changed file gets identified, dated, and tied to a revision notice.

Define the submission format

A standard bid form is the cheapest intervention available for reducing bid-day chaos. Require the base bid, a scope-specific line-item breakdown, alternates, allowances, unit prices, hourly labor rates, material escalation assumptions, tax treatment, bond cost, controlled-insurance adjustments, schedule duration and lead times, proposed manufacturers, major exclusions, qualifications, addenda acknowledgment, the bid-validity period, and a signature.

Accept supplemental proposals, but make the GC bid form controlling for comparison. Otherwise you are back to normalizing five formats by hand.

Give the market a real bid period

For a substantial private commercial package, a workable shape looks like this: four days to finalize package strategy and the bidder list, four days to prepare the ITB and scope and bid form, then issue. Confirm receipt and intent over the first four days, hold the site walk and pre-bid meeting in the first week, run Q and A for roughly ten days, close questions about ten days after issue, publish the final planned addendum a few days later, and leave a full week of pricing time after the last addendum before the bid deadline. Compliance review takes a day; leveling and clarifications take three or four more.

Expand it for design-assist work, public advertisement, significant site investigation, long-lead supplier coordination, or heavy takeoff.

Make bids comparable before they arrive

Start with scope clarity

Comparable bidding starts with a package that tells bidders what outcome they own and how that responsibility meets the adjacent trades. A trade scope that repeats specification section titles has done nothing. It needs to describe the work as it will be bought, coordinated, sequenced, tested, and closed out.

Per package, define furnish-and-install responsibilities, design and engineering responsibilities, the quantitative basis where one exists, trade interfaces, temporary work, access and logistics and hoisting and protection, testing and inspections, mockups and samples, permits and fees, coordination and BIM, schedule milestones, submittal and procurement dates, commissioning, training and attic stock and warranties and closeout, the exclusions you will accept, and the items bidders may not exclude.

Control the pricing basis

Alternates. Separate owner alternates in the contract documents from GC procurement options, value-engineering proposals, scope deductions, and voluntary bidder alternatives. Require a price and a schedule effect for each. Never let a bidder fold an owner alternate into its base price undisclosed.

Allowances. Every allowance states what it covers, whether it includes labor and material and equipment and overhead and profit, who controls selection, how quantity differences get adjusted, whether tax and freight and waste and escalation and installation are in, and what documentation will be required. An allowance without a defined basis creates the appearance of comparability and postpones the argument.

Unit prices. Valuable where quantities are uncertain, dangerous when collected casually. Define the measurement method, the unit, what labor and material and equipment and supervision and overhead and profit are included, the minimum mobilization or quantity, the applicable quantity range, the add and deduct basis, the validity duration, and whether unit-priced work changes the schedule.

Qualifications. Do not prohibit them. A ban on qualifications just moves assumptions underground. Require them in a designated section, classified as scope exclusion, design assumption, quantity assumption, schedule condition, commercial exception, manufacturer substitution, code or constructability concern, information request, or value-engineering option, with the price or schedule consequence stated where practical.

The quality-control checklist

Before issue. Package boundaries reconciled against the estimate. Every scope interface has a named owner. The correct drawings, specifications, reports, and models are attached, each with a revision date. Alternates, allowances, and unit rates are defined. The pricing form matches the leveling structure. Schedule milestones and long-lead requirements are included. Contract, insurance, bonding, and labor requirements are visible. The bidder list is reviewed for qualifications and capacity. Priority bidders have been contacted. Internal ownership of Q and A and addenda is assigned.

During the bid period. Receipt and intent confirmed. Weak packages have recovery plans. Questions logged and assigned. Material answers distributed consistently. Changed files issued through addenda. Acknowledgment tracked. The internal estimate reflects significant revisions. Site-walk information documented. No bidder has received private scope direction.

At close. Submission time logged. Bid form and proposal preserved. Addenda acknowledgment confirmed. Required alternates and breakouts complete. Bid security present. Exclusions and qualifications extracted. Bid validity and schedule recorded. Late or revised bids handled under the stated policy. The package goes to leveling only after compliance review.

Score comparability, not just price

A simple score separates a low price from a usable proposal. Rate each bid zero to two on eight criteria.

A bid with the lowest price and a comparability score of 6 out of 16 is not equivalent to a fully responsive proposal scoring 15. The score does not replace judgment. It makes the case for further clarification visible to everyone reviewing the package.

Governance, metrics, and failure modes

Decide who may do what

A documented governance model prevents inconsistent decisions and protects the GC when cost, schedule, relationships, or public-procurement rules create pressure. Name who may approve the package strategy, add or remove bidders, communicate scope direction, answer questions, issue addenda, change the bid date, accept a late bid, open sealed bids, conduct post-bid clarification, negotiate price, recommend award, approve a single-source or non-low award, release a letter of intent, and execute the subcontract.

On major packages, separate the roles of solicitation administrator, scope owner, commercial reviewer, risk reviewer, and award approver.

Treat bidder pricing as confidential

Subcontractor pricing is confidential business information. Clarifying and negotiating is legitimate; using one bidder's price or means and methods to pressure another firm damages market trust and may conflict with procurement requirements or your own policy.

Write down the rules for access to unopened bids, access after opening, internal distribution of proposals, disclosure of results, use of competing technical ideas, post-bid negotiation, documentation of revised proposals, conflicts of interest, gifts and hospitality, and retention of solicitation records. For public and sealed procedures, follow the owner's rules and applicable law exactly.

Metrics worth tracking

There is no universal "good" response rate. A specialized cleanroom package, a rural concrete package, and a metropolitan drywall package operate in different markets. Set baselines by trade, geography, project type, package size, delivery method, and relationship tier, then watch the trend rather than the absolute.

As a starting management target for an established private-commercial process, aim for intent response near 85%, addendum acknowledgment at 100%, on-time bids and bid-form completion near 95%, and decline reasons captured around 90% of the time. Your own data should replace those numbers as soon as you have a season of it.

On critical competitive packages, three credible bids is a reasonable operational floor. Modify it for specialized, negotiated, design-assist, or capacity-constrained work, and remember that three incomplete proposals are worse coverage than two strong ones.

A dashboard that forces action

Every red line needs a named owner, a recovery plan, and a date. A dashboard that reports status without assigning action is a status report, not a control.

The failure modes that recur

Inviting too many firms. A long list creates false confidence and signals to preferred partners that you will not evaluate seriously. Segment the list, call the priority firms, remove firms that are not appropriate, and measure viable coverage rather than invitation volume.

Issuing incomplete documents without explaining design status. Trade partners respond by declining, padding, or inventing their own design assumptions. Include a design-status narrative, an open-items log, an allowance strategy, and a reconciliation plan.

Using a generic scope template. The standard language survives; the project-specific systems, logistics, phasing, and owner requirements do not. Start from the company standard, then run a project-specific review against the drawings, specifications, schedule, estimate, site conditions, and prior lessons.

Treating an automatic "yes" as coverage. A bidder clicks intent early and disappears near bid day. Require multiple commitment signals: document access, personal confirmation, site-walk attendance, questions asked, reconfirmation before close.

Answering one bidder privately. Even a well-intentioned explanation changes that bidder's interpretation and unequalizes the pricing basis. Route material answers through controlled Q and A and publish them without exposing protected bidder information.

Issuing an addendum too close to bid day. Bidders cannot re-take off the work, get revised supplier pricing, and update their own subcontractor quotes in a day. Set a planned addendum cutoff and extend the deadline when a change is material.

Requiring lump-sum pricing on unresolved scope. The prices come back carrying inconsistent, invisible contingencies. Break the uncertainty into allowances, unit prices, alternates, quantified assumptions, or separately reconciled risk.

Discovering weak coverage on bid day. By then a replacement bidder cannot price the work fairly. Review coverage within two business days of issue and repeatedly after.

Failing to update the internal estimate. The market prices the revised documents while you compare bids to a stale estimate. Link every material addendum to an estimate-update task and preserve the pricing basis by revision.

Awarding the apparent low bid before scope closure. The team anchors on the price and treats later additions as surprises. Finish compliance review, scope leveling, commercial review, schedule validation, and risk review before recommending.

What a solicitation system has to understand

A capable bid-management system should maintain qualified bidder records, create and reuse package structures, distribute controlled document sets, track invitation receipt and intent, record communication history, manage bidder questions, issue updates consistently, receive standardized submissions, preserve bid confidentiality, compare proposals, report coverage metrics, and hand award information to procurement and contracting.

Those are real benefits, and they are process controls rather than judgment. Software will not tell you whether the scope itself is right. It is also worth checking whether the constraint is internal before blaming the market: when vendor questions and bidder activity route through individual estimators, weak response can look like a bidder-list problem while the actual bottleneck is one overloaded inbox. That is worth ruling out before anyone buys a tool to fix it.

Where AI genuinely helps

AI is well suited to the information-heavy parts: extracting dates and requirements from owner bid packages, classifying drawings and specifications and reports and addenda, identifying the specification sections relevant to a trade, drafting a first-pass scope from project documents and company templates, comparing document revisions and detecting changed sheets, extracting bidder exclusions and qualifications and alternates and lead times, checking bid-form completeness, mapping bidder questions to the related documents, suggesting scope-gap questions from company standards, summarizing coverage and unresolved risk, and linking every finding back to its exact source.

What it should not decide alone

AI should not have sole authority to conclude that a subcontractor is financially safe, interpret ambiguous contract risk conclusively, decide which firm gets invited, declare two scopes commercially equivalent, accept a nonresponsive or late bid, select a carry number, recommend award without estimator review, negotiate confidential pricing, resolve a design conflict, judge whether a trade partner can staff the project, or replace relationship-based market intelligence. Those need business judgment, accountability, and often legal or executive authority.

Why generic tools fall over

Solicitation is not document summarization. A production-grade system has to understand:

Trade context. "Controls," "testing," "supports," "firestopping," and "temporary power" belong to different parties on different projects.

Document hierarchy. Drawings, specifications, addenda, scopes, bid forms, owner instructions, and the proposed subcontract can conflict and do not carry equal authority.

Revision state. A correct answer drawn from an obsolete drawing is still wrong for the current bid.

Company standards. One GC puts temporary power on the electrical contractor; another carries it in general requirements. A model with no controlled company context cannot know your default.

Workflow state. The useful answer differs depending on whether the team is preparing an ITB, confirming coverage, analyzing an addendum, leveling proposals, or negotiating award.

Source traceability. An estimator has to be able to verify where a requirement came from.

Permissions. Bid prices, financial data, qualifications, and negotiation history cannot be exposed indiscriminately.

Structured output. The work has to return to your bid form, scope sheet, estimate, procurement log, and approval process, not sit inside a chat transcript.

Before adopting anything, test whether it can use your actual package and scope templates, process drawings and specifications and addenda and spreadsheets and proposals together, preserve revision and issuance history, cite every material finding, restrict access to confidential information, extract bidder qualifications into a structured comparison, distinguish a missing answer from an assumed one, apply project-specific and company-specific review questions, export into your existing estimating and procurement formats, maintain an audit trail of human edits and approvals, learn from award outcomes without overwriting controlled standards, and handle realistic project scale rather than a demo file.

What better solicitation actually changes

Consider a CM-at-risk hospital project releasing a mechanical package at 70% design.

Before. Twelve firms invited. Six clicked "intends to bid." Two bids arrived. One excluded controls, testing, temporary heat, seismic bracing, and design assist. The other covered most of that but carried a large design contingency. The estimating team spent four days normalizing two proposals, and the owner received a GMP package with unresolved mechanical scope inside it.

After. Seven firms invited after capacity and healthcare-experience screening. Five priority firms received pre-issue calls. The ITB separated mechanical construction, controls integration, delegated design, testing, and preconstruction services. Unresolved design was handled through allowances and unit rates instead of implied lump sum. Intent was reconfirmed twice. Four proposals arrived and three cleared the comparability threshold. The team could see that the real pricing spread was equipment selection and labor productivity, not missing scope. The recommendation documented the remaining design risk instead of burying it in one number.

This is an illustrative composite, not a customer claim or a benchmark. The point is what changed: not the quantity of bids, but the quality of the decision.

Where Piper fits

Good solicitation creates the conditions for a good estimate and a defensible award. It does not begin with "send invitation." It begins with package strategy, scope clarity, bidder qualification, market knowledge, and a realistic procurement schedule. It continues through controlled communication, revision management, and structured submissions. It ends only when the proposals are complete enough to level and the lessons from participation, pricing, award, and performance are retained for the next project.

The natural next step is construction bid leveling, which covers how to normalize proposals, price scope gaps, evaluate exclusions, and produce a defensible carry or award recommendation. If your packages keep producing proposals that cannot be compared, start with the scope-gap review instead.

See Piper on your project. Bring a current or completed bid package and see how Piper reads the requirements out of it, applies your company's solicitation checks, surfaces what is missing before the package goes out, and connects every finding back to its source. The same understanding then carries into leveling what comes back, so the scope you issued is the scope you compare against.

Sources

• Associated General Contractors of America (AGC)
• Construction Management Association of America (CMAA)
• Design-Build Institute of America (DBIA)
• American Institute of Architects (AIA)
• ConsensusDocs
• Occupational Safety and Health Administration (OSHA)
• Federal sealed-bidding framework, as cited in the body
• DBIA and FMI design-build spend projection, as cited in the body