An Opportunity Brief is a concise, evaluator‑aligned summary that highlights what will most influence bid/no‑bid choices and early strategy. Key uses include rapid bid/no‑bid, kickoff planning, extraction assignment, and identifying teaming needs. Primes expect to understand the whole opportunity in about five minutes, so the brief must prioritize scoring drivers, disqualifiers, and pricing constraints rather than every detail.

Core elements to include (short, scannable):

• Opportunity snapshot: agency, project title, RFP number, release and due dates, contract type, and pricing model.
• Evaluation criteria summary: scoring categories, weights, and any pass/fail items.
• SOW highlights: major tasks, deliverables, timelines, and required platforms.
• Compliance and submission flags: page limits, forms, mandatory certifications, and disqualifiers.
• Pricing overview: template, rate caps, and any cost restrictions.
• Contract and legal risks: indemnification, liability, data residency, and IP ownership.
• Addenda and contradictions: changes and any conflicts between documents.
• Early recommendations and clarification questions: suggested pricing posture, teaming gaps, and items to clarify with the issuer.

Imagine a state IT RFP with a tight 21‑day schedule, a fixed‑price model, and a pass/fail security attestation buried in an attachment. A two‑paragraph brief would: name the agency and due date, call out the fixed‑price requirement and rate caps, highlight the buried security attestation as a pass/fail disqualifier, flag the short timeline as a delivery risk, and recommend seeking a teaming partner with onshore security compliance. That short narrative lets decision makers see feasibility, compliance risk, and immediate next steps.

Rapid checklist to produce a usable brief:

• Perform a focused 15‑minute scan to capture structure, evaluation criteria, SOW scope, pricing, contract terms, and addenda.
• Extract mandatory requirements, scoring drivers, and disqualifiers first.
• Summarize the SOW and pricing constraints in plain language, avoiding long quotations.
• List red flags and recommended clarification questions, and add one clear early recommendation on bid posture.
• Format for a five‑minute read: clear headers, short bullets, and one-paragraph executive summary.

When you next review an RFP, ask: what three items would cause an immediate no‑bid decision, and what one capability gap must be filled to make a competitive bid? Capture those as the top lines of the brief. Remember, the most valuable briefs save hours of reading and convert extraction work into strategic insight for the prime.

Disqualifiers and mandatory requirements are decisive. If the brief flags items that remove eligibility, the prime will usually close the opportunity quickly. Early feasibility notes on staffing, certifications, or nationality restrictions directly affect bid/no-bid calls.

Pricing constraints and rate caps shape whether the opportunity fits the prime's margin targets. Flag rate limits and mismatches between SOW tasks and pricing forms so leadership can judge competitiveness fast.

Briefs set the kickoff agenda. Leadership uses them to assign extraction tasks, nominate lead authors, and sketch win themes before the formal kickoff meeting.

Highlight evaluator priorities and scoring drivers. These items drive early theme selection and the proposal outline, and they influence where subject matter experts should focus writing and proof points.

Note teaming gaps and capability shortfalls. When a capability gap appears in the SOW summary, primes use the brief to pursue specific partners or subcontractors quickly.

Capture early risk flags. Flag contradictions, missing attachments, unrealistic timelines, and domestic-handling or 'U.S. persons only' clauses so primes can escalate compliance or legal review immediately.

Start with an opportunity snapshot: agency, due date, contract type, pricing model. Call out pass/fail items and disqualifiers up front. List top 3 evaluator priorities and any scoring weights you found. Provide 3 short early recommendations: bid posture, teaming needs, and urgent clarifications. Deliver a red-flag summary with exact references to RFP sections and suggested owners for follow-up.

Evaluators reward clarity, feasibility, and alignment with stated criteria, so highlight the elements that map directly to scoring categories and pass or fail requirements. Use short bullets for each scoring driver and add a one line note that explains why it matters for evaluation. Avoid long extracts from the RFP; summarize the intent, not every clause.

Focus on items that stop a bid or change pricing materially. Key red flags include contradictory deadlines, missing attachments, undefined terms, unrealistic timelines, mandatory certifications, U.S. person or domestic handling requirements, and mismatches between SOW tasks and pricing templates. Flag each red flag with its location in the RFP and a recommended escalation priority: Critical, High, or Monitor.

