Would a Lunar Contractor Sign This Contract?

Before we talk about building on the Moon, we need to ask a more uncomfortable question: who would accept the risk?

Imagine a contractor receives a lunar construction package: site preparation, grading, landing pad works, regolith handling, robotic operations, dust mitigation, and foundation preparation.

The scope is ambitious.

The drawings are preliminary.

The ground model is uncertain.

The worksite is 384,000 km away.

Would they sign?

The first lunar construction dispute may not be technical. It may be commercial.

The Core Argument

Lunar construction is usually discussed as an engineering challenge: rovers, robotics, excavation tools, sintered pads, habitats, power systems, and ISRU. But before any contractor accepts responsibility for building physical infrastructure on the Moon, the problem becomes commercial.

A contractor does not sign a vision. A contractor signs a scope, a price, a schedule, a risk allocation, and a set of remedies if the assumptions fail.

On Earth, a contractor can price uncertainty because the construction industry has mature mechanisms to manage it: geotechnical baseline reports, site investigation records, specifications, drawings, bills of quantities, access provisions, change mechanisms, delay events, insurance, dispute boards, and decades of productivity data. Even then, ground risk remains one of the most common sources of claims in tunnels, dams, foundations, mines, and major infrastructure.

On the Moon, that maturity does not yet exist.

The ground model is incomplete. The regolith behavior is not validated at the construction scale. Robotic production rates are uncertain. Dust behavior may interfere with equipment, power systems, thermal control, vision systems, seals, and mobility. Interfaces between landers, rovers, habitats, power systems, communications, and construction equipment will be complex. Logistics will be constrained by mass, launch windows, mission priorities, spare parts, and energy availability.

That means the first lunar construction contracts cannot be treated as conventional fixed-price construction packages.

If procurement tries to transfer unvalidated lunar ground risk, robotic productivity risk, dust risk, power risk, communications risk, and interface risk to the contractor, the result will not be commercial certainty. It will be inflated prices, heavy qualifications, weak competition, or no responsible bidder at all.

The central issue is not whether lunar infrastructure can be built. It probably can.

The real point is whether it can be procured, priced, insured, executed, measured, accepted, and paid for under a contract that a serious contractor would actually sign.

That is where lunar construction must move from mission architecture to commercial architecture. The industry needs frameworks that recognize uncertainty rather than hide it. Early lunar construction should be procured through progressive delivery, open-book pricing, target-cost mechanisms, defined baselines, compensation events, and shared risk registers. Only after ground conditions, equipment performance, production rates, and acceptance criteria are validated should more traditional performance-based or fixed-price elements be introduced.

In simple terms:

A contractor can manage construction risk. A contractor cannot be expected to absorb planetary uncertainty.

That is the core commercial challenge. Lunar construction will not advance only by improving technology. It will advance when owners, agencies, primes, contractors, insurers, and investors agree on who owns which risk, under what assumptions, and with what contractual relief when those assumptions prove wrong.

Procurement - Are We Buying Hardware or Construction?

One of the biggest mistakes in early lunar infrastructure planning is treating construction as merely another space hardware delivery problem.

That is understandable. Space procurement has traditionally focused on delivering systems: a payload, a rover, a lander, an instrument, a robotic platform, a communications package, or a technology demonstrator. The success criteria are often tied to deployment, functionality, mass, power, data return, mission duration, and technical performance.

That mindset works well when the deliverable is a system.

It becomes incomplete when the deliverable is a constructed asset.

A lunar landing pad, road, berm, trench, foundation platform, or habitat preparation area is not just hardware. It is a physical work package executed on a real site, under uncertain ground conditions, with constrained access, limited logistics, risk of robotic productivity loss, dust exposure, power limitations, safety constraints, quality requirements, and performance expectations.

That changes the procurement logic. A rover can be procured as a system. A landing pad must be procured for construction.

The difference is not semantic. It affects pricing, risk allocation, schedule control, acceptance criteria, insurance, change management, and dispute resolution. A contractor building a lunar landing pad is not only delivering a piece of equipment or operating a robotic tool. The contractor is being asked to transform an uncertain ground surface into an engineered asset that performs under repeated loading, thermal cycling, dust disturbance, plume effects, and mission-interface constraints.

That is a very different obligation.

