A pass/fail requirement has a clear, verifiable threshold. Either the proposal provides the required evidence and meets the stated limit, or it does not. Typical places to find these rules include insurance sections, licensing clauses, financial-stability statements, and staffing minimums. Evaluators use pass/fail checks to eliminate proposals before detailed scoring, so these items influence whether a proposal is even considered, not just how it is scored later.

Insurance limits: If the RFP lists a dollar limit for liability or requires the prime to be named as an additional insured, failure to provide a certificate that matches the RFP language results in disqualification. Some states have recorded disqualifications for missing or insufficient insurance evidence.

Licensing and registrations: A license that must be active in the contracting state is binary. If an evaluator verifies the license and it is absent or expired, the proposal is nonresponsive.

Financial stability or bonding: RFPs may require a minimum credit rating, audited financial statements, or a bond. Missing or inadequate documentation is treated as a fail.

Staffing minimums: Stated minimums for credentialed staff or cleared personnel can be pass/fail. If required resumes or certifications are missing, the proposal fails that check. The course materials list these common examples explicitly for SLED RFPs.

Exact RFP wording and section reference.
Proof type defined and an example file name.
Responsible owner and internal due date.
Severity label: disqualifier or scoring impact.
Evidence status: available, pending, or not available.
Addendum review completed.

Where to look and what to capture: extract task descriptions, deliverables, timelines, required tools or platforms, reporting frequency and formats, acceptance criteria, and any performance metrics. These items are typically embedded in the Statement of Work and task lists, and should be captured verbatim with the RFP section reference for traceability.
Why it matters: technical requirements drive the technical volume, staffing decisions, and scope of work used to build labor estimates and schedules.

Common extraction fields: requirement text, source (section and page), deliverable ID, acceptance criterion, deliverable due date, estimated level of effort, and suggested proposal location.

Where to look and what to capture: capture submission instructions such as format rules, page or file limits, file naming conventions, mandatory forms, required attachments, and delivery method or portal rules. These items are often in submission instructions and attachments.
Why it matters: failing an administrative rule frequently causes proposals to be marked nonresponsive even if the technical solution is strong.

Common extraction fields: exact formatting phrasing, required file types, hard limits (page, file size), signature or notarization requirements, and submission deadlines.

Where to look and what to capture: extract every instruction found in pricing templates and cost proposal sections, including required cost categories, labor classifications, rate caps, billing increments, travel rules, and whether the model is fixed-price, time-and-materials, or another format. Pricing templates frequently hide pass/fail elements and deliverable-linked fees, so capture any table cells and footnotes.
Why it matters: pricing extraction aligns costs to the SOW and identifies rate caps or prohibitions that will change the price build.

Common extraction fields: pricing cell text, required supporting spreadsheets, allowed cost elements, escalation rules, invoicing frequency, and any rounding or precision rules.

Open the RFP, attachments, pricing template, and contract redline. Turn on document search. Set the 15-minute timer.
- Note key metadata: procurement name, issuer, closing date, amendment numbers, and contact email.

Skim the table of contents, evaluation criteria, and the SOW headings. Capture the primary evaluation weights if shown.
- Rapidly search the PDF for trigger words: must, shall, required, vendor shall, contractor must. Flag any instances that look like pass/fail language.

Open the pricing template and note rate caps, cost categories, and any mandatory pricing fields.
- Scan contract terms for data residency, indemnification, insurance minima, and IP clauses that could require legal review.

Check for addenda or amendments and read their summary lines.
- Scan attachments, appendices, and footnotes for required forms, certifications, or signature pages that could disqualify a bid.

Document map: list of main volumes and where the SOW and evaluation criteria live.
Evaluation snapshot: criteria names and weights, if present.
Mandatory forms list: any named forms or certification statements.
Pass/fail red flags: missing certification, residency requirements, insurance minima, or mandatory-only statements.
Pricing quick notes: rate caps, required cost categories, and updated pricing templates.
Contract risks to escalate: unusual indemnity, data residency, or nonstandard termination terms.
Addenda log: amendment numbers and short notes on what changed.

Imagine a state health RFP. In the 15-minute scan you find: evaluation split technical 50, management 30, price 20; a required signed certification in Appendix D; an insurance minimum that could be a pass/fail; and an addendum that changes a deliverable deadline. From that you create a skeleton Mandatory Requirements Matrix and a red-flag note for the prime to review.

• Create a skeleton Mandatory Requirements Matrix with the fields requirement text, source reference, requirement type, risk level, and proposed proposal section.
  - Assign deep extraction tasks by document area and hand off any immediate disqualifiers to the prime for fast resolution.
  - Schedule the extraction pass and confirm who will check contract terms that require legal input.

