Gather only decision-relevant evidence. Pull the few strongest signals from the agency profile, opportunity forecast, and competitor snapshot such as confirmed budget allocations, explicit program priorities, incumbent performance issues, or a hard timeline. Where possible, record the source and date for each signal so reviewers can validate it quickly. The templates and quality checks emphasise evidence over raw data, and clarity over length.

Start with the agency priority, then map to a prime capability. For each theme, state: agency priority, why it matters, and how the prime meets it. Keep themes short and defensible. Example format: "Improve user adoption for statewide LMS, because the agency cites training shortfalls; propose turnkey training plus change management, leveraging the prime's statewide training contracts." The capture input sheet template calls for early win themes tied to agency priorities and realistic discriminators.

Convert every risk into a mitigation action. For each risk, list the evidence, the impact, and one concrete mitigation step. Use a short table or triad: Risk, Evidence, Mitigation. Example: Risk: tight timeline; Evidence: agency calendar shows award by Q3; Mitigation: prepare a compressed capture plan and propose a phased delivery that reduces near-term staffing pressure.

Make next steps specific, timebound, and assignable. Use plain phrasing such as: "Call procurement officer to confirm incumbent contract end date, by May 5, assigned to S. Patel." Avoid vague items like "continue research." Include immediate low-effort wins. Examples include a targeted LinkedIn mapping outreach, scheduling a short SME interview, or requesting budget confirmation from a public records contact.

Use a strict heading hierarchy so content is scannable. Reserve the largest heading for the deliverable title, then use one lower level for major sections (for example, Opportunity Snapshot, Key Insights, Recommended Actions), and a third level for subpoints (for example, Funding signals, Timeline issues). Keep heading labels short and consistent across deliverables; use the same label for the same content type every time. Consistent headings, clean spacing, and clear section hierarchy are required standards for pre-bid work and reflect professional brand expectations.

Lead with a concise top-level summary (one to three bullets) that gives the decision and why. Use short paragraphs and bullets; limit bullets to three to six items each. Put evidence that supports a recommendation immediately after the recommendation, not in a separate appendix. Use bold sparingly to highlight the single most critical fact on a page, not to create visual noise. The goal is that a reviewer can read the title and the first bullet of each section and understand the core recommendation.

Write in plain, professional language and maintain a single tense across a deliverable, usually present tense for facts and present or modal verbs for recommendations. Avoid speculative language unless explicitly labeled as hypothesis and supported by a gap analysis. Maintain the same level of formality across headings, bullets, and captions so the document reads as a unified product. The course quality checklist lists consistent tense and tone as a nonnegotiable formatting criterion.

Use a single clean typeface and size palette for body text and headings. Align bullets and ensure line spacing leaves 30 to 40 percent white space between sections so the eye can rest. Keep tables narrow, with a single clear header row and no decorative borders. Avoid logos, decorative flourishes, or multiple color schemes unless the prime explicitly requires branding. Keep file formats consistent (typically editable DOCX plus a flattened PDF).

• Title present and accurate
• Heading levels consistent and labeled
• Top-level summary present (1 to 3 bullets)
• Bullets short, aligned, and prioritized
• Tone and tense consistent throughout
• No spelling or grammar errors
• Key evidence placed immediately with recommendations
• File exported to required formats (DOCX and PDF)

Washington often centers forecasts on IT renewals and technology refresh cycles, so emphasize validated renewal dates, incumbent behavior, and timeline certainty when building an opportunity forecast. California requires deep technical context and leadership mapping, so expand procurement officer and program leader details in agency profiles and tie priorities to current statewide initiatives. Texas has a dense vendor market, which raises the value of granular competitor snapshots that document recent wins, pricing patterns, and regional presence. New York’s recurring statewide contracts mean pre-bid briefs should highlight contract vehicle history, renewal patterns, and statewide scale implications. These state patterns come from real SLED examples used to guide RSP outputs.

Opportunity forecasts: Prioritize the signal most relevant to the state. In places where renewals drive activity, validate contract end dates and incumbent posture. In states with legislative funding fluctuations, flag budget changes as the top insight. Agency profiles: Map decision-makers and procurement behavior where political or technical leadership is decisive. Add program-level budget snapshots when statewide programs are common. Competitor snapshots: Add more pricing and recent-win evidence in high-vendor markets, reduce speculative scoring where public records are sparse. Pre-bid briefs: Make recommendations tightly actionable, matching the state context, for example go/no-go guidance driven by contract scale or incumbent advantage. These recommendations follow the same deliverable structure and quality priorities used by capture teams.

Scenario: A prime asks for a fast brief on a potential IT replacement contract in Washington. Start with an opportunity forecast that confirms renewal timing and incumbent identity, add a short competitor snapshot focused on typical bid ranges in that state, and finish with a one-page pre-bid brief that gives a clear recommended next step. The prime will use that brief to decide whether to assign SMEs and begin outreach. The example pattern for Washington shows why forecasts and timelines are the highest priority in that context.

While RSPs prepare these deliverables, the prime typically reviews pipeline strategy, aligns internal subject matter experts, evaluates competitive posture, and plans early capture activities and outreach. Knowing these parallel actions helps tailor deliverables to the prime’s immediate decisions, for example producing a decision-ready brief if the prime is about to commit SMEs.