DATA CENTER RADAR · Published Oct 31, 2026 · Sources checked October 31, 2026
A project directory supplies candidates. A bidding watchlist adds a reason to revisit each candidate, an evidence check and a next action. For contractors and suppliers, that next action should relate to a specific package or purchasing route rather than a campus headline alone.
Start with the project directory and the project-finding guide. The workflow below is Radar’s suggested operating method. Its buckets and review intervals are planning choices, not verified industry benchmarks or promises of available work.
Define what earns a place
Give each entry a short reason for inclusion: relevant geography, a potentially suitable scope, a documented milestone or a company relationship worth checking. Record the unresolved question that the next review should answer.
A useful entry identifies the project and phase, source date, date checked, recorded development stage, responsible party and next action. Missing information should create a research task. It should not be filled with an assumption or hidden by a numeric score.
The right list size depends on your team’s review capacity and territory. Use a weekly review as a starting routine for active pursuits, then adjust it. An arbitrary maximum number of records or a one-hour rule is not a qualification standard.
Keep these fields together
| Field | Question to answer | Why it matters |
|---|---|---|
| Project, site and phase | Which development does this entry describe? | Prevents campus and building information from being mixed |
| Stage and supporting evidence | What happened, at what scope, and when? | Separates a proposal, permission and physical work |
| Target package | What might our firm supply or build? | Makes the opportunity relevant to your capabilities |
| Companies and roles | Who specifies, approves and buys the package? | Supports a specific contact and qualification route |
| Capacity or value | What scale does the source actually describe? | Helps prioritize research without inventing package size |
| Dates and source links | When was the event, source and check? | Keeps old evidence from appearing newly current |
| Action, owner and review date | Who does what next? | Turns the record into a manageable commitment |
Keep conflicting evidence and unknowns attached. A recently reviewed article may repeat an old announcement. A record’s review date is not the date construction changed.
Route the entry into a practical bucket
Use three simple buckets: pursue now, prepare next and monitor. Assign them using evidence about your package, rather than automatically translating a project stage into a buying decision.
- Pursue now: a relevant package and an actionable qualification, solicitation or purchasing route have been identified. Confirm requirements and dates before committing estimating time.
- Prepare next: the project is relevant, but the buyer, design release, qualification route or package schedule still needs work. Name the question to resolve.
- Monitor: the project lacks a near-term action for your team, is paused, or needs a future milestone before further pursuit effort is justified.
An under-construction campus can have packages already bought and other packages still to be released. An announced development can have preconstruction or long-lead activity. Neither label alone establishes an open bid. The construction timeline guide helps separate the milestones.
Identify who can buy your scope
A developer, operator, general contractor, trade contractor and equipment vendor may all appear around the same project. Their involvement does not make them interchangeable purchasing contacts. Use the developer and contractor roles guide to establish the relationship behind each name.
Record whether the buyer accepts open bids, uses an approved vendor list, appoints suppliers through a contractor or has another route. A company’s national data center experience is context, not evidence that it holds a specific local package.
Use size as context, not a win probability
An investment headline may include several phases or owner-purchased equipment. An MW figure may refer to IT load, facility demand or future campus buildout. Neither establishes the value of the package your firm can pursue.
Read the investment guide and capacity guide before ranking by size. Consider delivery capability, geography, relationships, qualification requirements and a confirmed buying window alongside scale.
Do not turn a record into a production forecast by multiplying its announced MW by an unexplained equipment ratio. Specifications and a purchasing schedule need their own evidence.
Watch for signals that change the next action
- A documented package solicitation or qualification invitation, with the issuer and response date.
- An award identifying the recipient and actual scope; an award can close a prime opportunity while creating a different subcontract research task.
- A design, service or equipment-release milestone tied to the relevant phase.
- A dated change in permission, work on site or schedule, supported by the responsible source.
- A withdrawn application, pause or unresolved conflict requiring a revised action and review interval.
Match the signal to the project. An event nearby, a general market report or a hearing notice does not establish what happened at your site. Check the outcome and subsequent actions before changing the entry’s stage.
Treat public notices according to what they establish
SAM.gov Contract Opportunities carries federal procurement notices. It is useful for the federal part of a search; it is not a directory of private hyperscale buying activity. Use the responsible state, locality or institution’s procurement portal for its own opportunities, and the identified project team’s route for private work.
The GSA guide to researching active solicitations distinguishes a solicitation from sources-sought notices and requests for information used for market research. An RFI is not itself an invitation to price a construction contract. Read the notice type, scope, eligibility, amendments and deadline before assigning a pursuit action.
Run a review loop your team can sustain
- Gather new evidence and entries due for review.
- Check each material claim against its source and match the site, phase and package.
- Separate the event date from the date your team checked it.
- Reassign the bucket only when the evidence or your firm’s circumstances justify it.
- Give actionable entries one next step, a named owner and a due date.
- Record what changed and set the next review date.
For example, a fictional entry might read: “Prepare next; electrical package buyer not confirmed; Alex to identify the purchasing party by next Friday.” That is a task to investigate, not a claim that a real project has an open electrical bid.
Age entries according to a stated team policy. A lack of fresh public news does not prove a project stopped. Downgrade the confidence or review frequency where appropriate, while retaining the last evidence and unresolved question.
Keep the evidence visible
Radar’s free weekly digest can feed a review loop with reviewed previews. Membership provides available project research and sources; depth varies by record. Neither replaces your own confirmation of a buyer or a package’s availability.
Use the coverage statistics and methodology to distinguish tracked records, discovery leads and public previews. They are research coverage measures, not counts of qualified bidding opportunities.
Frequently asked questions
How many records should a watchlist hold?
Keep a set the team can review at its chosen cadence. Prioritize relevance, evidence and actionable questions rather than an arbitrary target count.
Is a recorded stage enough to plan a bid?
No. It helps frame research, but the package, buyer, procurement route and current timing need confirmation.
Should paused projects be deleted?
Use your retention policy. A lower-frequency monitor bucket can preserve useful evidence without consuming the same attention as an active pursuit. Keep the reason for the pause and its source visible.
Where do RFIs fit?
They can provide a market-research or qualification action. Read the issuing body’s notice; do not treat an RFI as a construction solicitation or an award.
Sources and research limits
SAM.gov and GSA support the federal-notice distinctions above; links were checked October 31, 2026. The watchlist fields, buckets and review loop are editorial guidance. They do not establish available work at any named project.