Read the sentence slowly and mark exact phrases that impose a duty, limit, or condition. Look for trigger words such as must, shall, required, vendor shall, and contractor must, which signal mandatory obligations in U.S. SLED RFP language.

Record at minimum: the verbatim requirement text, the document section or page reference, the requirement type (mandatory, pass/fail, technical, administrative, pricing, contractual), a short paraphrase that states what must be done, a risk level, and a short notes field for clarifying context or cross references. The course materials recommend these structured fields as the extraction baseline.

Decide whether the item is a mandatory requirement, a pass/fail condition, a technical deliverable, an administrative instruction, a pricing constraint, or a contractual term. Use exact language clues to assign the type. Mandatory and pass/fail items carry the highest risk.

If the text includes certifications, eligibility criteria, required forms, or numeric thresholds, mark it as a potential disqualifier. Escalate anything that would cause immediate rejection if unmet. The curriculum highlights certifications, required forms, and domestic-only clauses as common disqualifiers to flag early.

Use simple rules: high risk for mandatory or pass/fail items with tight deadlines or special proofs; medium risk for technical requirements that need staffing or tools; low risk for formatting and purely administrative items. Add an explicit next action, such as gather a certificate, confirm pricing, or clarify with the prime.

Scan attachments, exhibits, pricing templates, footnotes, and any referenced contract language because mandatory requirements and pass/fail items are often buried outside the main SOW or instructions. Note the exact file name and page for each cross reference to avoid ambiguity.

Each requirement must be easy to find and read. Evaluators reward clean, consistent matrices and penalize ambiguous or cluttered entries, because ambiguity slows scoring and raises risk concerns.

Requirements that read as mandatory or pass/fail, such as insurance limits or licensing, must show a definitive yes or no and the evidence location. Evaluators treat those items as immediate qualifiers for responsiveness.

Every matrix row should cite the RFP clause, page or exhibit number, and any addenda that alter the text. Evaluators check for alignment among the SOW, pricing, contract terms, and the matrix.

Evaluators flag contradictions between the matrix, pricing templates, and narrative as risk indicators. Showing the same answer in multiple places builds confidence.

One requirement per row. Keep rows atomic so evaluators can mark a single item without confusion. Exact quoted trigger text and a short canonical summary.

1. Each RFP mandatory term has one atomic row and a pass/fail marker. 2. Every row cites the RFP location and has an evidence pointer. 3. Addenda revisions are visible and dated. 4. No contradictions between matrix, pricing, and narrative remain unflagged. 5. Required forms in attachments are mapped and their file names shown.

Text removed from nearby clauses, footnotes, or exhibits often omits limits, exceptions, or conditions that change compliance outcomes.

Single extracts often contain administrative rules, technical tasks, and contractual language. If not separated, mapping and scoring become inconsistent.

Without a section reference and original location, reviewers cannot confirm compliance against the source, so evaluators mark items as unclear or nonresponsive.

Raw text does not show whether a requirement is pass/fail, a threshold, or a suggestive preference, which prevents correct prioritization.

Later changes are difficult to reconcile when extracts lack clear provenance and classification. These failure modes are consistent with common extraction mistakes identified in the materials.

- Do I have the exact quote and a short paraphrase?
- Is the original section and page recorded?
- What requirement type best fits?
- Is it pass/fail or scored? Assign risk level accordingly.
- Are there attachments, footnotes, or addenda that change meaning?
- Has the item been mapped to a proposal volume or form?

Mandatory and pass/fail. These are absolute gates. Treat certifications, minimum experience, and insurance limits as immediate compliance checks to escalate quickly.

Technical. Work, deliverables, schedules, and reporting belong to technical teams. Keep them out of pricing and contract buckets so writers and technical leads know what to address.

Administrative. Submission rules, page limits, formatting, and file naming requirements require focused handling so submission staff do not break compliance.

Pricing. Rate caps, cost categories, and labor classifications directly affect cost models. If mixed with technical tasks, pricing errors can create contract-level noncompliance.

Contractual. Liability, indemnification, and data residency sit with contracts and legal. Treat these separately so legal review happens early. The RFP often hides each of these in different places such as the main RFP, pricing templates, contract terms, or addenda, so check all locations for type-specific items.

A short, practical workflow for separating types:
1. Quick scan for structure, SOW, pricing, and contract terms so you know where different types usually live.
2. Tag each extracted line immediately with a type label, section reference, and risk level. Capture these fields: requirement text, section reference, requirement type, risk level, and notes. Use these fields consistently across the matrix.
3. Map the tagged requirement to the correct proposal owner. Technical to writers and SMEs, pricing to cost leads, contractual to legal, administrative to submission lead.
4. Escalate pass/fail items and contradictions to the prime immediately. Addenda can change type or priority, so recheck tags after any addendum is issued.

