By the time you sign a subcontract, the leveling spreadsheet is closed, the bidders have moved on, and the reasoning that felt obvious on award day is already fading. Six months later a delay claim lands, the owner audits your buyout, or your own PM asks why the second-low number didn’t win. The award memo is what answers that question. It is the durable record of why one sub got the work, and a good one survives scrutiny because every claim in it points back to a page in a bid. If you find yourself rebuilding that logic from memory, award memo software exists precisely so you never have to.
This guide covers what an award memo is, the seven sections a defensible one contains, how to justify awarding to a sub that wasn’t the lowest, and how to tie every statement to cited evidence. A short worked example follows.
What an award memo is and why it exists
An award memo (sometimes called a recommendation-to-award or buyout justification) is a one-to-three page document that records a subcontract award decision: who you picked, what you compared, and why. It is written by precon or the estimator who ran the leveling, and it lives in the project file alongside the executed subcontract.
It exists for three audiences. The owner may have a contractual right to review subcontractor selection, especially on cost-plus, GMP, or publicly funded work. Your own leadership needs to sign off on a buyout that may swing the job’s margin. And future you will need it when a dispute surfaces and the original logic has to be reconstructed under pressure. A memo that only says “ABC Paving was the best fit” helps none of them. One that shows the math, the gaps, and the trade-offs helps all three.
The seven sections of a defensible memo
A memo that holds up has a predictable shape. Skip a section and that is exactly where someone pokes a hole.
- Bidders and the field. List every sub that bid the package, not just the finalists. Include the bid total, bid date, and whether each bid was complete or qualified. Showing that you solicited and reviewed five bids, not two, is half the defense.
- Basis of award. State the decision rule before you state the winner. Lowest responsible bid, best value, lowest risk, schedule priority, scope completeness, budget-constrained, or a custom weighting. Naming the rule up front stops the memo from looking like you reverse-engineered a justification for a sub you already liked.
- Scope and price reconciliation. Show the leveled comparison: each bidder normalized to your scope of work, with apples-to-apples line items. This is where a $1.2M bid and a $1.35M bid become comparable once you add the items the low bidder excluded.
- Scope gaps. Call out what each bidder missed (uncovered work) and what they added (scope you didn’t ask for). A bidder who is low only because they left out traffic control isn’t actually low.
- Risk findings. Document the pricing red flags: unbalanced unit prices, line items priced at multiples of the peer median, a total that deviates sharply from the field, or front-loaded mobilization. These are the items most likely to become change-order leverage later.
- The reasoning. Two or three paragraphs tying the basis of award to the data. This is the narrative the owner actually reads. It should be boring, factual, and traceable.
- The override, if any. If a human decision departed from what the scoring or low number suggested, say so explicitly, name who made the call, and give the justification. A documented override is a strength. An undocumented one is what gets found in discovery.
How to justify awarding to a non-lowest bidder
This is the section that earns the memo its keep. Awarding to the low bidder is self-justifying; awarding to anyone else is where you need a paper trail. The reasoning almost always reduces to one of three arguments, and each has to be quantified.
- The low bid isn’t actually low. Once you add the excluded scope, the apparent low number rises above a competitor’s. Show the reconciliation. “Bidder A’s $1.20M excludes dewatering and erosion control valued at $185K against the peer median; adjusted, A is $1.385M versus Bidder B at $1.31M.”
- The low bid carries unacceptable risk. Unbalanced or front-loaded pricing, a total far below the field that signals a missed quantity, or a performance history that argues against the savings. Quantify the exposure and weigh it against the dollar gap.
- A non-price factor governs under the stated basis. If the basis of award is schedule priority or scope completeness, the rule itself permits a higher number. Point back to the basis you declared in section two.
The discipline is the same in every case: name the dollar gap you are accepting, name the reason, and attach the evidence. “We are paying $75K more than the apparent low bid because the low bid omits $185K of required scope” is a sentence an owner cannot argue with.
Backing every claim with page-cited evidence
The difference between a memo that holds up and one that gets picked apart is citation. Every quantitative claim should carry a reference to where it came from: bid PDF, page, line item. “Bidder C’s mobilization is 14% of the bid total” is an assertion. “Bidder C’s mobilization (Bid C, p.2, item 0201.0001) is $168K, 14% of the $1.2M total, exceeding the 10% front-loading threshold” is evidence.
Citations do two things. They let any reviewer verify the claim in under a minute instead of re-reading five PDFs, and they make clear the numbers came out of the bids, not out of an argument built to reach a conclusion. Before you write a word of narrative, it helps to run the package against a fixed list so nothing slips. This free bid-leveling checklist walks the normalization and gap-check steps the memo later cites.
A short worked example
Three subs bid a drainage package. The basis of award is lowest responsible bid. After leveling, here is the reconciliation that goes in the memo.
| Bidder | As-bid total | Excluded scope (peer-valued) | Adjusted total | Key risk finding |
|---|---|---|---|---|
| A – Northline Site | $1,200,000 | +$185,000 (dewatering, E&S) | $1,385,000 | Total 18% below field median |
| B – Cardova Civil | $1,310,000 | $0 | $1,310,000 | None flagged |
| C – Reilly Bros | $1,250,000 | +$40,000 (minor) | $1,290,000 | Mobilization 14% of total |
On the as-bid line, Bidder A looks $50K cheaper than C and $110K cheaper than B. After scope reconciliation, A is the most expensive of the three. C is now the low adjusted number, but C’s mobilization is front-loaded at 14%, which raises a cash-exposure flag if the sub defaults early. B is $20K higher than C but carries no risk findings.
The memo’s reasoning paragraph writes itself: under lowest responsible bid, A is disqualified as non-responsive on scope. The choice is C at $1.29M with a front-loading flag, or B at $1.31M clean. The award goes to C, with the override note documenting that the $20K premium over the clean bid was not paid because the front-loading risk was judged manageable given C’s schedule certainty and a mobilization cap written into the subcontract. Every number above traces to a bid page. That is a memo an owner can’t argue with.
How Bid Reasoner builds all seven documents
Doing this by hand for one package is an afternoon. Doing it for thirty packages a year, with citations, is where it falls apart. Bid Reasoner reads each sub bid PDF, extracts and normalizes the line items, and maps them to your scope of work, then scores every bidder across price, scope, schedule, compliance, performance, and risk under whichever of the seven decision modes you pick. The four deterministic risk rules — unbalanced unit prices, peer outliers, total-bid outliers, and front-loaded mobilization — run on every line automatically, so the findings in section five are flagged before you start writing.
From that analysis it generates seven Word documents, including the Reasoned Award Memo and the Evidence Report, with the page citations already filled in. If you override the recommendation, the audit trail records it. You edit the narrative, not the data. See how the award memo software assembles the full package, or walk the four risk rules and scoring in the bid analysis overview.