At shared commercial premises, each visitor should have an identifiable host or other authorised sponsor, with clear rules for reception and access. A booking or a familiar face does not establish permission to enter every tenant’s space. Agree who approves the visit, who admits the visitor and who closes the record when they leave.
Separate landlord and occupier decisions
The reception team may manage a shared entrance while each tenant controls its own workspace. Document the point at which responsibility passes from the shared-area team to the host. Do not leave reception to infer a tenant’s access decision from a delivery note or an informal message.
Consider ordinary visitors, contractors and deliveries separately where their needs differ. A contractor undertaking work may need an induction or another authorisation beyond an invitation to attend. The host should understand what they are approving.
Confirm the sponsor before granting access
Give reception a reliable way to contact the authorised host and a fallback when that person is unavailable. Where approval cannot be confirmed, follow the agreed process rather than extending access because the visitor is waiting or appears to know the building.
- Identify the tenant or department expecting the visitor.
- Confirm the approving host through the agreed channel.
- State any relevant access limits and escort arrangements.
- Provide clear departure and pass-return instructions.
Keep private contact lists and detailed permissions out of public visitor notices. The notice should tell visitors how to obtain assistance without exposing the building’s operational arrangements.
Match permissions to the visit
The NPSA’s overview of automatic access-control systems describes controlling who can go where and when. Apply that principle to visitor arrangements: permission should match the authorised purpose, rather than defaulting to the widest access the system can provide.
If a temporary credential is issued, establish who records it, who is responsible for its return and how its permission ends. A shared pass whose custody is unclear makes it difficult to distinguish an authorised visit from a missing or retained credential.
Collect only useful information
Decide what information is necessary for the visitor process and why it is needed. Avoid collecting extra identity details merely because the reception software has an empty field. Restrict access to the visitor record and agree its retention with the responsible organisation.
The ICO’s data-minimisation guidance is a useful basis for that review. A building’s security purpose does not automatically justify retaining every document or personal detail presented at reception.
Close the visit and resolve exceptions
Record the agreed departure action and deal with passes that have not been returned. Escalate an unresolved exception to the responsible tenant and system owner. Do not let an unclosed visitor record become an indefinite access arrangement.
For example, in a shared commercial building a tenant’s engineer may be authorised to attend one workspace while common-area work requires a separate approval. This illustrates the importance of a sponsor; it is not a claim about a K9 deployment.
Agree responsibilities before commissioning guarding
For a commercial site, review K9 Security Services’ current services and send an enquiry with the postcode, intended duties and relevant site conditions. Scope and feasibility need to be agreed for the individual premises; this guide does not promise availability or a particular security outcome.
Featured image: an illustrative electronic door-entry system, not a K9 installation.