Environment & Research
Make the trade-off visible before it becomes an argument.
Environmental engagement is a conversation about constraints: habitat, drainage, access, and what a proposal would change. Tortoise 40 publishes the layers and the proposal on the same page, so comments respond to what is actually proposed.
Why environmental comment is hard to use
- 01
The map is in the appendix
Habitat and drainage information sits in a PDF nobody opens, while the comments arrive about the part of the site that is easiest to see from the road.
- 02
Letters, mapped by hand
Objections arrive as email and paper. Someone decides which part of the site each one is about, and that decision never appears in the record.
- 03
Two publics, one form
Residents and technical reviewers read the same proposal for different reasons. A single comment box serves neither, and the review gets slower for it.
Four products, one record.
Each part of the platform does one job in the sequence, and the record stays in the same project throughout.
A public page that carries the proposal, the sources and the figures, readable without an account and dated as it changes.
Map comments on the site and page-level comments on the documents, with categories that keep a technical objection separate from a general one.
Drafts themes across both kinds of input, with the source of each, for a reviewer to accept or set aside.
Figures and renderings that show the proposal against the constraints, produced with the same evidence.
Evidence, proposal, comment, response
One sequence, with the technical record kept separate throughout.
- 01
Publish the constraints first
Habitat, drainage and existing conditions go up as reviewable documents beside the proposal, so a comment can be about a mapped constraint rather than about a rumour.
- 02
Collect comments where they belong
People comment on the page of the document or the point on the map they are responding to, and the position is kept with the comment.
- 03
Keep the categories honest
Each comment carries the category it was given: habitat, drainage, access, general. A technical objection is not averaged in with a general preference.
- 04
Review, then say what was heard
Themes, counts and original wording go back to the public, with the staff response recorded next to the comment it answers.
The same record, drawn.
A figure of the workflow above, labeled as an illustration rather than a screenshot.
- Habitatpublished layer
- Drainagepublished layer
- Proposaldocuments and map
- Commentby place and category
Next
Working through a contested site?
We will show how the constraints and the proposal are published together, and how the record answers for each comment.