Build the rig once. Pull it once.
A Setup is the bill of materials for a rig you build over and over — 45 panels, 50 data cables, 24 sandbags, plus the spec drawing and the power one-line. Drop it on a gig and it goes and gets real units off your shelves, skipping anything in service, flagged missing, or already promised to a show on the same dates. Whatever it can't fill becomes a rent-or-buy line with the reason attached. Then the PULL sheet walks the building in one pass and gathers the whole show.
The same rig, re-remembered every time.
You've built that wall forty times. Nobody has ever written down what it takes. So somebody counts panels off a photo, somebody else guesses at sandbags, and the data cable comes up eleven short at 6am on a Saturday — which is the first moment anybody finds out, because "we own plenty" was true right up until the other crew took forty of them to a corporate on the same weekend.
Then comes the gathering. Two people wander the warehouse with a printed gig list that's sorted alphabetically, walking past Bay 4 three separate times, arguing about whether the mic case was already loaded.
With GigPal PRO: the rig is written down once, applying it claims actual units and names anything it can't fill, and gathering it is one top-to-bottom pass through the building with a running count.
From guessing at the build to a ticked-off pull sheet.
Write the rig down as a bill of materials.
Name it — "45-Panel Ground Stack Wall" — and start adding lines from three sources: CASES, RACKS & KITS, or ITEMS. Add a whole road case and its contents land as lines in one tap; add the same case twice and the quantities sum instead of duplicating. Lines are generic on purpose. A like-item line says "45 LED panels" and any 45 matching units can fill it; a bulk line points at one pool and carries a count. As you type quantities the app shows what you actually own next to each line, and turns the number orange the moment you ask for more than that — own 18 — 6 will flag as a shortage, said at the desk instead of on the dock.
Nest builds inside builds.
A setup can reference another setup, or a wire package, instead of restating its contents. ＋ NEST A BUILD drops in a reference line with a multiplier: one loom, or four. At apply time a compiler expands every reference recursively into a flat parts list before anything touches inventory — and two branches that both want SDI-50 get summed into one line, so you get one shortage row to deal with rather than two half-rows that don't add up. Reuse of the same package on two branches is honoured (it really does need double the gear); a genuine loop is cut and reported. The editor tells you about a cycle or a deleted reference when you hit save, not six weeks later on a gig.
Drop it on a gig — it goes and gets the gear.
One tap on a gig and every line resolves against live inventory. It claims specific units by tag, and it deliberately refuses four kinds of gear: anything in service, anything your last audit flagged missing, anything hard-wired inside a flypack, and anything already committed to another gig whose dates overlap this one. Short lines land on that gig's rent-or-buy list carrying the arithmetic — own 42 · 4 on Fall Gala · 1 in service — so procurement starts from real numbers. Need two walls? Set the multiplier to ×2 rather than tapping twice.
Change the rig, push it to every show that uses it.
Setups copy onto a gig when applied, which means editing one doesn't reach shows that already have it. APPLY TO GIGS is how you push the change out, and it's one control with three positions. ADD ONLY is additive and is the safe default. MATCH SOURCE also trims gigs back to the setup's current definition — but skips any line somebody hand-adjusted on their own gig since the last apply, and tells you how many it left alone. REMOVE ALL takes back everything this setup placed, which is the undo. Filter the gig list by name, venue or category, select all thirty at once, and it applies them one at a time so the second gig can see what the first just claimed.
Walk the warehouse once and gather it.
PULL resolves every line on the gig to where it physically lives, then sorts the whole sheet into the walk order your crew arranged on the LOCATIONS tab — depth-first through the building, so it reads top to bottom as one pass with no backtracking. Anything riding in a case collapses into a single "grab whole case" row at the case's shelf; loose items and bulk pulls list at theirs. Tick a row by tapping it, or just point the scanner at the barcode. Scan an item that's inside a case and it ticks the case row it belongs to. The counter at the top runs 9/23 all the way to green, and every device on the gig sees the same sheet at the same time.
The parts that keep it honest.
Applying twice is safe
Units already on the gig count toward a line's need, so a second apply fills the gaps and stops. Nobody has to remember whether the wall was already added — and a rig that grew by three panels since last month can be pushed out without every show quietly becoming a 90-panel wall.
It won't book gear that isn't really free
In service, flagged missing by your last audit, hard-wired inside a flypack, or committed to a gig whose dates overlap — all four are skipped, and each one shows up by name in the shortage's reason line. A setup can't quietly pull from a case of broken panels.
It won't hand you three half-packages
When units are interchangeable by name, it prefers ones from a package that already has a foothold on this gig — so once a mic kit's receiver is taken, the rest of that kit follows instead of a receiver from kit 02 and a mic from kit 03. It only reorders equally valid choices; the counts and the shortages come out identical either way.
A rented line stays exactly where you left it
Re-applying recomputes need and have from scratch, but a shortage you already routed to a rental house, marked rented, or marked bought keeps its status, its note and its vendor. A change to the setup doesn't undo gear you already paid for. Lines that turned out fine — you bought more, the competing gig let go — drop off automatically.
MATCH SOURCE leaves your changes alone
It compares each line against what the setup itself last left there. Raise a quantity from 10 to 15 on one specific gig because that room needs it, and MATCH SOURCE skips that line and reports it as skipped rather than trimming you back to 10. It also only ever touches gear credited to this exact setup — never a hand-added item, never another setup's.
One button undoes the whole push
Pushed the wrong rig onto 21 events? The result screen has a single button that re-runs the same gig list through REMOVE ALL. Underneath it, a full org restore point is captured before any apply runs, labelled with the setup name and the gig count — so there's a net under the net.
Pulling records who, and when
Ticking a row stamps the crew member's name and a timestamp on it, flips the item's shelf flag so the warehouse view stops claiming it's on the shelf, and writes a pull entry into the scan history. Untick it and the flag comes back. Progress is saved on the gig itself, so a second phone joining the walk sees exactly what's already gathered.
The gun stays live for the whole pass
The scanner listener never tears down mid-sheet, so a crew moving at pace doesn't lose every other read. Scan something packed in a case and it resolves to that case's row. Scan a cable pool that's split across two boxes and it ticks whichever box is still unpulled — one trigger pull can't close out both. Anything not on this gig gets told so by name.
- A setup line is
- A like-item group (any unique unit sharing a name), a bulk pool (one tag with a quantity), a cable requirement (type plus length, e.g. "12× SDI 50ft"), or a reference to another build with its own multiplier.
- Setups carry
- A name, crew notes (rigging notes, truck order, gotchas), the gear lines, attached wiring builds, and spec drawings / data & power plans — drawings, PDFs, spreadsheets, CAD files, or a pasted link. The plans copy onto every gig the setup lands on, deduped so re-applying never stacks them up.
- Nesting limits
- Eight levels deep, with a cap on total expansion. Loops are detected and cut with the path named; reusing one package on two branches is allowed and correctly doubles the gear. Zeroed nested lines stay zero instead of being resurrected as one unit.
- Cable lines
- Allocated in a separate exclusive pass after everything else, from a pool snapshotted once and decremented as each line claims — so two lines can never both count the same physical coil. Length-specific requirements claim before length-agnostic ones.
- The PULL sheet counts
- One row per road case that's actually holding something for this gig, plus one row per loose unique item or bulk pull. Order comes from the location tree you arranged; anything with no location set sinks to the bottom in its own group with a note telling you where to fix it.
- Who can edit
- Setups are org standards, so only Admins create, edit or delete them — enforced in the database, not just hidden in the interface. Leads see the builds and their plans read-only. Anyone on the gig can run its PULL sheet.
The standard rig, standard every time.
Write down your most-repeated rig.
Pick the build you've done forty times, add its lines from your cases and inventory, and drop it on the next gig on the calendar.
Get Started → All features →