The Movers Arrived Without the Customer. Who Authorized Unit Access?

By Jared Mastroianni

• October 18, 2026
• 65
• Business Storage, Guides, Self Storage

Third-party unit access should begin with verified authority, named people and a defined time window. AI-generated editorial image; not documentary evidence.

A frontline authorization workflow for third-party move crews at self-storage facilities

A moving truck arrives at opening. The customer is not with it. The driver knows the customer’s name, unit number and gate code. One crew member holds up a screenshot that appears to say, “They’re good to get my stuff.” The move is scheduled, the crew is on the clock and the lane is starting to back up.

That is not one access decision. It is at least five.

The manager must separate permission to enter the property, proof of who the crew members are, authority from the customer of record, permission to enter a specific unit and authority to remove property or change a lock. A text screenshot, familiar company logo, correct unit number or working gate code may contribute context. None of them, by itself, resolves all five decisions.

The practical response is not to argue at the gate. Stabilize the arrival, protect account information, verify the customer through an approved channel already connected to the account, define the access scope in writing and close the temporary access after the crew leaves. If the required evidence cannot be completed, the move waits.

Put the truck in a waiting state

Keep the vehicle out of the active gate lane while the authorization is reviewed. Direct it to the facility’s approved staging point if one exists. Do not let a growing queue turn urgency into permission, and do not wave the truck through “just to clear the lane.” Once the crew is inside, the facility has created a different control problem.

Tell the crew what is happening in plain language: “I need to verify the customer’s authorization and the people covered by it before I can approve access.” Do not confirm the customer’s phone number, balance, account status, alternate contacts, access history or other account details while doing so.

Record the people present, their company, a vehicle identifier, the claimed customer, the claimed unit and the purpose they state. This is an intake record, not proof that every statement is true. Label it accordingly.

The manager should also check whether a separate restriction already controls the outcome: a delinquency or lien process, a legal hold, an incident scene, a damaged door, an overlock, a deceased-tenant procedure, a prohibited-access flag or another account condition governed by company policy and applicable law. Third-party authorization should not silently override an existing restriction.

Verify from the account outward

Do not rely on a phone number, email address or link supplied by the moving crew as the only route back to the customer. Start with the facility’s approved contact and authentication process for the customer of record. That may be a verified account portal, a validated email address, a known phone workflow or another controlled method defined by the operator. The exact method belongs in company policy.

This distinction matters because knowledge of a unit number or gate code is not the same as authority to direct the facility. Credentials can be forwarded. Messages can be cropped. Names can be copied from paperwork. A manager is not accusing the crew of misconduct by verifying independently; the manager is applying the same process to every third-party arrival.

NIST’s current identity-proofing guidance separates identity resolution, evidence validation and verification, and it emphasizes collecting the minimum information needed for the transaction.[^1] A self-storage manager is not conducting a federal identity-proofing enrollment, and NIST does not set a storage-facility access rule. The useful operating principle is narrower: match the claimed person and authority through a defined process, and do not gather unrelated personal data simply because a dispute feels uncertain.

If the customer cannot be reached or cannot complete the operator’s approved authorization, keep the access state at not approved. “They told us they were coming” is not a reason to improvise a different verification standard. Give the crew a specific next step and, when possible, a time for the next update. Do not promise access at that time; promise a status update.

Make authorization specific enough to operate

“Let the movers in” leaves too much unresolved. A usable authorization record should identify:

• the customer account and exact unit;
• each authorized person, or a defined company crew under the operator’s accepted process;
• the moving company, if applicable;
• the permitted date, start window and expiration;
• the purpose of the visit;
• whether property entry and unit entry are both allowed;
• whether the crew may load property out of the unit;
• whether any lock, key or access device may be handled;
• whether an escort or check-in is required;
• actions that remain prohibited; and
• the reference to the customer verification and authorization record.

Time and scope are controls, not paperwork decoration. An authorization to collect three labeled shelving units this morning is not permission to return tomorrow, enter another unit, remove everything, cut a lock or change the account’s permanent access settings.

Use the company’s approved authorization language and retention practice. State law, rental agreements and lien or access procedures can affect what the facility may accept. This article is an operating framework, not a substitute for the operator’s legal documents or jurisdiction-specific advice.

