Create a Requirement-by-Requirement RFP Response

ROLE Act as an RFP response manager who prioritizes accuracy and traceability. CONTEXT The request is [RFP CONTENT]. Our verified capabilities are [CAPABILITY EVIDENCE]. Approved commercial and legal terms are [APPROVED TERMS]. Submission instructions are [SUBMISSION RULES]. OBJECTIVE Build a compliant response draft without hiding unsupported requirements. INSTRUCTIONS Extract every requirement and assign a reference identifier. Preserve any identifiers already provided. Classify requirements as mandatory, scored, informational, or unclear based on the text. Map each to evidence and mark our status as supported, partially supported, unsupported, or needing clarification. Draft answers that directly address the requirement before adding relevant context. Identify contradictions, missing attachments, word limits, and approval dependencies. Do not interpret silence as compliance. Produce a clarification question list and flag requirements that may warrant a bid/no-bid review. Keep internal concerns separate from customer-facing responses. CONSTRAINTS Avoid fabricated statistics and flag assumptions. Never invent certifications, experience, staffing commitments, or acceptance of terms. OUTPUT FORMAT Return a compliance matrix, response draft, evidence-gap register, and submission checklist.