Package room overflow is handled with four disciplines: log every package the moment it arrives, record where it was shelved, release it only against proof of pickup, and return what nobody claims inside a written hold window. The room drowns when arrivals outrun closures, so each discipline exists to make the close-out as fast as the intake. Software makes the logging cheap; the disciplines themselves work on paper, just slower.
Thursday, 4:40 PM, the second week of December. The courier wheels in a cart carrying 31 packages and holds out the scanner for one signature that covers all of them. Behind him, the resident from unit 908 is asking about a parcel that showed as delivered last Tuesday and has not been seen since. The desk has until the evening rush to shelve the cart, and one signature just made all 31 of those boxes the building's problem.
Why the package room overflows
A package room fills up because it sits at the end of everyone else's supply chain. United States carriers moved 23.1 billion parcels in 2025, up 3.3% in a year, which works out to 732 parcels entering the network every second, per the Pitney Bowes Parcel Shipping Index (verified August 2026). In a multifamily building, a meaningful share of that stream ends at the lobby, because carriers deliver to the desk, not the door.
The overflow mechanic is an imbalance, not a mystery. Arrivals come in bursts: one cart, dozens of boxes, minutes apart at peak season. Departures dribble: one resident at a time, whenever they happen to come home. Any shelf where intake runs in batches and close-out runs in singles will grow unless something caps it, and the cap is procedural: fast intake, findable storage, proven pickup, and a return policy that actually executes. Buildings that treat overflow as purely a space problem buy shelving and refill it.
Chain of custody, from the courier's scanner to the resident's hands
Chain of custody is the documented trail of who held an item from the moment it changed hands to the moment it left: what arrived, who accepted it, where it sat, and who carried it away. Courts use the term for evidence; buildings need it for cardboard. The reason is the same in both places: when an item goes missing, the question lands on whoever held it last on paper.
A package crossing a staffed lobby changes hands three times. The courier hands it to the desk, and the carrier's tracking ends there; "delivered" is the last event their system will ever record. The desk hands it to a shelf, which is a real transfer, because a package the log cannot place is lost for all practical purposes even while it sits in the building. The shelf hands it to a resident, and that is the transfer disputes care about most. The building's record has to begin the second the courier's record ends, or the hole in the chain sits exactly where the questions land. The package shelf is one of six custody records a staffed desk keeps; Front Desk Operations for Residential Buildings maps the full set.
The package log: what intake records
A package log earns its keep at intake, and intake happens under the worst conditions the desk faces: the cart is full, the lobby is busy, and the courier is already leaving. The record each arrival needs is short: the carrier, the tracking number, the recipient and unit, the arrival date, a note saying where it was shelved, and the label itself as an attachment. Everything else is optional; these six fields are the chain.
Each field answers for a different failure. The tracking number ties the building's record to the carrier's, which is what a delivery dispute gets argued from. The recipient and unit tie the parcel to a person instead of to whoever asks for it. The arrival date starts the hold window. And the storage note is the quiet workhorse: most package delays are not lost parcels but unfindable ones, and "row C, bottom shelf" turns a fifteen-minute search into a reach. The log is written against the resident directory, not from memory, because the building has four Johnsons and two of them are in unit 1104's household.
Proof of pickup: the half that settles disputes
Proof of pickup is what separates a package log from a list of arrivals. The intake half of the record proves the building received a parcel; the pickup half proves it left, in a named person's hands, on a date. That is the half disputes turn on, because "we handed it over" is an assertion, and a signature or a photo of ID is a fact. It also protects the ordinary case where someone collects a household member's box: the record does not say the recipient took it, it says exactly who did.
The disputes a package shelf actually produces, and the record that answers each:
| The dispute | The record that answers it |
|---|---|
| "It never arrived." | The intake entry: carrier, tracking number, and arrival date, with the label photo attached |
| "It arrived, but it's gone." | The storage note and the status: where it was shelved, and whether it ever left |
| "Someone else took my package." | The pickup capture: who collected it, on what date, with photo ID or a signature |
| "The carrier says delivered; the desk has nothing." | The log's silence: a desk that records every arrival can say a parcel never reached it |
The last row is the one operators underrate. A log with no gaps proves negatives: if every arrival is recorded and this one is not on the record, the building never took custody, and the dispute belongs to the carrier. A log kept "when things calm down" cannot say that about anything.
Statuses and the return policy: what caps the shelf
Every package on the shelf should be in exactly one of three states: received, picked up, or returned to sender. Received is the only state that occupies shelf space, which makes the status list a live inventory of the room; anything received and older than the hold window is a decision waiting to be made, not background scenery.
The hold window is the building's own policy, and the policy is what caps the shelf. Pick a number of days, write it into the building's rules, display it where residents see it, and enforce it by actually returning what expires, with the return recorded like any other custody transfer. Common practice runs 3 to 14 days. The number matters less than the follow-through: a return policy that never executes is a shelf that only grows, and every stale parcel on it is a dispute aging toward the desk.
How to run package intake, from cart to closed record
The procedure below is software-neutral; it is the discipline the record depends on, whatever holds the record:
- Log each package as it comes off the cart: carrier, tracking number, recipient, and unit, before the courier leaves.
- Photograph the label and attach it to the entry, so the original evidence survives any typing error.
- Match the recipient against the resident directory, not against memory; same-name households are where misdirected parcels start.
- Record where each package goes: shelf row, bin, oversize floor spot, or cold storage, in the entry itself.
- Release only against proof: a photo of ID or a signature on every pickup, including the neighbors everyone knows by name.
- Sweep the shelf weekly against the hold window and flag everything past it.
- Return what expires and record the return, so the week ends with zero packages in an unexplained state.
How Scaalr logs a package from a photo of the label
Package tracking software earns its keep at intake, where the desk's time is scarcest. In Scaalr, logging a package starts with a photograph: point the camera at the shipping label and the Scan Slip feature reads it, fills in the carrier, tracking number, and recipient, matches the recipient to a resident, and shows a confidence level on how clearly the label read, then attaches the photo to the record. The person at the desk confirms the resident match and corrects any pre-filled field before saving, which keeps a human decision between the camera and the record. A cart of 31 packages becomes 31 records at roughly the pace of taking 31 photos.
Pickup runs the proof half. Whoever collects a package is recorded by name, and the desk captures either a photo of their ID or an on-screen signature, attached to the record as chain-of-custody proof, with the pickup date and the "picked up by" kept on the entry. Every package carries one of the three statuses (received, picked up, or returned), so the packages tab, which shows a live count inside each building's front desk workspace, doubles as the shelf inventory and the weekly sweep list. The workspace runs in the browser and switches to stacked cards on a phone, so intake happens standing at the cart rather than back behind the counter. Every front desk action lands on the record as it happens.
The label scan is one of two places Scaalr attaches AI to a shipped, daily job; the other is the resident inbox, covered in AI for the Property Management Inbox: What Alex Reads, Flags, and Answers. The front desk, including package tracking and the label scan, is part of Growth and up: $99 for the first 50 units, then $1.49 per additional unit.
The same cart, on the record
Back to 4:40 PM. The cart gets photographed label by label, and all 31 packages are on the record with shelf locations before the courier's van pulls out. The parcel from unit 908 turns out to have been collected last Wednesday, by a name the resident recognizes, with a signature on file; the question took forty seconds and ended in "oh, right." The weekly sweep flags two boxes past the hold window, and both go back to the carrier as recorded returns. The shelf ends the day shorter than it started, which is the whole game.
Key questions
How long should the front desk hold a package before returning it?
There is no universal rule; the hold window is the building's own policy, and common practice runs 3 to 14 days. What matters more than the number is that the window is written down, displayed where residents see it, and enforced with a recorded return at the end. A stated policy nobody enforces reads as no policy the first time it is challenged.
Is the building responsible for a lost package?
Sometimes; it depends on what the building accepted and what it promised. A desk that signs for parcels takes custody of them, and a building that advertises package service is expected to run one with reasonable care. The operational answer is the record: intake, storage, and pickup proof on every parcel. For where your building's liability actually sits, ask your counsel and your insurer, not a software vendor.
Does the resident get notified when a package arrives?
No. Scaalr's package tracking is a custody record for the desk: what arrived, where it sits, and who took it. It does not send arrival notifications to residents; telling residents a parcel is waiting stays with the building's own routine. The record's job is different: when a resident asks where their package went, the desk answers with a date, a status, and a signature instead of a search.
What happens if the label scan gets something wrong?
The scan pre-fills the form; it does not commit the record. Scaalr reads the label from the photo, fills in the carrier, tracking number, and recipient, and shows a confidence level on the label read itself, and the person at the desk confirms the resident match and corrects any field before saving. The label photo stays attached to the record either way, so the original evidence outlives any typing.
Do we need package lockers, or is a log enough?
They solve different problems. Lockers are storage hardware: secured capacity and self-serve pickup for buildings that want less desk involvement. A log is custody proof: who accepted what, where it sat, and who took it, which is what settles disputes. A staffed desk with a disciplined log already has custody covered, and can add hardware later if capacity, not proof, turns out to be the constraint.