Purpose: Find early indicators that an opportunity may appear. Key signals to monitor include expiring contracts, budget allocations, legislative changes, technology moves, and agency notices. Action: Log the signal, date found, and source. If no clear funding or timeline appears, mark a red flag immediately. The course materials list the main signal types to track.

Purpose: Gather basic agency facts and procurement context so the prime can form a go or no go impression. Key outputs: agency contact list, procurement cycle markers, funding sources, and recent awards. Quality check: confirm source dates and at least two corroborating references for each factual claim.

Purpose: Decide whether the opportunity is worth pursuing. Criteria: budget availability, prime past performance fit, competitive intensity, technical fit, and timeline feasibility. Action: Produce a short qualification summary with a clear yes or no recommendation and the top three reasons.

Purpose: Build a profile that explains the agency priorities and procurement habits. Key outputs: budget lines, stated priorities, pain points, procurement behavior, and known decisionmakers. Use this to shape early win themes.

Purpose: Identify likely bidders and how they compete. Key outputs: incumbent data, recent wins, pricing patterns, partnerships, and geographic strength. Quality check: confirm past-win facts from award notices or FPDS records.

Purpose: Estimate likely timelines and presolicitation events. Key outputs: expected release window, renewal cycles, and funding milestones. Action: give a confidence level and the evidence behind the forecast.

Purpose: Turn research into actionable capture items for the capture manager. Outputs: early win themes, discriminators, draft positioning ideas, and a list of open research questions. Quality check: ensure each capture input ties back to a named piece of evidence.

Purpose: Surface strategic risks early so the capture team can decide mitigation steps. Typical risks include incumbent advantage, budget uncertainty, political shifts, technical misalignment, and strong competitors. Flag each risk with likelihood and potential impact. The course materials recommend clear, early flags for these items.

Purpose: Give clear, decision ready guidance. Provide a concise go or no go, immediate capture actions, relationship building steps, and specific research gaps. Make recommendations actionable, with owners and deadlines.

Purpose: Deliver a clean, compact package the capture team can use without rework. Required handoff elements: structured summary, evidence links, risk notes, recommended actions, and analyst availability for questions. The materials describe what to include in a proper handoff to prevent rework.

Confirm the signal and collect source links, contract ID, and expiry date. Deliver: Signal brief with source list and confidence level.

Do quick early research on the agency, funding, and past awards. Deliver: Agency snapshot listing budget indicators, funding source, and prior LMS vendor.

Qualify the opportunity against simple criteria: budget fit, prime past performance, timeline feasibility, and likely competition. Deliver: Go/no-go recommendation and short rationale.

Build a one-page agency profile with priorities, procurement behavior, and likely decision roles. Deliver: Agency profile summary.

Make a simple competitor map, noting the incumbent, likely bidders, and any partner ecosystems. Deliver: Competitor map with 3 to 5 entries and short strength/weakness notes.

Forecast timing and key milestones, based on renewal cycles and presolicitation signals. Deliver: 6- to 9-month forecast and recommended watchpoints.

Produce early capture inputs: two or three win themes, suggested discriminators, and key risks to watch. Deliver: Capture input memo.

Flag risks and red flags clearly, and include recommended mitigation steps. Deliver: Risk register with severity and suggested actions.

Handoff: compile structured summaries, clear insights, and recommended next steps the prime can act on immediately. Deliver: Decision-ready package for capture. These steps reflect the standard prebid sequence and required outputs for effective pre-bid support.

Expiring contract: Countywide help-desk support, incumbent holds contract through September, contract value listed at about $850,000 annually. Record the exact end date, incumbent name, and any automatic renewal language.
New budget line: Fiscal planning documents show a new line item for "IT modernization services" allocated $1.2 million for next fiscal year. Note the appropriation code, fiscal year, and approval status.
Agency announcement: County IT posts a short announcement about a "digital services initiative" and invites stakeholder feedback at an upcoming board workshop. Capture the announcement text, date posted, and named contacts.

Expiring contracts create procurement timing, budget allocations supply funding, and agency communications reveal priorities and political cover for a buy. These categories of signals are standard early indicators to monitor in SLED work.
When timing, funding, and public intent overlap, probability of a solicitation rises from possible to likely. Treat that combination as medium or high priority for pre-bid research.

