Content lifecycle
Every date shown on this site comes from a written revision entry. Nothing is derived from a build timestamp, because that would advertise changes that did not happen.
Published by the Land Clearing Authority editorial team · Last revised 2026-07-29 · Editorial policy · Corrections
Almost every content site advertises freshness it does not have. The usual mechanism is accidental: the sitemap takes its modification date from the build, so every rebuild tells search engines that every page changed, whether or not anything did.
This site cannot do that. There is no code path from a build clock to a published date. The revision log is a hand-written list of dated entries, the route registry refuses to assemble if any route lacks one, and both the sitemap and the syndication feed read from that log. A page that has not been revised keeps its original date, indefinitely.
What counts as a revision
A revision is a substantive change to what a page says. Fixing a claim, adding a section, correcting a source, changing a recommendation, or updating a threshold all qualify.
These do not: correcting a typo, adjusting styling, reordering a list without changing its content, or rebuilding the site. If the meaning did not change, the date does not move, because moving it would be a claim that something changed.
What triggers a review
| Trigger | Response |
|---|---|
| A cited authority changes a programme, a threshold, or a document location | Immediate revision of every page citing it, recorded with the date and what changed. |
| A reader reports an error | Investigated, corrected in place if confirmed, and recorded in the revision log. |
| A decision rule changes | The rule, the tool that renders it, and every page describing it are updated together, because they read from the same array. |
| A research dataset reaches its minimum sample size | Results published with sample size and limitations; the dataset page stops saying it has no observations. |
| Annual review falls due | The page is re-read against its sources. If nothing substantive changed, no revision is recorded and the date does not move. |
| Two pages have drifted into saying the same thing | One is rewritten around a distinct angle, or retired and redirected in the registry. |
| A page can no longer be supported | Retired rather than rewritten, and removed from the registry so it leaves the sitemap. |
Cadence
Every published page is re-read against its sources at least annually, and immediately whenever a cited authority changes a program or a document moves.
The annual pass is a re-read against sources, not a rewrite for its own sake. A page that is still correct is left alone. Editing a correct page in order to refresh its date would be the same dishonesty as deriving the date from a build clock, achieved by hand.
Retirement, and why it is sometimes right
Some pages should stop existing rather than be updated. A page whose subject has been absorbed by another, one that duplicates a neighbour, or one making a claim that can no longer be supported is better retired.
Retirement means removal from the route registry, which automatically removes it from the sitemap, the search index, the feed, and the internal link graph — all of which are generated from that one registry. Nothing has to be remembered in five places.
How corrections are handled
Corrections are made in place and recorded in the revision log with the date and what changed. A correction is never made silently, and a page that has been corrected keeps the record.
Questions about dates and updates
Why do so many pages share the same date?
Because they were published together. That is factually what happened, and staggering the dates to look more organic would be a fabrication. As pages are revised individually, their dates will diverge on their own.
Does rebuilding the site change the dates?
No. There is no path from the build clock to a published date. The sitemap and the feed read from hand-written revision entries, and the registry will not assemble if a route is missing one.
What if a page is wrong?
Report it through the corrections process. If confirmed, it is corrected in place and the change is recorded in the revision log with the date and what changed. Corrections are not made silently.
Do you delete pages?
Retirement is preferred over deletion where a page has served a purpose, and it happens by removing the route from the registry — which removes it from the sitemap, feed, search index, and link graph at once, because all four are generated from that registry.
Work out the scope before you ask for prices
Answer the five questions every quote depends on — what is growing, where the material goes, how deep removal has to reach, whether equipment can get in, and what the land is for afterwards. Then send one properly described project to the right kind of contractor.
Nothing on this site is a recommendation of a specific company. The guidance describes categories of work and the questions worth asking. If you decide to request quotes, the introduction is free to you, contractors may pay to receive it, and you are under no obligation to hire anyone.