Construction procurement normally requires a defined scope, budget, construction schedule, site layout, assumptions for temporary works, access provisions, resource plan, safety plan, risk register, quality requirements, and commercial mechanisms for change. Before a contractor prices the work, it needs to understand not only what is being built, but also how the site will be accessed, how work fronts will be organized, how temporary facilities will be supported, how production will be measured, and what happens if the actual site conditions differ from the assumed conditions.

The Moon will be no different in principle. It will be more difficult.

A lunar construction package cannot simply say: “Prepare the site and deliver the pad.” It must define the baseline assumptions behind that instruction. What regolith strength is assumed? What bearing resistance is required? What settlement tolerance is acceptable? What surface roughness is allowed? What dust level is tolerable? What equipment availability is assumed? Who provides power? Who controls communications? Who owns the delay if a lander arrives late? Who owns rework if plume interaction damages the prepared surface? Who verifies acceptance?

These are procurement questions before they are engineering questions. A lunar landing pad is not just a technology package. It is a construction work package exposed to geotechnical uncertainty, logistics uncertainty, interface risk, and operational risk.

If procurement treats it only as hardware, the contract will likely miss the real risk drivers. It may over-focus on the machine and under-define the work. It may specify the rover but not the ground baseline. It may define the technology demonstration but not the acceptance criteria for the constructed surface. It may fund the system and forget the construction method, the temporary works, the production assumptions, and the commercial relief mechanisms.

That is where disputes are born. A practical concern is: can we procure a construction outcome that a responsible contractor can price, execute, measure, and defend?

For lunar infrastructure, procurement must shift from buying isolated systems to buying integrated construction capability. That means the contract should integrate hardware, operations, ground characterization, construction methodology, quality verification, interface management, and risk allocation into a single coherent commercial framework.

Otherwise, we may successfully deliver the machine and still fail to deliver the asset.

Contractor Perspective - What Would They Ask First?

Before signing a contract for a landing pad, road, trench, berm, foundation platform, utility corridor, or habitat preparation area, the contractor would ask a basic question: What exactly am I being asked to price?

That question is not conservative. It is how construction works.

Contractors do not price ambition. They price scope, risk, productivity, remedies, and payment certainty.

The first question would be about the ground model.

What is the interpreted ground condition at the proposed worksite? Is the regolith loose, dense, layered, blocky, cemented, ice-bearing, highly variable, or affected by ejecta deposits? What is the expected thickness of surficial regolith? Are there boulders, buried blocks, voids, hardpan layers, or abrupt changes in density? What assumptions are being made for bearing resistance, settlement, trafficability, excavation effort, dust generation, and surface stability?

Without a ground model, there is no construction baseline.

The second question would be about the data supporting the regolith parameters.

Are the values based on orbital data, Apollo-era data, simulant testing, remote sensing, rover observations, penetrator data, geophysics, sampling, or actual in-situ testing at the construction site? Are the parameters measured, inferred, estimated, or assumed? What confidence level is attached to the data? What variability is expected across the work area?

A contractor will not treat a remote interpretation with the same commercial confidence as local ground-truthed data.

The third question would be: Who owns unknown subsurface conditions?

This is one of the most important questions in contract law. If the contractor encounters materially different regolith conditions, buried boulders, unexpected hard layers, excessive sinkage, low trafficability, unstable slopes, voids, or ice-bearing material that behaves differently from the baseline, who pays? Who owns the delay? Who owns the additional energy demand? Who owns the rework? Who owns the failed production rate? Unknown ground conditions are already a major source of claims. On the Moon, they could become the first major construction claim.

The fourth question would be about access and mobility.

How does the contractor reach the worksite? What is the trafficability of the route from the lander to the construction area? What slopes are acceptable? What turning radius is available? What surface roughness can the robotic plant tolerate? Are there exclusion zones around landers, habitats, science assets, power systems, and communications equipment? What happens if the access route deteriorates due to repeated rover traffic, dust disturbance, wheel sinkage, or slope instability?

A construction site is not only the final asset location. It includes the access route, staging area, equipment operating envelope, charging location, communications line of sight, maintenance area, spoil placement area, and emergency recovery path.

The fifth question would be about production rates.

What production rate is assumed for excavation, grading, compaction, sintering, material handling, trenching, berm construction, or surface finishing? Are those rates demonstrated in relevant lunar-like conditions or estimated from laboratory trials and terrestrial analogs? Do they include downtime for dust cleaning, battery charging, thermal constraints, communication delays, tool wear, wheel slippage, sensor degradation, and operational hold points?

A production rate is not just an engineering number. It is a commercial number. It drives exposure to price, duration, contingency, staffing, equipment redundancy, and liquidated damages.