Low: single isolated signal with no funding or public mention.
Medium: contract expiration plus either budget or announcement.
High: contract expiration, explicit budget allocation, and an agency communication that aligns with the budget purpose.

Log a single consolidated entry. Include: title (county help-desk), source links, contract end date, incumbent, budget line details, announcement text and contact, and first-observed date.
Tag urgency: if the contract ends within 6 months and funding is approved, tag high; if 6–12 months and funding is proposed, tag medium.
Verify quickly: check the county procurement calendar and upcoming board or committee agendas for procurement items. Scan meeting minutes for procurement intent.

Identify the procurement officer named in the announcement or budget document, and prepare a one-paragraph informational email asking about anticipated timelines and whether an RFI or draft scope is expected. Keep the tone informational, not sales.
Escalate when needed: if verification shows active solicitation planning or a pre-proposal meeting scheduled, notify the prime and recommend capture actions.

County Help-Desk Renewal | Contract ends 2026-09-30 | Incumbent: Acme Support | Budget: $1.2M IT modernization line FY2027 (approved) | Announcement: Digital services initiative, public workshop 2026-05-12 | Signal strength: High | Next action: Check procurement calendar, draft outreach to procurement officer.

Renewal windows and expiration dates often predict upcoming procurements.

New or rerouted funds increase the likelihood of new solicitations.

Laws or rules can create or delay opportunities, and sometimes add requirements.

Platform or standards changes signal procurement for upgrades or services.

Public statements and meeting notes can foreshadow priorities.

Tag signals as weak, moderate, or strong based on source and corroboration.

Early signals allow time to influence strategy, later signals demand faster action.

Prioritize based on impact, not volume. Focus first on signals tied to funding, contract expirations, or clear agency intent. Cite and summarize the strongest evidence when escalating.

What to capture: official agency name, parent department, procurement office contact page, procurement portal URL, and whether procurement is centralized or decentralized. Note any alternative agency names or acronyms used in solicitations.

What to capture: short agency mission statement, recent strategic priorities, published budgets or budget summaries, and recent news or press that affect purchasing. Save links and the date you checked each source.

What to capture: expiring contracts, known renewal dates, fiscal year timing, published procurement forecasts or presolicitations, and any legislative or budget calendar items that could change timing. Track the source and the likely month or quarter for action.

What to capture: whether funds are state operating budget, federal grant, bond funding, or one-time appropriations. Record the funding line or citation and any limits on allowable uses. Note whether funding appears secure or conditional.

What to capture: recent awards for the same or similar scope, award dates, contract values, vehicles used, and incumbent contractor names. Save links to award notices or public procurement records.

What to capture: incumbents, frequent contractors in that agency, likely national primes, and local firms. Add one-sentence strength notes for each (for example, technical strength, pricing posture, or local presence). Keep this list short at first, then refine.

Look for a current appropriation, line item, or public budget document showing funding for the requirement. Check procurement notices, budget reports, and agency spending plans. Score green if funding is explicit and current, amber if funding is probable but not confirmed, red if no funding is visible. Budget availability is a primary qualification criterion listed in the course materials.

Match required services to past awards, contract descriptions, or performance narratives. Prefer recent, local SLED awards or similar scope. Score green when there are clear, closely aligned past wins; amber when experience is partial; red when no relevant past performance exists.

Identify likely bidders, incumbents, and known strong competitors from past awards, bid listings, and partner networks. High competitor density, strong incumbents, or multiple well-matched primes push score toward red. Low competition or niche requirements favor green.

Compare stated requirements, referenced standards, or prior solicitations to the prime’s capabilities. Note any technical gaps that would require new staffing or partnerships. Score green if the solution aligns with existing capabilities, amber for manageable gaps, red for major misalignment.

Check expected solicitation dates, submission windows, and required start dates against typical teaming, proposal, and staffing time. Short windows or immediate start requirements increase risk. Score green when timelines match normal prep time, amber for tight timelines that need extra resources, red for unrealistic schedules.

Estimate contract size, strategic value, and likelihood of win. Combine budget signals, past performance alignment, competitive intensity, and timeline into a single quick score. Use green for high value and reasonable win chances, amber for moderate value or higher risk, red for low value or high effort with low odds. Pursuit value is the synthesis that tells whether to place an opportunity in the pipeline.