Deliver a compact set of outputs the prime can scan in five minutes: an opportunity snapshot, an evaluation criteria summary, a concise SOW summary, compliance highlights, a pricing overview, contract risk notes, an addenda summary, a red flag list, recommended clarification questions, and one or two early strategic recommendations. Use consistent headings and a one page executive summary so the leadership team can brief others without reading the full brief.

1. Perform a 15 minute scan to find structure, evaluation criteria, SOW, pricing, contract terms, and addenda. Note items that must be verified later. 2) Extract mandatory requirements, scoring drivers, disqualifiers, and pricing constraints. Put each item on a single line with a citation to the RFP section. 3) Draft recommendations that tie back to scoring drivers and to risk mitigation. Keep recommendations tactical: ask one clarification question per unclear requirement, and state the likely impact on cost or schedule.

Scenario: A state agency RFP requires a cloud-hosted solution, lists a per-user rate cap in the pricing template, and has an addendum that adds a new monthly reporting deliverable. The brief should show: • Scoring driver: technical approach to cloud security, weighting if provided. • Pass/fail item: any mandatory certification such as FedRAMP or specific state certification. • Pricing risk: per-user rate cap that may force rework of the staffing plan. • Red flag: addendum introduces recurring deliverable not reflected in original pricing template. For each item, add the RFP citation and one recommended action, for example, request a pricing clarification and propose an alternative staffing mix if the cap applies.

• Use consistent, minimal formatting so the brief reads in five minutes. - Prioritize capture of pass or fail items first, then scoring drivers, then pricing constraints. - Attach the one page snapshot as the first document and the red flag list as the second. - Always supply at least one specific clarification question for each major ambiguity. - Date and time stamp your brief and any addenda checks so reviewers know you validated the latest documents. Reflective prompt: After you finish a brief, ask which two items would most change a bid or no bid decision, and whether those items are clearly supported by RFP citations.

Capture identifying facts: agency, project title, solicitation number, release and due dates, basic contract type, and the stated pricing model. These items create the executive snapshot leaders read first. Note any obvious timing pressure such as an imminent due date or unusually short questions window.

Scan the evaluation or instructions section for scoring categories, weights if listed, and explicit pass/fail requirements. Flag any mandatory qualifications or certifications. Evaluator priorities guide early theme and staffing choices. Write one line summarizing the top scoring driver, for example: "Technical approach 40%, past performance 30%, price 30." If weights are absent, mark scoring as unknown.

Skim the SOW or requirements to list major tasks, deliverables, timelines, and required platforms or tools. Call out any deliverables that imply onshore presence or specific security or data handling rules. Note any mismatch between task descriptions and where the RFP asks for pricing or labor categories.

Open pricing templates and contract terms. Extract rate caps, allowed cost types, renewal options, and noteworthy clauses such as indemnity, insurance, or IP rules. Flag items that will constrain pricing posture. Check for addenda or amendment notices and record them. Look for red flags including missing attachments, contradictory deadlines, undefined terms, unrealistic timelines, mandatory U.S. person requirements, or required certifications. Escalate any disqualifier immediately.

Snapshot: agency, title, solicitation no., dates, contract type, pricing model.
Top scoring drivers: brief phrase and any weights found.
Must have compliance items: pass/fail forms, required certifications, domestic handling rules.
Key SOW points: three core tasks, deliverables, and critical deadlines.
Pricing constraints and contract risks: rate caps, cost model limits, insurance or IP notes.
Red flags and missing info: list with one-line impact statements and suggested next action.

1. Send the one page snapshot and top three red flags to the prime contact.
   2. Open a follow up extraction ticket for the capture team for detailed compliance and pricing work.
   3. If a disqualifier exists, stop further work until clarified, and recommend a no bid if unresolved.

Clarity: State the requirement, expected deliverable, and any assumptions in plain, short sentences so reviewers can confirm compliance quickly.

Feasibility: Show realistic schedules, staffing assumptions, and evidence that the work can be delivered within stated constraints.

Alignment with evaluation criteria: Map major SOW tasks to the scoring categories and highlight the highest-weighted scoring drivers.

Risk mitigation: Call out contractual, technical, or timeline risks and simple mitigation options or tradeoffs.

Structured presentation: Use consistent headings, bulleted lists, and short summaries so an evaluator can grasp the opportunity in minutes.

Missing mandatory requirements or pass/fail items: If a required certification, form, or attachment is absent, the proposal can be removed from consideration.

