What should be checked before issue?
Illustrative example. Confirm the scope, document revision, return fields, clarifications path, evaluation basis and distribution record.
| Control | Evidence |
|---|---|
| Scope | Package boundary and interfaces approved |
| Documents | Current index and revisions |
| Response | Technical, commercial and deviation fields |
| Questions | Clarification channel and addenda process |
| Evaluation | Criteria and approval path documented |
What is outside the tool?
It does not verify supplier capability, decide a commercial position or perform engineering review. The procurement team remains responsible for the issue.
Common questions
What else should the bid team know?
Does the tool send an RFQ?
No. It checks issue readiness only.
Are selections stored?
No. Checklist selections remain in the browser.
Who approves the package?
The responsible procurement, commercial and engineering leads.
Primary sources
- FAR 13.106, Soliciting competition, evaluation of quotations, and awardAcquisition.gov
- FAR 13.106-2, Evaluation of quotations or offersAcquisition.gov
- Request for QuotationsUS General Services Administration