County administrative system upgrade affecting finance and permitting.

Moderate, public budget documents suggest funding but no formal allocation yet.

Strong, prime already has similar implementations and reusable components.

High, two local incumbents and one national competitor routinely win these procurements.

Tight, anticipated solicitation in 6 weeks with only 3 weeks to respond.

First, look for recent awards on similar scopes and nearby agencies; past winners often try again.

Second, identify consistent partners or subcontractors who show up with multiple primes; those relationships influence teaming choices.

Third, watch pricing signals or contract award values to see whether competitors compete on low price, niche capability, or breadth of services. These elements form the basic competitor list and the simple facts you can confirm from public procurement records.

Create a one-page grid with five columns: Competitor name, Typical win themes, Pricing pattern, Key partners, Geographic strength. For each competitor, add one short phrase under each column. Typical win themes describe what the competitor emphasizes in proposals or contracts, for example local support, specialized compliance expertise, or low-cost delivery.

• Gather three recent awards for similar scopes in the same region. - For each likely competitor, record one win theme and one pricing pattern. - Flag any recurring partners or local offices as relationship advantages. - Rank competitors by threat level: high if they win similar procurements often, medium if occasional, low if no recent wins. - Share the one-page map with the capture lead along with a short recommendation: emphasize local relationships, adjust price posture, or develop a niche differentiator.

Past wins: Direct contract history with the city, recent delivery on incremental releases. Presence on historical awards creates familiarity with stakeholders.
Pricing style: Higher day rates, lower risk allowances, often tied to existing contract vehicles.
Strengths: Institutional knowledge, proven integrations, fast onboarding for maintenance work.
Weaknesses: Limited innovation, potential complacency, costly for larger new features.
Likely behavior: Will bid to protect renewal; may propose a continuity-focused solution.

Past wins: Multiple mid-size municipal and county engagements across the region.
Pricing style: Competitive on packaged solutions, flexible on financing for multi-year deals.
Strengths: Broad technical capability, deep local relationships, ability to scale for larger delivery.
Weaknesses: Less specialized in niche UX work, heavier project management overhead.
Likely behavior: Will position as low-risk full-service prime, pursue partnerships with niche specialists.

Past wins: High-rated UX or CRM projects, often for specific agencies or departments.
Pricing style: Value-based or higher per-hour rates for expert work, fewer concessions on scope.
Strengths: Differentiated technical depth, innovative methods, strong references in specific areas.
Weaknesses: Limited capacity for enterprise-scale hosting or large integrations.
Likely behavior: Will team as a subcontractor, highlight demonstrable outcomes and user metrics.

Past performance: Incumbent strong for continuity, SI strong for scale, niche strong for specialty outcomes.
Pricing tendencies: Incumbent premium for continuity, SI mid-range with packaged pricing, niche premium for expertise.
Reach and delivery: Incumbent local, SI regional with staffing, niche limited but deep.
Partners: SI often partners with niche firms; incumbents may keep subcontractor relationships; niche firms seek primes.
Threat level for the prime: SI is primary threat for full-solution bids, incumbent is primary threat on continuity and cost, niche is a threat only if the prime underestimates specialist requirements.

Positioning: Emphasize a blended approach that matches the city’s need for continuity and innovation. Highlight past performance on both integration and user outcomes to bridge the incumbent and niche narratives.
Pricing strategy: Offer a clear baseline for maintenance continuity, with optional priced bundles for innovation sprints. Avoid lowest-price traps by showing value in reduced risk and faster outcomes.
Teaming recommendation: Proactively offer the city a named niche partner for UX or CRM to neutralize that niche’s advantage and present a single accountable prime.
Risk flags to surface early: Incumbent advantage for procurement decisions, potential budget uncertainty, and aggressive regional SI pricing. Flag these in the prime’s go/no-go and capture planning.

Opportunity: City requests proposals for a 3-year, $3M digital services contract focused on CRM migration, mobile citizen services, and a usability overhaul.
Quick RSP analysis: The incumbent will push for renewal citing uptime and integrations; the regional SI will undercut on end-to-end delivery; a niche UX firm may try to influence requirements to focus on user research outcomes.
Suggested prime response: Lead with a short case study that shows CRM migrations completed on time and a measurable increase in citizen satisfaction. Offer an optional UX sprint priced as a separate deliverable, and propose a named niche partner to show capability while owning delivery.