Scenario: An RFP requires a 12 month delivery, a specific security certification, and provides a pricing template with a labor rate cap. A high-value brief will open with a two line snapshot that lists the deadline, pass/fail certification, and the rate cap. Next, show a one row mapping of the heaviest scoring categories to the SOW tasks. Then flag the certification as a disqualifier if missing, note any tasks that the pricing template does not cover, and recommend two clarifying questions to ask the contracting officer. The prime can then decide bid or no bid and assign extraction tasks immediately, because the brief highlights exactly what evaluators will check first.

Identify the top scoring drivers from the RFP and place them at the top of the Evaluation Criteria Summary and the Opportunity Snapshot so they are visible in one glance. Use the 15-minute scan to extract those drivers, disqualifiers, and pricing constraints rapidly, then surface them as the brief's primary callouts.
For each scoring driver, add a one-line implication: where in the SOW it appears, what capability the prime must show, and any immediate risks or missing evidence. That makes the scoring impact actionable for capture leads.

One-sentence strategic summary, one-sentence feasibility verdict, and one-line recommended posture (bid, pass, or conditional). Emphasize feasibility and alignment so leadership can act without deep reading; primes expect a concise, executive-ready brief they can absorb in five minutes.
Quick table: Top 3 scoring drivers, pass/fail items, price constraints, and top 2 risks. Keep language tight, using bullets and bold labels so reviewers scan instead of read.

Use neutral, evidence-focused language tied to evaluation criteria. Replace vague adjectives with specific facts, for example: "SOW requires X certification for Task 2, no waiver allowed," rather than "may need certification." That reduces perceived risk and shows attention to compliance. The brief should highlight feasibility, alignment to criteria, and mitigation steps rather than narrative filler.

If a disqualifier, missing attachment, or contradictory deadline appears, mark it as "Immediate Escalation" and include the exact citation (page or clause). Common red flags to escalate include missing attachments, undefined terms, conflicting deadlines, and domestic-handling or "U.S. persons only" clauses. Escalate early to protect bid/no-bid decisions.
Assign an owner and a deadline for clarifications. Add two recommended clarification questions tied to scoring impact, so the prime can request vendor clarifications that matter to evaluators.

Scenario: RFP weighting shows Technical Approach 40 percent, Past Performance 30 percent, Price 30 percent. Action: lead with a short line that ties SOW tasks to the technical approach score, list three SOW tasks that map directly to evaluator expectations, then provide a one-paragraph past-performance framing (what evidence to extract) and a pricing note that flags rate caps or unusual templates. This maps evaluation weights into priorities for capture and proposal teams.

Use the brief to recommend win-theme direction, pricing posture, and teaming gaps. Highlight where scoring priorities create opportunity to differentiate or where pricing rules force a conservative posture. Primes rely on these early signals to shape kickoff and make bid/no-bid choices.

Run a 15-minute scan to extract scoring drivers, disqualifiers, and pricing constraints.
Write a one-sentence feasibility verdict and one-line recommended posture for leadership.
Populate a two-column table: scoring driver versus required evidence (where to extract it).
Flag any red flags, add two targeted clarification questions, and assign an owner.
Format the brief for a five-minute read, using a concise snapshot up top and clear labels.

Which two scoring drivers would change the bid/no-bid decision if they were unmet, and what immediate steps would you recommend to verify or mitigate each? Use those answers to prioritize the extraction and escalation work.

Scan the brief for the two to three highest-weighted evaluation criteria and any pass/fail items. Those priorities are the starting points for themes because they reflect what evaluators care about most.

Write a one-line theme that states the customer benefit, points to a specific proof element, and, when appropriate, signals how risk is managed. Keep each theme short and evaluator-facing.

Link the theme to specific SOW tasks, deliverables, staffing plans, past performance examples, or pricing posture described in the brief. The Opportunity Briefs already summarize SOW and pricing constraints, so use those snippets as direct proof anchors.

Use words and measures evaluators value, such as feasibility, schedule certainty, or measurable outcomes. Where the brief flags disqualifiers or mandatory requirements, frame a theme so it demonstrates compliance up front.

Rank candidate themes by how many high-weighted criteria they address and how many strong proof points exist. Keep two to four themes total to maintain focus.

An RFP used attachments to hold required compliance forms rather than listing them in the main submission instructions. Evaluators treat missing mandatory forms as disqualifying items. Using the 15-minute scan method and the red-flag checklist helps find those buried items before the prime completes internal bid/no-bid and kickoff planning.