The sixth question would be about dust-related loss of performance.

Who owns the consequences if dust reduces solar-panel efficiency, blocks sensors, degrades seals, increases wheel slip, damages joints, affects radiators, contaminates mechanical systems, or reduces visibility for robotic navigation? Is dust an ordinary contractor risk, a shared environmental risk, or an owner-retained mission risk? What level of dust exposure is considered foreseeable? What level triggers relief?

Dust is not a housekeeping issue on the Moon. It is a construction, operations, safety, and asset-performance risk.

The seventh question would be about serviceability.

What happens if the completed landing pad, road, trench, berm, foundation, or prepared platform does not meet the required serviceability criteria? What are those criteria in the first place? Surface tolerance? Bearing resistance? Settlement under load? Dust-generation limit? Thermal performance? Sintered crust thickness? Trafficability after repeated passes? Resistance to plume erosion? Compatibility with robotic mobility?

A contractor cannot guarantee performance unless performance is defined.

The eighth question would be about change.

What is the change mechanism if the mission architecture evolves after award? What happens if the habitat location changes, the lander mass changes, the rover type changes, the construction sequence changes, the pad size increases, or the acceptance criteria are modified? Is there a compensation event? Is there a time-extension mechanism? Is there a process for revising the ground baseline or production assumptions?

A contract without a change mechanism is not firm. It is fragile.

The ninth question would be about payment.

How is the contractor paid? Milestones? Measured quantities? Target cost? Reimbursable cost? Performance incentives? Unit rates for excavation volume, graded area, compacted area, sintered area, berm length, trench length, or haul distance? What evidence is required for payment when the work is remote, robotic, and verified by sensors?

Payment certainty will matter as much as technical feasibility.

The tenth question would be about disputes.

If the parties disagree on ground conditions, production losses, dust impacts, serviceability failure, delay, rework, or acceptance, how is the dispute resolved? Is there an independent technical reviewer? A dispute board? A mission-level adjudication process? A predefined hierarchy of contract documents? A baseline report that governs entitlement?

The more remote and uncertain the worksite, the more important the dispute mechanism becomes.

A responsible contractor would not ask these questions to slow the mission down. They would ask them because these are the questions that convert a concept into a buildable, priceable, and executable contract. The Moon does not remove the commercial logic of construction.

It intensifies it.

Risk Transfer - The Dangerous Part

Risk transfer is where lunar construction becomes serious.

In every construction market, there is a line between reasonable contractor risk and irresponsible risk transfer. Cross that line, and the market does not become more efficient. It becomes more expensive, more defensive, and less competitive.

The Moon will make that line sharper.

If an owner, agency, prime contractor, or mission integrator transfers unknown lunar ground behavior, untested robotic productivity, dust interference, equipment degradation, communication delays, power interruptions, launch-interface risk, and mission architecture changes to the contractor, the contractor has only three rational responses.

Qualify the bid.

Inflate the price.

Or walk away.

That is not because contractors are unwilling to take risks. Construction contractors take risks every day. They take means-and-methods risk, productivity risk, sequencing risk, temporary works risk, safety risk, subcontractor risk, and quality risk. In tunneling, mining, dams, underground works, and major infrastructure, contractors routinely manage difficult ground, constrained access, complex interfaces, and aggressive schedules.

But contractors cannot responsibly price uncertainty that has not been defined, bounded, investigated, allocated, or linked to contractual relief.

That is the dangerous part of lunar procurement.

There will be a temptation to write bold contracts that push everything downstream: “The contractor shall be responsible for all site conditions, all robotic performance, all dust impacts, all operational interruptions, all interface delays, and all final performance outcomes.”

That may look strong on paper.

Commercially, it is weak.

A contract that transfers unpriced planetary uncertainty does not remove risk from the project. It simply hides it until pricing, claims, failure, or non-performance exposes it.

The better approach is to separate risks that the contractor can reasonably manage from risks that should remain with the owner, mission integrator, or be treated as shared baseline risks. A contractor may reasonably own means and methods within defined constraints. If the ground baseline, access limitations, equipment envelope, power availability, work windows, acceptance criteria, and operational restrictions are clear, the contractor can decide how to execute the work. That is normal construction logic.

A contractor may also own equipment maintenance within known operating envelopes. If the robotic plant is designed for specific dust exposure, temperature range, duty cycle, slope tolerance, regolith abrasiveness, and power cycle, then maintaining that equipment within those assumptions is a reasonable contractor obligation.

