Your crews can now document the condition of the customer's property itself — not just the items.
Property Exceptions, new in Mover Inventory (Mobile QR Inventory), lets the crew record property damage with photos, structured details, and a driver signature at the beginning and end of stage activities, at both origin (Add Items To Inventory) and delivery (Remove Items From Inventory) stages.
A pre-existing scuff on the door or peeling paint on the wall gets captured before work starts; anything that happens during the move gets captured before the crew leaves. Every record syncs across the App, the CMS, and the Customer Portal — giving you timestamped proof when a damage complaint arrives, and a fair, transparent record for your customer. It's part of the default workflow, with an optional setting to make it mandatory.
✨ What's New
- Property Exceptions in the app — available by default at (Add Items to Inventory, origin Stage) and (Remove Items from Inventory, delivery at destination Stage), captured at Begin Stage (before starting stage activities) and End Stage (after completing them).
- Structured damage capture — photos, damaged property (wall, floor, door, elevator, landscaping, and more), area/room, damage type, a note, worker name, and driver initials and signature.
- Three synced sources — crew records in the app, the shipment owner records in the CMS (Admin), and the customer records in the customer portal — each shown under its own tab, grouped by Origin and Destination.
- Email alerts — When a customer adds a property exception in the customer portal, the shipment owner is notified immediately via email with the full details.
- Optional mandatory flow — a Shipment Type setting can require a property exception before the crew can start or complete the stage.
👥 Who This Is For
- Moving company owners and claims handlers — who need timestamped, signed, photographic proof of property condition when a damage complaint comes in.
- Crews and drivers — who can protect themselves by recording pre-existing damage before touching a single item.
- Operations managers and shipment owners — who can log phoned-in reports from the CMS and see every exception from every source in one place.
- Your customers — who get a transparent view of everything recorded, and can report property damage themselves through the portal.
⚙️ How to Configure
Property Exceptions is on by default — it's already in your current workflow. In the app:
- At Origin (Add Items To Inventory) or Delivery (Remove Items From Inventory) stages, the shipment menu shows Property Exception – Begin Stage. When completing the stage, the crew sees Add Property Exception – Stage End before finalizing.
- Tapping it opens the Add Property Exception form: choose the stage timing, add photos, and select the Property Damage, Area/Room, and Damage Type, then add a note, worker name, and the driver's initials and signature, and submit.
- The recorded exception appears as a card with all details and photos, with options to edit or delete — and it syncs to the CMS automatically.
- To make property exceptions mandatory, go to Settings → Shipment Type → Edit Shipment Type → Exception Settings and enable Allow Property Exception. Then select whether an exception is required at the Beginning of Stage, the End of Stage, or both. Crews will be prompted to record an exception at the selected point before they can proceed.
- In the CMS, open View Shipment → Exceptions → Property Exceptions. The Crew tab shows everything recorded in the app, grouped by Origin and Destination with Begin/End Stage badges.
- Something reported by phone? The shipment owner can record it from the Admin tab with + Add Property Exception — the same layout the crew uses, including images, damage details, worker name, and signature.
- Customers see every recorded exception in the customer portal — and can add their own under Exceptions → Property Exceptions → Customer Portal. Their entries appear in the CMS under the Customer tab.
- When a customer submits one, the shipment owner receives a New Property Exception email with the shipment, customer, and damage details — so nothing reported through the portal goes unnoticed.
🔎 Good to Know
- Default workflow, optional enforcement. Property Exceptions is live in the app with no setup; only the mandatory requirement uses the Allow Property Exception setting, and it applies to Origin and Destination Stages.
- Source-labeled and synced. App entries appear under Crew, CMS entries under Admin, and portal entries under Customer — in both the CMS and the customer portal, grouped by Origin and Destination.
- Records lock when the stage completes. Crew-recorded exceptions become read-only once the stage is completed — for the customer and the shipment owner alike. Only exceptions added from the CMS or by the customer remain editable on the CMS side, keeping the crew's field record tamper-proof.
🎉 Available Now
Property Exceptions is live across the Mover Inventory app, CMS, and Customer portal. Walk the property, snap the photos, capture the signature — and every complaint conversation starts from proof, not memory.
