Flag it once. Nothing books it again.
The moment a tech marks something broken — from a scan, from the gig list, from the item itself — every screen in the app that hands out equipment stops offering it, with the reason attached. The note and the photos travel with the item, the repair bill lands on a ledger, and when it's cheaper to replace than fix, the same record prints as a financing request with a signature line.
The broken one goes right back in the case.
Somebody finds the bad DI at 11pm during load-out. It gets set aside, mentioned to one person, and then — because the case has a slot shaped exactly like it — packed anyway. Three weeks later the same box goes out on a corporate show and the same input crackles, this time in front of a client. Nobody was lying to anyone. Nobody wrote it down anywhere the next person packing that case would ever see it.
Meanwhile the money side is worse. You know roughly what you spend on repairs, the way you know roughly what you spend on fuel. When it's finally time to ask for four new wireless channels, there's no record to point at — just a feeling, and a quote you got last Tuesday.
With GigPal PRO: the flag is attached to the asset, not to a person's memory — so it's blocked from every list it could be packed onto, and every dollar spent fixing it lands on a ledger you can print.
From a crackle at load-out to a signed request.
Flag it where it broke, on the device in your hand.
Scan the tag and hit the ⚠ button — repair or replacement, a plain-English note, done. You can also flag from the item editor, or select a batch on the inventory list, or pick the damaged rows straight off a gig's contents and mark them all at once. Every route asks the same two questions and writes the same record, so it doesn't matter which one your tech reaches for first.
Every list that hands out gear stops offering it.
This is the part that actually protects a show. One truthy service flag and the item is unavailable to pack lists, cases, flypacks — and to a scan trying to put it into any of them. The block comes back with a reason rather than a shrug: IN SERVICE, right next to the name. Add a whole case at once and the summary line tells you exactly what it held back, like "MISSING ×4 · IN SERVICE ×1", so you're never guessing why the count came up short.
The queue tells you where the broken things physically are.
SERVICE opens grouped by location, not by problem — because the first question on a repair morning is "where is it," and the answer for a shop with three buildings isn't obvious. Mark any location as a workbench and it pins to the top of the list, with a banner counting what's sitting on it and a one-tap SEND TO WORKBENCH from any record. Flip to BY STATUS when you'd rather see repairs and replacements split. Rows sort most-expensive-first out of the box, so the costliest problem is the one you're looking at.
Clearing it and logging what it cost is one action.
Type the amount and the vendor in the same panel where you clear the flag, then press ✓ BACK IN SERVICE — an unlogged cost still lands, because to the person holding the soldering iron "it's fixed and here's the bill" is one thought, not two. The entry writes to a real ledger with the date, the decision, the tag, the vendor and the note. Reports totals it as TOTAL SPENT, spend for the current year, items still flagged, and value at risk — and hands you the whole thing as a CSV when your bookkeeper asks.
When it's time to buy new, print the argument.
Generate a financing report and every flagged item arrives pre-filled from its own record — decision, the problem note the tech already wrote, the asset's current value as a starting projected cost. Add as many vendor quotes per item as you gathered, untick anything you're not asking for yet, and it prints on your letterhead: numbered items, quote tables, a grand total, and an "Approved by (signature)" line. Print to PDF and it's an email to your bank or your accountant. The draft autosaves as you type — filed under the workspace you're in, never pooled across companies.
The parts that keep it honest.
3 down doesn't mean 50 down
A pool of fifty cables is one row in the database, and a single broken-gear flag on that row would remove all fifty from every gig, case and rent-list calculation in the app. So a pool doesn't take the flag at all — it keeps a count of units down. That rule is enforced in one place the whole app writes through, not at each button, because the same mistake was fixed at five separate buttons before it was moved.
Broken gear stays in its case
Nothing gets yanked out of a case roster because it's flagged — the panel with the bad channel belongs in the video-wall case until the part shows up. Service warns on a case roster; it never blocks or caps. The scan screen prints "⚠ 3 in repair — stays in case" with the repair note, so the crew packs it on top instead of digging for it in a parking lot.
Flagged by a name, at a time
Raising a flag writes a scan-log entry tied to the real login that raised it, and the item shows "flagged by Roe · Aug 11, 2:14 PM" from then on. Clearing a flag deliberately isn't logged as a service event — the record you want is who found the problem, not who closed the ticket.
Crew can flag. That's the point.
The person who finds the fault is usually the least privileged account in the building, so flagging is open to every role while the rest of the item stays manager-write. It goes through a narrow, purpose-built write rather than a full item save — otherwise a crew flag shows on their screen and quietly reverts on the next sync, and the gear ships broken.
Damage photos, on the record
Drop an image on the record or tap the square — on a phone that opens the camera. Photos downscale to about 1000px before upload so a hundred repair shots don't bloat your storage, and any of them opens full-screen. It's the difference between "it arrived like that" and a dated photo, for warranty and for insurance.
A location kind, not a status
Mark any shelf, room or bench in your location tree as a workbench. The service queue pins those groups to the top, a banner counts what's on them, and every record offers a direct move — which also lands in the item's location history, so the trail from "shelf" to "bench" to "back on shelf" is intact.
Moves and money on one timeline
Open a flagged item and the last twenty events read as one list, newest first: every location move interleaved with every repair charge, with vendor and note. You can see that this DI has been to the bench three times this year before you approve a fourth repair on it.
Gear that never comes home gets flagged automatically
Archive a gig with items still scanned out and it asks what happened. Anything you mark missing gets flagged for replacement with a note naming the gig and the date it closed — "Clear this if it turns up." A pool adds the missing count to its units-down instead. Nothing books it in the meantime, and nothing is quietly forgotten either.
- A service record holds
- Repair or replacement, a free-text "what's wrong" note, any number of damage photos, and — for a bulk line — how many units are down. Plus who raised it and when, pulled from the scan log.
- Blocks
- Adding to pack lists, cases and flypacks, and scanning into any of them — each refusal names the reason. Case rosters warn instead of block: gear already in a case rides with it until parts are secured.
- Availability math
- Owned − out − in repair, applied identically on add-to-gig, bulk check-out, setup placement, the conflict radar and demand windows. A shortfall it causes shows its reasoning: "own 42 · 4 on PL-016 · 1 in service".
- The ledger
- Seven columns — date, decision, tag, item, vendor, cost, note — exportable as CSV. Reports tiles show total spent, spend this year, items still flagged, and total value at risk.
- Financing request
- Per item: decision, problem / justification, projected cost, and unlimited vendor quotes with notes. Prints under your company name — never the software's — with a grand total and an approval signature line.
- Won't lose your work
- A typed repair note, cost or vendor prompts before the panel closes, including on Escape and the Android back button. The financing draft saves per workspace, so one company's numbers can never prefill another's request.
Broken gear that can't be packed by accident.
Stop shipping the same broken box.
Bring your inventory in by CSV, flag what you already know is bad, and watch it disappear from next week's pack list.
Get Started → All features →