Contracts & Purchase Orders Bridge

​

Overview

The Contracts & Purchase Orders Bridge lets you monitor public procurement data across your target accounts so you can track active contracts, upcoming expirations, and purchase orders tied to specific vendors. This is the bridge to use for competitive intelligence, renewal timing, and account prioritization based on real spend data.

​

Building your Bridge

The bridge building flow for Contracts & Purchase Orders follows the same three-phase structure as other bridge types in Starbridge: Describe → Refine → Create.

​

Searching for specific vendors

When your goal is to find contracts or purchase orders for specific vendors, input the names of those vendors directly as your search terms. The bridge will look for results for those specific vendors across your target buyer set. This is distinct from searching for contracts by topic or keyword.

​

Purchase Order-specific bridges

When building a Bridge where you’ve narrowed down Purchase type to Purchase Orders only, you won’t be able to input any scoring criteria because as mentioned above, it’ll look for the vendor names you inputted as the core signal.

​

Understanding scores and match reasoning

​

Purchase Order-only results

If you set the Purchase Type filter to Purchase Order only (without adding any match score criteria), every result in the bridge will behave as follows:

• Match score: 5
• Match reasoning: “This purchase order met all your search criteria”
• Summarized relevance: “N/A”

This is expected behavior. When filtering to Purchase Orders only, Starbridge is performing a straightforward lookup - confirming whether a purchase order exists for the vendors you searched. Because the check is binary (found or not found), there is no deeper document analysis to summarize, so the summarized relevance field is left blank.

​

Contracts with no match score criteria

If you are searching for contracts and do not provide any match score criteria, all results will also receive a score of 5 with the match reasoning: “This contract met all your search criteria.” This happens because without scoring criteria, there’s no rubric to evaluate contracts against — so every result that passes your filters is treated as a full match. To get more differentiated scoring, add match score criteria that describe what a strong contract match looks like for your use case (for example: “involves a multi-year renewal”).

​

Contracts with no available files

For some contracts in the public record, no underlying document files are available — only the record metadata (vendor, value, dates, etc.). When this happens, Starbridge is unable to analyze the contract in depth. These results will show the following in the Summarized Relevance field:

“No files are available for this contract”

This is not an error — it reflects the limits of the underlying public data source. You can still act on these results using the available structured fields (contract value, expiration date, vendor name, etc.), but AI-powered analysis of the document content won’t be possible.

---

​

Next steps

Explore other Bridge types to round out your Starbridge setup: