Bottom line: a time schedule assumes the site is ready to receive people. Requiring a real authorized arrival can prevent an empty building from unlocking automatically, but only if the trigger and reset behavior match operations.
\nThe AXIS Camera Station Feature Guide describes unlocking schedules in Secure Entry. It explains a first-person-in option under which the unlocking schedule does not unlock the door until someone first enters. The guide also lists product and version compatibility information for features.
\nThis is a conditional schedule, not a substitute for opening procedures. The event that satisfies the condition, the doors affected, and the behavior after a late arrival or exception must be proven in the exact configuration.
\nThe guide documents an Axis feature and does not define the safety, staffing, public-access, school, retail, or workplace policy for a site. Compatibility and exact behavior depend on deployed products and software. The source does not guarantee holiday, daylight-saving, controller-offline, emergency-release, or reset outcomes; those are acceptance questions for the installed system.
\nThe following steps are DSE recommendations based on the cited source.
\nName the eligible arrival group, trigger reader, controlled doors, schedule, reset boundary, and manual exception authority. Require the arriving person to complete the site’s readiness checks before using the trigger where operations permit. Protect that reader and credential group from casual or remote activation.
\nTest arrival before schedule, during schedule, after a late start, no arrival, holiday, denied credential, controller offline, server outage, emergency release, scheduled relock, and next-day reset. Observe physical locks and door states, not only the schedule display. Provide a time-limited, logged manual opening path with independent confirmation for exceptional operations.
\nTest two eligible arrivals in quick succession and an arrival at the schedule boundary. The resulting event order should not extend unlocking beyond the approved window or create an unexplained second transition.
\nRetain the operating requirement, compatibility record, schedule and eligible-group export, test identities, complete scenario matrix, access and unlock events, physical observations, time-source evidence, exception approvals, scheduled relock result, and acceptance signatures. Review first-arrival events periodically for unexpected identities or times.
\n