1) Start with the 15-minute scan, targeting attachments, exhibits, and referenced file names for the words required, mandatory, certification, exhibit, form, and attachment. The course recommends this as the initial rapid triage to catch compliance risks early.

2) Cross-check any found attachment against the Compliance and Submission Requirements section to confirm whether a form is pass/fail or required for submission. The core components list shows where to record pass/fail items and submission methods.

3) If a mandatory form appears only in an attachment, mark it as an immediate red flag and escalate with a one-line impact statement for the prime. Red flags to capture include missing attachments and pass/fail requirements that are not obvious in the main SOW or checklist.

- Opportunity Snapshot: Include agency, RFP number, and due date so the prime sees urgency. Core components guidance shows what to include in the snapshot and compliance summary.

1) Open all attachments and search for keywords: mandatory, required, certification, form, exhibit. 2) Match each attachment to the Compliance and Submission Requirements section. 3) Mark any attachment that looks required but is not referenced in the main instructions as a red flag. 4) Draft a one-line impact statement and one recommended clarification question. 5) Deliver the brief as an executive-ready page the prime can read in five minutes; include the snapshot, compliance summary, red-flag list, and recommended next steps.

Pricing templates can be changed or clarified after release, and those changes often redefine how the SOW maps to the price form. A brief that identifies where the SOW and the pricing template diverge reduces risk, speeds internal review, and shapes early decisions about fixed versus rate-based offers. Use the core Opportunity Brief approach of scanning for pricing model, rate caps, and addenda during the 15-minute scan; those items are primary inputs for pricing recommendations.

1. Locate and lock every pricing artifact. Capture the original pricing template and every addendum or clarification document. Note which version is official for submission.
   2) Map SOW tasks to pricing lines. Create a two-column mapping: left column lists SOW deliverables or tasks, right column lists the specific pricing line item(s) where cost should appear.
   3) Highlight mismatches and missing lines. Mark any SOW work that has no corresponding pricing line, and any pricing line that does not match a SOW deliverable.
   4) Quantify constraints. Extract rate caps, mandatory ceilings, and any cost-limiting language. Record whether pricing requires blended rates, separate labor categories, or fixed-price milestones.
   5) Draft a concise recommendation. Propose how to populate the pricing form: which labor categories to use, where to place one-time costs, and whether the prime should seek clarifications or propose a pricing alternative.
   6) Flag required clarification questions for the prime to submit before final pricing is set.

SOW Task | Pricing Line Item | Gap or Conflict | Suggested Action
Example: Onsite installation of 150 devices | Line 12: Hardware install, hourly | Line lists hourly labor only, no fixed per-device cost | Recommend per-device rate or ask for template update via clarification.

Imagine a solicitation where the pricing template lists only hourly labor lines, but addenda introduce a milestone deliverable tied to deployment completion. The Opportunity Brief should note the addendum, map the milestone to the nearest pricing lines, and recommend either converting estimated hours into a milestone price or asking the agency to add a milestone line. Present the recommendation in one short paragraph, with the estimated hours-to-milestone conversion shown as a simple calculation so the prime can decide quickly.

Keep the pricing summary at the top of the brief, no more than three bullet points: current template version, one critical mismatch, recommended pricing posture. - Attach the mapping table and any addenda snapshots as an appendix. - Include a one-sentence escalation: accept as-is, submit clarification, or propose alternate pricing. Primes rely on short, definitive guidance to set internal pricing teams moving quickly.

1. Confirm the official pricing template version and list all addenda.
   2) Ensure every SOW task appears in the mapping or is explicitly noted as uncovered.
   3) Extract rate caps and cost restrictions into a single line.
   4) Provide one clear pricing recommendation and, if needed, the exact clarification question to ask the agency.

certifications, past performance, and mandatory experience are verified first, because gaps can immediately disqualify a bidder.

primes gauge available staff, technical capability, and delivery readiness to see whether they can staff and manage the work if they pursue the opportunity.

liability clauses, insurance limits, data residency, and IP rules are reviewed to identify deal breakers or negotiation needs.

leadership will expect a short briefing to shape strategy and to assign extraction and drafting tasks for the proposal team.

primes form an initial view of feasibility, competitiveness, and acceptable risk tolerance that your brief will influence.

Primes rely on a fast snapshot to brief leadership, set early strategy, and allocate work. An effective brief identifies disqualifiers, scoring drivers, pricing constraints, and contract risks so the prime can make an informed call without re-reading the full RFP.