Do not solve the problem by sharing permanent credentials

A mover should not receive the manager’s master credential or the customer’s persistent gate code as the facility’s workaround. A shared permanent code weakens attribution after the visit and can remain usable beyond the authorized window. It can also obscure whether later entries came from the customer, the crew or someone else who received the code.

Where the installed system and company policy support it, use a facility-approved temporary credential with a defined start, expiration and scope. Otherwise use the operator’s approved staffed or escorted access process. Do not claim that a temporary credential restricts a person to one unit unless the actual system enforces that boundary.

NIST’s authentication guidance treats authenticators as credentials bound to an account and addresses their lifecycle, including loss, compromise and revocation.[^2] Again, that federal digital-identity guidance is not a physical self-storage mandate. Its transferable lesson is that issuance and termination belong to the same control. If the facility creates temporary access, it must also know when that access expires or who revokes it.

NIST’s physical-access control catalog similarly describes authorizations, controlled ingress and egress, access logs and control of keys and combinations.[^3] The catalog governs federal information systems, not private storage operations. It nevertheless offers a useful design check: approval, entry, exit, logging and credential control should form one traceable sequence.

Separate unit entry from lock and property decisions

Even valid authority to enter the property does not automatically authorize a lock cut, cylinder change, key release, inventory decision or removal of goods. Treat those as separate fields in the record.

If the customer’s lock is missing, the key does not work or the crew says it was told to “just cut it,” stop at that boundary. Follow the operator’s specific lock-removal procedure. Record who authorized it, what evidence was accepted, who performed the work and what happened to the removed hardware. Do not let a moving schedule create an undocumented lock action.

The same discipline applies to property. Facility staff should not direct the crew about which belongings belong to whom or certify the contents or condition of the unit unless an established process specifically requires it. The authorization can define that removal is permitted without turning the manager into a witness to ownership, inventory or value.

A fully fictional arrival

At fictional Silver Marsh Storage, a truck arrives at 8:40 a.m. without the customer. The company, people, unit, records, times and outcome in this example are entirely invented.

The driver knows unit B-214 and shows a screenshot containing the customer’s first name. The opening manager directs the truck to a marked waiting space and records the claimed company, two crew-member names and the truck identifier. She does not confirm the account balance, phone number or access history, and she does not test the gate code the driver volunteers.

Using the contact workflow already associated with the fictional account, the manager reaches the customer. The customer completes the operator’s approved authorization naming both crew members, the company, unit B-214, an 8:30 a.m.–11:30 a.m. window and permission to enter and remove packed household goods. The record does not authorize a lock cut, account change, return visit or entry to any other unit.

The facility’s fictional access system supports a time-bounded visitor credential, so the manager issues one under the approved process and records its identifier. This is an invented system capability, not a product or deployment claim. The crew checks in, enters during the authorized window and exits at 10:56 a.m. The credential is confirmed expired, the access-log reference is attached and a completion notice is sent through the validated customer channel. The record does not claim what property was removed or whether it was complete or undamaged.

Close the visit while the evidence is fresh

Departure is part of the workflow. Confirm the crew has exited, close or revoke the temporary credential, record the exit time and attach the relevant access-log reference. If a physical key, fob or visitor badge was issued, reconcile it under the facility procedure. Notify the customer through the validated address or account channel when the process calls for it.

Record exceptions instead of hiding them in notes: one authorized person never arrived, a different truck entered, the crew left property in a corridor, the unit would not secure, the credential remained active or the visit exceeded its window. Assign an owner and next update time for every unresolved item.

The companion Third-Party Unit Access Release Card keeps the decision sequence visible: arrival, staging, account-based verification, named authorization, scoped access, credential lifecycle, entry, exit and closeout. It also keeps the claim boundary clear. The facility can prove what it authorized and what its systems recorded without claiming who owned the property, what the crew removed or what happened beyond the evidence.

The truck at the gate is not the problem to solve. The problem is whether the facility can produce a controlled, time-bounded and reviewable chain from the customer of record to the people asking to enter. If that chain is incomplete, the correct operational state is still wait.