Member voice intelligence

Things members have asked for

This fictional register shows how suggestions, questions and requested design changes can move from member input to professional review, working inclusion, confirmation or closure. The goal is to stop useful requests from disappearing inside chat threads or meeting notes.

MEMBER REQUEST REGISTER
10 REQUESTS
OWNER + OUTCOME VISIBLE

Need to know

Status: Requests tracked
What it means: Member questions and requested clarifications are recorded with their current position.
Your action: Follow only the items relevant to you.

The full record, supporting detail and evidence remain available below.

Requests tracked
10
Accepted / implemented
4
Under review
2
Working / proposed / open
4

Sample data for Shree Harmony, a fictional society. Not a real record.

18 Jul 2026
INCLUDED IN WORKING SPEC
Washing-machine provision
Show the exact washing-machine water inlet, drain point and appliance location in the member layout.
Outcome: Dedicated inlet + drain now shown as a working requirement.
Owner
Architect + MEP
Ticket
RQ-2026-001
Ticket owner
Architect
Response promise
Reply within 10 working days
18 Jul 2026
UNDER REVIEW
Stackable dryer space
Reserve usable space for a dryer above or beside the washing machine.
Outcome: Space is reserved in the working specification; final clearance remains pending.
Owner
Architect
Ticket
RQ-2026-002
Ticket owner
Architect
Response promise
Reply within 10 working days
18 Jul 2026
WORKING DESIGN
AC outdoor-unit locations
Define external AC-unit zones with safe maintenance access and ventilation.
Outcome: Common external service zone is being coordinated.
Owner
Architect + MEP
Ticket
RQ-2026-003
Ticket owner
Architect
Response promise
Reply within 10 working days
18 Jul 2026
OPEN
Parking dimensions
Show actual bay dimensions and access path before member-specific allocation.
Outcome: Final parking matrix awaits sanctioned planning position.
Owner
Architect + PMC
Ticket
RQ-2026-004
Ticket owner
PMC
Response promise
Reply within 5 working days
18 Jul 2026
PROPOSED
Senior seating area
Provide a quiet common seating area suitable for elderly residents.
Outcome: Included in the working amenity schedule; not yet confirmed.
Owner
Developer + Architect
Ticket
RQ-2026-005
Ticket owner
Developer
Response promise
Reply within 10 working days
18 Jul 2026
PROPOSED
EV charging readiness
Plan electrical capacity and practical provision for future EV charging.
Outcome: Subject to electrical load and final parking configuration.
Owner
MEP + Developer
Ticket
RQ-2026-006
Ticket owner
Developer
Response promise
Reply within 10 working days
22 Aug 2026
ACCEPTED
PAAA annexures
Ensure the member plan, area statement and specification are attached and versioned with the final PAAA.
Outcome: Tracked as a required member-document control item.
Owner
Legal + Developer
Ticket
RQ-2026-007
Ticket owner
Developer
Response promise
Reply within 10 working days
22 Aug 2026
UNDER REVIEW
Rent protection clarity
State when transit rent starts, escalation applies and payment protection becomes active.
Outcome: Commercial terms are recorded; final member wording remains under review.
Owner
Legal + Developer
Ticket
RQ-2026-008
Ticket owner
Committee
Response promise
Reply within 7 days
30 Aug 2026
ACCEPTED
Approval evidence
Do not mark IOD or sanctioned plans as received until the supporting document is available.
Outcome: Portal status remains IOD awaited / sanctioned plan pending.
Owner
PMC
Ticket
RQ-2026-009
Ticket owner
PMC
Response promise
Reply within 5 working days
30 Aug 2026
IMPLEMENTED
Simple member summary
Show one clear answer telling members whether they need to do anything today.
Outcome: “Your action today” is now a primary portal control.
Owner
Society Portal
Ticket
RQ-2026-010
Ticket owner
Committee
Response promise
Reply within 7 days

Member-request lifecycle

A simple governance standard for requests raised through meetings, forms, email or member discussions.

Acknowledge
Every material member request should be recorded instead of disappearing into informal communication.
Assign
A request without an owner is not an actionable project item.
Classify
Working, proposed, accepted, rejected and implemented are different outcomes and should look different.
Close the loop
Members should be able to see what happened to the request and why.

Why this matters

Redevelopment projects generate hundreds of small but important requests.

Less repetition
Members can see that a point has already been recorded instead of repeatedly raising it.
Clear accountability
The Society can show which professional or project party owns the response.
No accidental promises
A proposed request remains visibly proposed until evidence supports a stronger status.
Institutional memory
Future committee members can understand why a request was accepted, changed or closed.