Portfolio Thinking:
Deciding Across Several Sites at Once

Portfolio decisions fail in two opposite ways. One method treats every facility as interchangeable and ranks weak estimates to two decimal places. The other commissions a full study everywhere and spends scarce time proving that many sites were never actionable. The useful middle is a staged portfolio screen: consistent enough to compare, specific enough to trust.

Section 01The portfolio is a decision system, not a spreadsheet

A single-site study asks which credible path best serves one operating need. A portfolio study adds a second question: where should the owner spend its next unit of attention and capital? The best technical answer at one location may not be the best corporate action if another site has a harder deadline, better control, stronger evidence, or a decision that unlocks several later sites.

The U.S. Department of Energy's current distributed-energy project process starts by defining goals, collecting site data, and screening either one site or a portfolio. Its first phase says headquarters or regional teams can screen multiple sites to identify and prioritize locations for further study. It also warns that technical and economic potential are not the only considerations; mission compatibility and an on-site project champion matter too.¹

That is the right division of labor. A portfolio screen does not approve equipment, establish a utility outcome, or replace site diligence. It decides which questions deserve resolution first. A site study then tests the shortlisted location against its actual load, tariff, utility path, fuel, space, controls, operating requirements, economics, and approval structure.

The portfolio view should therefore carry three honest outcomes: advance, hold for evidence, and stop. A hold is not a disguised recommendation. A stop is not a failure. Both protect the organization from turning incomplete site facts into corporate commitments.

Standardize the questions. Do not standardize the answers.

Section 02Build one comparable site record

Comparison begins with a common record, not a common technology. Each location should answer the same owner questions: what decision is pending, when it matters, who controls the premises and meter, what load must be served, what utility evidence exists, which physical resources are available, who can approve spending, and what happens if the owner does nothing.

Energy-use benchmarking is a useful first layer. EPA says ENERGY STAR Portfolio Manager can track and assess energy, water, waste, and greenhouse-gas data across a building portfolio, establish baselines, identify buildings to target, set goals, and track improvements.² Those functions make portfolio data visible. They do not, by themselves, establish service capacity, interval shape, project rights, operating criticality, or investability.

A location with high annual use can have little need for new firm capacity. A smaller account can hold the business's most time-sensitive expansion. A poor benchmarking result can point to efficiency work, while a strong result can coexist with an urgent resilience or growth constraint. Portfolio data should create questions, not preselect the answer.

Keep the record short and evidence-labeled. For every field, identify the source, date, owner, and confidence level. Separate measured usage from a planning forecast; a utility document from a verbal expectation; a current equipment quote from an allowance; and a confirmed approval route from a plausible internal sponsor. Unknowns belong in the record because they determine the next step.

Section 03Separate eligibility from priority

Eligibility asks whether a site has enough basis to enter the portfolio race. Priority asks whether it should receive effort before other eligible sites. Mixing the two rewards dramatic assumptions. A location should not rank highly because someone entered a large load forecast while leaving control, timing, and authority blank.

Use a first gate that cannot be overcome by points. Confirm the business decision, accountable sponsor, site and meter control, defensible load basis, and a technology-neutral reason to act. If the site fails one of these, resolve the fact or hold it. Do not let an attractive model compensate for the absence of a customer, meter, deadline, or decision right.

Then rank the eligible sites. DOE's project-identification guidance describes screening as a way to down-select viable technologies and locations before spending heavily on unlikely projects.¹ In a private portfolio, the same principle can be applied without importing federal requirements: use the cheap screen to select the next bounded study, not to declare a winner.

Priority should reflect consequence and executability together. A severe constraint with no controllable path may deserve an urgent fact-finding action, but not capital approval. A modest opportunity with clean rights, reliable data, and a near-term equipment replacement may be ready to move. The ranking must distinguish “important to understand” from “ready to fund.”

Section 04Use a score to expose judgment, not conceal it

A scorecard is valuable when it makes assumptions visible. It becomes dangerous when arithmetic creates confidence the evidence does not support. Use broad bands, written reasons, and a separate confidence marker. Do not add decimal precision to qualitative judgments.

An illustrative scorecard might use a scale from zero to three for decision urgency, value of resolving the constraint, site and utility control, evidence quality, path diversity, and internal ability to execute. These values and categories are illustrative estimates, not measured performance or a recommendation for any specific portfolio. The owner should set weights before seeing which site wins and should record why any exception was made.

Run a sensitivity test by changing one weight at a time. If a site falls from first to last under a small weighting change, the ranking is fragile. The right response is not to average the answers. Show the competing priorities and identify the fact or governance choice that would settle them.

Section 05Put economics on one basis

Portfolio comparison requires consistent economic boundaries. One site cannot be ranked on simple payback, another on internal rate of return, and a third on an avoided-loss estimate without showing how those measures relate. Use the same study period, price-date basis, discount convention, tax treatment, terminal assumptions, and treatment of operating, maintenance, replacement, and residual costs wherever the decisions are comparable.

NIST Handbook 135 explains life-cycle-cost methodology for facility investments and notes that the underlying method is generic enough to be useful in private-sector analysis. It also cautions that examples in its August 2025 edition still use data from an older annual supplement and should not be read as current economic conditions.³ The lesson for owners is direct: a durable method does not make stale inputs current.

DOE's Building Life Cycle Cost program compares alternatives on life-cycle cost and also calculates net savings, savings-to-investment ratio, adjusted internal rate of return, and payback.⁴ Those are different views of the same modeled cash flows, not substitutes for defining the decision. Use the metric that fits the owner's capital rule, but preserve the underlying costs and assumptions so another site can be compared on the same basis.