Start by locating evaluator priorities in the compliance matrix. Pass/fail items, mandatory certifications, and explicitly stated evaluation criteria reveal what evaluators care about most. Convert those priorities into short, evidenceable messages. For example, if the RFP emphasizes security controls and onshore data handling, a win theme could read, "Proven secure delivery with domestic data residency and accredited staff," and each claim must point to a mapped requirement and supporting evidence. Use requirement references rather than general statements so evaluators can confirm alignment quickly.

Identify hard pricing constraints first. Pricing templates often include rate caps, mandatory cost categories, and labor classifications that constrain how rates can be offered; addenda may change these rules or add deliverables, so update pricing inputs when addenda arrive. Treat three price layers as working options: 1) compliant baseline, priced to meet all mandatory caps and deliverables exactly; 2) competitive posture, a carefully reduced margin where allowed and supported by efficient staffing plans; 3) risk buffer, added where mandatory staffing mixes, domestic requirements, or unclear deliverables raise execution cost. Choose the posture that matches the prime's risk tolerance and the bid/no-bid decision.

1. Flag pass/fail and domestic-only requirements, and mark their impact on labor sourcing and cost. 2) Extract any rate caps or required categories from pricing templates and lock them into the pricing workbook immediately. 3) Map high-priority evaluator requirements to one-line win themes, and attach the requirement reference and evidence source to each theme. 4) Model at least two price scenarios, baseline and buffer, and annotate which compliance items drive cost differences. 5) Escalate contradictions, hidden deliverables, or late addenda to the prime for pricing guidance before finalizing rates, because addenda commonly change pricing templates and deliverables.

An RFP shows a rate cap for junior staff, a mandatory US-resident project manager, and a required 24/7 support deliverable. The compliant baseline uses the capped junior rate, sources a US-resident manager at the market rate, and includes the full cost of 24/7 coverage. The competitive posture optimizes by shifting noncritical tasks to capped roles while ensuring the US manager remains. The risk buffer adds overtime and subcontractor contingency for the 24/7 requirement. Win themes focus on cost control within mandatory limits and low-risk staffing for continuous support, with references to the pricing table and staffing requirement in the compliance matrix.

• Win themes must be traceable to specific, mapped requirements so evaluators can find evidence quickly. - Pricing posture is constrained by mandatory pricing rules, staffing requirements, and hidden deliverables; model scenarios that show those impacts. - Treat addenda and pricing-template details as high priority, update the pricing workbook, and escalate inconsistencies immediately. - Use one-line win themes tied to requirement references to show evaluator-focused compliance and reduced risk.

Start with pass/fail items and mandatory language. Identify certifications, required forms, domestic-only restrictions, minimum staffing or experience floors, insurance limits, and any contractual clauses that would eliminate the vendor if unmet. The RFP often hides these in attachments, pricing templates, and addenda, so capture them immediately. If a mandatory requirement is missing, the prime is typically forced to rule out bidding because failure to meet mandatory items can cause immediate disqualification.

Immediate no-bid: Any unfixable pass/fail disqualifier, such as a missing mandatory certification or a domestic-only requirement that cannot be met. The consequence is disqualification, not a negotiable risk.
Conditional pursue with mitigation: Technical gaps, staffing shortfalls, or pricing mismatches that can be resolved by teaming, hiring, or scope reshaping. These require quantified mitigation plans and cost impact estimates.
Competitive concern: Pricing caps, hidden deliverables in pricing templates, or contract terms that erode margin. If the numbers make the bid noncompetitive, present clear cost and revenue projections so the prime can decide on posture or decline. Pricing templates often contain hidden deliverables that change the competitiveness equation.

Provide the prime with focused, evidence-based artifacts the moment extraction is complete:
- Pass/Fail List: each mandatory item, where it appears, and whether the team meets it. Flag any that are unmet as immediate disqualifiers.
- Mandatory Requirements Matrix: mapped requirement, requirement type, contract reference, and the proposal section that will address it. This becomes the prime’s compliance backbone.
- Pricing Requirements Mapping: note rate caps, cost categories, and hidden deliverables that affect competitiveness.
- Contract Risk Summary: liability, indemnity, data residency, IP ownership items and whether the prime accepts or needs redlines.
- Red-Flag Memo: a short decision memo stating feasibility, recommended path (no-bid, pursue with partners, pursue with mitigation), and the estimated cost or capability gap.

