Every visitor on the record. No sign-in book.
Residents invite visitors from the app. Passes are time-boxed and expire on their own, and every entry is written to the same searchable trail as every other door event.
Live in pilot. What we demo is what is running.
Invited, time-boxed, recorded.
Invited from the resident app
Residents invite their visitors from the app. No lobby forms, no calls to the front desk, no paper.
Time-boxed by default
Every pass has a start and an end. When the window closes, access closes with it. Nobody has to remember to cancel a pass.
Same doors, governed the same way
A visitor pass is an access grant like any other: role-scoped, running on the same Suprema BioStar Air hardware and the same door schedules.
A searchable entry trail
Every visitor entry lands on the same audit trail as resident and operator events. Who came in, through which door, on whose invitation: one query.
One record. Not another silo.
Visitors are not a separate portal with a separate log. A pass is an entry on the same record, tied to the resident who issued it and the door it opened.
Rides on the access module
Same doors, same hardware, same revoke-in-seconds control if something is wrong.
ExploreEvery pass has an owner
Passes are tied to the resident who issued them, so visitor activity always has an owner on the record.
ExploreEntries count without a report
Visitor entries are access events, so they show up in portfolio access insight without a separate export.
ExploreThe entry trail is the point.
Sign-in books tell you who wrote their name, not who came in. A visitor entry in BTR OS is a fact: an event tied to a pass, a door and the resident who sent the invitation. The trail it lands on is immutable, access to it is role-scoped through Microsoft Entra, and the data never leaves Australia. When an incident question arrives, the answer is a query, not a hunt through the lobby book.
Why not a standalone visitor management system?
A standalone system gives you another portal, another login and another log to reconcile. Visitors in BTR OS are entries on the same trail as every other door event, tied to the resident who invited them.
Where it sits, from application to keys.
Living
Visitors, amenity bookings and rent run from one app, until move-out reverses the flow.
See the sign-in book retired.
Time-boxed passes, invited from the app, every entry searchable on one trail. It is running in pilot today. Book a pilot and query the entry trail yourself.
Prefer email? hello@ark360.com.au