Child & Senior Safety Alerts in Housing Societies

Child and senior safety alerts

Two groups of residents generate most of the genuine worry in a housing society, and for opposite reasons. Children leave when nobody meant them to. Senior residents living alone stop leaving, and nobody notices for a while.

Both problems have the same shape: the society already holds the information that would answer the question, but it is scattered across a guard's memory, a register nobody reads, and a WhatsApp group where the message scrolls past.

Safety alerts turn that into something structured — a small, consent-based watch on a named set of residents. This page covers how the two flows work, what to configure, and the privacy questions you should settle before you switch it on.

Two different features under one name

Vendors bundle these together, but they behave differently and you should evaluate them separately.

Child exit alerts. A child on the watch list is logged by the guard when they leave the gate and when they return. The registered guardian gets a notification either way. The point is not to imprison the child; it is to close the gap where a parent believes their eight-year-old is in the building and they left forty minutes ago.

Senior wellness check-ins. A senior resident who lives alone confirms they are fine on a regular cadence — a tap a day is typical. If the check-in is missed, the system escalates: first a reminder to the resident, then a notification to the family contact, then to the committee or guard for a physical door knock.

The first is about movement. The second is about the absence of an expected signal. Do not let a vendor demo only the first and imply you get both.

Consent is the whole design

This is a feature that goes wrong in a specific, predictable way: it becomes surveillance of adults who did not ask for it.

Settle these rules in a committee resolution before rollout, and write them into the society's data policy:

• Enrolment is opt-in, per resident, by the flat. A committee cannot add a resident to a watch list because it thinks it knows best.
• Seniors of sound mind enrol themselves. A wellness check-in that an adult resident did not consent to is not a safety feature.
• Only the registered guardian or family contact sees the alerts — not the whole committee, and never a broadcast group.
• The resident can leave the list at any time, immediately, without needing to justify it.
• Movement logs are retained for a fixed, short window and then purged. A permanent record of when a child left the building every day for four years is a liability, not an asset.

If your committee is not comfortable writing these down, the society is not ready for the feature.

Setting up child exit alerts

1. Enrol the child from the flat's profile. Name and, if your guards need it, a photo. Keep the list to residents the guards can actually recognise.
2. Register the guardians. Usually both parents; sometimes a grandparent who is home during the day. They receive the notifications.
3. Brief the gate staff. This is the step that decides whether the feature works. The guard has to log the exit at the moment it happens. If logging lags by ten minutes it is worse than useless, because the parent gets a false sense of timing.
4. Set the notification rule. Most societies want both directions — exit and return. Some want exit only during school hours. Keep it simple to start.
5. Handle the multi-gate case. If your society has more than one gate, a child can leave by one and return by another. Every gate must be logging, or the return event goes missing and the parent is left with an unresolved exit.

Setting up senior wellness check-ins

1. Enrol the senior resident, with their agreement. Record who the escalation contact is.
2. Choose a cadence they will actually keep. Daily is standard. Anything more frequent gets ignored, and an ignored check-in produces false alarms that destroy trust in the whole system.
3. Set the check-in window generously. A resident who taps at 9am one day and 2pm the next is fine. Only a full missed window should escalate.
4. Define the escalation ladder explicitly: reminder to the resident, then family contact, then committee or guard for a physical check. Put a time gap between each step.
5. Decide who does the door knock, by name and by shift. An escalation ladder whose last rung is "someone should check" has no last rung.
6. Plan for travel. Seniors visit their children for three weeks. There must be a "pause my check-ins" option, or every holiday triggers a false emergency.

The failure modes worth knowing about

Alert fatigue. If guardians get twelve notifications a day, they stop reading them. Tune the rules until each alert carries information.

The guard bottleneck. Both flows depend on a human being doing something reliably at a gate during a busy shift. Audit it in the first month — compare logged exits against what actually happened for a couple of known cases.

Stale contacts. The family contact who moved abroad is still listed. Re-confirm annually.

False confidence. The most dangerous outcome is a parent who stops checking because they assume the system will tell them. Communicate the limits honestly at rollout.

How this works on Plinth

Safety profiles are created per resident with an explicit type — child or senior — and can be deactivated at any time from the flat's profile.

For children, the gate logs a movement event on exit and on return, and the registered guardians are notified. For seniors, the resident records a wellness check-in on their own screen; a missed window moves the profile into a missed state that drives the escalation.

Profiles are scoped to your society, alerts reach only the registered contacts rather than a society-wide broadcast, and every state change is written to the append-only audit log so the committee can review how the feature has actually been used.

Frequently asked questions

Does this track children with GPS? No. It records gate events logged by a guard — an exit and a return. There is no continuous location tracking, which is deliberate: continuous tracking of a minor by a society body raises consent problems that a gate log does not.

Can we enrol a senior resident who does not want it? No, and you should not want to. Enrolment requires the resident's agreement. A society that overrides this is creating a data-protection problem for itself.

What if the senior forgets to check in but is perfectly fine? That is what the escalation ladder is for — the reminder catches most cases before anyone is disturbed. It is also why the check-in window should be generous.

Who sees the movement history? The registered guardian and the resident. It is not a committee-wide report, and it should not be retained indefinitely.

Does it work if the guard forgets to log an exit? No, and this is the honest limitation. The feature is exactly as reliable as your gate discipline, which is why the rollout should start with staff briefing rather than a resident announcement.

Step-by-step guides

• Admin: Set Up Child & Senior Safety Alerts
• Resident: Use Child & Senior Safety Alerts

Related: Emergency SOS panic button · guard patrol and QR checkpoints · visitor gate management