Section 12
Transparency & Evidence Archive
A tagged, anonymized archive of resident-reported incidents. Each entry notes the type of material reviewed, its verification label, and whether a management response or remediation was reported.
How to read these labels
Reviewed does not mean proven
A verification label describes what material the platform examined — not whether an allegation is true. Allegations remain allegations unless independently verified by a competent authority or court. Definitions follow the Source Verification Policy.
- Court document reviewed
- A filed court document was examined. Court filings may contain competing allegations by different parties; allegations by either side remain allegations unless determined by a court.
- Management correspondence reviewed
- Written correspondence from management or its representatives was examined. Reviewing the correspondence does not confirm the accuracy of statements inside it.
- Resident-submitted media reviewed
- A resident-supplied screenshot, photograph, video still, invoice or message thread was examined and found internally consistent. This does not mean the allegation has been proven.
- Multiple resident reports reviewed
- Comparable material or accounts were examined from more than one resident. Corroboration between residents is not independent verification.
- Resident report only
- A resident account with no supporting documentary material submitted or reviewed.
- External reporting
- Drawn from independent third-party reporting. External coverage is context, not confirmation of every claim in this archive.
- Verification pending
- Material has been received but review is not complete. No conclusion should be drawn from the entry in its current state.
Approximate periods are used where an exact date could identify a resident. Management, contractors, and any named party may respond via the Right of Response page.
- LegalINC-017
Court documents reviewed by this archive show that civil proceedings were commenced concerning enakitown.com and related online and social-media publications, including TikTok. The existence of proceedings is not evidence that any underlying resident concern documented here is true or false. Court filings may contain competing allegations by different parties; allegations by either side remain allegations unless determined by a court. No case numbers, procedural history or hearing details are published in this archive.
Approx. period: 2026
LegalEvidence Type
Court document
Verification Status
Court document reviewed
Mgmt Response
Not reported
Remediation
Not reported
Supporting material reviewed: filed court documents. No interlocutory ruling, judgment or outcome is characterised here, and no legal analysis is published.
Entry updated: June 2026
- Access ControlINC-016
Multiple residents in a submitted WhatsApp discussion reported difficulty with the main-gate RFID/barrier system. Reported concerns included RFID tags requiring repeated forward/backward vehicle movement before detection, slow or inconsistent barrier operation, one resident reporting that the barrier had contacted the roof of their vehicle on several occasions, another resident reporting a similar barrier contact, and a resident stating they had complained and been asked to be patient with the barrier. The platform does not state that vehicle damage occurred, that the barrier was defective as an established engineering fact, or that management was negligent.
Approx. period: Q2 2026
Access ControlSecuritySafetyRepairEvidence Type
WhatsApp screenshot
Verification Status
Multiple resident reports reviewed
Mgmt Response
Partial
Remediation
Not reported
Supporting material reviewed: a resident WhatsApp discussion involving several residents. Individual barrier-contact incidents not independently verified. Clarification requested on inspection of the RFID/barrier system, logging of barrier-contact incidents, sensor/detection/timing adjustments, the reporting process for vehicle contact or alleged damage, and whether residents received a written maintenance update.
Entry updated: June 2026
- ConstructionINC-015
Resident-submitted screenshots show residents raising concerns about construction activity near the Botanical Garden / neighbouring school side at unusually late or early hours. One resident submitted a short video and asked that the construction respect working hours. A later resident message at approximately 4:04 AM asked who was conducting construction at that time. A resident reported that Enaki reception attributed the activity to the neighbouring school and said the matter was being escalated. The platform has not verified who carried out the work, the applicable working hours, or whether any rule was breached; statements about illegality are residents' own allegations.
Approx. period: Q2 2026
ConstructionNoiseEvidence Type
Multiple sources
Verification Status
Multiple resident reports reviewed
Mgmt Response
Partial
Remediation
Not reported
Supporting material reviewed: resident-submitted screenshots and a referenced short video. Source of the construction, contractor identity and applicable working hours not independently verified. Clarification invited from Enaki management, the neighbouring property/project, and contractors if identifiable.
Entry updated: June 2026
- Emergency PreparednessINC-014
A resident asked whether management had implemented preventative measures for increased flood risk and extended power interruptions, including flood barriers or berms and sufficient generator/fuel capacity. This entry records a resident question and request for clarification. It does not report that flooding occurred, that flood-prevention measures were absent, that generator capacity was inadequate, or that the property was unprepared.
Approx. period: Q2 2026
PreparednessSafetyEvidence Type
WhatsApp screenshot
Verification Status
Resident-submitted media reviewed
Mgmt Response
Not reported
Remediation
Not reported
Supporting material reviewed: one resident-submitted screenshot. Preparedness status not independently verified. Clarification requested on flood-risk assessment, drainage and flood-mitigation measures, backup-power capacity, generator/fuel endurance for essential systems, and whether an emergency-preparedness plan is available to residents.
Entry updated: June 2026
- Resident Safety / AccessINC-013
A resident sent a contemporaneous written complaint to Enaki / HassConsult representatives on the evening of 24 June 2026, alleging that security and reception delayed or restricted his attempt to leave the property shortly after approximately 9 PM. On 25 June 2026 Enaki Resident Services acknowledged the complaint, apologized for any inconvenience experienced during the exit, and stated that an internal review had commenced. The resident subsequently stated that multiple witnesses supported his account and that video/audio recordings of parts of the incident existed. The legal characterization of the incident is disputed; this archive presents no legal conclusion as established fact.
Approx. period: 24–25 June 2026
Access ControlSafetySecurityEvidence Type
Email correspondence
Verification Status
Management correspondence reviewed
Mgmt Response
Reported
Remediation
Partial
Supporting material reviewed: the resident's contemporaneous correspondence and the management acknowledgement of 25 June 2026. Supporting media and witnesses reported by the resident but not reviewed. CCTV footage, gate logs, occurrence-book records, radio communications and the internal review outcome have not been reviewed.
Entry updated: June 2026
- ConstructionINC-012
Resident-submitted video stills and WhatsApp screenshots appear to show ongoing construction/concrete-related activity around 4:58 PM on Saturday, 20/06/2026. The submitting resident alleges residents had been told Saturday work would stop at 1 PM and expressed frustration that construction appeared to continue into the late afternoon. The platform has not independently verified the promised cutoff, permitted hours, contractor identity, or regulatory status of the works.
Approx. period: 20 June 2026
ConstructionNoiseEvidence Type
Multiple sources
Verification Status
Resident-submitted media reviewed
Mgmt Response
Not reported
Remediation
Not reported
Supporting material reviewed: resident-submitted video stills and WhatsApp screenshots showing apparent construction activity around 4:58 PM on Saturday, 20/06/2026. Personal identifiers must be redacted before publication. Management response: clarification requested, not yet reported.
Entry updated: June 2026
- ConstructionINC-011
Resident-submitted WhatsApp screenshots appear to show an Enaki Support notice for Block D rooftop waterproofing works (mobilization 17/06/2026; active works 18/06/2026, 9am–5pm, 20 working days). Follow-up resident messages describe noise concerns and headache/migraine-type discomfort. See the full update for context.
Approx. period: June–July 2026
ConstructionNoiseRepairEvidence Type
WhatsApp screenshot
Verification Status
Resident-submitted media reviewed
Mgmt Response
Reported
Remediation
Partial
Supporting material reviewed: two resident-submitted WhatsApp screenshots. Personal identifiers redacted before any publication.
Entry updated: June 2026
- RepairINC-010
Resident described positive experience with a preventative maintenance visit following formal complaint.
Approx. period: Q2 2026
RepairInspectionEvidence Type
WhatsApp screenshot
Verification Status
Resident-submitted media reviewed
Mgmt Response
Reported
Remediation
Reported
Supporting material reviewed: WhatsApp screenshot.
Entry updated: June 2026
- Utility BillingINC-009
Resident reported deductions from a deposit referencing utilities and disputed the calculation.
Approx. period: Q2 2026
Utility BillingElectricityEvidence Type
Email correspondence
Verification Status
Management correspondence reviewed
Mgmt Response
Partial
Remediation
Not reported
Supporting material reviewed: email correspondence. Reviewing the correspondence does not confirm the underlying calculation.
Entry updated: June 2026
- SecurityINC-008
Resident reported inconsistent screening at access points and concerns about unauthorized access.
Approx. period: Q2 2026; month withheld for privacy
SecurityEvidence Type
Resident account
Verification Status
Resident report only
Mgmt Response
Partial
Remediation
Not reported
Entry updated: June 2026
- Rent IncreaseINC-007
Resident discussion of a lease-renewal rent increase during a period of ongoing repairs and disruption.
Approx. period: Q2 2026; specific date withheld for resident privacy
Rent IncreaseConstructionEvidence Type
Resident account
Verification Status
Resident report only
Mgmt Response
Not reported
Remediation
Not reported
Entry updated: June 2026
- ConstructionINC-006
Daytime drilling and dust reportedly disrupted remote-work calls over multiple weeks.
Approx. period: Q2 2026
ConstructionNoiseEvidence Type
Multiple sources
Verification Status
Multiple resident reports reviewed
Mgmt Response
Not reported
Remediation
Not reported
Supporting material reviewed: photographs and WhatsApp screenshots.
Entry updated: June 2026
- InspectionINC-005
Residents discussed an inspection campaign reportedly covering shower enclosures and door adjustments.
Approx. period: Q1 2026
InspectionSafetyRepairEvidence Type
WhatsApp screenshot
Verification Status
Multiple resident reports reviewed
Mgmt Response
Reported
Remediation
Reported
Supporting material reviewed: WhatsApp screenshots from multiple residents.
Entry updated: June 2026
- LeakINC-004
Recurring leak in a unit; multiple repair attempts described as temporary by the resident.
Approx. period: Q1 2026
LeakRepairEvidence Type
Photograph
Verification Status
Resident-submitted media reviewed
Mgmt Response
Reported
Remediation
Partial
Supporting material reviewed: photograph; repair records not received.
Entry updated: June 2026
- ElectricityINC-003
Resident questioned an unusually high electricity bill received during a period of limited occupancy.
Approx. period: Q1 2026
ElectricityUtility BillingEvidence Type
Invoice / bill
Verification Status
Resident-submitted media reviewed
Mgmt Response
Not reported
Remediation
Not reported
Supporting material reviewed: invoice. Tariff and metering methodology not reviewed.
Entry updated: June 2026
- SafetyINC-002
Second resident in a different block reported a comparable shower-glass collapse; discussion referenced hinge installation.
Approx. period: 2025–2026
SafetyConstructionInspectionEvidence Type
Multiple sources
Verification Status
Multiple resident reports reviewed
Mgmt Response
Reported
Remediation
Reported
Supporting material reviewed: WhatsApp screenshots from multiple residents.
Entry updated: June 2026
- SafetyINC-001
Resident reported shower glass shattering during use; injuries described in subsequent screenshots.
Approx. period: 2025–2026
SafetyConstructionRepairEvidence Type
Photograph
Verification Status
Resident-submitted media reviewed
Mgmt Response
Reported
Remediation
Partial
Supporting material reviewed: photograph and resident statement.
Entry updated: June 2026
Frequently Asked
Evidence archive: questions & answers
- What does each evidence card represent?
- Each card represents an anonymized resident-reported incident or pattern, with an internal ID, category, approximate period, summary, evidence type, verification status, management-response status, and remediation status.
- What does 'verification status' mean?
- A verification label describes what material the platform examined — not whether an allegation is true. Allegations remain allegations unless independently verified by a competent authority or court. The archive uses seven source-specific labels: Court document reviewed — A filed court document was examined. Court filings may contain competing allegations by different parties; allegations by either side remain allegations unless determined by a court. Management correspondence reviewed — Written correspondence from management or its representatives was examined. Reviewing the correspondence does not confirm the accuracy of statements inside it. Resident-submitted media reviewed — A resident-supplied screenshot, photograph, video still, invoice or message thread was examined and found internally consistent. This does not mean the allegation has been proven. Multiple resident reports reviewed — Comparable material or accounts were examined from more than one resident. Corroboration between residents is not independent verification. Resident report only — A resident account with no supporting documentary material submitted or reviewed. External reporting — Drawn from independent third-party reporting. External coverage is context, not confirmation of every claim in this archive. Verification pending — Material has been received but review is not complete. No conclusion should be drawn from the entry in its current state.
- Are raw screenshots published?
- No. Raw WhatsApp or messaging-app screenshots containing identifiers are not published. Identifiers are removed before any publication.
- Does an entry being archived mean the underlying allegation is proven?
- No. Archived entries are resident-reported allegations or experiences. They are not findings of fact and may be disputed by management or other parties.
- How can management dispute or clarify an entry?
- Management is invited to submit clarifications via the Right of Response page. Responses will be published in full alongside the relevant entry.
- How are entries dated?
- Entries are tagged with approximate periods (for example a quarter or year range) where safer than naming a specific resident or unit. Specific dates may be withheld to protect resident anonymity.