TO RECORD: Press F for fullscreen, then Spacebar to play. Capture with Loom, OBS, QuickTime, or your screen recorder. Total runtime approx 3:30.
GUIDE GSC
Government Contract Service Center
00:00
GUIDE GSC RESOURCE LIBRARY

Writing a Winning
Technical Volume

Six rules that separate scoring proposals from compliant-but-forgettable ones — with real examples.

WHY THE TECHNICAL VOLUME MATTERS MOST

It's where most of the points live —
and where most proposals lose them.

50–70%
of evaluation points typically assigned to technical volume on best-value awards
15 min
average time an evaluator spends on each technical volume in initial scoring
#1
reason proposals score low: failure to address the evaluation criteria explicitly
RULE
1

BEFORE QUALITY, COMPLIANCE

Build the compliance
matrix first.

A non-compliant proposal is a non-scored proposal. The first artifact you build — before any drafting — is a matrix that maps every Section L instruction and Section M criterion to a specific location in your volume.

  • Trace every "shall," "will," and "must" from Sections L, M, and C
  • Assign each requirement an owner and a section in your outline
  • Verify the matrix is 100% green before red team review
  • Reverify after final edits — late changes break traceability
RULE
2

WRITE FOR THE EVALUATOR'S RUBRIC

Mirror Section M
in your headings.

Evaluators score against the criteria in Section M — and they score one section at a time. Make their job effortless by using the same evaluation language as headings, in the same order.

  • Use Section M criterion names verbatim as your subheadings
  • Address each evaluation factor in the order it appears
  • Open each section with "Our approach to [criterion] is…"
  • Don't hide a discriminator in a section the evaluator won't score
EXAMPLESection M says "Quality Control Approach." Your heading should say Quality Control Approach — not "How We Ensure Excellence."
RULE
3

EVIDENCE BEATS ADJECTIVES

Replace claims
with quantified proof.

"We have extensive experience" scores nothing. Evaluators are trained to look past adjectives and reward verifiable evidence — numbers, outcomes, examples.

  • Trade adjectives for numbers: years, dollars, percentages, headcounts
  • Tie every claim to a specific past contract by number
  • Use CPARS ratings as proof of customer satisfaction
  • If you can't quantify it, cut it
BEFORE / AFTERReplace "Significant cost savings" with "$2.4M saved over the base year (Contract W912-XX, CPARS Rating: Exceptional)."
RULE
4

DISCRIMINATORS, NOT CAPABILITIES

Thread win themes
through every section.

Capabilities are what every bidder claims. Discriminators are what only you can claim — and they should appear in every major section, not just the executive summary.

  • Identify 3–5 win themes at capture, not at draft
  • Open and close each major section reinforcing one theme
  • Use "Unlike other offerors…" sparingly but deliberately
  • Ghosting competitors works — only with evidence
RULE
5

GRAPHICS EARN POINTS, NOT JUST ATTENTION

Every graphic needs
an action caption.

Evaluators skim. Many will read only your headings and graphic captions on the first pass. A caption that just labels the graphic wastes that real estate; a caption that asserts the benefit wins points.

  • Caption format: "Figure X. [Benefit statement to the customer.]"
  • Tell the evaluator what to conclude from the graphic
  • Reference the win theme the graphic supports
  • Every figure number must be referenced in body text
EXAMPLEBad: "Figure 3. Organizational Chart." · Good: "Figure 3. Our flat, three-layer structure cuts decision time by 40% versus the incumbent's seven-layer chain."
RULE
6

FORMAT IS A SCORING TOOL

Write for the skim,
then reward the deep read.

Evaluators don't read linearly. They scan headings, jump to graphics, sample body text. Your structure has to deliver value to both the 15-minute first pass and the 90-minute deep review.

  • Use descriptive headings that summarize the point
  • Lead each paragraph with a topic sentence that stands alone
  • Pull-quote your most evaluable claims into callouts
  • White space is not waste — it's air for the evaluator
SEE IT IN PRACTICE

Same content. Different score.

✗ BEFORE — Scores poorly
Quality Control
Our company has extensive experience providing high-quality services to many government clients. We have a robust quality control process that ensures excellent outcomes. Our team is highly skilled and committed to customer satisfaction.
Adjectives, no evidence. Heading doesn't match Section M. Nothing for the evaluator to score.
✓ AFTER — Scores high
Quality Control Approach
Our QC approach achieved a 99.2% deliverable acceptance rate on first submission across 47 contract deliverables under Contract W912DY-22-D-XXXX (CPARS: Exceptional, FY24). Three layers of review — author, peer, QC lead — close defects before customer receipt, reducing rework cycles from industry-average 1.8 to 0.3 per deliverable.
Heading mirrors Section M. Claims are quantified. Past contract cited. Discriminator (rework rate) stated.
THE SIX RULES, IN ONE FRAME

Print this. Pin it above your desk.

RULE 1
Build the compliance matrix first
If it isn't traced to Section L & M, it doesn't ship.
RULE 2
Mirror Section M in your headings
Use the evaluator's language verbatim.
RULE 3
Quantified proof, not adjectives
Numbers + past contract + CPARS = scoreable.
RULE 4
Thread win themes throughout
Discriminators in every section, not just the exec summary.
RULE 5
Action captions on every graphic
Tell the evaluator what to conclude.
RULE 6
Write for the skim, then the deep read
Descriptive headings. Topic sentences. White space.
YOUR NEXT STEP
Compliant proposals get read. Winning proposals get scored.
Build the discipline now —
before your next RFP drops.
START AT GUIDE GSC
Proposal templates · Color team checklists · Capture playbooks
INTRODUCTION
Spacebar = Play/Pause · Arrow keys = Scenes