Some decisions are mandatory rather than discretionary. A failed transformer, a lease obligation, a committed production expansion, or a safety correction should not be forced into the same ranking as an optional cost-reduction project. First define the minimum compliant or operational path. Then compare alternatives around it. Portfolio discipline means separating unlike decisions before it compares their economics.

Section 06Map dependencies, concentration, and learning

Sites do not always move independently. Several can depend on the same utility process, internal engineering group, fuel arrangement, controls standard, maintenance team, vendor class, or capital committee. Selecting the apparent top projects one by one can create a portfolio concentrated in a single unresolved dependency.

Draw a dependency map beside the ranking. Mark shared approvals, common equipment or service assumptions, staff bottlenecks, construction windows, and data gaps. A portfolio with several high-ranked sites can still be brittle if all depend on one unconfirmed premise. Conversely, one carefully selected first site can create reusable meter-data methods, controls requirements, commercial questions, and commissioning evidence for later locations.

Learning has value, but call it what it is. A first project should not carry an invented financial benefit for “repeatability.” Record the exact reusable output: a verified tariff interpretation for comparable accounts, a standard data request, an approved controls architecture, observed maintenance needs, or a tested internal approval path. Confirm that later sites are similar enough before transferring the lesson.

Diversification is also not automatically good. Mixing technologies and vendors can reduce concentration while increasing training, spares, cybersecurity, service, and controls complexity. Standardization can reduce those burdens while making the portfolio more exposed to a common defect or service constraint. The owner should choose the trade consciously rather than let separate site teams create it by accident.

Section 07Compare complete paths at every shortlisted site

Portfolio thinking remains technology-neutral. Each viable site should compare complete paths against the same load, boundary, operating objective, evidence standard, and economic basis. The table below makes no site-specific cost, savings, output, emissions, availability, or schedule claim.

Section 08Sequence studies before capital

The first portfolio allocation is usually study effort, not equipment capital. A short screen can expose where a utility letter, interval dataset, site-control confirmation, fuel check, or operating decision will change the ranking. Resolve the highest-value uncertainty before building detailed models everywhere.

DOE's published multi-site REopt case provides a useful bounded example. FEMP evaluated solar and battery options at nine EPA facilities and identified five locations where the modeled options could be cost-effective; the agency then moved one location toward a feasibility study.⁵ Those dated results belong only to that public case. The transferable lesson is the sequence: consistent screening across locations, downselection, then deeper site work.

Use decision branches. If a utility response confirms an acceptable path, the next study may narrow to schedule, cost, and execution. If the response does not, the site may advance a broader onsite comparison. If meter or site control fails, stop technical work until authority changes. If load evidence is weak, collect data before sizing.

Do not order studies merely by expected project value. Order them by the value of the next answer. A modest data check that closes an entire branch can outrank an expensive model that refines an option the owner cannot yet approve.

Section 09Rebalance when facts change

A portfolio ranking has a timestamp. Loads move, service answers arrive, expansions slip, leases change, fuel and equipment offers expire, site leaders turn over, and capital limits tighten. Preserve the prior ranking and record each change rather than silently overwriting the model.

Use a fixed review cadence appropriate to the owner's decision cycle, plus event-driven reviews when a load commitment, utility document, site-control change, quote, operating failure, or capital decision alters a material input. Revalidate only what can change the decision. A portfolio process should reduce repeated work, not create a reporting ritual detached from action.

Track evidence age separately from project status. A site can remain strategically important while its supporting quote or load forecast expires. Another can move rapidly because one confirmed utility response eliminates a major uncertainty. The status should tell leadership whether the site is screened, evidence-held, under bounded study, ready for approval, executing, or stopped.

Keep resource limits visible. Advancing more sites than the organization can govern is not diversification; it is dilution. Each active location needs a named decision owner, the next question, a due event, and capacity to review the answer. Everything else belongs in a watch list with a defined trigger.

Section 10Produce a portfolio decision packet

The final packet should let leadership see the portfolio without mistaking a summary for site diligence. It should preserve comparable inputs, show evidence quality, identify dependencies, and make the next allocation explicit.

1. Portfolio objectiveState the business decisions the portfolio must support and separate mandatory needs from discretionary opportunities.
2. Comparable site recordsUse one field set for decision, deadline, control, load, utility evidence, physical resources, economics, sponsor, and no-project case.
3. Eligibility gateHold any location missing an accountable decision, defensible load basis, site and meter control, or technology-neutral reason to act.
4. Priority and confidenceShow broad ranking bands, source dates, uncertainties, weighting choices, and sensitivity rather than false precision.
5. Complete path screenCarry the honest case for and against utility, load-side, on-site, hybrid, and no-project paths at each shortlisted location.
6. Dependency mapIdentify common utility, staff, fuel, controls, service, approval, and capital constraints, plus evidence that can be reused.
7. Next allocationName which site receives the next bounded study or fact-finding step, what answer is required, and what outcome would change the queue.

The point is not to make every site look alike. It is to make every recommendation legible. Leadership should be able to see why one location advances, why another waits, why a third stops, and which new fact could reverse the order.

A sound portfolio is a sequence of decisions under constraint. It spends little to reject weak cases, enough to resolve material uncertainty, and capital only after site rights, operating needs, utility facts, complete technology paths, and economics describe the same project. That is how several sites become one disciplined program without turning a ranking sheet into a promise.