Build a source-linked opportunity pipeline with clear evidence states, owners, decision dates, and capacity gates for federal, state, and local bids.
A useful public-sector RFP pipeline is a source-linked operating queue, not a list of hoped-for revenue. For each possible bid, record the buyer, official source, evidence state, date checked, fit questions, owner, next action, decision date, and response capacity. Promote an opportunity only when the buyer evidence becomes stronger and a named person accepts the next commitment. For FY2027, use each buyer's actual fiscal and procurement calendar rather than treating the federal October 1 boundary as universal.
Federal acquisition planning can begin well before the fiscal year in which an award or order is needed. FAR 7.104 tells federal planners to begin when the need is identified and preferably well in advance of that fiscal year. (Acquisition.gov — FAR 7.104) That makes early signals useful, but it does not turn every forecast entry into a funded, final solicitation.
State and local calendars do not line up behind the federal October 1 boundary. NCSL reported that 46 states began FY2027 on July 1, 2026; New York, Texas, Alabama, and Michigan use other start dates, and several states had late or continuing budget arrangements in its July 1 review. (National Conference of State Legislatures — FY2027 State Budget Status) Cities, counties, school systems, and special districts can follow still different budget and board cycles.
So every pipeline row needs the buyer's jurisdiction, fiscal period, budget or planning source, and next official procurement event. “FY2027” is context, not proof that a bid will be released.
The row should preserve where the opportunity came from and what the team actually knows. A practical minimum looks like this:
| Field | What to record | Control question |
|---|---|---|
| Buyer and jurisdiction | Agency, department, city, county, school, state, or federal office | Are we tracking the actual buying office? |
| Need hypothesis | Plain-language description of the work | What source supports this description? |
| Evidence state | Signal, public notice, current solicitation, changed, or closed | Has the buyer made this stage public? |
| Official source | Direct URL, notice ID, document-set identifier, and date checked | Can another reviewer reopen the evidence? |
| Fit and blockers | Scope, geography, eligibility, vehicle, partner, delivery, and past-performance gaps | Which facts are confirmed versus assumed? |
| Ownership | Account lead, capture lead, estimator, proposal lead, and decision owner as applicable | Who must act next? |
| Next action and date | One observable action with a due date | What will strengthen or disprove the opportunity? |
| Capacity decision | Watch, investigate, qualify, pursue, respond, stop, or monitor | What work are we committing now? |
Do not collapse these fields into a single CRM percentage. A stage should describe the evidence and authorized work, not imply a win probability that the team has not measured.
Acquisition.gov maintains an official directory of recurring federal agency procurement forecasts. (Acquisition.gov — Agency Recurring Procurement Forecasts) Use forecast entries, enacted budgets, capital plans, board agendas, expiring-contract research, and authorized buyer conversations to form hypotheses.
At this stage, record the expected buying office, likely need, source date, and next event to watch. Do not copy an estimated date or value into committed revenue. The separate 2026 government contracting forecast explains how to rank these external signals; this guide governs what your team does with them.
SAM.gov's help center identifies contract-opportunity search, saved searches, notifications, NAICS and PSC filters, and federal-organization filters among its current search resources. (SAM.gov — Help) For local work, the City of Houston's Office of Business Opportunity illustrates why one account may require several official sources: it links the city's strategic purchasing, airport, public works, METRO, Port Houston, HISD, Harris County, state, and federal opportunity pages. (City of Houston — Current Contracting Opportunities)
Record the portal and buyer that control each row. An aggregator alert may trigger research, but it should not replace the official notice, current files, deadline, or authorized contact.
USAspending's Advanced Award Search exposes federal award data with filters including fiscal year, agency, recipient, NAICS, Product or Service Code, set-aside, and extent competed. (USAspending.gov — Advanced Award Search) That history can help test incumbent, contract-structure, buyer, and timing hypotheses.
Historical awards do not prove that a requirement will recur or that its scope, vehicle, set-aside, value, or winner will repeat. Keep “history reviewed” separate from “current opportunity confirmed.”
When a current notice or solicitation appears, reopen the opportunity from the buyer's actual files. Capture the notice identifier, deadline, complete attachment set, addenda, portal instructions, eligibility rules, delivery scope, evaluation method, and response burden. A live document set should replace—not merely decorate—the assumptions in the earlier row.
Use the go/no-go decision framework for the pursuit decision. If a prime and subcontractor are involved, the prime-versus-subcontractor responsibilities guide helps separate who owns submission, pricing, compliance evidence, flow-downs, and post-award changes.
The review should end with decisions and dated actions, not a tour of every account. Use this sequence:
Open the official source for every row whose date, status, or scope may have changed. Mark inaccessible or conflicting evidence as unresolved. Do not treat an absent update as confirmation that the old date still holds.
Review rows whose next action is due, whose evidence state changed, or whose blocker could reverse the pursuit. Decide whether to investigate, qualify, pursue, stop, or monitor. Record the decision owner and the facts used.
Compare likely response windows with the people who must estimate, write, review, approve, and assemble packages. If the team cannot support every plausible bid, explicitly defer or stop the weaker rows. A pipeline is useful when it exposes tradeoffs before deadlines overlap.
Every active row should leave the review with one named owner, one observable action, and one date. Examples include reopening an official forecast, attending a public industry event, confirming a vehicle requirement, requesting a teaming decision, or scheduling a formal go/no-go review.
Keep the source URL, access date, decision, and reason when a row changes stage. That history lets the team distinguish a buyer change from an internal choice and prevents the same weak opportunity from repeatedly reentering the pipeline without new evidence.
For federal negotiated acquisitions, FAR 15.201 encourages exchanges from the earliest identification of a requirement through proposal receipt, subject to procurement-integrity rules. It lists techniques such as industry conferences, market research, one-on-one meetings, presolicitation notices, draft RFPs, RFIs, conferences, and site visits. (Acquisition.gov — FAR 15.201)
That authority does not mean every buyer will engage in every way. Follow the stated channel, protect confidential strategy, and separate public buyer information from inference. After a solicitation is released, use the contracting officer or other authorized contact identified by the buyer.
GreenLight starts from the current opportunity files your team supplies from an agency portal or approved discovery source. It can help apply your organization's qualification rules and documented gaps to a human-reviewed GO, No Go, or Go With Conditions decision. If the team proceeds, GreenLight can organize detected response requirements into a source-linked package inventory with ready, missing, and needs-review states.
GreenLight is not a universal opportunity-search database or a replacement for SAM.gov, buyer portals, or your CRM. It does not predict an award or make the final pursuit decision autonomously. Automated extraction can miss a requirement, so the current solicitation and authorized buyer instructions remain controlling. The search-platform versus bid-readiness guide explains that handoff in more detail.
This framework was researched on September 17, 2026. Forecasts, budgets, portal records, notices, and solicitation dates can change after review. Public agencies do not share one fiscal calendar or procurement process. The framework does not predict solicitation volume, award value, competition, buyer acceptance, or win probability. Verify the current official source and controlling documents before committing resources or submitting a response.
Research reviewed September 17, 2026.
No. Treat it as a planning signal until current official evidence provides enough scope, timing, eligibility, and response information for a human qualification decision.
No. Use those fields only when your organization has a defined, evidence-based method and the buyer evidence supports the inputs. A source state, next action, decision date, and capacity commitment are more useful than invented precision.
Track the buyer opportunity and the prime relationship separately. Record who controls the buyer submission, what scope and evidence the prime needs from you, the internal commitment date, and the condition under which you will stop or proceed.
No. GreenLight complements official portals and discovery tools after your team has the current opportunity files. It helps with qualification and response-package readiness; it is not a universal replacement for government opportunity databases.
See how GreenLight helps your team qualify the opportunity, organize the buyer's requirements, and check the package before you submit it.