For developers & site selectors
Screen your development pipeline before you commit.
Review individual sites or a portfolio against the same infrastructure, ground and entitlement constraints. See which parcels deserve further diligence, which need verification and which should be ruled out.
01
Start with the sites and the decision.
Send the locations or parcel identifiers you already have, along with the load, timeline and decision criteria. The screen should answer the question your team is facing.
Inputs
- Parcel identifiers, addresses or map links.
- Portfolio size and geographic scope.
- Target load and development timeline.
- Known constraints.
- The acquisition, diligence or prioritization decision being evaluated.
02
Separate screening from verification.
Apply consistent infrastructure and site constraints across the pipeline. Then identify what still needs utility, site-specific or professional verification before a parcel can advance.
How each parcel is classified. These describe the decision framework, not results from a real portfolio.
Advance
Warrants further diligence based on the screen.
Verify
Has an unresolved condition affecting suitability.
Exclude
Fails a stated requirement, with the reason documented.
03
Put the findings into your workflow.
Use the results to prioritize diligence and communicate the reasoning downstream. Available formats include ranked results, reports, searchable maps and data exports, as agreed in the scope.
Outputs
- Consistent parcel rankings.
- Documented exclusions and constraints.
- Sourced findings.
- Outstanding verification items.
- Next steps for the sites that advance.
Watch · Screening at scale
Thousands of parcels in. The few worth buying out.
How a screen runs every parcel through the same constraints, rules out the rest with a reason, and ranks what’s left by the largest data center each one could hold.
How the work runs
Screen, verify, assemble, position.
01
Screen
Apply infrastructure and ground constraints to identify candidates.
02
Verify
Investigate the capacity, timing, access and site conditions that maps alone cannot establish.
03
Assemble
Identify adjoining parcels where the engagement requires a combined site.
04
Position
Document the reasoning and findings in the agreed format.
Questions
- Can we send a large list of parcels?
- Yes. BlackForge describes portfolio screening at scale. Provide the parcel locations or identifiers and the criteria the screen needs to apply.
- Does passing a screen mean a site is ready to build?
- No. Screening identifies the sites worth advancing and the conditions that still need verification. It does not replace the required utility, engineering or permitting work.
- Can we search for new sites instead of reviewing an existing portfolio?
- Yes. Use “Find a development site” to start with the project requirements rather than a parcel list.
Read and run the numbers
- Methodology How we screen and verify a site, in full.
- Screening at scale What you send, what comes back.
- Site Selection for Data Center Developers: What to Answer, in Order A guided path for data center developers: define requirements, screen power first, test land and approvals, then secure control and run diligence in order.
- What Does a Data Center Feasibility Study Cover? What a data center feasibility study examines, from power and buildable land to water, fiber, zoning and schedule, and how it differs from due diligence.
- Buildable acreage calculator Gross acres down to buildable acres.
Not you?
Know where to spend the next diligence dollar.
Bring the pipeline, target load and decision criteria. Start with a clearly scoped screen.
Scope my portfolio screen