Skip to content

Solutions

Engagement for the whole plan.

A comprehensive plan takes years, touches every part of a community, and asks people to weigh trade-offs that are hard to see. Tortoise 40 keeps the whole engagement in one project space, from the first visioning survey to the final report.

What this covers

Engagement for comprehensive plans

  • Visioning
  • Existing conditions
  • Map feedback
  • Community priorities
  • Surveys
  • Draft plan review
  • Public comments
  • What We Heard
  • Progress updates
  • Final engagement reporting
01

Visioning that people can actually answer

Broad questions produce broad answers. A visioning survey in Shell asks about specific places, specific choices, and specific trade-offs, so the responses can be counted and grouped instead of summarized by hand.

  • Short, mobile-friendly survey that works without an account
  • Place-based questions tied to the map
  • Priority allocation instead of open-ended wish lists
02

Existing conditions, shown before opinions are collected

People give better input when they can see the data. Publish the existing conditions report or the background maps as a reviewable document, so comments arrive attached to the page and the figure they are about.

  • Page-level comments on a PDF
  • Background maps and exhibits published for review
  • Plain-language summary alongside the technical document
03

Map feedback for land use and growth areas

Growth scenarios, opportunity areas, and future land use are spatial questions. A map activity lets residents place a comment where the issue actually is, and gives staff a georeferenced record instead of a description of a location.

  • Comment pins with categories
  • Scenario comparison inside a survey
  • Coordinate export for the GIS analysis
04

Testing priorities across the whole community

A comprehensive plan has to balance housing, jobs, mobility, open space, and services. Shell surveys can ask people to allocate a fixed budget or rank priorities, which produces a real distribution rather than a list of demands.

  • Priority allocation and ranking questions
  • Optional postal code and neighborhood fields for geographic context
  • Results available as soon as the survey closes
05

Draft plan review in public

The draft plan is the moment most people engage. Publish the document, open comments on the pages that matter, and keep every comment linked to its page and version.

  • Comment period with an open and close date
  • Comments tied to the document version they were made against
  • Staff response recorded next to each comment
06

From comments to What We Heard

Thousands of comments are only useful if they become evidence. Shell groups comments into themes, keeps the original wording, and produces a What We Heard report that a planning commission or council can read.

  • Theme development with counts
  • Representative comments kept in context
  • Appendix data for the record
07

Reporting that matches the plan

Engagement reporting is part of the plan record. Shell produces a report designed like a planning document, with the participation summary, the themes, and the supporting data.

  • Participation summary by method and geography
  • Theme summary with comment counts
  • Export for the public record

Next

Give your public project a Shell.

Tortoise 40 is free to use. Set up a project, publish it, and start collecting public input.