Scenario: An RFP requires U.S. residency for 60 percent of staff, a specific insurance limit that the vendor does not currently carry, and a pricing template that caps labor rates below the vendor’s standard. After extraction the RSP documents the residency requirement and insurance limit as pass/fail items and identifies the rate cap in the pricing mapping.
Steps the RSP should take:
1. Mark residency and insurance as pass/fail disqualifiers and notify the prime immediately. Provide evidence that the team cannot meet residency without a U.S. subteam or partner.
2. Quantify mitigation options: partner cost and availability, short-term insurance rider cost, or the cost to recruit U.S. staff. Present dollar and schedule impacts.
3. Recommend one of three paths with rationale: no-bid if disqualifiers cannot be timely fixed, pursue with a named partner if feasible, or decline because pricing caps make the work loss-making. Include the Mandatory Requirements Matrix and Red-Flag Memo to support the recommendation.

• Run the quick 15-minute scan to locate SOW, pricing, contract terms, and addenda. Capture obvious pass/fail items first.
  - Build or update the Mandatory Requirements Matrix and pass/fail list immediately after the scan. Make the red-flag list visible to the prime.
  - Create short cost impact estimates for any mitigation. Put numbers on staffing, insurance, and partner rates so the prime can compare options.

• Treat any unmet mandatory requirement as a potential disqualifier. A clear pass/fail list is the fastest way to avoid wasting writer and pricing effort.
  - Use the Mandatory Requirements Matrix as the single source of truth for eligibility, pricing alignment, and kickoff assignments.
  - When in doubt about a requirement that affects bid viability, escalate immediately with a concise red-flag memo that states the gap, its impact, and a recommended path.
  
  Deliver the artifacts listed above to help the prime decide quickly and confidently: the pass/fail list, the mandatory requirements matrix, the pricing mapping, the contract risk summary, and a one-page red-flag recommendation.

Purpose: Capture every explicit and implicit requirement from the RFP, attachments, pricing templates, contract terms, and addenda.
Minimum content: verbatim requirement text, document reference (page and section), extraction timestamp, extractor name, initial risk flag.
Format and owner: single searchable spreadsheet or database, standardized columns, owned by the extraction lead.

Purpose: Serve as the prime single compliance backbone that writers, pricing, and contracts reference.
Minimum content: unique ID per requirement, requirement type (mandatory, technical, administrative, contractual, pricing), pass/fail flag, mapped proposal section, remediation notes.
Format and owner: table (CSV/XLSX) with filters and version control, owned by the compliance manager.

Purpose: Quick reference of disqualifiers and strict binary checks evaluators apply.
Minimum content: requirement ID, exact compliance criteria, evidence required, current status (met/unmet), escalation path.
Format and owner: filtered extract from the matrix, owned by the compliance lead and verified with contracts.

Purpose: Translate SOW tasks and deliverables into proposal obligations and writer instructions.
Minimum content: SOW clause reference, mapped proposal subsection, acceptance criteria, delivery timeline, required evidence or sample deliverable.
Format and owner: mapping tab in the matrix or a linked document, owned by the technical lead.

Purpose: Link pricing template elements to specific deliverables, rate caps, and cost assumptions to prevent pricing mismatches.
Minimum content: pricing line item, linked requirement ID, allowed rates or ceilings, cost driver notes, assumptions to be disclosed to the prime.
Format and owner: annotated pricing spreadsheet, owned by pricing analyst.

Purpose: Identify contractual clauses that create liability, compliance burden, or performance risk for the prime.
Minimum content: clause text, risk rating (low/medium/high), suggested mitigations or exceptions, escalation to legal.
Format and owner: concise risk register (one page summary plus details), owned by contracts/legal.

Purpose: Ensure all addenda are reconciled with prior extraction and the matrix reflects current requirements.
Minimum content: addendum reference, changed requirements, delta view (added/modified/removed), update timestamp, verifier initials.
Format and owner: tracked changes in the matrix with an addenda log, owned by the extraction lead.

Purpose: Immediate visibility for items that could cause disqualification or require prime-level decisions.
Minimum content: item, why it is high risk, required prime decision or waiver, deadline for resolution.
Format and owner: prioritized action list (top of the matrix or separate dashboard), owned jointly by compliance and proposal manager.

Purpose: A short, decision-focused briefing the prime can use at kickoff to allocate writers, pricing, and legal tasks.
Minimum content: top pass/fail items, required forms, critical deadlines, outstanding decisions, file references for each requirement.
Format and owner: one- to two-page briefing plus linked artifacts, delivered by the compliance lead.