Definition, look for contract end dates and extension clauses. Signals to watch: listed contract expiration dates, automatic-extension language, recent amendments. Quick RSP actions: extract contract end date into the tracking sheet, flag required lead time for outreach.

Definition, early public notices that an agency plans to buy. Signals to watch: presolicitation notices, draft RFPs, vendor outreach events. Quick RSP actions: capture notice text and date, add to timeline and set a reminder for follow up (30, 60, 90 days).

Definition, the timing of budget approvals and fiscal years that enable spending. Signals to watch: agency budget releases, grant awards, line-item funding notes. Quick RSP actions: note fiscal year boundaries on the forecast, mark any funding uncertainty for the prime.

Definition, expected replacement or upgrade schedules that trigger purchases. Signals to watch: vendor EOL notices, agency IT roadmaps, OEM refresh announcements. Quick RSP actions: match refresh dates with contract timelines, surface likely technical requirements to capture team.

Definition, how the agency has bought similar goods or services in the past. Signals to watch: prior award cadence, incumbent renewals, procurement method (RFP, sole source). Quick RSP actions: build a 3 to 5 event timeline of past awards, note repeating timelines and favored vendors.

Definition, a simple rating of how likely and how soon an opportunity will appear. Signals to watch: number and strength of converging indicators, source reliability, funding clarity. Quick RSP actions: assign Low/Medium/High confidence with a one-sentence rationale, update after each new signal.

Gather timing clues, including expiring contracts, budget allocations, agency announcements, and technology shifts, and mark the source and date for each item.

Check historical procurement patterns for the same agency and similar work, noting typical gaps between signals and solicitation release. Use at least two past examples when available.

Reconcile the clues and history, then estimate a most likely release window (example, month or quarter), plus an earliest and latest plausible date. Record the logic used to move from clues to dates.

Assign a simple confidence rating, such as High, Medium, or Low, based on signal strength and historical match. Write one sentence that explains why that rating was chosen.

Attach concrete actions tied to the forecast and confidence level so the prime knows what to do next, and include a review date to update the forecast.

Read the gathered evidence and mark facts, confirmed assumptions, and open questions. Keep each annotated item one sentence and cite its source.

Group repeated agency priorities, procurement behaviors, and competitor moves into 3 to 5 patterns. Label each pattern (for example: ‘cost control priority’ or ‘prefers local vendors’).

Convert each pattern into a short persuasive line that speaks to the agency priority and the prime’s capability. Aim for 2 to 4 win themes, each 8 to 12 words.

List abilities or assets likely to separate the prime from others, such as local presence, unique past performance, or a specific subcontractor. Keep discriminators factual and verifiable.

Record risk items with a simple likelihood note and an immediate mitigation idea.

One-paragraph strength and one-paragraph weakness, each focused on the opportunity, not general company background.

Offer one concise positioning sentence plus two tactical steps the capture team can use next.

Opportunity identifier: County K12 network refresh, procurement owner: anticipated RFP Q3, expected timeline: priority on security and remote learning.

Win themes: 1) Rapid secure deployment tied to recent County cyber memo. 2) Local district support team reduces disruption.

Onshore support partner, proven K12 implementation playbook (2019 award).

Past K12 award; clear local subcontractor relationships.

No incumbent replacement experience; limited state contract vehicles.

Risks: Incumbent strong relationship, budget uncertainty; mark incumbent as high risk in red.

Next steps: verify incumbent end date, confirm funding line, schedule capture sync.

Win Themes: Short phrase linking agency pain to the prime's benefit, framed as an outcome.

Discriminators: Specific capabilities or relationships the prime can claim that rivals lack.

Risk Indicators: Clear signs to watch, with likely impact and urgency noted.

Opportunity Strengths: Evidence that the prime can meet needs or that funding and timing are favorable.

Opportunity Weaknesses: Gaps or barriers the prime must address or mitigate.

Recommended Positioning: One-sentence messaging that ties a win theme to a discriminator and a proof point.

