Source-to-Signal: How Public Documents Become Opportunity Intelligence

Every signal in Vendor Radar starts with a real public document — an agenda, a meeting packet, a budget resolution, a procurement posting. Below are illustrative examples showing how raw government documents become the actionable signals that land in your dashboard. Details are representative of the document types and signal patterns we process nightly across our monitored states.

Example 1: City Council Agenda → Project Planning Signal

FieldValue
Source documentCity council meeting packet — staff memo recommending authorization of a feasibility study for water main replacement along a downtown corridor
Government bodyCity of Moorhead, MN
Signal typeProject Planning (RFP Anticipated)
Service categoryWater/Sewer, Engineering
Contract value indicator$2.4M estimated
Forward-looking relevanceFeasibility authorization means an engineering firm will be selected for design within 3-6 months

Why This Matters

An engineering or water/sewer contractor who sees this signal can introduce themselves to the city engineer while the project is still in the study phase — months before a formal RFQ posts. A bid board would not show this until the solicitation is already live.

Example 2: County Board Minutes → Funding Authorization Signal

FieldValue
Source documentCounty board meeting minutes — resolution approving a $1.8M bond issuance for courthouse HVAC system replacement
Government bodyYellowstone County, MT
Signal typeBudget Allocation
Service categoryHVAC/Mechanical
Contract value indicator$1.8M bonded
Forward-looking relevanceFunding approved; procurement for design and installation will follow

Why This Matters

An HVAC contractor who sees this signal knows the county has committed money and will be soliciting for the work. They can reach out to the county facilities director to learn about project scope and timeline before any bid hits the street.

Example 3: QuestCDN Procurement Page → Active RFP Signal

FieldValue
Source documentSchool district procurement page via QuestCDN — RFP for roof replacement at two elementary buildings
Government bodyBismarck Public Schools, ND
Signal typeRFP Posted
Service categoryConstruction
Forward-looking relevanceActive solicitation with mandatory pre-bid meeting and submission deadline

Why This Matters

Active RFPs are valuable — but even more valuable when you have already seen the earlier planning signals. Vendor Radar threads these signals together so you can see the budget approval, facility assessment, and board discussion from months earlier, alongside the live solicitation.

Example 4: Park Board Budget → Budget Approval Signal

FieldValue
Source documentPark board annual budget adoption — $650K trail reconstruction + $180K irrigation replacement
Government bodyMinneapolis Park and Recreation Board, MN
Signal typeBudget Approval
Service categoriesLandscape/Public Realm, Construction
Contract value indicators$650K trail, $180K irrigation
Forward-looking relevanceBudget adopted — procurement is next

Why This Matters

A landscape contractor or civil engineer who sees this budget signal knows exactly which park board has money allocated and what it is earmarked for. That is a warm lead grounded in a public record, not a cold call.

Example 5: Committee Report → Contract Expiration Signal

FieldValue
Source documentCity finance committee agenda — upcoming expiration of managed IT services contract, staff recommends new RFP
Government bodyCity of Eau Claire, WI
Signal typeContract Expiring
Service categoryIT Services
Forward-looking relevanceExpiring contract with RFP recommendation — solicitation likely within 60-90 days

Why This Matters

IT service providers who track contract expirations can position themselves before the new RFP posts and demonstrate familiarity with the body's needs, instead of scrambling to respond two days before deadline.

Live Signals With Full Provenance

These are real published signals from Vendor Radar's production pipeline from 873 processed source documents. Each one links to the original public document. Signal dates, bodies, and summaries are pulled directly from our database — not illustrative examples.

Last refreshed: July 7, 2026

Live Signal 1: Budget Allocation

Government bodyCity of Lino Lakes · Anoka, MN
Signal typeBudget Allocation
Service categoryBuilding Facilities
Document dateJun 1, 2026
Signal generatedJun 1, 2026
Source documentView original public record

Lease revenue bonds fund a new Lino Lakes Public Works Facility.

Live Signal 2: Budget Allocation

Government bodyBismarck City Council · Burleigh, ND
Signal typeBudget Allocation
Service categoryConstruction
Contract value$450,000 planning allocation
Document dateMay 2, 2026
Signal generatedMay 9, 2026
Source documentView original public record

Bismarck discussed early funding for a public works maintenance facility study.

Live Signal 3: Rfp Anticipated

Government bodyMandan City Commission · Morton, ND
Signal typeRfp Anticipated
Service categoryHvac Maintenance
Contract value$180,000 estimated project
Document dateMay 2, 2026
Signal generatedMay 9, 2026
Source documentView original public record

Mandan staff previewed a facilities controls replacement that may move to RFP this quarter.

Live Signal 4: Rebid Recommended

Government bodyMinneapolis City Council · Hennepin, MN
Signal typeRebid Recommended
Service categorySecurity
Contract value$320,000 annual contract
Document dateMay 2, 2026
Signal generatedMay 9, 2026
Source documentView original public record

Minneapolis recommended rebidding contracted security services before the current term ends.

Live Signal 5: Contract Expiring

Government bodySt. Paul City Council · Ramsey, MN
Signal typeContract Expiring
Service categoryLandscaping
Contract value$95,000 annual contract
Document dateMay 2, 2026
Signal generatedMay 9, 2026
Source documentView original public record

St. Paul listed a grounds maintenance agreement nearing expiration in its committee packet.

The Pattern

Every example follows the same discipline:

  1. A real public document from a real government body is collected through our nightly scraping cycle
  2. The extraction pipeline identifies the forward-looking signal, classifies it by type and service category, and extracts relevant details
  3. Quality checks suppress noise, duplicates, and non-actionable content
  4. The published signal lands in your dashboard with a link back to the original source document

No speculation. No AI hallucination. Every signal traces back to a public record you can verify yourself.