Equipment Checkout Checklist: From Pull Sheet to Check-In

Gear rarely disappears at the event. It disappears in the transitions — between the shelf and the truck, the truck and the venue, the venue and the check-in bench. Each phase below closes one of those gaps. Print it, tape it to the warehouse door, or rebuild it in whatever tool you use. The only rule that matters: the same list travels with the gear from pull to check-in, so every count is against the same source of truth.

Before the pull: verify, don't assume

The most expensive mistakes happen before anything leaves a shelf — pulling against an outdated list, or pulling gear that was never going to work. Five minutes of verification here saves an hour of load-out panic.

Pack and load: count twice, load once

Packing is where counts become real. A case count and a cable count made here are what every later count gets compared against — so make them carefully and write them down where they cannot be lost.

At handoff: make the condition and the count official

Whether the receiver is a client, a venue contact, or your own site lead, the handoff is where custody changes. If the count and condition are not agreed out loud here, every later dispute becomes your word against theirs.

Return check-in: count it the day it lands

A truck that sits unopened overnight is where missing gear stops being findable. Check in against the original checkout list — never a fresh list — the same day the gear returns, while the crew still remembers the job.

After: close the loop or lose the money

Everything above only pays off if someone finishes the paperwork. Missing gear that never becomes a conversation becomes a write-off; damage that never becomes a service ticket becomes a failure on the next job.

Running this without the paper

OpsVue runs this checklist as the actual shape of a job. Gear moves through the same phases — allocate, pull, pack, load, check out, check in, resolve — and units advance by scanning or typing a code, with printable barcode labels for anything you want to scan. Missing is computed, never remembered: what went out minus what came back is the missing list, automatically. Damage flagged at check-in feeds a separate charge pipeline with an explicit bill-or-waive decision on each item, and repairs get their own service records so downtime shows up in availability. Because availability is date-scoped, the conflict check in phase one happens when the quote is built, not when someone reaches for the shelf.

To be clear: the paper version above works, and plenty of good shops run on it. OpsVue is in early access, and the honest pitch is narrow — if your checkouts keep failing at the same step, the software version is this same list with the counting, the missing math, and the follow-up tasks done for you, attached to the job record where the quote and the money already live.