Home · Condo exit
Condo visitor QR revoke
Revoke guest QR and helper codes while the resident app login still works — cards alone are not enough.
Last reviewed 2026-09-15
Leaving a condo with guest QR, temporary access, and delivery PINs still live — revoke lists, helper / tutor codes, and how visitor apps collide with MCST card return and movers week.
Inventory every QR, PIN, and guest link
Condo apps often keep visitor QR, one-day PINs, and recurring helper / tutor codes after the unit is empty. Physical access cards are a separate path — guest digital access can still open the lobby after you fly. Export the active guest list from the condo app before SIM or email changes lock you out.
- Screenshot every active visitor / delivery / helper code with expiry
- Note which adult account issued each code (resident vs tenant admin)
- Pair with /journeys/condo-mcst-exit for physical cards and IU return
Revoke digital access before key handover
Revoking guest QR after the agent collects keys is harder — your app login may already be deactivated with the MCST resident profile. Kill recurring helper, pet-sitter, and tuition codes on the last full day you still control the app. Keep one short delivery PIN only if movers still need a lobby pass.
- Revoke recurring codes first; leave at most one movers-day delivery PIN
- Confirm the managing agent will close the resident app profile on checkout
- Do not leave guest links in family WhatsApp history as if they still work
Helper, tutor, and vendor standing access
FDW, tutors, cleaners, and aircon contractors often hold standing visitor profiles that outlive the tenancy. If the helper is transferring or cancelling separately, revoke condo guest access on the same morning as the handoff — not after Changi. Vendors with QR for warranty visits need a written cancel too.
- Align helper condo revoke with /journeys/helper-handoff-exit when that playbook is on main
- Email tutors / cleaners that lobby QR dies on a named date
- Ask MCST whether vendor QR is estate-wide or unit-scoped
Delivery PIN vs loading-bay booking
Movers and parcel lockers are not the same access problem. A loading-bay booking does not revoke yesterday’s GrabFood PIN. Clear delivery PINs and locker codes after the last inbound parcel, and tell the agent which codes were active so they do not chase “unknown visitors” on CCTV after you leave.
- Cancel parcel-locker holds tied to your mobile number
- Keep the movers PIN only for the booked lift / bay window
- Photograph the app’s “access revoked” confirmation where available
Same-week stack with MCST and utilities
Visitor QR revoke, MCST card return, and utility meter photos often land in one fortnight. Sequence so digital revoke happens while the resident login still works, then physical tokens, then meter handover. Do not schedule app revoke after Singpass / SIM changes that break 2FA.
- Put app revoke, card return, and meter photos on one family calendar
- Pair with /journeys/utility-exit-handover for meter photo backups
- Keep one adult’s condo app login alive through checkout morning
Cash float: lost-token fees vs deposits
Some estates charge for unreturned cards or “lost” remotes even when the real issue was a forgotten guest profile. Keep a small SGD float for replacement fees while landlord and MCST deposits are still open. School device bonds are a separate cash pot — sketch those on the device tool if kids still hold iPads.
- Ask MCST published fees for missing cards vs admin revoke
- Do not raid school device bond cash for condo fees
- Sketch device risk on /tools/school-device-bond
This playbook is editorial guidance, not legal or tax advice. Confirm current IRAS and MOM requirements before you act.
Related: Condo MCST exit · School device bond · Mover lift booking