Blogbid exclusions and clarifications3 November 202615 min read

Proposal Clarifications Examples for Construction Bids

Proposal Clarifications Examples for Construction Bids ! Construction bid sketches frame a clear title area A good bid clarification is a short, specific statement that tells the owner or general contractor exactly what your price includes, what it leaves out, and what it assumes.

A good bid clarification is a short, specific statement that tells the owner or general contractor exactly what your price includes, what it leaves out, and what it assumes. It cites the document, names the item, and says how any excluded work would be priced if someone later wants it. Below are working examples for clarifications, exclusions and assumptions, plus the wording habits and compliance checks that keep them from costing you the job.

arosbid
Catch Bid Details Before Submission
ArosBid combines human oversight and technology to scrutinize bid details, track document compliance, and reduce the risk of errors.
Explore ArosBid

TL;DR

  • A clarification asks about or explains the documents, an assumption states a condition your price relies on, and an exclusion removes work from your price.
  • Name the sheet, spec section or addendum in every line, and say how excluded work is priced if it is later directed.
  • Exclusions that remove work the documents require are qualifications, and many tender instructions treat them as grounds for rejection.
  • Ask conflicts and gaps as pre-bid questions first. Use bid-day clarifications only for what the answers did not settle.
  • Reconcile the final clarification list against every addendum before submitting, and hand the revision history to operations at award.

Table of Contents

Clarification, assumption, exclusion: three different tools

People use these words interchangeably, and that is where bids go wrong. Each does a different job.

Clarification. A question or explanation about unclear documents. In the British Columbia Ministry of Transportation’s Conditions of Tender, a clarification is a written request about an unclear part of the tender documents. An official answer comes by amendment, and informal answers are not binding. That pattern shows up in most public procurement: if the answer is not in an addendum, do not price from it.

Assumption. A condition your price depends on. If the condition is false, the price changes. The American Society of Concrete Contractors (ASCC) lists assumptions such as normal work hours, safe access to metal decks, embedded items furnished by others, timely access and all-weather access.

Exclusion. Work or cost you are not pricing. The same ASCC article describes exclusions as items the contractor does not price or perform, including testing, survey control, temporary utilities, dewatering, cleanup caused by others and work outside the building footprint.

A useful test: if the sentence starts with “if” or “provided that,” it is an assumption. If it starts with “not included,” it is an exclusion. If it ends with a question mark, it is a clarification request and belongs in the RFI process, not buried in your proposal.

Clarification, assumption, and exclusion compared

Examples of pre-bid clarification questions

The best clarification questions are the ones an owner can answer in one line. Guidance on pre-bid RFIs from bid-support practitioners says to reference the specific document, sheet or specification section, describe the conflict plainly and, where possible, propose an interpretation for the owner to confirm. Most scope gaps, the same guidance observes, sit in the seams between documents and between trades.

Here are examples written that way. Swap in your own sheet and section numbers.

Situation Weak question Better question
Spec and drawing disagree “Which one governs?” “Sheet A-301 shows 5/8" Type X gypsum at corridor walls. Section 09 29 00, 2.3.B calls for 1/2" regular. We are pricing 5/8" Type X. Please confirm.”
Scope gap between trades “Who does the blocking?” “Section 06 10 00 excludes blocking for wall-mounted accessories. Section 10 28 00 assumes it is provided. We are not including blocking. Please confirm it is by others.”
Missing information “Where is the subgrade info?” “The drawings reference a geotechnical report on Sheet C-001, but it is not in the bid set. Please issue the report by addendum.”
Ambiguous allowance “What’s in the allowance?” “Section 01 21 00 carries a $50,000 flooring allowance. Does the allowance include installation, or material only?”
Site condition “Is there access?” “Please confirm the laydown area shown on Sheet G-002 is available from mobilization through substantial completion.”

Three habits make these work. They quote the document. They state what you will do if no answer comes. And they ask a yes or no question where possible. If you want a deeper process for running these, our pre-bid RFI management guide covers logging, deadlines and follow-up, and our piece on spec versus drawing conflicts goes through the order-of-precedence steps.

When the documents conflict

Some solicitations settle conflicts for you. One Connecticut bid package, for instance, instructs bidders to price the more stringent, more costly requirement when documents conflict and to notify the construction manager in writing before the stated deadline. A sitework scope checklist from a contractor offers similar advice: price the requirement set by the order of precedence and note the conflict, and if the stricter requirement governs, price it.

Sample wording for your proposal:

Conflict noted between Sheet S-201 (4,000 psi) and Section 03 30 00, 2.1 (5,000 psi) at elevated slabs. Priced at 5,000 psi per the stricter requirement.

That sentence is a clarification and a pricing statement in one. It does not remove work. It tells the reader which way you read the conflict.

