Contracting: Opportunity review, pursuit decisions and proposal preparation
Existing engine · Live for signed-in organizations
Source authority and account linkage must be verified before hosted use.
Open in the applicationWINROVE / CONTRACTING / NETWORK & TEAMING
Permitted profiles only. No invented graph.
Network is a relationship graph with verification classes: an award record is stronger evidence than a handshake, and the graph says which one you are looking at. Private vehicle and partner records appear only for entitled accounts.
Open Pursuits ↗What this is not
Boundaries from the customer guide, stated on the record.
- A pursuit teaming roster, workshare, or NDA store.
- Profiles invented to fill an empty graph.
- Private vehicle opportunities without entitlement.
Keep the scope visible.
Task views describe the same workflow the workspace exposes. Availability is confirmed per organization.
Operation availability
INSIDE THE WORKFLOW
See the work in detail.
Choose a task to understand the records, decisions and next step.
Find and monitor relevant opportunities
Review public notices with their source, retrieval date and current availability. Save searches and monitor changes without treating empty or stale sources as fresh opportunities.
What you leave with: A reviewed opportunity with a source trail.
Availability is confirmed per organization before this operation is enabled.
Build the case for a pursuit
Keep the opportunity, source-located requirements, owner and bid/no-bid decision together. First-pursuit setup prepares contracting work; it is separate from joining an employer.
What you leave with: A recorded decision and accountable next step.
Availability is confirmed per organization before this operation is enabled.
Read instructions before drafting
Distinguish explicit instructions from interpretation and unresolved questions. Keep amendment versions and locators attached to the requirements used in a response.
What you leave with: Requirements that can be traced back to their source.
Availability is confirmed per organization before this operation is enabled.
Write, review and validate a proposal
Prepare sections from permitted evidence, review changes and inspect the final package. Preserve Word round-trip versions, section authority and review receipts. Readiness does not submit a bid to a buyer portal.
What you leave with: A reviewed package with unresolved issues visible.
Availability is confirmed per organization before this operation is enabled.
Explain the estimate behind the price
Work with rate evidence, labor assumptions, scenarios and a basis of estimate. Keep revisions and approval separate so a draft rate change cannot become an approved price silently.
What you leave with: An estimate whose assumptions can be inspected.
Availability is confirmed per organization before this operation is enabled.
Review award and spending context
Explore organizations, awards and spending within source access and freshness limits. Analysis informs a human decision; a model score is not a guaranteed award probability.
What you leave with: Source-aware intelligence for your review.
Availability is confirmed per organization before this operation is enabled.
Review teaming and workshare
Keep partner identity, proposed responsibilities and workshare with the relevant pursuit. Review relationship evidence and required agreements before carrying the team into a delivery handoff.
What you leave with: A team proposal with explicit responsibilities.
Availability is confirmed per organization before this operation is enabled.
Prepare reusable evidence and SF330 work
Find past-performance material, reusable documents and capability statements. SF330 preparation keeps its own fields and supporting evidence, rather than becoming a generic text draft.
What you leave with: Selected evidence and a package suited to the task.
Availability is confirmed per organization before this operation is enabled.