The contractor should own quality control of executed works. If the scope is to grade a surface, compact a zone, excavate a trench, form a berm, or prepare a foundation platform, the contractor should be responsible for verifying that the executed work meets the agreed specification.

The contractor can also own production planning based on agreed assumptions. If the contract defines baseline production rates, working windows, charging cycles, expected regolith conditions, haul distances, downtime allowances, and survey hold points, then the contractor can plan resources and manage productivity against that baseline.

The contractor should also own the safety of its own robotic and operational system, provided the mission environment and interface constraints are properly defined.

Those are legitimate contractor risks. But there are risks the contractor should not fully own.

• The contractor should not fully own unknown regolith behavior outside the provided baseline. If the site contains unexpected buried boulders, hardpan layers, loose zones, voids, ice-bearing material, excessive sinkage, slope instability, or strength conditions materially different from the baseline, that is not ordinary contractor risk. That is a ground-risk event.

• The contractor should not fully own unvalidated bearing capacity or settlement assumptions. If the owner requires a landing pad, habitat platform, or road to perform against criteria based on parameters that have not been confirmed at the construction scale, that risk must be shared, qualified, or linked to staged validation.

• The contractor should not fully own the dust plume effects from landing and launch operations by others. If a lander, ascent vehicle, or nearby mission asset damages the prepared surface, re-mobilizes dust, erodes a berm, contaminates equipment, or changes the serviceability condition of the asset, that is an interface and mission operations risk.

• The contractor should not fully own communication blackouts or mission-level constraints. If remote operation is interrupted by communication architecture, line-of-sight limitations, bandwidth restrictions, command latency, or mission-priority decisions, those delays cannot be treated as ordinary contractor delay.

• The contractor should not fully own power availability controlled by others. If excavation, grading, compaction, sintering, surveying, or robotic mobility depends on mission-supplied power, then power interruptions, reduced availability, or charging constraints must be treated as owner or shared risk.

• The contractor should not fully own interface risk with landers, rovers, habitats, ISRU systems, power assets, communications infrastructure, or science payloads unless those interfaces are fully defined, frozen, and controlled.

• The contractor should not fully own changes in mission architecture after award. If the pad size changes, the landing location moves, the rover fleet changes, the habitat load increases, the construction sequence changes, or the acceptance criteria evolve, that is a compensation event.

This distinction is essential because lunar site preparation remains an immature construction environment. The industry is still dealing with limited in-situ data, extrapolated regolith models, uncertain construction-scale behavior, unproven production rates, and the need for iterative field validation. That does not mean lunar construction is impossible. It means the commercial model must be honest about uncertainty.

How much risk can be pushed to the contractor? Or which party is best able to understand, control, price, mitigate, and absorb each risk?

That is how real construction markets mature.

• If the contractor controls the means and methods, let the contractor own them.

• If the owner controls the mission architecture, the owner should own changes to it.

• If the mission integrator controls power, communications, landing sequence, and interface requirements, those risks cannot be quietly buried in a construction subcontract.

• If the ground is uncertain, define a baseline.

• If the baseline proves wrong, provide relief.

That is not contractor favoritism. That is commercial realism.

The first lunar construction market will not be created by asking contractors to gamble on unknown ground, untested equipment performance, and mission-level constraints beyond their control. It will be created by allocating risk with discipline. The Moon does not need contracts that look tough. It needs contracts that can actually be signed, priced, executed, and defended.

Commercial Frameworks - What Could Work?

If lunar construction is treated like mature terrestrial EPC work too early, the market will struggle before it even starts.

The first lunar construction contracts should not pretend to be mature EPC contracts. They should be structured as progressive delivery frameworks with baselines, hold points, open-book cost, shared risk registers, and defined compensation events.

That is the more realistic path.

A contract risk-allocation matrix showing which lunar construction risks should sit with the contractor, which should remain with the owner or mission integrator, and which require a shared baseline mechanism such as a Lunar Ground Baseline Report, interface control document, compensation event, or validated performance criteria.

A fixed-price lump-sum contract may look attractive to an owner because it appears to create price certainty. But in an immature construction environment, that certainty can be artificial. If ground behavior, robotic productivity, dust impacts, equipment degradation, power availability, communications reliability, logistics constraints, and interface requirements are not yet validated, then a lump-sum price does not eliminate uncertainty. It either hides it in contingency, pushes it into qualifications, or converts it into future claims.

