Managing a Courier’s Visit Properly
Summary: A delivery is a visit that needs handling. This article walks through how Aregnum handles a delivery from the courier’s arrival to completion.
A delivery to a community is a visit that needs handling, from the courier’s arrival through to the delivery being completed. Deliveries are a common and growing form of arrival, and handling them properly, controlling the courier’s access, dealing with the delivery, and keeping a record, is part of managing a community’s visitor activity. Walking through how a delivery is handled from start to finish shows how a platform supports managing a courier’s visit, so the delivery is handled with control and record rather than couriers being an uncontrolled stream of arrivals.
The handling starts with the courier’s arrival, which is a visit to be controlled. A delivery begins when the courier arrives, and this arrival is a visit whose access should be controlled. Because Aregnum manages access and visitors, the courier’s arrival is handled as a controlled visit, so the delivery starts with the courier’s access being managed rather than the courier simply entering uncontrolled, which brings the delivery within the community’s visitor management from the start.
The courier’s access is controlled to what the delivery requires. A courier needs access to make the delivery, but this access should be controlled appropriately rather than giving the courier free run. Because the platform controls access, the courier is given access suited to making the delivery, so their access is appropriate to what they are there to do, which manages the courier’s presence properly during the delivery.
The delivery is dealt with according to whether the resident is available. The delivery proceeds differently depending on whether the resident is there to receive it, and the community handles this. Where the resident is available, the delivery is made to them; where they are not, the community handles it according to its approach, which for communities that take in parcels can involve the platform’s support for logging and notification. So the delivery is dealt with appropriately whether or not the resident is present.
The courier’s visit is recorded, so the community has an account of the delivery. As the courier’s visit is handled, it is recorded, so the community knows the delivery occurred and who made it. Because the platform records the courier’s visit, the community has an account of the delivery, so deliveries are captured in the community’s record of who came, rather than couriers being an unrecorded stream of arrivals the community cannot account for.
Notifying the resident, where the community handles parcels, completes the handling for an absent resident. Where the community takes in a parcel for an absent resident, notifying them that it arrived completes the handling. Because the platform supports notifications, the community can inform an absent resident that their delivery arrived, so the delivery’s handling is completed by the resident being told, rather than the parcel sitting with the resident unaware it came.
The completed delivery leaves the community with control exercised and a record kept. When the delivery is complete, the community has controlled the courier’s access and recorded the visit, so the delivery has been handled properly from start to finish. Because the platform supported the whole handling, the completed delivery leaves the community having exercised control and kept a record, which is what handling a delivery properly means, rather than the delivery being an uncontrolled, unrecorded event.
It is worth drawing out that deliveries deserve proper handling precisely because they are so frequent and easy to treat carelessly, so that an uncontrolled delivery stream becomes a real security gap. Because deliveries are routine and often hurried, communities are tempted to wave couriers through without control or record, but the very frequency of deliveries means an uncontrolled delivery stream is a significant and recurring gap in who enters. Because the platform brings deliveries within the community’s controlled, recorded visitor management, it closes a gap that the sheer routineness of deliveries tempts communities to leave open, so handling deliveries properly addresses a security weakness that is easy to overlook precisely because deliveries are so common and seemingly innocuous.
It also helps to recognise that good delivery handling serves residents as a real convenience, especially for the increasingly common case where a resident is out when a delivery arrives. A resident who is out risks missing a delivery entirely, but a community that handles the delivery, taking in the parcel where that is its approach and notifying the resident, spares them the missed delivery and the hassle of rearranging it. Because the platform supports handling the delivery and notifying the resident, it turns good delivery handling into a genuine service to residents, who benefit from their deliveries being dealt with even when they are not there to receive them, so managing deliveries well serves residents’ convenience as well as the community’s security, addressing a matter that grows more relevant as deliveries multiply.
A delivery is a visit that needs handling from the courier’s arrival to completion, and handling it properly is part of managing a community’s visitor activity. Aregnum supports this by controlling the courier’s access, letting the delivery be dealt with whether or not the resident is present, recording the visit, and, for communities that handle parcels, supporting notification. For a community managing the common and growing matter of deliveries, handling each from start to finish is what keeps deliveries controlled and recorded, so couriers are managed as the visits they are rather than an uncontrolled stream of arrivals.
Frequently Asked Questions
Why does a delivery need handling?
A delivery is a visit, from the courier’s arrival through to completion. Deliveries are a common and growing form of arrival, and handling them properly, controlling the courier’s access, dealing with the delivery, and keeping a record, is part of managing a community’s visitor activity.
How is the courier’s access handled?
Because Aregnum manages access and visitors, the courier’s arrival is handled as a controlled visit, and the courier is given access suited to making the delivery, so their access is appropriate to what they are there to do rather than free run.
What happens if the resident is out?
The delivery is dealt with according to whether the resident is available. Where they are not, the community handles it according to its approach, which for communities that take in parcels can involve the platform’s support for logging the parcel and notifying the resident.
How is the delivery recorded?
As the courier’s visit is handled, it is recorded, so the community has an account of the delivery and who made it, and deliveries are captured in the community’s record of who came rather than couriers being an unrecorded stream of arrivals.
See Aregnum in action
Ready to turn your community into an effortless, secure haven? Book a demo and we will show you how Aregnum fits your property.