Move-in and move-out without the chaos

A family moves out of B-702 on the last Sunday of the month. The lift is booked by someone else, the packers arrive at the gate unannounced, the exiting tenant's dues are discovered on Tuesday, and the new tenant's police verification surfaces as a question in the WhatsApp group three weeks later. None of this was anyone's fault — which is exactly the problem. Move-ins and move-outs fail because they are everyone's job, and a workflow is how you make them someone's.

Why handovers go wrong by default

A move touches five parties who don't share a system: the owner (often absent), the tenant, the broker, the security gate, and the society office. Each holds one piece — the agreement, the dues position, the lift booking, the ID documents — and the society finds out what was missing only after the truck has left. The fix is not more rules; it's a single checklist that all five parties can see, with a state that advances only when each step is done.

The move-out sequence that protects the society

1. Notice of vacancy — owner or tenant raises it in the app, which timestamps the intent and starts the clock.
2. Dues clearance — the system checks the unit ledger automatically. This is the step paper processes always fumble: the accountant learns about the move after it happened. A workflow blocks the gate pass until arrears, amenity fines and deposit adjustments are settled — politely, and in advance.
3. Facility booking — lift protection pads and a service-lift slot, booked like any other amenity so two moves never collide on one Sunday.
4. Gate authorisation — a move-out pass listing the truck and crew, issued only when steps 1–3 are green. The guard scans it; no debate at the barrier.
5. Handover record — meter readings, key count, and the "no dues" acknowledgment, captured with photos. Ninety percent of deposit disputes die here.

The move-in sequence that protects the resident

The incoming side mirrors it: tenancy documents and IDs uploaded before arrival, police-verification acknowledgment where local rules require it, vehicle and family details captured once (not re-asked by three different registers), gate pass for the incoming truck, and app access granted the moment the checklist completes. A tenant whose first day includes working gate passes and a live helpdesk account starts as a citizen of the community rather than a stranger negotiating with it.

Decide the four policy questions once

Every society's workflow needs four local decisions, and they belong in a committee minute, not in each move's argument:

• Moving days and hours — most societies land on weekdays plus Saturday mornings, sparing Sunday's parking chaos.
• Refundable move deposit — covers lift and lobby damage; refunded against the handover record's photos.
• Who signs off dues — treasurer or manager, but exactly one of them.
• Broker access — whether brokers can raise the workflow on an owner's behalf, and with what proof of authorisation.

What changes when it's software

On paper, this checklist is a diligent manager's personal system, and it retires when they do. Encoded as a workflow — as it is in Radiatus Communities — it becomes the society's institutional memory: every step timestamped, every approval attributed, every document attached to the unit's record where the next committee can find it. The manager stops being a bottleneck and becomes an approver; the owner in another city watches the same checklist advance that the gate guard sees.

The measure of a good handover process is negative space: the Sunday that passes without a lift dispute, the deposit returned without a fight, the new tenant who never had to ask "who do I talk to about a gate pass?" If your society averages more than a move a month, the workflow pays for its setup in the first quarter — see it configured live for your society's rules.