For early lunar construction, progressive contracting is more defensible. The commercial framework should evolve as the technical maturity evolves.

The first phase should be advisory and preconstruction services.

At this stage, the contractor, engineering advisor, mission integrator, and owner should not pretend they are ready for a full construction contract. The objective should be to define what is known, what is assumed, what is missing, and what must be tested before construction risk can be priced responsibly.

This phase should include a construction-readiness review, site data gap assessment, preliminary ground-risk register, constructability screening, access and mobility review, robotic production assessment, dust-risk review, interface mapping, and a preliminary commercial framework.

This is where the project asks the right questions before it buys the wrong certainty.

The second phase should use target cost or cost-plus mechanisms with incentives.

This is appropriate while robotic performance, regolith response, construction methodology, quality control, and production rates are still being validated. A target-cost model allows the owner and contractor to work against an agreed budget while maintaining transparency on actual cost, productivity, contingency, and risk events. Incentives can be tied to useful outcomes: validated production rates, reduced downtime, successful surface preparation, energy efficiency, dust reduction, or completion of defined work fronts.

This model is not a blank check.

It is a controlled way to learn while building.

The third phase should introduce unit-rate or reimbursable work packages for repeatable construction activities.

Once some site and production data exist, the contract can begin to price measurable quantities. This could include excavation volume, graded area, compacted area, sintered surface area, berm length, trench length, haul distance, processed regolith volume, or number of verified mobility corridor segments.

This is closer to how construction actually works.

A contractor can price a cubic meter, a square meter, a meter of trench, or a defined haul distance more responsibly than an undefined promise to “prepare a lunar site.” Unit-rate mechanisms also allow the scope to evolve without renegotiating the entire contract every time the mission needs change.

The fourth phase should introduce performance-based elements, but only after the system has demonstrated repeatability.

Performance obligations should not be imposed before the baseline is mature. Once ground response, robotic productivity, dust behavior, and quality verification are better understood, the contract can include performance requirements such as landing pad serviceability, bearing resistance thresholds, settlement limits, dust-generation targets, sintered crust thickness, mobility corridor availability, or surface roughness criteria.

Performance-based contracting has a role. But it must come after validation, not before it.

The sequence matters. Advisory first. Target cost while learning. Unit rates when quantities become measurable. Performance obligations when repeatability is proven.

This phased approach gives each stakeholder a practical role. Agencies can fund learning without pretending all risks are known. Primes can manage interfaces and mission architecture without forcing construction risk into the wrong place. Startups can demonstrate technology within a commercial structure that recognizes uncertainty. Contractors can participate without being asked to gamble on unknown ground and unvalidated production. Investors can see a path from advisory services to repeatable revenue.

That is how a market begins. Not with one oversized contract that tries to transfer everything. But with a commercial framework that matures with the evidence.

A realistic lunar construction contract should include defined baselines, staged validation, open-book cost, shared risk registers, clear hold points, measurable quantities, compensation events, and acceptance criteria linked to the level of data available at that stage.

The goal is not to remove risk. That is impossible. The goal is to make risk visible, priced, managed, and allocated to the party best able to control it.

That is the difference between procurement theater and a buildable lunar construction market.

What Document Is Missing?

Contractors do not price major construction works from ambition alone. They rely on geotechnical baseline reports, specifications, drawings, schedules, quantities, access constraints, temporary works assumptions, method statements, quality requirements, and compensation mechanisms. These documents do not eliminate risk, but they define the contractual baseline from which risk can be priced, challenged, managed, and, when necessary, disputed.

On the Moon, the equivalent document does not yet exist.

That is a problem.

A contractor cannot responsibly price lunar excavation, grading, compaction, sintering, trenching, berm construction, foundation preparation, or landing pad works without a defined ground baseline. The issue is not simply whether lunar regolith is strong or weak. The issue is whether the contract defines what the contractor is entitled to assume.

That is why lunar construction needs a new contractual and technical document:

A Lunar Ground Baseline Report - LGBR

The LGBR would not be a final design report. It would not pretend to remove all uncertainty. Its purpose would be to establish the ground-related assumptions against which scope, price, schedule, risk allocation, and compensation events are measured.

1. It should define the interpreted regolith stratigraphy across the proposed work area. Even if the interpretation is preliminary, the contractor needs to know what layering, density variation, ejecta deposits, hardpan zones, loose surficial material, buried blocks, or possible ice-bearing intervals are assumed in the contract.

