Comparing Greens Project Update Emails by Evidence Type, Not Enthusiasm

The Greens Project editorial ·

Miniature Golf at Hastings Hastings Adventure Golf is the UK home of Miniature Golf and features no less than 3, 18-hole courses. The flagship course is the Florida-style Adventure Golf, with landscaped gardens, waterfalls, dancing fountain
Illustrative image. Paul Gillett · CC BY-SA 2.0 · Cropped and resized. Image source

The Greens Project presents a proposed network of golf-first, solar-powered off-grid communities, and people who sign up for its updates will receive messages over time that vary widely in weight. Some describe a milestone, some describe an intention, and some are mostly atmosphere. The Greens Project site collects consented names and email addresses for project updates, and by its own description it does not offer confirmed locations, home prices, membership terms, or investment terms. That means the most useful habit a subscriber can build is the ability to read an update and classify what it actually establishes. This article offers a field method for doing exactly that, without assuming anything the public information does not state.

Start With What the Signup Actually Is

Before comparing any messages, be clear about the relationship you have with the project. A list of names and email addresses collected for updates is a communication channel. It is not a reservation, a purchase agreement, a membership, or an investment. Reading the site's description of its own function is the first step, because it sets the ceiling on what an update can commit anyone to.

Write down, in one sentence, what you consented to. For example: you agreed to receive project news by email. If an update later seems to imply that you have secured a lot, reserved a parcel, or gained a right of any kind, that gap between the implication and your original consent is worth noting immediately.

Classify Each Claim by Its Verb

Update emails reveal their confidence through verbs. Phrases such as 'has been completed,' 'is signed,' or 'was approved' describe events that have happened. Phrases such as 'plans to,' 'aims to,' or 'is exploring' describe intentions. Phrases such as 'imagine,' 'envision,' or 'picture' describe aspirations and should be treated as creative framing rather than data.

A practical method is to take any update and sort every substantive sentence into three columns: confirmed, proposed, and imagined. Keep the sorting honest. A sentence that mentions solar power in general terms, for instance, is not the same as a sentence describing a specific installed system with a named capacity, and the second kind of statement would need to be explicit in the message to count as confirmed.

Compare Two Updates Side by Side

Comparison is more revealing than reading a single message. Pick two updates separated by some time and list the claims each contains. Then check whether a claim from the earlier message still appears, has changed, or has quietly disappeared. A claim that is repeated without new supporting detail should not gain confidence through repetition. A claim that shifts from 'planned' to 'in progress' to nothing is informative in its own right.

Look also at what was added and what was removed. An update that introduces a new amenity while failing to mention the amenity promised before has changed the picture even if no one announces a reversal. Record these shifts in a simple two-column note so the trajectory is visible instead of relying on memory.

A Checklist for Each Update

Use the following questions on every message you receive. First, does this update state any specific location, price, membership term, or investment term? If not, it cannot be used to evaluate those things. Second, does it name any party responsible for a shared facility, such as who would build, fund, operate, or maintain a clubhouse or golf course? If it does not, the responsibility is unassigned in the message. Third, does it describe the energy system in terms of what exists now, or in terms of what is hoped for? Fourth, does it use the word 'guaranteed,' 'secured,' or 'reserved,' and if so, does it explain under what documented terms?

Fifth, does the update ask you to take an action such as paying, committing, or referring others? Treat any such request as a separate decision that deserves its own research, independent of the newsletter's tone. Sixth, is there an obvious way to ask a follow-up question and receive a written answer? A message that invites questions but offers no way to get a response has limited value as evidence.

Keep Your Own Evidence File

Save each update with its date, so you can review it later. Over several months, a simple file becomes a record of what the project has and has not said. Mark which items remained unresolved, which were quietly dropped, and which were confirmed with specifics. This file is also useful if you later want to ask the project directly for clarification, because you can quote the exact sentence you are asking about.

The goal is not to reach a verdict about the project from a few emails. The goal is to know, at any point, the difference between what you have been told is established and what you have simply been invited to imagine. Keeping that distinction clear is the most durable form of due diligence a reader can practice, and it costs nothing beyond attention.