Physical underwriting intelligence · infrastructure capital

Underwrite what the physical world will actually deliver.

Physical underwriting intelligence

Atlas reconstructs project state from evidence, tests the assumptions under the capital structure, and returns a recommendation you can take into committee.

Request a demo Client login

The problemThe layer

A financed project can still fail to deliver.

Land, sponsor, permits, and a target COD can all be true — and the asset can still sit behind a conditional interconnection, a shared upgrade, or a clock that was never measured. Atlas connects physical reality to the capital decision.

See how it works

You bringThe decision

Decision objectives

The gap is not information. It is an independent read of the physical world.

A project can have land, a sponsor, financing, permits, contracts, and a target COD — and still lack the infrastructure required to operate on that date.

Illustrative. Not a published model output.

500 MW data center

An 500 MW data center deciding whether a Q4 2028 COD can actually energize. Atlas tests the node it sits on, who else is asking for that wire, and how interconnection, equipment, and upgrades move the date — then carries the slip into the capital terms on the case.

interconnection.csvequipment.pdf

01Find the binding path most likely to slip the COD
02Find the date where deliverability starts to fall — or withhold the score
03Find the dependency that should receive capital first

A1 PowerA2 PermittingA3 Equipment

Q1 What exists?Q2 What does it depend on?Q3 What is material?

Start

Dependencies

The project is only as strong as what must happen next. Each dependency is a named object on the path.

A node is the wire. An upgrade is shared. A slot has a lead. Atlas carries those objects — and who else sits on them — as conditions of the decision, not as a blended score.

Power

Description: Interconnection, generation, transmission, substations, transformers — and who else is asking for the same capacity.
Nodes held: 4,200

Permitting

Description: Zoning, environmental approvals, regulatory milestones — stated clocks held beside observed clearance.
Nodes held: 1,140

Equipment

Description: OEM slots, production, shipment, installation, commissioning — measured leads only where printed.
Nodes held: 860

Construction

Description: EPC, schedule, labor, site progress — construction is not energization.
Nodes held: 2,080

Utilities

Description: Service agreements, upgrades, capacity, connection dates — at the grain the utility actually published.
Nodes held: 640

Offtake / financing

Description: Contracts, financing conditions, milestone dependencies — claims held apart from delivery.
Nodes held: 310

Questions

Questions run against the reconstructed graph. Against a named construct.

Use the formats the desk already speaks. Add a slip, a hypothetical, a binding path. Every follow-up runs against the same construct and the same case terms.

What exists on the path to energization?

AThe node
BNetwork upgrade
CTransformer slot

What does the contractual COD actually depend on?

APermitting clock
BOEM lead
CEPC progress

At which dates would this project still deliver the contracted MW?

AQ4 2028
BMar 2029
CAug 2030

In your own words, what would make you hesitate to treat the deck date as a base case?

Two similar campuses, one wire. What decides between them?

AWho else is asking
BObserved clearance
CCapital already spent

Inside AtlasExplore · Ask · Scenario · Report

Evidence first. Then reconstruct the physical world under the decision.

Atlas is independent physical underwriting and re-underwriting intelligence for infrastructure capital. It reconstructs physical state from evidence, tests capital assumptions, and produces an auditable recommendation. Evidence before confidence. Refusal before invention.

Interconnection queues

ISO / RTO planning

Permit dockets

EIA-860 and EIA-930

PUC orders

The explorer above is a sample of the records Atlas draws on — examples, not the full catalog. Each source stays at its available grain and cadence. Gaps, irregular updates, and bias remain part of the system's limits — and of every report we write.

01 · Explore

Explore

Search the infrastructure universe — projects, markets, sponsors, nodes, and load books — without treating a printed pile as a named roster.

What this holds

Four surfaces. One decision loop.

Dependencies move together. A project is not a spreadsheet of independent columns.

Interconnection and equipment are not independent; neither are permits and construction. Atlas models those nodes jointly. Without those relationships, a project can match every one-way total and still energize a hall with no transformer behind it.

d = 2

What it depends on

Edges. A campus sits on a node; the node sits behind a 345 kV upgrade; the upgrade sits behind a transformer slot.

Why preserve it

Pairwise tables miss the three-way joint: this campus, this upgrade, this factory date.

Calibration works at two resolutions. The path, and the book it sits in.

Fit only the project and each path may look plausible while the portfolio totals drift. Fit only the book and the totals can match with no coherent asset underneath them. Atlas holds both — and reconciles them against what sponsors told you.

Predicted and observed mix

On contractual COD43% / 31%

Within 12 months62% / 54%

P90 tail22% / 28%

Capacity at date71% / 64%

Blue is predicted. Ink is observed.

Effect estimated during calibration

Select a trait to remove its effect.

A run does not claim to predict one project’s next act. Individual paths contain chance the profile does not observe. Atlas estimates how delivery changes across a population under the stated conditions — and refuses where the population does not clear.

Validation

Internal validation

Atlas withholds evidence from model development. Tests measure whether the system recovers delivery outcomes, preserves differences between projects, and carries learned relationships across time.

Validation

Validation in an engagement

Each engagement starts by naming the outcomes that matter and the performance needed for the decision. Those criteria are set before results are interpreted. Gaps remain part of the report.

What Atlas measures1 / 3

See what the project actually depends on.

The campus, the node it sits on, the load book it is counted in. If the wire moves, what else moves?

Decision exhibit

Ask a capital question.

A campus can look close on paper and still sit far from deliverable. The sponsor date stays a claim. The wire is a different object. Atlas holds them apart — then asks what capital should do.

View asTerminalMemoDeckSheet

Request a demo

Illustrative. Not a published model output.

500 MW data center

Contractual COD: Q4 2028
Deliverability Probability: 43%
P50 COD: Mar 2029
P90 COD: Aug 2030
Binding dependency: 345 kV network upgrade
Node: Named POI · shared upgrade

Every number you put your name on has a trail.

Atlas does not ask a committee to trust an unexplained score.

Material assessments connect back to the underlying evidence, observation date, source quality, and model version — so a VP can footnote the finding without inventing completeness.

See the chain behind the number See deliverability grades

Who it's for

Built for people who decide under physical risk.

Infrastructure investors

Infrastructure capital is underwritten on schedules, contracts, engineering assumptions, and expected capacity. Atlas reconstructs those assumptions as an observable physical state — then returns a distribution only where the record supports one. You take a recommendation into IC, not a brochure score.

Lenders

Debt repayment depends on physical infrastructure delivering the capacity assumed in the financing case. Atlas reconstructs the delivery path — the node, the other asks on that wire, the upgrade they share — and carries physical delay through debt service and downside scenarios under the covenants you attach.

Insurance

Construction and operational risk often starts with physical dependencies that can be observed before a loss occurs. Atlas provides an independent view of project progress, critical dependencies, and delivery uncertainty — stated clocks beside observed clearance, shared gates named as shared.

Developers

Your project schedule is a network of dependencies. Atlas names the node each site sits on, who else is asking for that wire, and which constraint should take the next dollar — so development capital is sequenced against the bind, not the deck narrative.

Large load

A lease is a claim. A printed load book is a pile. Named megawatts are footprints on a wire. Atlas holds them in separate columns, so a campus is not treated as live capacity and a metro is not treated as a published book.

Built for infrastructure investors, lenders, insurers, developers, and large-load buyers who cannot treat a sponsor date as a base case.

Engage

Put the next capital decision on the physical record.

Request a demo. We will show you how Atlas reconstructs a live file — what is proven, what is unknown, what a slip does to capital, and what the recommendation should be.

Request a demo Client login