Skip to content

Writing a Blue-Carbon Credit RFP: A Buyer's Procurement Playbook

A practical RFP playbook for blue-carbon credit buyers: what to specify, which questions to ask, how to score bids and what to contract for.

Priya RamanBlue Carbon Analyst9 min read
On this page

Most blue-carbon purchases are still made the way art is bought: a broker call, a pitch deck, a handshake on price. That works until the audit committee asks why these credits, from this project, at this price — and nobody wrote down the answer. A request for proposals (RFP) fixes that. It forces you to define what quality means before anyone tries to sell you something, and it creates a paper trail your CFO, auditor and future self will thank you for.

This playbook walks through how to structure an RFP for blue-carbon credits — mangrove, seagrass, salt marsh and emerging kelp-forest projects — from scoping to contract signature. It assumes you've already done the strategic thinking in our buyer's guide to blue carbon credits and are ready to run a process.

Step 1: Scope the purchase before you write a word

An RFP is only as good as its specification. Before drafting, pin down four decisions internally:

Volume and delivery schedule. Are you buying 10,000 tonnes retired now, or 100,000 tonnes delivered annually over seven years? Spot purchases and multi-year offtakes are different products with different risk profiles — don't blur them in one tender. For forward purchases, our explainer on blue-carbon offtake agreements covers the structural choices.

Credit type. Removals, avoided emissions, or a mix — and do you need them characterized as removals vs avoidance for your claims framework? Many corporate standards only count removals toward neutralization claims. Say so explicitly.

Geography and ecosystem. Open or restricted? A global tender maximizes price discovery but multiplies diligence work. If your brand story is coastal restoration in your home market, say that — respondents will stop offering you distant projects you were never going to buy.

Claim requirements. Do you need correspondingly adjusted credits, registry labels, or compatibility with a specific reporting standard? State claims requirements as pass/fail criteria, not preferences. Ambiguity here is where deals die after months of work.

Step 2: Structure the RFP document

A clean blue-carbon RFP has five sections. Keep it under ten pages — you're eliciting comparable answers, not writing a regulation.

1. Buyer context and intent

Half a page: who you are, what you're buying and why, and the claims the credits must support. This filters out sellers whose inventory can't serve you and signals seriousness to the ones who can.

2. Minimum eligibility criteria (pass/fail)

The gates every proposal must clear before evaluation. Typical criteria:

  • Credits issued or planned under a recognized standard and methodology, listed publicly on a reputable registry
  • Independent third-party verification completed (for spot) or scheduled (for forwards)
  • Demonstrated, uncontested tenure over the project area, including sea tenure and carbon rights where relevant
  • No unresolved disputes with host communities; documented benefit-sharing arrangements
  • Seller willing to disclose the project design document, monitoring reports and verification statements

Anything you will absolutely not compromise on belongs here — not in the scoring matrix.

3. Technical questionnaire

This is the heart of the RFP. Ask for specifics, in writing, with page references to public documents. Good questions force comparable answers:

  • Describe the baseline scenario and the evidence supporting it. What is the project without carbon revenue?
  • Quantify uncertainty: what error bounds does the methodology carry on credit volume, and what deductions are applied?
  • How are reversal risks addressed? State the buffer contribution rate and who bears shortfall if buffers are exhausted.
  • Describe additionality under regulatory, financial and common-practice tests.
  • What is the monitoring cadence, methods and data availability? Will raw monitoring data be shared with the buyer under NDA?
  • Provide the benefit-sharing structure: percentages, recipients, governance rights of local and Indigenous communities.
  • List project risks (ecological, political, tenure, delivery) and current mitigations.

The due-diligence checklist maps neatly onto this section — the RFP simply makes the seller do the first pass of the work.

4. Commercial terms requested

Ask respondents to quote a fixed price per tonne, payment structure (milestone vs on-issuance vs advance), delivery schedule, replacement obligations for failed vintages, and their stance on price adjustment if verification volumes come in below forecast. Request all-in pricing: registry fees, broker margins, legal costs. Sticker prices in this market hide a lot.

