Manage Facility Operations And Security

---
name: manage-facility-operations-and-security
description: Run a self-storage facility's operations — choose the operating model (staffed vs hybrid vs remote-unmanned + kiosk) against the site's volume and labor market, set the staffing, harden security and access control (gate/keypad, individual door alarms, cameras with retention, lighting, overlock discipline), keep climate control, maintenance, and curb appeal to standard, protect the move-in/move-out flow (agreement, protection-plan and autopay offer, gate-code provisioning, overlock-release), and standardize a multi-site portfolio with an SOP, PMS-config parity, a district-manager cadence, and a per-site scorecard. Reach for this when the user asks "staffed or remote/kiosk?", "how do I tighten security after a break-in?", "our move-in process is leaky", or "how do I run five sites to one standard?". Used by `self-storage-operations-lead` (primary).
---

# Skill: manage-facility-operations-and-security

> **Invoked by:** `self-storage-operations-lead` (primary). Also consulted by `storage-revenue-and-occupancy-specialist` for the move-in capture point (protection-plan/autopay) and the operational overlock the lien process depends on.
>
> **When to invoke:** "Staffed vs hybrid vs remote-unmanned + kiosk?"; "tighten security / access control after a break-in"; "our move-in/move-out flow is leaky"; "run five facilities to one standard"; any facility-operations, staffing, security, maintenance, or multi-site question.
>
> **Output:** the operating-model recommendation + staffing + a security/access posture with a prioritized remediation list + a maintenance/curb-appeal read + the move-in/out flow integrity + (for a portfolio) a multi-site standard and per-site scorecard.

## Procedure

1. **Name the operations sub-branch first.** Operating-model/staffing, security/access, maintenance/curb-appeal, move-in/out flow, or multi-site consistency — traverse [`../../knowledge/self-storage-operations-decision-tree.md`](../../knowledge/self-storage-operations-decision-tree.md) before prescribing.
2. **Choose the operating model deliberately.** Staffed vs hybrid vs remote-unmanned + kiosk sets the **labor line — the largest controllable operating cost** — and the access-control, call-center, and security requirements. Weigh the site's volume and the local labor market; don't default to "hire a manager." Remote/kiosk requires solid access control, cameras, and an inbound funnel.
3. **Build security as a system, not a camera.** Confirm all of: **gate/keypad access control**, **individual door alarms**, **cameras with adequate coverage and retention** (and someone who reviews them), **lighting**, and **overlock discipline** (including lien overlocks). A single camera, or cameras nobody monitors, is theater — produce a prioritized remediation list for the gaps.
4. **Hold maintenance and curb appeal to standard.** Climate control (where offered) working, grounds and units clean, and the **first 30 feet** — signage, gate, office, lighting, cleanliness — to standard, because curb appeal sets the street-rate ceiling and the review score. Track the maintenance backlog with owners.
5. **Protect the move-in / move-out flow.** The rental agreement, the **tenant-insurance/protection-plan offer**, **autopay enrolment**, gate-code provisioning, and the move-out/overlock-release are one flow — a break is lost recurring revenue (protection plan), higher delinquency (no autopay), or a compliance gap. The *economics* of protection-plan/autopay route to the revenue specialist; the *flow integrity* is owned here.
6. **Standardize the portfolio (multi-site).** For more than one site: a common **SOP**, **PMS-config parity** (rates, fees, autopay, access all configured the same way), a **district-manager cadence**, a maintenance/curb-appeal checklist, and a **per-site scorecard** (occupancy, security exceptions, maintenance backlog, move-in capture rate).
7. **Name the seams.** Pricing/ECRI/occupancy-economics/lien-economics/ancillary → the revenue specialist; lease/asset → commercial-real-estate; residential → property-management; generic dispatch → field-service-management.

## Worked example

> User: "We had a unit broken into overnight. What do I fix, and should I keep paying a full-time manager for a site this size?"

- **Sub-branch:** security/access + operating-model.
- **Security remediation (prioritized):** (1) verify gate/keypad access logs and reset codes; (2) confirm **individual door alarms** exist and are armed — the break-in suggests they don't; (3) audit **camera coverage + retention** and confirm someone reviews footage; (4) fix **lighting** at the breached row; (5) tighten **overlock discipline**. A camera alone didn't prevent this — the system did not.
- **Operating model:** for a lower-volume site, model **remote-unmanned + kiosk** (smart access + cameras + call center) against the full-time manager's fully-loaded cost — the security upgrades (access control + alarms + monitored cameras) are also what *enable* the remote model, so the two decisions reinforce.
- **Move-in flow:** confirm autopay + protection-plan capture aren't being skipped (route the attach-rate economics to the revenue specialist).
- **Seam:** the insurance-claim economics and any lien overlock route to the revenue specialist; the physical remediation is owned here.

## Guardrails

- Security is a **system** (access control + door alarms + monitored cameras + lighting + overlock), never a single camera — flag any "we have cameras" as incomplete.
- Labor is the largest controllable cost — always weigh staffed vs hybrid vs remote-kiosk; don't default to a manager.
- Curb appeal is a revenue lever (street-rate ceiling + reviews), not cosmetics.
- The move-in flow must always include the protection-plan and autopay offer — skipping it is lost recurring revenue and higher delinquency (economics → revenue specialist).
- For a portfolio, standardize on an SOP + PMS-config parity + a per-site scorecard — not five bespoke operations.
- Volatile claims (PMS features, access-control/camera vendor capabilities) carry a **retrieval date** — re-verify before a client commitment.