Definition: A current contractor has strong relationships, proven delivery, or contractual terms that make it hard for others to win.
Why it matters: Incumbents can block or slow new entrants, raising effort and cost to win.
Signs to spot: recent renewals, visible long-term contract, agency praise for existing vendor.
Action: Note the incumbent name, past performance highlights, and suggest whether outreach or differentiation is realistic.

Definition: Funding level or source is unclear, conditional, or at risk before procurement.
Why it matters: Without confirmed funding, pursuing the opportunity wastes time.
Signs to spot: no line item in current budget, pending budget votes, reliance on grants or one-time funds.
Action: Flag the funding status, cite the source, and recommend waiting or low-effort monitoring until funds appear.

Definition: Changes in leadership, priorities, or political support at the agency or government level.
Why it matters: New leaders can change priorities or pause projects.
Signs to spot: recent elections, new appointees, public statements changing direction.
Action: Record who changed, summarize likely priority changes, and rate the impact (low, medium, high).

Definition: New or pending laws that affect funding, procurement rules, or program scope.
Why it matters: Legislation can enable or block opportunities and change requirements.
Signs to spot: introduced bills, committee activity, scheduled votes.
Action: Note bill numbers, expected timelines, and whether the law would help or hinder the opportunity.

Definition: The prime or potential solution does not match the agency technical needs or standards.
Why it matters: Poor fit makes winning unlikely and increases rework.
Signs to spot: requirements referencing tech the prime does not support, incompatible legacy systems, or strict certifications.
Action: List the specific technical gaps and suggest whether teaming, subcontracting, or walking away is appropriate.

Definition: Competitors likely to bid with strong pricing, deep relationships, or aggressive teaming that reduces win chances.
Why it matters: Aggressive competitors raise competitive intensity and reduce margin.
Signs to spot: recent aggressive bids, major local presence, rapid partnership announcements.
Action: Identify the competitor, their likely strengths, and recommend whether to compete, partner, or deprioritize.

Definition: How clear and evidence-based the identified risks are to decisionmakers.
Why it matters: Low visibility hides important threats; high visibility supports prompt decisions.
Signs to spot: sparse or conflicting information, few corroborating sources, or strong, repeated signals.
Action: Rate visibility (clear, uncertain, hidden), attach supporting facts, and state recommended confidence in any go/no-go suggestion.

What to do: Review all recent research outputs, agency signals, and competitor notes for anomalies or changes. Prioritize items tied to funding, timelines, legislation, contracts, or tech shifts. Signals to watch include expiring contracts, budget allocations, and legislative changes.
Quick check: Is there a new or changed date, funding line, named decisionmaker, or public announcement? If yes, flag as a potential indicator.

What to do: Look for known red flags such as incumbent advantage, budget uncertainty, political or legislative shifts, technical misalignment, or aggressive competitors. These are common pre-bid risks RSPs must flag early.
Example indicator: A county posts a procurement notice but shows no new budget line for that program. Mark as possible budget uncertainty.

Categories to use: Strategic, Financial, Political, Technical, Competitive, Visibility. Choose one primary category per risk. Keep a secondary category only if it changes the recommended action.
Why classification matters: It guides who should handle the follow up and what mitigation is possible.

Simple rubric: Rate impact as Low, Medium, or High. Rate likelihood as Unlikely, Possible, or Likely. Combine into a priority judgment: High impact and Likely equals Immediate priority.
Rule of thumb: If impact affects the program budget or incumbent lock, lean toward High impact. If a recent public action or directive supports the risk, increase likelihood.

Minimum fields to record: Risk title, category, one-sentence evidence summary, likelihood, impact, recommended next step, confidence level, source(s) and date. Include a one-line executive summary at the top.
Example entry: Risk: Incumbent renewal advantage. Category: Competitive. Evidence: Incumbent’s contract expires 06/2026 with public renewal option; no presolicitation notices. Likelihood: Possible. Impact: High. Recommended step: Elevate to capture lead to assess teaming options. Confidence: Medium.

Elevation criteria: Any risk rated High impact and Likely, missing visible budget for the effort, or sudden legislative action that changes scope. When elevated, send a short brief, the one-line executive summary, and the supporting source links or documents. Handoffs should include structured risk notes so capture teams can act without rework.
Communication format: 1-line subject, 3-sentence summary, one-piece of supporting evidence attached or linked.

