Comparing Project Updates by What Each Message Actually Proves

The Greens Project editorial ·

Amby "No Horse" Golf Course, 2019.
Illustrative image. Kerry Raymond · CC BY 4.0 · Cropped and resized. Image source

A subscription to a community project's update list can feel like progress. Each email arrives with polished language, a new rendering, or a note that something is moving forward. But an update is a message, not a record of decisions. For readers following a concept-stage project such as The Greens Project, which presents itself as a proposed network of golf-first, solar-powered off-grid communities, the useful question is not whether an email sounds encouraging. It is what the email actually proves. This article offers a comparison method you can apply to any project update, along with the specific questions that separate verifiable information from aspiration. Nothing here is a recommendation to buy, invest, join, or avoid any project. It is a way to read carefully.

Start by Sorting Each Claim Into One of Three Bins

Take any update email and list every substantive statement it contains. Ignore adjectives for the moment and focus on nouns and verbs: what is said to exist, what is said to be scheduled, and what is said to be possible. Then sort each statement into one of three bins. The first bin is confirmed: the statement names a specific fact that you could check against a published, dated, and attributable source, such as a recorded decision, a filed document, or a named counterparty who has agreed to something in writing. The second bin is planned: the statement describes an intention with a stated timeline or step, but nothing has been finalized. The third bin is imagined: the statement describes an experience, a feeling, a lifestyle, or a future state without any mechanism for verifying it.

Most concept-stage updates are heavily weighted toward the third bin. That is not automatically a warning sign, since vision statements are a normal part of early planning. The problem arises when imagined material is presented in the same grammatical register as confirmed material. Watch for sentences that place a rendering or a lifestyle description next to a factual claim, separated only by a line break. The layout invites you to read them as equivalent. They are not.

Check the Verbs Before the Promises

Verb choice carries more information than most readers notice. Compare the difference between 'the community has secured,' 'the project is working toward,' and 'residents will enjoy.' The first is a claim of completed action. The second describes effort in progress. The third is a forecast about an experience that has not happened and may not happen. A careful reader keeps a running note of which verbs appear and whether each one is backed by anything specific.

Modal verbs deserve particular attention. Words such as 'will,' 'can,' 'could,' 'aims to,' and 'envisions' signal that a statement is conditional or forward-looking. These are not dishonest by default, but they are not confirmations either. If an update uses several modal verbs in a row around a central claim, treat that claim as planned or imagined until something firmer appears.

Build a Comparison Table in Plain Text

When you receive updates over several months, the most useful tool is a simple running record. Create a list with four columns: date of the email, claim made, bin assigned, and evidence cited. Keep the claim wording close to the original so you are not reshaping it in memory. Over time, patterns appear. You may notice that a particular amenity is mentioned in every update but never accompanied by a decision date, a responsible party, or a document. Or you may see that a timeline keeps moving without any explanation of what changed.

Comparing one update against the one before it is especially revealing. Ask whether a claim that was 'planned' in March has been upgraded to 'confirmed' in June, and if so, what evidence changed. Ask whether a feature mentioned in one email has quietly disappeared from the next. Silence about a previously stated item is information too.

Questions to Ask Before Acting on Any Update

Before you treat any update as meaningful, work through a short set of questions. Who is making this statement, and in what capacity? Is there a named decision-maker, and is the decision recorded anywhere outside the email itself? What is the source of the factual claim: a public filing, a signed agreement, a government record, or the project's own description of its plans? Has the claim been independently reported or confirmed by anyone without a stake in the project? What would have to be true for this claim to be wrong, and has the project addressed that possibility? If the answer to most of these is unclear, the update belongs in the planned or imagined bin regardless of how confident it sounds.

Also ask what the update does not say. A concept-stage community site that collects names and email addresses for project updates is offering a channel for communication, not a confirmation of locations, pricing, membership structure, or financial terms. If you are looking for any of those specifics and they are absent, that absence is a fact to record. Do not fill it in with optimism from the surrounding imagery.

Keep Your Own Evidence File

The final step is to maintain a personal evidence file that you update independently of the project's messaging. Save the original emails, note the dates you received them, and record any primary documents you locate yourself, such as public records relevant to land use or energy permitting in the area the project discusses. Revisit the file periodically and compare it against the project's latest communications. Your goal is not to catch anyone out. It is to ensure that your own understanding remains tied to what can be verified rather than to what is most recently and attractively described. A subscription can keep you informed of a project's direction, but only your own documented comparison will tell you how much of that direction has actually been decided.