Contract Strategy — Local Content

Local Content Requirements Across Brazilian FPSOs: A Strategy Comparison

September 2026·11 min read·Public data only

What local content requirements actually control

A local content minimum sets the share of a contract's scope — by value, not just by physical component count — that must be sourced, fabricated, or performed in Brazil. It isn't a single number applied uniformly: contracts typically break it down by phase or work package (construction versus operation and maintenance, for instance), and a shortfall against the committed percentage can trigger financial penalties written into the contract itself.

Brazil's regulatory approach to this has moved substantially since the earliest concession rounds, when local content minimums for E&P activities ranged as high as 77% depending on block location and activity — a level that later proved difficult for operators to hit without cost or schedule strain. Reforms starting with CNPE Resolution 07/2017 and ANP Resolution 726/2018 introduced formal mechanisms for adjusting or waiving local content commitments, and the direction since has generally been toward more flexibility, not less — the CNPE has continued adjusting local content percentages tied to specific concession blocks as recently as 2024.

That history matters for reading today's numbers: a 20% or 25% minimum on a current FPSO tender isn't an arbitrary figure — it's a data point in a policy line that has moved, over two decades, from treating local content as a near-mandatory majority of scope to treating it as one negotiated variable among several.

Case study: two sister hulls, two different floors

P-84 (Atapu) and P-85 (Sépia) were awarded to Seatrium in a single joint contract announcement, signed the same day, for the same buyer, on hulls from the same build program. By every measure that normally predicts a matching requirement, they should carry the same local content floor. They don't: P-84's minimum is publicly reported at 20%, while P-85's is 25%.

† One source (Fundo da Marinha Mercante council records) puts SEAP-II's target at 30% rather than 33% — the two figures are close enough to plausibly reflect different reporting dates or a later adjustment, but the discrepancy isn't resolved here; both numbers exist in the public record.

The gap between P-84 and P-85 is small in absolute terms but strategically significant: it means the same contractor, on the same building program, is operating under two different sourcing constraints depending on which unit's scope it's pricing. A bid team that treats "local content requirement" as a single number for a whole build program — rather than checking the specific field's own floor — is working from the wrong input.

SEAP-I and SEAP-II: two percentages, not one

SEAP-I and SEAP-II add a layer the P-84/P-85 comparison doesn't show: each tender carries two different local content numbers, not one. The headline target — what SBM Offshore committed to when it qualified for the contract — is 40% for SEAP-I and 33% for SEAP-II (one source puts the latter at 30%). But the threshold that actually triggers a financial penalty for non-compliance is set lower: 25% for SEAP-I, 18% for SEAP-II. The gap between "what you promised" and "what you get fined for missing" is itself a negotiated buffer — roughly 15 and 15 percentage points respectively on these two contracts.

That distinction matters because the two contracts are worth more than US$7.8 billion combined (signed May 2026), and the target/floor gap is exactly the kind of detail that gets lost when local content is summarized as a single headline percentage in a press release or a competitor benchmark.

Why the gap exists: field-specific, not contractor-specific

Local content minimums attach to the concession block and the specific tender, not to the contractor. That's the mechanical reason two sister hulls awarded the same day can carry different floors — each field's development plan negotiates its own local content commitment, shaped by factors like the block's original concession terms, the specific scope split between construction and operations, and how recently that particular local content clause was last adjusted under the post-2017 flexibility mechanisms.

For a bidder, that means local content strategy has to be built per-tender, not templated from the last contract win — even when the last win was for what looks like a nearly identical unit.

Local content as a cost lever, not just a constraint

The strategic angle worth sitting with: a local content minimum isn't purely a compliance cost to be absorbed. It interacts directly with schedule and price, because sourcing locally versus internationally carries different lead times, different supplier qualification risk, and different currency exposure. A bidder with strong Brazilian fabrication or service partnerships can treat a higher local content floor as a competitive advantage rather than a penalty risk — while a bidder without that base has to price in the cost of building or renting one, or accept the penalty exposure of falling short.

That's why local content shows up as its own line of strategic analysis in a competitive FPSO bid, alongside contract model and $/ton benchmarking — it's not a fixed cost that every bidder absorbs identically, it's a variable that different bidders are structurally better or worse positioned to meet.

See also: the full 18-platform benchmarking piece, BOT & charter cost analysis, and Brazilian shipyards & moduleiros.