A single-line verdict, for example, Go, No-go, or Go with conditions. Keep it explicit so decision makers can act without asking clarifying questions.

Two to three sentences that connect the decision to the strongest evidence. Name the top two factors that drove the verdict, such as budget signal, incumbent strength, or technical fit.

List concrete next steps, each with an owner and a target date. Use verbs: confirm, contact, draft, or validate. Example format: 1) Confirm budget and timeline — Research Lead — due in 5 business days.

Mark each action as High, Medium, or Low priority, and show the order when steps depend on each other.

Go when a verifiable funding source exists, timeline fits the prime capacity, and no incumbent lockout is evident. No-go when budget is unclear, timeline is impossible, or the prime lacks required past performance. Quick evidence to collect: budget line item, procurement vehicle, recent solicitations.

Draft a one-paragraph capture memo stating rationale, assign a single capture lead, and schedule a 30-minute sync with the prime to confirm interest.

Build a 1-page strengths/weaknesses map, list potential partners, and prepare a draft outreach email for agency contacts.

Map program manager, procurement officer, and technical lead. Prioritize contacts by decision influence and access.

Use a 15-minute ask, reference a recent agency action (press release or budget item), and offer a short capability brief. Example line: "I noticed the county budget added funds for X. Can we schedule 15 minutes to share a brief capability update and learn about priorities?"

List three differentiators tied to agency priorities (cost, local presence, past program outcomes). Attach one sourced example of a similar win or capability that supports each differentiator.

Missing budget authority, incumbent identity and contract end date, evaluation criteria, and procurement vehicle. How to fill: check agency budget documents, state procurement portal, FOIA summary notices, and incumbent contract archives.

Each recommendation has a clear decision (go or no-go), required evidence, next action owner, and a deadline. Deliverables: 1-paragraph recommendation, supporting evidence list, and a 7-day action calendar.

Scan the core findings for 3 items: evidence that supports opportunity fit, clear risks, and deadline signals. Keep each item to one sentence. Mark any source with a date and owner so facts can be rechecked fast.

Ask which choices the prime must make now. Typical decision points include go or no-go, pursuing a teaming approach, or investing in further research. For each decision, note the minimum evidence needed to decide and the deadline for that decision.

Lead with a one-sentence recommendation the prime can act on. Follow with 2 to 4 evidence bullets that directly justify the recommendation. Primes need direction, not just data, so include go or no-go guidance and the main reason behind it.

For each recommended action, add who will do it, what they will deliver, and when. Use short, concrete tasks such as: "Contact procurement lead to confirm budget by Apr 15," or "Assign capture lead to confirm incumbent relationships within 3 business days."

List gaps that block a confident decision, and say how urgent each gap is. Example gap language: "No confirmed budget; treat as high priority until procurement note found." Flag red flags that require immediate escalation, such as contradictory agency signals or missing funding evidence.

Combine the one-line recommendation, 3 evidence bullets, 3 next actions with owners and due dates, and 2 open gaps into a single page or short email. Use plain headings so the prime can scan and act.

Confirm each key fact links to an original source. Save the URL or citation and note who published it.

Add collection or last-checked dates to every table, quote, and data point. If any item is older than the expected window, flag it.

Turn raw facts into short statements that explain why the fact matters for the opportunity, using one or two sentences per insight.

Use consistent fonts, labelled tables, and short headings so a busy capture lead can scan rapidly.

Cross-check competitor names, recent wins, and roles with at least two sources for anything that affects strategy.

Give each risk a short label, the reason it matters, and an immediate next step (for example, ‘confirm budget’).

Each recommendation should show what to do next, who should do it, and one expected outcome.

Prefer primary, official records first. Examples: agency procurement or contracts pages, state procurement portals, official award notices, published budgets and appropriations, procurement forecasts, and registered vendor/award databases. Note the exact source URL or file name and the page or section used for the fact. Cross-check at least one independent source when possible. Support for performing these checks is included in the course guidance.

Always include a visible date stamp for each fact. Use format: Last checked: 2026-05-19 (source name or URL). If a source contains its own date, show both: Source date: 2026-03-01, Last checked: 2026-05-19. If source dates are older than 12 months, flag as stale and add a verification task.

Write one 1 to 2 sentence summary that answers: What changed, why it matters to the prime, and the likely next step. Under the summary add 2 supporting bullets with the strongest evidence and the single most important implication for capture strategy.

