| name | rfp-response |
| title | RFP Response |
| description | Drafts evaluation-ready U.S. federal RFP responses across all standard proposal volumes (cover letter, technical, cost/price, reps and certs). Enforces FAR compliance, CPARS references, and Section L/M alignment. Use when preparing federal solicitation submissions, responding to government RFPs, or drafting procurement bids. |
| author | CaseMark |
| author_url | https://github.com/CaseMark/skills/tree/main/skills/legal/rfp-response |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | us |
| practice | government-contracts |
| language | en |
| tags | ["drafting","letter"] |
RFP Response
Produces a complete federal proposal structured to FAR requirements and scored against typical source selection criteria.
Prerequisites
Collect before drafting:
- RFP package — solicitation number, title, SOW, Section L/M instructions
- Contracting Officer — name, title, agency, address
- Offeror profile — legal name, UEI/CAGE, NAICS, small business certifications, SAM.gov status
- Past performance — 3–5 relevant contracts with CO/PM contacts, values, CPARS ratings
- Key personnel — resumes, clearance levels
- Cost data — indirect/fringe rates, labor categories and rates, subcontractor quotes
Quick Start
- Parse Section L (formatting) and Section M (evaluation factors) — these control everything
- Build a compliance matrix mapping every SOW/Section L requirement to a proposal section
- Draft volumes in order: cover letter → technical → cost/price → reps and certs
- Verify every capability claim cites past performance, test results, or published research
- Confirm all FAR/CAS citations against current regulations before submission
Proposal Volumes
1. Cover Letter (≤2 pages)
Include: addressee (named CO), solicitation reference, agency-specific mission knowledge, qualifications with CPARS ratings, compliance affirmation for all mandatory requirements, validity period (per solicitation, typically 60–120 days), authorized signatory with binding authority.
2. Executive Summary (≤3 pages)
- Restate requirements interpretively — connect SOW to agency mission (do not paraphrase)
- Differentiated solution with named methods, partnerships, or innovations
- Quantified value proposition tied to documented past performance
- Key personnel highlights and organizational depth
3. Technical Approach
Mirror SOW structure — one response per major task. For each task address:
- Methods, tools, technologies, and rationale for selection
- Resource requirements, dependencies, GFE/GFI needs
- Integration points with agency systems or other contractors
- Applicable standards (cite by name and number)
- QA/QC protocols, acceptance criteria, corrective action process
- Risk identification with specific mitigation plans
- Technical diagrams (professional quality, labeled, referenced in text)
4. Management Plan
Org structure: management philosophy, org chart with key personnel (% time, reporting lines, sub interfaces), PM authority and span of control.
