← Knowledge base

What BidNotes reviews in a bid package

BidNotes reads the whole bid package for a project, not one file at a time. Requirements that change your number are often split across documents: the contract sets a term, a spec section narrows it, and an addendum changes it again. Reading them together is the point.

Documents it reads

Upload the set you would normally review before pricing:

  • Contract and general conditions. Payment terms, retainage, liquidated damages, schedule, indemnity.
  • Specifications. Your trade’s sections, plus related sections that assign work to you or away from you.
  • Drawings. Notes and schedules on the sheets that affect scope.
  • Addenda. Changes and clarifications issued during the bid.
  • Exhibits. Insurance requirements, bonding, safety and site logistics.
  • Bid forms. Unit prices, alternates and anything you must fill in.

What it produces

BidNotes drafts review notes. Each note is short and plain, tagged by what it affects:

  • Scope - work that is in or out of your contract.
  • Cost - terms that change your price or your risk.
  • Compliance - requirements you must meet to be responsive or to work on site.

What a cited note looks like

Every note points back to where it came from. A note reads like this:

Cost. Liquidated damages of $2,500 per calendar day after substantial completion. Source: Contract, §8.3, page 22.

The citation names the document, the section where there is one, and the page. Click it to open the source page and read the requirement in context. If the note and the page disagree, the page wins, and you fix the note.

What it does not do

BidNotes does not do takeoff, price the work, or decide what to bid. It does not promise to find every requirement. It gives your estimator a faster first pass through the documents, with sources attached, so the review time goes to judgment instead of searching.