Loading Training Academy...
Training Academy
Module 7: Assemble a Response Package. Written explanation, fictional example, and sources.
Educational content. Follow the applicable solicitation and contract. Official sources are provided below.
10 min · Progress tracking is not available yet
After this lesson you should be able to tell a company capability statement from a technical response to this solicitation, reuse only evidence you actually hold in Company Documents, and refuse to invent certifications or references. The document generator does not draft those files in this product phase.
A capability statement is a company overview your team already wrote: who you are, what you make, NAICS you claim, and examples you choose to list. It lives in Company Documents so you can reuse it. A technical response answers this notice’s specifications and the evaluation factors in Section M or 52.212-2. Those are different documents unless this solicitation expressly says to submit a capability statement as the technical file.
Registration evidence, Unique Entity ID records, and past-performance samples in the vault are starting files. They do not become Volume I by being stored. FAR 4.1201 and 52.204-7 address electronic representations in SAM.gov; completing SAM is not a substitute for a signed offer or for any Section K copy the instructions still require. Do not invent an ISO certificate, a CPARS rating, or a customer letter that you do not have.
If you name a subcontractor’s experience, say that it is the subcontractor’s work and that the firm will perform the major or critical portion FAR 15.305(a)(2)(iii) is about. The solicitation still decides whether that information will be considered. AsherGate vendor notes are not a past-performance volume.
Using the Hollowreed story below, Company Documents holds a two-page capability PDF and a SAM Active screenshot. Section L wants a five-page technical approach to filter change-out, not a company brochure.
Open the capability PDF for facts you can prove. Write a new technical file that maps to the evaluation factors. Leave the generator on Coming soon. Do not submit.
Fictional example
Hollowreed Water Filters Co is a fictional filter shop in Bend, Oregon. Company Documents holds a two-page capability PDF the owner wrote and a SAM.gov Active screenshot. It stores fictional RFP AG-CAP-26-0428 from a fictional Deschutes Field Station Desk for quarterly filter change-out.
Section L asks for a five-page technical approach covering replacement interval, waste handling, and staffing. A teammate uploads the capability PDF as Volume_I_Technical.pdf because the file was handy. The capability PDF never mentions waste handling.
They pull the capability PDF back to Company Documents. They write a five-page technical file that answers those three factors with work Hollowreed has actually done. They do not add a made-up NSF mark. They do not ask the document generator to invent the volume. Nothing is submitted.
Each official source is listed with the teaching claim it supports. Product behavior is labeled separately. Review dates are when AsherGate last checked the page.
Acquisition.gov · Official source · Reviewed 2026-09-27
Supports: Technical and past-performance parts, when required, are defined in Section L of that solicitation, not by a company’s marketing file.
Acquisition.gov · Official source · Reviewed 2026-09-27
Supports: Technical evaluation assesses ability to accomplish the technical requirements. Subcontractor past performance may be considered when relevant to major or critical work. Do not invent history to fill a volume.
Acquisition.gov · Official source · Reviewed 2026-09-27
Supports: Offerors complete representations and certifications in SAM.gov on the schedule FAR 4.1201 sets. A stored SAM screenshot is evidence of a copy, not a signed proposal.
AsherGate · AsherGate product · Reviewed 2026-09-27
Supports: Company Documents stores reusable registrations and capability files. Storing a file does not submit it as a proposal volume.
AsherGate · AsherGate product · Reviewed 2026-09-27
Supports: Federal document drafts, including capability statements and proposal outlines, are labeled Coming soon and are not generated in this product phase.
AsherGate · AsherGate product · Reviewed 2026-09-27
Supports: AI does not certify that a company, document, or proposal is eligible or complete.