
Government RFP Analyzer & Compliance Mapper
Parse RFPs, build compliance matrices, and draft compliant proposals instantly
What You Can Do
You can upload government RFPs and Claude extracts all requirements, maps them to compliance obligations, identifies regulatory gaps and risks, and generates proposal sections with full requirement traceability. The skill builds compliance matrices that show exactly which RFP sections address each regulation, flags non-compliance issues before submission, and produces draft response text keyed to specific requirements.
Features
Automatically identifies and categorizes all requirements from RFP documents, including technical specs, compliance obligations, submission criteria, and evaluation factors, with precise section references
Creates structured matrices that cross-reference RFP requirements against regulatory standards (NIST, FAR, DFARS, etc.), showing which sections of your proposal address each requirement
Flags compliance gaps, conflicting requirements, and areas where regulations may not align with RFP criteria, with severity levels and remediation suggestions
Maintains bidirectional links between RFP requirements, compliance obligations, and proposal sections, enabling quick verification and change impact analysis
Generates draft response sections for complex compliance and technical areas, keyed to specific RFP requirements with regulatory citations
Produces detailed reports showing which RFP requirements you've addressed, which need revision, and which create regulatory or technical conflicts
Simultaneously maps requirements against multiple regulatory frameworks, showing where regulations overlap or diverge
Example Output
Compliance Matrix Excerpt:
| RFP Section | Requirement | NIST Control | FAR Clause | Coverage Status |
|---|---|---|---|---|
| 3.2.1 Cybersecurity | Encrypt data in transit | SC-7(2) | 52.204-21 | Draft Section 4.1 |
| 4.1 Performance | 99.9% uptime SLA | CM-3 | 52.239-1 | Section 5.2 (needs review) |
Risk Flagged: Requirement 3.2.1 demands FIPS 140-2 encryption but RFP accepts commercial standards. Regulatory conflict: NIST SC-7 requires defense-in-depth; RFP requires single-layer approach. Recommendation: Request clarification before submittal.
Draft Proposal Section: Section 4.1 Cybersecurity Controls (addresses RFP 3.2.1, 3.2.2; implements NIST SC-7, SC-28): "Our solution implements AES-256 encryption for all data transit (RFP 3.2.1) and at-rest protection (RFP 3.2.2), meeting NIST SP 800-171 requirements and FAR 52.204-21 compliance obligations. [See Exhibit A: Security Control Mapping]"
What's Included
- RFP Parser Template: Workflow for extracting requirements from any government RFP format, with metadata tagging (type, scope, deadline, evaluation criteria)
- Compliance Matrix Builder: Reusable template that maps RFP requirements against FAR, DFARS, NIST, GSA, and agency-specific regulations in structured table format
- Risk Flagging Checklist: Framework for identifying regulatory gaps, conflicting requirements, unclear criteria, and feasibility concerns with severity scoring
- Traceability Log Template: Spreadsheet and markdown templates for maintaining bidirectional requirement-to-proposal links with status tracking
- Proposal Section Generator: Prompts and examples for drafting compliance-focused proposal sections with regulatory citations and evidence callouts
Who It's For
- Government Proposal Managers
- Compliance and Risk Officers
- Federal Bid Managers and Prime Contractors
- Technical Proposal Writers
Best For
- Analyzing complex federal RFPs with multiple regulatory layers
- Building compliance matrices for bid decisions and risk assessment
- Drafting technically sound proposal sections with regulatory traceability
- Identifying gaps and conflicts before proposal submission







