A practical after-hours security stack for Metro Vancouver office towers

For a multi-tenant office tower, an after-hours security stack works best when electronic keycard records and physical inspections answer different questions. Access records can show credential activity, where the building system captures it. A guard’s documented inspection can report conditions at doors, shared spaces and other agreed locations. Neither record proves the whole building was secure. Together, they give a property manager a clearer account of what happened and what needs follow-up.

This is a practical workflow, not a report of a particular building or Zentra assignment. The details should be set for the property, its access arrangements and the coverage required.

Start with the handoff, not the technology

Before assigning overnight checks, the property manager should confirm who owns each part of the process. Building staff or the access-system administrator can review keycard activity. The security provider can follow agreed post instructions, record observations and report incidents. A named contact should receive urgent exceptions and know how they will be handled.

Put the working rules in writing: which entrances and areas are in scope, what counts as an exception, who is authorized to enter restricted spaces, and how an urgent issue is escalated. Do not give guards system credentials or ask them to interpret records unless that responsibility is explicitly authorized and included in the assignment. Keep access to tenant and credential information limited to people who need it for their role.

Build the overnight sequence

1. Set the baseline. The property manager identifies the expected after-hours state: which doors should be secured, which areas remain accessible and what scheduled activity may explain unusual entry. Share only the information the assigned personnel need.
2. Review relevant access activity. The authorized building contact checks the records available from the property’s system. Depending on the system and its configuration, the records may help identify recorded entry attempts or unusual activity. Confirm the time period and account for known tenant, cleaning or maintenance schedules before treating an event as an exception.
3. Give the guard a defined inspection plan. Specify the assigned entrances, shared areas and other priority points, along with any limits on entry. The plan should say what to observe and how to report a door that is unsecured, damage, an unexpected person or another condition that needs attention. Avoid vague instructions such as “check the building.”
4. Record observations and escalate exceptions. The guard’s shift record and patrol notes should make clear what was checked, what was observed and what action or notification followed. Photo documentation can help show a relevant physical condition, where appropriate and permitted. It should not become a routine way to capture tenants, screens, access cards or unrelated personal information.
5. Close the loop in the morning. The property contact compares reported exceptions with available access records and known activity, then assigns follow-up. If the records do not explain a condition, mark it as unresolved rather than assuming the system or the inspection has ruled out risk.

Keep the evidence in its lane

A keycard event is a record of activity captured by a system, not proof of who used a credential or what happened after a door opened. It may not show someone following an authorized user through a door, a door left ajar, or activity outside the system’s coverage. The available fields and the reliability of timestamps depend on the building’s setup. Managers should confirm those limits with their system administrator.

A guard inspection has limits too. It is a snapshot of assigned locations at particular times, not continuous observation of every floor or tenant space. A photo can make a reported condition easier to review, but it does not replace a clear written note about location, time and what the guard observed. Define when a photo is appropriate and how it is handled under the property’s privacy and records practices.

Managers looking to formalize the people-and-records side of an access process may find useful background in this guide to access records, shift handover and perimeter routines. Its setting differs from an office tower, but the principle carries over: make each responsibility clear, and do not treat one record as proof of everything.

Choose coverage around the building’s actual gaps

Continuous on-site coverage, scheduled mobile patrol, temporary coverage and blended plans solve different problems. A tower with a staffed lobby may need checks of selected after-hours areas; another property may need a guard at a specific post. The decision depends on access patterns, layout, known concerns, reporting needs and how quickly someone must respond. More checks can mean more documented observations, but they also require time and a clear scope. A record without a workable response path is not much of a control.

Zentra Protection provides on-site guard and mobile patrol services, along with customized coverage and documented shift records, patrol notes, photo documentation and incident reporting. For Metro Vancouver commercial security, a property manager can ask Zentra to scope coverage around the building’s agreed inspection points and reporting requirements. The useful first step is a site-specific conversation about what must be checked, who reviews the records and what happens when the overnight evidence does not match expectations.