> ## Documentation Index > Fetch the complete documentation index at: https://hc.starbridge.ai/llms.txt > Use this file to discover all available pages before exploring further. # Contracts & Purchase Orders Bridge > A deep dive into building and configuring a Contracts & Purchase Orders Bridge — covering vendor search, scoring behavior, and how to interpret results. ## 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**. For a full walkthrough of the bridge building flow — including how to set buyer filters, search phrases, match score criteria, and preview results — see the [Bridge Building Flow](/builders/how-to-build-a-bridge) guide. ## 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. For PO lookups, vendor name is the primary signal — the more precise the vendor name, the more targeted your results. ## 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. Think of a PO-only result as a confirmation signal: Starbridge found a purchase order matching your vendor search. The match score of 5 means it passed all your criteria — in this case, simply that it's a PO for the right vendor. ### 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"). Add match score criteria to surface the most relevant contracts at the top of your bridge. See the [Bridge Building Flow](/builders/how-to-build-a-bridge) guide for guidance on writing effective scoring criteria. ### 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: Track board meetings and strategic plans across your target accounts. Monitor open RFPs and RFIs relevant to your product or category. Build a bridge from any web source using AI-powered scraping. Find and enrich key decision-makers across your buyer list. Track new hires, promotions, and departures at target accounts. Find and score conference lead lists based on attendance and relevance.