The submission section looks boilerplate but does meaningful work. A clear format spec produces comparable proposals; a hard deadline keeps the process fair; a sealed cost mechanism reduces evaluator bias; a receipt log creates the audit trail that protects the award from protest. This guide is the format, the mechanism, and the why behind each.
Comparable proposals require comparable format. Without a format spec, vendor A submits a 60 page deck with 8pt margins; vendor B submits a 12 page document with screen reader friendly layout; vendor C submits a Word file with embedded macros. Evaluators normalise by spending hours they should be spending on substance. The format spec to require:
| Element | Standard requirement |
|---|---|
| File format | PDF (PDF/A for archive-grade) |
| Page limit (technical narrative) | 15 to 25 pages depending on complexity; excludes appendices |
| Font | Arial, Calibri, or Times New Roman, 11pt minimum |
| Margins | 1 inch / 2.5cm minimum on all sides |
| Line spacing | 1.15 minimum |
| Section order | Required: executive summary; methodology; team; experience; pricing (separate file); references; appendices |
| Pricing | Separate sealed file (see Part II below) |
| Bookmarks / TOC | Required for proposals over 10 pages so evaluators can navigate |
| File naming | Standardised: VendorName_RFPName_TechnicalProposal.pdf |
| File size limit | 25 MB per file typical for email; 100 MB per file for portal submissions |
Federal procurement under FAR Part 15 requires technical and cost proposals to be separated so technical evaluators do not see the price during scoring. Private sector procurement increasingly adopts the same discipline. Three practical mechanisms in 2026:
Modern portals (Coupa, Ariba, Loopio, BidNet) support separate cost upload that is locked until technical scoring is signed off. The cost file is encrypted at rest and access logged. Cleanest mechanism for client-side, vendor-side, and audit trail.
Vendor submits technical proposal to one address and cost proposal to a different address. Technical evaluators do not have access to the cost mailbox; cost reviewer (procurement officer) does not share until scoring complete. Workable for small procurements without a portal.
Vendor submits both files to the same address but cost PDF is encrypted with a password the vendor releases only after technical scoring is signed off. Workable; requires procurement officer discipline.
For public sector and federal grant funded procurements, the FAR 15.305 (proposal evaluation) framework requires technical / cost separation; e procurement platforms support this natively (see the deep dive on e-procurement portals).
Accepting late proposals undermines the fairness of the process. It exposes the procurement to protest (other vendors did not have the same time and so the playing field was uneven), and it signals to all vendors that future deadlines are negotiable. The Federal Acquisition Regulation 15.208 allows late proposals only in narrow circumstances: received before award, and the delay was caused by government mishandling. Private sector procurement should adopt the same hard line.
The late bid policy to include in the submission instructions:
Proposals received after the published submission deadline will not be opened or considered. The deadline is fixed; the burden of timely submission rests with the vendor. Vendors are encouraged to submit at least 24 hours before the deadline to allow time for technical issues. The client is not responsible for transmission failures, portal outages on the vendor side, or postal delays. Vendors who experience technical issues with the submission portal must contact the procurement officer at the published email and phone number at least 2 hours before the deadline; the client may, at its sole discretion, accept a workaround submission method if the issue is attributable to the portal. Vendors who do not contact the procurement officer before the deadline will not receive an exception.
For the Q&A schedule that establishes when vendors can ask deadline clarifications, the meeting agenda template is useful for structuring the formal Q&A response meeting if your procurement uses one.
Every proposal that arrives is logged in a single procurement file. The log is the audit trail if the award is later challenged. Standard log fields:
Reference framework: FAR 15.207 (handling proposals) sets the federal standard. NIGP publishes equivalent best practices for state and local procurement.