Use consistent headings, short bullet lists, and clear citations. Required elements: one-line executive summary, date stamps, source list, one-sentence recommendation, and an attachments section. Name files clearly, for example AgencyName_competitor_map_2026-05-19.xlsx.

Verify who bids or wins similar contracts, recent award amounts, incumbent status, typical teaming partners, and observable pricing patterns. Verify each claim with an award notice, vendor press release, or contract registry entry. If competitor intelligence is missing, note the gap and list where to search next.

Use three lines: Risk label, Evidence, Impact and recommended mitigation. Example: Incumbent advantage. Evidence: incumbent won last two awards and is listed on recent renewal notice. Impact: High. Mitigation: pursue subcontracting with incumbent, or identify differentiator X within 10 business days.

Give a clear decision and next steps. Use this template: Recommendation (Go/No Go or Further Research), Owner (role), Top 3 actions (short, dated), and Timeframe. Example: Recommendation: Proceed to capture. Owner: Capture lead. Actions: 1) Confirm budget by 2026-05-26; 2) Contact agency POC within 3 days; 3) Identify 2 potential partners by 2026-06-02.

Tick to confirm: sources validated, source dates recorded, last-checked date present, 1 to 2 sentence synthesis written, formatting consistent, competitor facts verified, risks labeled with evidence and impact, recommendations show owner and dates. If any box is unchecked, hold delivery until fixed.

Scenario: County IT contract shows a presolicitation notice and a budget line in the county ordinance. Example entries: Source: county procurement portal (URL), Source date: 2026-04-15, Last checked: 2026-05-19. Insight: County aims to replace legacy system within fiscal year, likely award Q4. Risk: budget reallocation possible, impact medium, mitigation: confirm appropriation at next county meeting. Recommendation: Schedule call with capture lead and flag for follow up after next county meeting.

1. Add a Last-checked date to every deliverable. 2) Use the three-line risk statement format for every risk. 3) Always end with a single, dated recommendation that names an owner. These checks strengthen credibility and reduce rework for the prime and the RSP.

• Date: "FY 2022 funding assumed."
• Source: "Unknown blog and internal note."
• Recommendation: "Engage agency soon and track competitors."
• Competitor note: "Large incumbent likely to bid."

• An outdated date can lead the prime to assume funding is secured when it is not.
• Weak sourcing makes insight unusable for decision making.
• Vague recommendations do not tell the capture team what to do next.
• Competitor statements without evidence risk misdirecting strategy.

1. Verify sources. Confirm each factual claim has a named, reliable source.
2. Confirm dates. Check that funding, timelines, and award windows are current.
3. Check synthesis quality. Turn raw facts into a one line implication for capture.
4. Review formatting. Make headings, bullets, and data labels clear and consistent.
5. Validate competitor data. Cite prior awards or procurement records for claims about incumbents.
6. Confirm risk clarity. State what could go wrong and how likely it is.
7. Test recommendation actionability. Each recommendation must say who should do what and by when.

Flawed line: "Date: FY 2022 funding assumed."

• Check: Confirm funding year with public budget or solicitation notice.
• Fix: "Funding signal: FY 2024 provisional allocation in state budget notice dated 02/14/2024 (State Budget Portal)."

Before: "Agency may have funding. Sources unclear. Engage soon."
After: "Agency funding appears in the FY 2024 draft budget published 02/14/2024. Source: State Budget Portal. Recommended action: Prime to request an agency clarification call by 03/20/2024. RSP to monitor presolicitation postings for ABC Corp and two other vendors weekly."

• Use named links or file names for every source so the prime can check fast.
• Add one short implication sentence after each fact: what it means for the go or no go decision.
• Keep recommendations to one line with owner and deadline.
• Use consistent date format (MM/DD/YYYY) and label whether a date is published, estimated, or confirmed.

• Are all facts tied to a named source or document?
• Are dates labeled and current?
• Does each paragraph end with a one line implication?
• Are competitor claims backed by an award or procurement record?
• Does each recommendation name an owner and a deadline?

After applying these fixes, ask: Which remaining facts still need confirmation, and what is the next smallest research step to confirm them? A clear, simple follow up usually avoids larger rework later.