Banksia Row
12 terraces in Brindlewood Park, NSW (a fictional suburb). Presented by Example Developments, a fictional developer.
- Headline support score
- Silent supporters
- Support over time
- Support by postcode
- Where people came from
- Poll results
- Top questions and how they were answered
- What doubters raised
- Enquiries to buy or rent
- Campaign results
- Method and limits
Prepared by PLACE Technologies for Example Developments, 6 October 2026. This sample shows the format of a PLACE Pulse report. The project, places, people and every figure in it are made up.
Support score: 7.8, Good.
A single number for how the people who responded feel about Banksia Row, from 1 to 10.
Good: a mix, leaning towards support.
412 support, 141 undecided and 87 oppose, from 640 responses.
- 1 to 5.9PoorMainly detractors
- 6 to 7.9GoodA mix
- 8 to 8.9ExcellentMainly supporters
- 9 to 10OutstandingAlmost only supporters
How the score is calculated
Everyone who responds on the project page chooses one of three answers: support, undecided or oppose. The score is net support (the share who support minus the share who oppose) placed on a 1 to 10 scale, where everyone opposing would be 1 and everyone supporting would be 10.
Support 64.4% − oppose 13.6% = net support +50.8
1 + 9 × (50.8 + 100) ÷ 200 = 7.8
It's counted from the answers people chose. It isn't worked out by AI reading the tone of their comments.
Most supporters never said so in public.
of supporters (354 of 412) backed the project without leaving a public comment.
Public comments, at a meeting or online, tend to come from the people most worried about a project. Silent supporters are the people who say yes on the project page but never comment. They rarely show up in a submissions count, so this is the group a planning panel is least likely to hear from.
640 responses: 64% support, 22% undecided, 14% oppose.
122 public comments: 48% from supporters, 19% undecided, 34% oppose.
People who oppose made up 14% of responses but 34% of public comments. Reading the comments alone would suggest much more opposition than the responses show. Of the 87 people who opposed, 41 (47%) commented; of the 412 supporters, 58 (14%) did.
Support over the 13 weeks.
The share of all responses so far, week by week. Support rose most while the ads were running (weeks 5 to 10), then held steady.
Support was lowest right next door, and still a majority.
Responses grouped by the postcode people gave. Postcodes with fewer than 5 responses are merged into one row, so no small group can be singled out. Postcodes and suburbs here are fictional.
| Area | Responses | Support | Undecided | Oppose | Support share |
|---|---|---|---|---|---|
| Postcode ABrindlewood Park, the site | 238 | 141 | 52 | 45 | 59.2% |
| Postcode BLarchfield, adjoining | 164 | 112 | 35 | 17 | 68.3% |
| Postcode CCoolabah Bend | 121 | 84 | 26 | 11 | 69.4% |
| Postcode DQuenda Vale | 68 | 45 | 15 | 8 | 66.2% |
| Other or not givenpostcodes under 5, merged | 49 | 30 | 13 | 6 | 61.2% |
| All responses | 640 | 412 | 141 | 87 | 64.4% |
Where people came from.
How visitors reached the project page, and how many of them went on to respond. The letterbox drop brought fewer visits than the ads, but a higher share of them responded.
| Source | Visits | Responses | Response rate |
|---|---|---|---|
| Facebook and Instagram ads Campaign | 880 | 152 | 17.3% |
| TikTok ads Campaign | 390 | 48 | 12.3% |
| Letterbox drop (QR code) | 610 | 158 | 25.9% |
| Example Developments' website and email list | 560 | 131 | 23.4% |
| Shared by visitorsLinkedIn, Facebook and Instagram shares | 430 | 88 | 20.5% |
| Direct, search and other | 470 | 63 | 13.4% |
| All sources | 3,340 | 640 | 19.2% |
What people told you they want.
Three polls set by Example Developments on the project page. Anyone visiting could answer, whether or not they gave a support response.
What matters most to you about this site?
Which façade finish would you choose?
How do you feel about the shared laneway garden?
Top questions, and how they were answered.
41 questions were asked and Example Developments answered 37, in a median of 2 days. Questions appear on the project page once they're answered. These five were asked most often (similar questions counted together).
How many car spaces will each terrace have?
34askedAnswered in 1 day. One garage space per terrace and four visitor spaces on site. The traffic report summary was added to the page.
Will the street trees be kept?
29askedAnswered in 2 days. Two of the three street trees are kept and four new trees planted along the laneway. The arborist's summary was added to the page.
When would building start, and how long would it take?
22askedAnswered in 3 days. Only after approval. Because the frames are built off site, work on the street is expected to take about seven months.
Will any homes be set aside as affordable or for key workers?
18askedAnswered in 4 days. Not at this stage. Example Developments said it is looking at this and will post an update on the page by December.
What hours would construction work happen?
15askedAnswered in 1 day. Standard council hours, with no work on Sundays or public holidays.
4 questions were still unanswered at the end of the period and are listed in the dashboard.
What doubters raised.
Themes from the 64 comments left by people who were undecided or opposed, summarised for this report. A comment can raise more than one theme. Themes include comments that weren't approved for public display; no comment is quoted or attributed.
- 26 of 64
Parking and traffic on the street
Worry that visitors and second cars would park on an already busy street, and about traffic at school times.
- 17 of 64
Height and overshadowing
Whether the two-storey terraces would shade the back gardens of the houses to the south.
- 11 of 64
Noise and disruption while building
How long the work would last and when trucks and cranes would be on the street.
- 9 of 64
Who could afford them
Doubt that the terraces would be priced for local people, especially younger buyers and renters.
- 8 of 64
Losing trees
Concern about the street trees and the large gum at the back of the site.
Parking, trees and construction hours were also the most asked questions (section 07), and all three now have answers on the page. Affordability is still open.
Automated AI sentiment analysis is on the PLACE Pulse roadmap. It isn't part of reports today. In this report, comment themes are read and summarised for this report, and the support score is counted from the answers people chose.
46 people asked to buy or rent.
Every enquiry counted here came with the person's consent to share their details with Example Developments. Enquiries were sent to the developer's CRM as they arrived; a CSV is also available.
| Home | To buy | To rent | Total |
|---|---|---|---|
| 3-bedroom terrace | 17 | 10 | 27 |
| 4-bedroom terrace | 9 | 3 | 12 |
| Not sure yet | 5 | 2 | 7 |
| All enquiries | 31 | 15 | 46 |
6 more people started an enquiry but didn't give consent. They aren't counted, and none of their details were shared.
Campaign results.
PLACE turned the project page into six posts and three short videos from the renders, all labelled “presented by Example Developments”, and ran them on Facebook, Instagram and TikTok in weeks 5 to 10, to adults living within about 5 km of the site. Ad spend was paid by the project.
- Reach, impressions and clicks are reported by the ad platforms. Visits, responses, supporters and enquiries are counted by PLACE.
- Cost per supporter is ad spend divided by supporters who arrived from an ad (A$1,350 ÷ 128). Some of them might have found the page another way.
- Ads also brought 9 of the 46 enquiries. Cost per response was A$6.75.
- All figures are illustrative. Real costs depend on each platform's rates at the time, and the budget is agreed with you before anything runs.
How to read this report.
PLACE Pulse reports what people did on the project page. It's useful evidence of community feeling, and it has limits worth stating plainly.
What it can show
- How many people chose to respond, and how they answered
- How that changed over time and differed by postcode
- Which channels brought people who responded
- What people asked and voted for in polls
- How many people asked to buy or rent, with consent
What it can’t show
- The view of the whole community, or of everyone in a postcode
- Why someone answered the way they did, beyond what they wrote
- That every response is a unique local resident
- Whether a project will or should be approved
- Self-selected. People chose to visit and respond. They aren't a random sample, so this is not a representative survey and shouldn't be presented as one.
- Presented by the developer. The project page is labelled “presented by Example Developments”. It's not independent consultation, and doesn't replace council's own notification or submissions.
- Counted, not guessed. The support score comes from the answers people chose: support, undecided or oppose. Comment themes are summarised for this report. No AI sentiment analysis is used.
- De-identified. The report contains no names, emails or comments that could identify someone. Postcodes are self-reported.
- Small groups merged. Any group with fewer than 5 responses is combined with others, so no one can be singled out.
- Consent. Enquiry details go to the developer only when the person agrees. Polls and support responses are counted without sharing personal details.
- Repeat responses. PLACE takes steps to limit repeat responses, but online responses can't be fully verified.
Banksia Row, Brindlewood Park, Example Developments and every figure in this report are fictional and for illustration only. A real report is prepared for each PLACE Projects pilot from that project's own page and dashboard. Shareable project reports are available on request.
Back to PLACE Projects