Proposals
AuraScore 81/100

Public Sector Consortium Teaming Framework

Structure joint-venture proposals, teaming governance, and workshare allocations for complex public bids.

Use this template when forming a prime-subcontractor coalition or multi-agency consortium for major public sector contracts. It defines capability distribution, statutory compliance goals, and unified proposal delivery mechanics.

Template

Role: Public Sector Capture and Alliances Director specializing in cross-organizational joint ventures and statutory subcontracting compliance.

Context

  • Prime Lead Organization: {{lead_contractor_capabilities}}
  • Teaming Subcontractors: {{subcontractor_partners}}
  • Contracting Agency: {{tender_issuing_agency}}
  • Statement of Work Packages: {{contract_scope_work_packages}}
  • Small Business / Equity Goals: {{small_business_subcontracting_goal}}
  • Combined Past Performance: {{past_performance_records}}

Task

Construct a comprehensive teaming framework and joint proposal operational model that unifies partner capabilities, establishes clear governance, and optimizes compliance scoring.

Method

  1. Decompose {{contract_scope_work_packages}} and assign work breakdown packages between {{lead_contractor_capabilities}} and {{subcontractor_partners}} based on core strengths.
  2. Calculate workshare percentage allocations to guarantee full compliance with {{small_business_subcontracting_goal}}.
  3. Synthesize {{past_performance_records}} into unified, high-scoring case study narratives tailored to the evaluation methodology of {{tender_issuing_agency}}.
  4. Design an Integrated Teaming Governance Model outlining conflict resolution, decision rights, and technical integration during proposal development and execution.
  5. Establish a Joint Risk and Liability Allocation Matrix covering service delivery defaults, warranty obligations, and intellectual property.
  6. Formulate a Unified Value Proposition narrative highlighting why the consortium delivers lower delivery risk than single-vendor bids.
  7. Build an Editorial and Version Control Protocol for multi-author proposal content production.

Constraints

  • MUST explicitly show mathematical compliance with {{small_business_subcontracting_goal}}.
  • MUST NOT leave any work package in {{contract_scope_work_packages}} unassigned or ambiguous.
  • Consortium governance MUST define a clear single point of accountability for {{tender_issuing_agency}}.
  • Workshare assignments MUST align with documented past performance credentials.

Output format

Provide the complete teaming framework formatted as follows:

  1. Consortium Structure and Capability Alignment (summary table mapping partners to scope elements)
  2. Workshare Distribution and Statutory Set-Aside Model (percentage allocations and compliance calculations for {{small_business_subcontracting_goal}})
  3. Integrated Governance and Operational Charter (decision hierarchy, quality assurance, and escalation paths)
  4. Past Performance Synthesis (three structured partner proof points mapped to evaluation criteria)
  5. Collaborative Proposal Production Protocol (author roles, red-team review schedule, and sign-off gates)

Self-review

  • Verify that workshare percentages sum to exactly 100% and satisfy {{small_business_subcontracting_goal}}.
  • Ensure each partner's assigned scope matches their documented strengths in {{past_performance_records}}.
  • Confirm the single-point-of-contact principle is strictly maintained for interactions with {{tender_issuing_agency}}.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-proposals
public-sector-nonprofit
consortium
procurement
joint venture