Rigging, Staging and Temporary Structure Safety Software: Why a Rig That Is Built and Struck Every Night Cannot Live in a Construction Safety System

Why rigging safety records are the only defence you have after a failure

An overhead rig is the most consequential thing in a live event. Motors, trusses, shackles, steels, spansets and the structure they hang from sit above an audience, get loaded and unloaded, travel in a truck, and are assembled by a different local crew in a different building every day. When something fails, the investigation asks four questions. Was the equipment within its inspection regime. Was the load calculation done and by whom. Was the venue point capacity respected. Did a competent person sign off the build before it was flown.

In most touring and staging businesses the answers exist, but they exist across a certification folder in the warehouse, a set of load calculations in a design file, a venue technical specification PDF, and a head rigger's memory. Assembling them after an incident takes days and produces gaps. The gaps are what the insurer and the lawyers work on.

The buyer here is a head of technical production or a safety lead at a staging contractor or production company, and the honest framing is that this is an asset compliance and sign off system that happens to be about rigging, not a design tool.

Problem 1: design software calculates loads, it does not manage the fleet

Vectorworks Braceworks is genuinely good at what it does. It sits inside a design environment and calculates loads on a rigging system so a designer can see whether a hang works and where the forces go. That is one half of the problem and it is the half that gets the attention, because it produces a drawing and a number.

The other half is everything the calculation assumes. That the specific motor with that serial number is within its inspection interval. That the shackle in the bag is rated for what the design assumes and has not been swapped for a similar looking one from another job. That the truss section with a repair record is not being used in a position the repair does not permit. That the crew hanging it hold the competency the job requires. A design file assumes conforming equipment. A fleet of touring gear does not automatically conform, and nothing in a drawing package tracks that.

What a custom build does: an asset register at serial number level covering motors, chain, trusses, shackles, spansets, steels, ground support components and structures, each with its certification, inspection interval, defect history and current location. The interval is not a global setting, because statutory examination regimes for lifting equipment differ by country and by equipment class, and a touring fleet crosses those boundaries constantly. Every item carries its own next due date, and an item that is out of date cannot be picked for a job without an explicit override that names who authorised it.

Problem 2: the venue is a constraint and you learn it from a PDF

Every venue has point capacities, structural limits, permitted attachment methods and house rules, and they arrive as a technical specification PDF of variable quality and age. The head rigger reads it, does the mental arithmetic against the tour hang, and either it works, or it works with modifications, or the venue's own rigging house has to be involved. That knowledge is regenerated in every city and lost every time.

What a custom build does: a venue record holding point capacities, structural constraints, house requirements and, crucially, the history of what your company has actually hung there before and what had to change. The second time you play that room, the rigger starts from what happened last time rather than from the PDF. Over a touring season this is one of the more valuable things the system accumulates, and it costs almost nothing to capture if you make it a byproduct of the sign off rather than a separate task.

Problem 3: sign off is a signature on paper, on a stage, in the dark

The competent person sign off is the control that matters most and is documented worst. It typically happens at the end of a build, under time pressure, on a clipboard or on nothing at all, by someone who is also doing three other things. Then the strike happens overnight, the paperwork goes in a flight case, and the next build starts.

What a custom build does: sign off on a phone against the specific rig, at the specific venue, on the specific date, with the equipment actually used recorded against it. Photographs of key points attached. Any deviation from the design recorded as a deviation with a reason. It has to be achievable in under two minutes or it will not happen, and that constraint should drive the whole interface design. The output is that for every show you can produce, in seconds, the rig, the gear by serial number, the certification status of each item on that date, the calculation used and the person who signed it. That is the record that ends an investigation quickly instead of extending it.

Problem 4: defects, quarantine and the item that goes back in the truck

A steel gets a nick. A motor sounds wrong. A truss takes a knock in transit. On a good day that item is tagged and pulled. On a bad day it goes back in the case because the truck is loading and nobody wants to be the person who delays the departure, and it gets used in the next city by someone who was not there.

What a custom build does: a defect raised from a phone immediately quarantines the item in the register, so it cannot be picked, and the quarantine travels with the item rather than living on a piece of tape that falls off. Repairs and post repair inspections are recorded against the serial number, building a life history per item. That history is also what tells you when a category of gear is failing early, which is a purchasing decision nobody currently has the data to make.

Outdoor structures need one more thing: a wind management plan is only as good as the record of readings and decisions taken against it. Capture the readings, the thresholds, the action taken and who took it. A show stop or a load out decision on a temporary demountable structure is exactly the decision that gets examined afterwards, and a logged reading with a named decision maker is a completely different position from a recollection.

What this costs and how long it takes

A first release, meaning the serial level asset register with certification intervals and due dates, mobile pre use and defect capture with quarantine, job kitting so a rig knows which items went out on it, and competent person sign off, runs $60,000 to $150,000 and ships in 12 to 18 weeks. A full platform adding venue records with point capacities and hang history, crew competency records tied to job requirements, integration with your design and calculation workflow, wind and environmental logging, repair and inspection scheduling, and client facing compliance reporting runs $180,000 to $400,000 phased over 6 to 12 months.

What pushes cost up in this category specifically: the initial data load, because getting several thousand items into a register with correct serials and current certification dates is a warehouse exercise measured in weeks and is the single most underestimated part of the project. Scanning hardware choices, since tags on rigging gear take abuse and the tagging method has to survive a truck and a wet load out. Multi country operation, which multiplies inspection regimes and language requirements. And any integration with design and calculation tooling, which is worth doing but should follow the register rather than lead it.

Build versus buy, and when buying is the right call

Buy, or rather keep using what you have, if you are a small production company with one warehouse and gear that rarely leaves your control. A carefully maintained register and disciplined pre use checks are proportionate. And keep Vectorworks Braceworks for what it is good at, because a custom build should not attempt to replace load calculation inside a design environment. Those are different disciplines and different software.

Build when the fleet is large enough that nobody can hold its state in their head, when gear crosses borders and therefore inspection regimes, when you sub hire in and out and need to know whose gear is on your rig, or when a client or insurer has asked for evidence and you needed a week to produce it. Our position is that the register plus quarantine plus sign off is the core, and everything else is optional. If a proposal starts with calculation features and treats the asset register as a supporting detail, the priorities are backwards.

How to choose a developer for rigging and staging safety software

Ask them how an out of date motor gets prevented from going out on a job. If the answer is a report that someone checks, it will fail on the day the truck is loading late. It has to block the pick and require a named override.

Ask how the sign off works physically. A competent person on a dark stage at the end of a build will not fill in a form with twelve fields. Two minutes on a phone with the rig pre populated, photographs and a deviation note is the target, and a developer who has not thought about that has not been on a get in.

Ask how they will handle the initial data load of several thousand serial numbered items. If they treat it as your problem and price it at zero, the project will stall in week three. It needs a plan, a tagging method that survives transit, and warehouse time booked in advance.

Ask who owns the code, the infrastructure and the inspection data, in writing before kickoff. Equipment life histories and sign off records are your evidence in an investigation and may be needed many years after the show. At Digital Heroes the client owns the repository and the data from the first commit.