5. Evaluation criteria and timeline

Publish your scoring weights. Not only is that good procurement hygiene — it improves bid quality, because sellers tailor answers to what matters to you. A reasonable starting framework:

Criterion Suggested weight
Environmental integrity (methodology, baseline, additionality) 30%
Permanence and reversal risk management 15%
Social integrity and benefit sharing 15%
MRV quality and data transparency 15%
Commercial terms and delivery risk 15%
Seller track record and financial health 10%

Step 3: Run the process like a diligence exercise, not an auction

Issue the RFP to a longlist of six to twelve sellers — a mix of project developers, aggregators and registries' listed intermediaries. Allow three weeks for responses, then a clarification round with written Q&A shared across all respondents. Invite the top two or three to diligence calls, and — this matters — talk to the verifier, not just the seller, on shortlisted projects. Independent auditors will often tell you things a pitch never would.

Resist the temptation to let price dominate. In blue carbon, a cheap credit is usually cheap for a reason reverberating through your risk register. Score first, negotiate second.

Step 4: Contract what the RFP promised

The most common RFP failure is that the careful criteria never make it into the contract. Translate them:

  • Representations and warranties on registry status, tenure, no double selling, and that the credits match the methodology and vintage stated.
  • Delivery and replacement clauses: if a vintage under-delivers at verification, what happens? Define replacement credits, cash compensation or termination rights in advance.
  • Claims alignment: the credits sold must support the buyer's stated use, with seller cooperation on any Article 6 or labeling documentation.
  • Change-in-law provisions: blue-carbon policy is moving fast; build in renegotiation triggers if host-country rules on carbon rights, exports or adjustments change.
  • audit and data access rights for the life of the claim, not just the life of the contract.

Keep in mind how blue-carbon prices are actually set when benchmarking bids: a forward price below direct project costs is not a bargain — it's unfinished risk priced as hope.

Step 5: Document the decision

Close the loop with an internal memo: what you bought, from whom, at what price, evaluated against the stated criteria, including why non-winning bids were declined. This memo is your greenwashing defense if a journalist, auditor or court ever asks. Procurement discipline is reputational armor.

Key takeaways

  • An RFP converts blue-carbon quality from a vibe into a scored, documented, defensible decision.
  • Scope first: volume, credit type, geography and claim requirements are pass/fail decisions made before the tender, not during.
  • Make the technical questionnaire force written, referenced answers on baseline, additionality, reversal risk and benefit sharing.
  • Publish your scoring weights — better bids follow clearer criteria.
  • Contract what the RFP promised: replacement clauses, claims alignment and audit rights belong in the agreement, not the email thread.
  • Talk to the verifier on shortlisted projects; diligence calls with sellers alone are marketing calls.

FAQ

How many sellers should receive the RFP?

Six to twelve. Fewer than five risks weak price discovery; more than fifteen usually means you haven't scoped tightly enough and will drown in incomparable bids.

Should we run one RFP for spot and forward purchases?

No — separate them. Spot purchases trade on current registry status and audit results; forwards trade on delivery risk, developer track record and contract structure. Combining them produces bids you can't score on a common basis.

Can we run an RFP for small volumes, say 5,000 tonnes?

Yes, but simplify: a two-page request for quotations with pass/fail criteria and a short questionnaire achieves the same discipline without six weeks of process. Serious developers will respond to a lean, well-specified small tender.

What if no bid meets our integrity threshold?

Then don't buy — and say why in your decision memo. A clean "no purchase" with documented reasons is a better outcome than a compromised purchase, and it strengthens your hand in the next cycle.

Do we need external advisors to run this?

Not necessarily. A sustainability lead, procurement and legal counsel can run a competent process using published criteria. Consider a technical reviewer for the shortlisted projects' baselines and MRV evidence if volumes or claim sensitivity are high.