Build a proposal support scope before comparing quotes

Start with the response you actually have to deliver

Read the live solicitation, attachments and amendments before making a list of writing tasks. For a negotiated acquisition using the uniform contract format, FAR 15.204-5 describes instructions in Section L and evaluation factors in Section M. Other formats can place those instructions elsewhere. Record the actual reference rather than assuming every opportunity has the same volumes.

Separate a complete response from the part you want help producing. A technical draft, a pricing narrative, an independent review and final assembly are different deliverables. “End-to-end” is too loose unless its boundaries are written down.

Write acceptance criteria that someone can check

Describe what the provider hands over, in what editable format, and what your team checks. A compliance matrix can be checked against identified instructions; a draft can be checked against an agreed outline and supplied facts. A review log can identify who decides each comment and when it is closed.

Treat acceptance as a collaborative review of the agreed output. It is not a guarantee that the government will find the offer acceptable or award a contract.

• Name the volume, outline or planning artifact.
• Identify the source version and planned review round.
• State who approves technical, price and corporate claims.
• Confirm who assembles and submits the final files.

Ask what changes the price, without guessing a market rate

Ask how the quote treats document volume, technical complexity, source-material quality, SME availability, graphics, review rounds, amendments and turnaround. A smaller page count can still require substantial research and coordination. A low quote with unpriced client work is difficult to compare with a more complete scope.

Request a written assumption for each cost driver and a change-control rule for work outside it. Compare included deliverables first. Do not multiply a fictional hourly rate by this worksheet or treat a provider’s fee as a government charge.

Read the fictional scope example

The example separates a compliance matrix, a technical draft and an independent review. The draft remains “Needs review” because its source inputs are not approved. That is a useful discussion point: a writer cannot turn an unverified claim into an approved fact simply by improving the prose.

Change one acceptance criterion and notice whether the quote would need to change too. Ask whether revisions caused by new requirements, unavailable inputs or a new decision are part of the original scope.

Leave the discussion with a clear division of work

Use the exported brief to compare the same request across providers. Keep proprietary solicitation material and internal pricing in your approved working environment. The brief should identify categories and decision owners; any document sharing needs a separate agreed route.

Before starting, agree the deliverable list, client inputs, schedule, review authority, exclusions, handoff format and handling of amendments. Ask FBP to discuss that bounded scope rather than sending an unexplained collection of files.