Examples of exclusions

Exclusions work when they are specific and foreseeable. The American Subcontractors Association (ASA) says in its scope best-practices guidance that foreseeable exclusions should not be boilerplate, and that both contractor and subcontractor should review exclusions during preconstruction, bidding and bid leveling.

Examples grouped by cost type:

Category Example exclusion wording
Site and survey “Survey control, layout stakes and as-built surveys are by others.”
Utilities “Temporary power, lighting and water are furnished by the general contractor at no cost to us.”
Water management “Dewatering and groundwater control are excluded.”
Hazardous materials “Testing, abatement and disposal of hazardous or contaminated materials are excluded.”
Testing and inspection “Special inspections and material testing are by the owner.”
Permits and fees “Building permit is by others. Trade-specific permits and inspection fees are included.”
Taxes “Sales tax is included at the rate in effect at bid date.” or “Sales tax is excluded.” State which one.
Subcontracted work “Fire-stopping at rated penetrations is by the fire-protection subcontractor.”
Cleanup “Cleanup of debris caused by other trades is excluded.”
Boundary “Work outside the building footprint is excluded.”

Several of these, including dewatering, surveys and hazardous-material remediation, appear in the ASCC list of typical exclusions and assumptions. Taxes are different: the ASA’s Subcontract Documents Suite suggests using an additional-information or clarification section for items such as who is responsible for sales taxes or what warranty terms are proposed, and attaching the subcontractor’s bid proposal to the subcontract.

Implied exclusions

Some trades work from published standards that set what is outside their scope unless the documents say otherwise. The Painting Contractors Association’s Standard P23 says listed items are excluded from a painting contractor’s scope unless the specifications or contract documents expressly include them, and that requested excluded work is compensated under Standard P18. If you bid a trade with such a standard, cite it in your proposal rather than retyping a long list. For a view of how roofers set scope boundaries, a roofing scope of work explainer shows the kind of line items that belong in a written scope.

Say how excluded work gets priced

An exclusion that stops at “not included” invites an argument later. A sitework checklist recommends stating how excluded work will be priced if later directed, for example at time-and-material rates. Sample wording:

Rock excavation is excluded. If encountered and directed by the owner, it will be performed at the unit rates in Attachment B.

That sentence protects you and gives the other side a number to plan around.

Examples of assumptions

Assumptions are your conditions. Write them so someone can check whether they were met.

  • “Building pad is prepared to within 1/2 inch of subgrade elevation and accepted prior to our mobilization.”
  • “Work is performed during normal working hours, Monday through Friday. Overtime is excluded.”
  • “Safe access to metal decks is provided by others.”
  • “Embedded items are furnished by others and delivered to the site no less than 10 working days before placement.”
  • “Site access is available for delivery trucks and a crane, with all-weather surfaces.”
  • “Pricing is based on Addenda 1 through 4 and RFI responses 1 through 12.”

The last one matters more than it looks. It ties your price to a document set, which gives you a clean basis for a change if a later revision alters the scope.

How to word and organize them

Write one item per line, each with a verb, a noun and a document reference. Group them by spec division or by the same order as the scope of work. Put the exclusions you most expect to be questioned first.

The ASA’s guidance on scope also covers the process around the words: mark up scope exhibits throughout preconstruction, document revisions in writing, apply them to the final exhibit, and send the revision history to operations at award. That last step is where many projects slip, because the person who negotiated the clarifications is rarely the person who builds the job. If you want a primer on keeping those handoffs tidy, this overview of construction document control is a good starting point.

A structure that works on most proposals:

  1. Basis of bid: the drawings, specifications, addenda and RFIs priced, by number and date.
  2. Inclusions: the headline scope in one paragraph.
  3. Clarifications: conflicts you resolved and how.
  4. Assumptions: conditions the price relies on.
  5. Exclusions: what is not priced, with the pricing method if later directed.
  6. Alternates and allowances: each stated separately.
  7. Validity: how long the price holds. Our seven-part bid proposal format shows where each of these sits in a full proposal.

Avoid vague catch-alls such as “all work not specifically shown.” They look like protection and read as boilerplate, and the ASA guidance cautions against boilerplate for foreseeable exclusions.

Checking your list against the documents

Before submitting, run every line through four checks.

  1. Is it priced against the right set? Confirm you used the correct specifications, drawings, addenda and RFIs, and reconcile the final scope exhibit before contract execution, as the ASA advises.
  2. Does an addendum already answer it? Ohio’s design-build definitions describe an addendum as a written instrument issued before the proposal deadline that modifies or interprets the documents through additions, deletions, clarifications or corrections. If the owner issued one on your point, cite it instead of restating a position.
  3. Does it contradict the instructions to bidders? Some owners prohibit qualifications entirely. Read the instructions before you write the first exclusion.
  4. Does it match your vendor quotes? An exclusion in your proposal means little if the supplier quote you carry includes the item, or the reverse. Level the quotes against each other and against your scope. Our subcontractor bid leveling guide walks through it, and our note on quote scope gaps shows how mismatches hide in vendor exclusions.