2. It should define design parameter ranges. These may include density, friction angle, apparent cohesion, bearing resistance, excavation effort, trafficability, sinkage potential, settlement behavior, particle size distribution, abrasiveness, and response to compaction or sintering. The key point is not false precision. The key point is a declared range of assumptions.

3. It should define the expected boulder frequency. Buried boulders, floaters, blocky ejecta, and oversized fragments could control excavation productivity, tool wear, rover mobility, trenching performance, and surface preparation tolerances. If the contractor encounters a materially higher boulder frequency than the baseline, the contractor needs a remedy.

4. It should define excavation classes. Lunar excavation should not be treated as one uniform activity. Loose regolith, dense regolith, blocky regolith, cemented or sintered crust, hardpan-like layers, ice-bearing material, and buried rock fragments may require different tools, energy demand, production rates, and acceptance methods.

5. It should define trafficability assumptions. A prepared construction site is useless if the equipment cannot reach it, cross it, maintain traction, or repeatedly traverse it without excessive sinkage, dust mobilization, or route deterioration. Trafficability should become a contractual assumption, not a casual operational note.

6. It should define dust-risk assumptions. Dust adhesion, dust lofting, electrostatic behavior, abrasion, visibility loss, sensor interference, seal degradation, radiator contamination, and solar-panel performance reduction can directly affect production and serviceability. The contract should define the expected dust operating envelope and the threshold beyond which relief applies.

7. It should define bearing and settlement assumptions. A landing pad, habitat platform, road, berm, or foundation zone is ultimately judged by performance. The LGBR should state what bearing resistance, deformation tolerance, settlement range, serviceability criteria, and load cases are assumed for pricing and acceptance.

8. It should define sintering and compaction acceptance criteria. If the work requires densification, surface hardening, or in-situ stabilization, the contract must define what success means. Is acceptance based on density, surface stiffness, penetration resistance, crust thickness, compressive strength, surface roughness, dust reduction, trafficability, or performance under repeated passes?

9. It should define known unknowns. This is important. A credible LGBR should not hide uncertainty. It should state where the data is weak, where assumptions are inferred, where remote sensing is being extrapolated, where in-situ validation is missing, and where future testing is required.

Finally, it should define compensation events for materially different lunar ground conditions. If actual conditions differ from the LGBR in a way that affects productivity, cost, schedule, equipment wear, energy demand, quality, or serviceability, the contractor should have a defined route to time and cost relief.

Without a lunar ground baseline, every contractor is bidding against an unknown site. That is not procurement. That is speculation.

The LGBR would not solve every problem. But it would do something essential: it would turn lunar ground uncertainty into a contractual baseline. That is the first step toward a market where contractors can price the work without gambling on the Moon itself.

Takeaway

The first lunar construction market will not be created by slogans, renderings, or aggressive risk transfer.

It will be created by a commercial discipline.

A credible lunar construction market will not be created by transferring all uncertainty to contractors. It will be created by allocating risk to the party best able to manage it.

Contractors can manage construction means and methods. They can manage quality control. They can manage production planning against defined assumptions. They can maintain equipment within known operating envelopes. They can deliver physical work packages if the scope, site, access, interfaces, and acceptance criteria are clear. But contractors cannot be expected to absorb every unknown linked to regolith behavior, dust effects, communication architecture, power availability, launch sequence, lander interfaces, mission changes, and unvalidated performance criteria. That is not risk transfer. That is commercial overreach.

The Moon will require a different maturity path. Early contracts should begin with advisory services, preconstruction reviews, construction-readiness assessments, data gap analysis, risk registers, and baseline development. Then they can move into target-cost or cost-plus frameworks with incentives. As production data improves, unit-rate and reimbursable work packages can emerge. Only after repeatability is demonstrated should performance-based obligations become dominant.

This is how the industry moves from exploration logic to construction logic. The key question is no longer only whether we can build on the Moon. The better question is whether we can procure lunar construction in a way that serious contractors, agencies, primes, startups, insurers, and investors can trust.

That requires a ground baseline.

• It requires realistic risk allocation.

• It requires progressive delivery.

• It requires defined compensation events.

• It requires acceptance criteria linked to validated data.

• It requires the courage to admit that the first lunar construction contracts will not look like mature terrestrial EPC contracts.

And they should not.

The Moon does not need the cheapest bidder. It needs the most realistic commercial framework.

Roberto Moraes

Author | SpaceGeotech Founder | Lunar Construction Governance Specialist