A technical volume can be complete and still fail to compete. We see it when a team treats Volume II as a shall-statement warehouse: every requirement restated, every tool listed, every process named — and an evaluator still cannot picture how the work will run on the Monday after award. Completeness keeps you eligible. It is not, by itself, what a human evaluator can score with confidence.
Proposal calendars compress. Matrices turn green. Page count fills. Then a color team asks a question no matrix answers: what will they actually do, and why should we believe this method fits this requirement? If the narrative cannot answer that without borrowing a history you are not allowed to claim, the volume is not ready.
Two jobs in one volume
We treat a Volume II–style technical approach as two systems sharing one document. Confusing them is how teams over-write and under-score.
Compliance completeness is a checking job. Can a reviewer confirm that each instruction, factor, and requirement has a home? Headings match the government outline. The matrix is honest. Nothing required is missing. This work is necessary. It is also not the evaluation.
Competitive clarity is a scoring job. Can an evaluator follow a method, see who is accountable, and defend a rating against the stated factors — including to a dissenting reviewer? That needs a performable sequence, not a restatement of the PWS, and discriminators tied to this solicitation’s operating problem, not a generic capability catalog.
Evaluators are not looking for a brochure, and they are not looking for the SOW read back to them in future tense. They want a method they can follow, a team construct they can believe will execute it, and enough specificity that the rating is not wishful. They also notice when past performance is implied rather than evidenced. We do not invent clients, logos, or win histories to fill that gap. If proof belongs in another volume — or is thin — the method, staffing logic, artifacts, and controls have to carry the technical approach.
When time is short and a worksheet is open, we look for:
- Headings that map to evaluation factors so scorers are not hunting.
- An operating picture: what happens, in what order, with which roles, using which artifacts, and what the government sees.
- Discriminators that change how this work will run — interfaces, transition, scarce labor, data, quality — not slogans about excellence.
- Risks that sound like the PWS, plus mitigations that actually change the method.
- Measures a COR or PM could use, even if the RFP did not demand a metrics annex.
What they typically only check, and do not raise a rating for: restating the requirement in contractor voice; tool lists with no operating picture; unattributed “we have done this before”; guarantees the RFP did not ask for; a perfect matrix paired with a narrative that never leaves the happy path.
We are not offering a universal scoring formula. Evaluation is fact-specific. The useful question is still: if you were filling that worksheet tonight, what would you be able to cite from our volume?
Practical moves
These are checks we use when a technical narrative is thick but not yet competitive. They are not a template for every vehicle.
1. Map coverage before you write the story.
Build a requirements-to-narrative map: evaluation factor or instruction → section heading → the one sentence that would let a checker tick “addressed.” Write to those sentences. If a paragraph does not serve a factor, an instruction, or a real interface in the work, it is decorating the page count.
2. Make the first paragraph of each factor answer the operating questions.
For each major factor we ask: What will we do? How? Who is accountable? What does the government see, and when? If the opening cannot answer those without a feature list, the section is not yet a technical approach. Lead with a scoring sentence an evaluator can lift into a worksheet, then support it with sequence, roles, and artifacts. Use the government’s factor names in headings so the worksheet and the volume share a spine.
3. Separate method from proof — especially when past performance is elsewhere.
Method is how work flows: intake, execution, review, correction. Proof is evidence you are allowed to cite under the RFP’s rules. Smuggling invented history into Volume II to sound experienced is a credibility problem, not a workaround. When citation is limited, get specific about the control, the artifact, the review cadence, and the staffing logic. “We will staff appropriately” is not a method. “Who decides, with what input, by when, and what happens if the assumption breaks” is.
4. Write to the worksheet, not the page limit.
Evaluators skim, then drill. Put the discriminator in the open, not in paragraph seven. Cut the sentence that repeats the government’s own requirement language; they already wrote it. Prefer an operating sequence (how work enters, how it is done, how quality is seen, how defects are closed) over a tour of tools. A simple flow that names roles and handoffs helps a scorer more than a logo stack or an unreadable org chart.
5. Name the hard parts of this PWS.
Volumes that only describe the happy path read as incomplete to people who have run the work, even when the matrix is green. Transition, government-furnished information, interface partners, surge, scarce labor, data rights, quality escapes — whatever the solicitation actually makes hard — belong in the method, with mitigations that change staffing, sequence, or controls. A risk register that could be pasted into any bid is a tell. So is a mitigation that does not alter how the work will be done.
None of this replaces a pink/red team that reads as an evaluator would. It does give that team something worth marking besides missing shalls.
Who this is for
This is for federal contractors who need a Volume II–style technical approach to do two jobs at once: survive compliance review, and give a human evaluator something they can score without inventing a past they cannot cite. It is not legal, procurement, or evaluation advice, and it is not a promise about ratings.
If you are in that bind — matrix green, narrative still generic, calendar shrinking — we help teams frame proposal packages around that split: coverage you can defend, and a method an evaluator can follow. Tell us about the pursuit and the constraint. We will tell you whether a tight collaboration on the technical approach is a fit.