For large international or multilateral projects, the rules are stricter. The World Bank’s 2010 standard bidding document requires clarification requests and responses in writing, issues amendments by addenda, ignores bid clarifications the employer did not request, and bars changes to price or substance after the deadline except arithmetic corrections. On those projects, the time to raise a point is before the deadline.

When a clarification makes a bid non-compliant

This is the risk the reader most needs to understand. An exclusion that removes work the documents require is a qualification, and a bid with qualifications the tender instructions do not allow may be treated as non-compliant. That is the point made in guidance on qualifications and exclusions: an exclusion removes work, while a qualification makes the offer conditional on a stated fact or allocation.

Post-submission clarifications have limits as well. The Australian Capital Territory’s Standard Conditions of Tender limit clarification to explaining or supplementing information consistently with the submitted tender, and it must not materially alter the original offer. That rule comes from an Australian jurisdiction, but the principle is common: after the deadline you can explain your bid, not change it.

The flip side is costly too. The ASCC’s technical division warns that incomplete preparation of assumptions and exclusions can undermine a carefully built estimate and leave contractors liable for unfunded scope.

Practical rules that follow from this:

  • Resolve anything that changes scope through a pre-bid RFI, not a bid-day exclusion.
  • If the instructions forbid qualifications, price the documents as written and note only conflicts and basis of bid.
  • If you must take an exception, call it one, state it plainly and expect it to be evaluated.
  • Never exclude an item the documents explicitly require in the hope nobody notices. Someone usually does.

Our AI tender review page describes how we approach catching front-end clauses that restrict qualifications before they become a disqualification.

Bid versus proposal: does the wording change?

In day-to-day construction usage, a bid is typically a price against a defined scope, often on a form the owner supplies, while a proposal tends to include more narrative, approach and terms, which is where clarifications and exclusions usually live. The terms overlap, and the solicitation type sets the rules: an RFQ usually asks for price against full documents, and an RFP asks for approach as well. Our guide to when to issue an RFQ or RFP explains the full-spec test. Either way, the clarification habits above apply: document references, written answers, no silent exclusions.

Perspective: why clarifications fail in practice

We see the same pattern in bid after bid. The clause that sinks a bid is rarely in the scope pages. It sits in the front end, in instructions to bidders, general conditions or an addendum cover sheet, and the estimator never reads it because the deadline is tight and the takeoff is not done.

Our view is that clarifications should be a byproduct of a complete read, not an afterthought typed the night before. That means reading the whole document set, logging each conflict with its sheet and section, and carrying that log from intake through vendor quotes, proposal assembly, buyout and debrief. We built ArosBid to support that cycle while leaving authority over every submission with your people. The software flags what needs attention. Your estimator decides what goes in the proposal.

It also means your clarification list should still exist after award. When the revision history goes to operations, the project team starts with the same scope your estimator priced.

arosbid team

Build clarifications into the bid cycle

If your team keeps clarifications in scattered emails and spreadsheets, a structured workflow is the fix. ArosBid’s bid management platform tracks documents, vendor quotes and compliance in one command center, and works with the Excel and Outlook files your estimators already use. Plans are listed on our pricing page, and you can see the workflow on your own bid in a live demo.

arosbid

FAQ

What is the difference between a bid clarification and a bid exclusion?

A clarification explains or asks about the documents, such as how you read a conflict between a spec and a drawing. An exclusion removes work from your price. Exclusions that remove work the documents require can be treated as qualifications, which some tender instructions do not allow.

Should I put exclusions in my bid or send an RFI?

Send an RFI first when the question could change scope, because the answer will arrive as an addendum that binds everyone. Use bid exclusions for foreseeable items the addenda did not settle, and keep them specific to the project.

Can I change my clarifications after the bid deadline?

Usually not in substance. Many owners limit post-deadline clarification to explaining what you already submitted, and some bar any change to price or substance except arithmetic corrections. Check the instructions to bidders for your solicitation.

How should I price work I excluded if the owner wants it later?

State the method in the exclusion itself, for example time-and-material rates or unit prices from an attachment. That gives both sides a basis for a change order without renegotiating from zero.

Sources

Claims about ArosBid describe how the product works. Pursuits, companies, and prices named in examples are fictional demo data.

Book a live demo
NextProject Bid Timeline: How to Plan Every Stage