← BACK TO CASE STUDY GENERATOR
CREATIVE TECHNOLOGYPublic sector & social impact exclusive

PROPOSED PROJECT

Consultation Response Map

Help planning teams work through public feedback on a proposed development or transport change. Group submissions by issue and referenced location, link each theme to original passages, and produce a map and response register that preserve minority and conflicting views for the consultation report.

STREET CONSULTATION / SIX SUBMISSIONS

Keep every place. Keep both sides.

Six unique records
Seven reviewed topic links

ABC

Schematic street locations · not to scale

A

School crossing

S02 + S04

B

Bus-stop approach

S01 + S06

C

Parking area

S03 + S05

Fictional street, comments, and review classifications. S04 links to two topics. These counts describe the supplied records and do not measure the views of the wider community.

The project in practice.

A fictional street consultation has six submissions and seven reviewed topic links. S01 and S04 mention traffic speed; S02 and S04 mention the school crossing; S03 opposes removing parking while S05 supports it; S06 raises a quieter-street concern. A schematic links each issue to the referenced street section. Counts describe these six records, not the views of all residents.

WHAT IS USUALLY DONE

Consultation teams summarize feedback by volume or manually place comments on a map. Multi-topic submissions, unclear locations, and opposing views can disappear when the report is condensed.

WHAT SOVRUN CAN DO FOR YOU

Sovrun would create a source-linked map and response register for a defined consultation. It suggests issues and referenced places, retains multi-topic comments, and shows disagreements alongside the original passages. Staff approve the classifications and responses before preparing the public report.

The same place.
Opposite requests.

S03 wants the parking spaces retained; S05 supports removing them. Grouping both under parking should help staff find the disagreement, not erase it. S06’s single noise concern remains part of the report.

S03 / LOCATION C
“Keep the parking spaces for local customers.”

Parking / response pending

S05 / LOCATION C
“I support removing parking here for more walking space.”

Parking / response pending

S06 / LOCATION B
“Please consider noise near the bus-stop approach.”

Quiet street / response pending

COUNT THE RECORDS, THEN THE TOPICS

Speed appears in S01 and S04; crossing in S02 and S04; parking in S03 and S05; quiet-street concerns in S06. That is seven topic links across six submissions. The report retains the original passages and records who reviewed each classification.

A map with evidence.
A response register with owners.

The team can move from a place on the proposal to the comments about it, including disagreements and concerns raised by one respondent.

ABC

Schematic street locations · not to scale

A

School crossing

S02 + S04

B

Bus-stop approach

S01 + S06

C

Parking area

S03 + S05

01 / An issue-location mapKnown places link to the relevant submissions; uncertain locations would remain in a review queue.
REVIEWED TOPICS

Six submissions. Seven links.

Speed
2 / S01 + S04
Crossing
2 / S02 + S04
Parking
2 / S03 + S05
Quiet street
1 / S06
02 / A complete topic countMulti-topic records remain linked to one original submission rather than being counted as additional people.
ISSUE C / PARKING

Record the disagreement.

Keep spaces
S03
Remove spaces
S05
Response owner
Planning team
Response draft
Pending review
Adopted decision
Not recorded
03 / A response and decision registerStaff can assign the parking question and retain both positions before a project decision is adopted.

How we’d make it happen.

  1. Link each response to its source

    Retain submission IDs and original passages while removing unnecessary personal details.

  2. Review issues and locations

    Allow multiple topics per submission and keep ambiguous locations and opposing views visible.

  3. Prepare the response register

    Staff record an answer and owner for each issue without presenting a draft as an adopted decision.

Where AI helps

Language models propose topic and location labels from supplied submissions. Mapping uses known project locations, with ambiguous places held for review. Counts come from confirmed classifications, not sentiment guesses or an assumed population sample.

What people approve

Consultation staff confirm locations, topic labels, redaction, and the interpretation of minority views. The planning team approves responses and distinguishes submitted feedback from an adopted project decision.

What we’d need to start

  • Authorized consultation submissions and project maps
  • Known place references and topic definitions
  • Review, redaction, and reporting requirements

How we’d test it

Test comments with several topics, conflicting opinions, repeated responses, unclear locations, and identifying information. Reconcile topic counts to unique submissions and ensure a small group’s concern is not removed by a popularity threshold.

Prepared for Public sector & social impact. We would agree on the work after reviewing your brief, materials, and requirements.

DISCUSS THIS PROJECT

This is a proposed project, not completed client work. The visuals and numbers show example outputs, not measured results.