Exclusivity agreement vs right of first refusal for solar land leases

A BD team scoping a new parcel will hear both terms thrown around in the same landowner call, and they get treated as interchangeable more often than they should. An exclusivity agreement and a right of first refusal protect a developer against different things, and mixing them up in a term sheet can leave a real gap in site control.

What an exclusivity agreement locks down

An exclusivity agreement (sometimes called an exclusivity period or a feasibility hold) is a landowner's promise not to shop the parcel to another developer for a set window, usually somewhere between 60 and 180 days depending on how much diligence the site needs. It's signed before an option or a lease, while a developer is still running interconnection screening, wetland delineation, title work, or whatever else has to clear before anyone commits real money.

It's a contract right, not an interest in the land itself. Nothing gets recorded against title. If the window lapses and nobody extended it, the landowner is free to take a call from a competing developer the next morning, and there's no instrument stopping them. That expiration date is the whole risk: a parcel can look locked up on a BD team's pipeline tracker for months after the exclusivity period has run out, because nobody flagged the date internally.

What a right of first refusal does instead

A ROFR doesn't give a developer control of the parcel now. It gives them the right to match a specific offer later, if and when one shows up from someone else. The landowner can keep talking to other developers, keep taking calls, even get close to a deal. They just have to bring the terms back to the ROFR holder before signing with anyone else.

Because of that structure, a ROFR usually runs much longer than an exclusivity period, sometimes for the life of a lease or option, and it often does get recorded against the parcel or at least referenced in title. It's a defensive instrument more than an acquisitive one. It doesn't stop a competitor from working the site, doing their own feasibility pass, or getting a landowner to a term sheet. It only guarantees a last look before the landowner signs.

Where the gap shows up on a real pipeline

The practical risk for a BD team is keeping track of which instrument is actually live on a given parcel, because deal logs rarely get updated the day a clause expires or a ROFR gets triggered. An exclusivity agreement that expired eight weeks ago with nobody renewing it is functionally no protection at all, even though it's still sitting in the deal log as "exclusive." A ROFR gives a false sense of security if a team assumes it means nobody else can touch the site, when in practice a competitor can run a full feasibility study, get a landowner to a handshake deal, and only then trigger the right-to-match clock.

Either way, a developer who's been counting on paper protection can get caught off guard by finding fencing posts, a staging area, or a cleared access road already on a site they thought was theirs to work quietly. By the time a landowner call confirms someone else has been out there, weeks or months of competitor diligence may already be behind that activity.

That's the gap a quarterly satellite pass over a watch list is built to close: checking which candidate sites in a pipeline already show fencing, clearing or construction on the ground before a BD team sinks more time into a site someone else has already started working. It doesn't replace reading the exclusivity clause or the ROFR language carefully, but it catches the thing the paperwork can't: whether someone is already standing on the parcel.

If your pipeline has sites where the exclusivity clock is uncertain or a ROFR leaves the door open, it's worth putting them on a watch list and seeing what the ground shows.