Rigging and Staging Safety Software Problems: The 7 That Fail on a Get In, and How to Avoid Them

Why does the asset register keep getting descoped for calculation features?

The biggest scope failure in this category is letting the project become about load calculation. Calculation is the visible, technical, satisfying part. It produces a drawing and a number, it demos well, and everyone in the room understands what it does. So the requirements drift toward modelling forces, and the serial level asset register gets pushed into phase two, where it dies.

That is backwards, and it is backwards because Vectorworks Braceworks already calculates loads competently inside a design environment. What no drawing package can do is confirm the assumptions the calculation rests on: that this specific motor is inside its inspection interval, that the shackle in the bag is the rated one and not a similar looking item from another job, that the truss section with a repair record is not in a position the repair does not permit, and that the crew holding it are certified for the work.

The fix is to make the register the first release and defend it. A rig is safe because conforming equipment was used, not because a drawing said the forces worked. Write the scope as three things: an asset register at serial number level with per item inspection due dates, defect capture that quarantines instantly, and a competent person sign off tied to the gear actually used. If a proposal opens with calculation features and treats the register as supporting detail, the priorities are the wrong way round and the project will not survive its first incident.

What goes wrong when you load several thousand serial numbers into the register?

This is the part that stalls projects, and it stalls them in week three rather than week thirty. Getting a touring fleet into a register means physically handling every motor, truss section, shackle, spanset and steel, reading a serial that may be stamped, etched, faded or missing, matching it to a certificate in a folder, and tagging it with something that will survive a truck and a wet load out.

Three specific problems appear every time. Certificates exist for items whose serials cannot be read, so you have paperwork with no asset and assets with no paperwork. Consumable items such as spansets and small steels were bought in batches and never individually identified, so there is no serial to record. And the warehouse is only empty enough to do this work during a narrow window between tours, which is also when everybody is on holiday.

The approach that works is to sequence by risk rather than by shelf. Load motors, chain, structural components and anything with a statutory examination regime first, because those carry the exposure. Batch identify consumables with a new tagging scheme applied at first use rather than retrospectively. Book warehouse days in advance as a project workstream with named people, run it in parallel with development rather than after it, and accept that a small percentage of the fleet will end up retired because its provenance cannot be established. Pricing that data load at zero is the clearest sign a developer has not done this before.

Why do design, scheduling and sub hire integrations break after launch?

They break because the register is finally telling the truth and the neighbouring systems are not. Your scheduling or job costing system thinks in kit lists and dry hire lines. The design workflow thinks in positions and forces. The register thinks in serial numbers. Those three views are reconciled by a warehouse manager today, and once the register becomes the gate, every disagreement becomes an argument at load out.

Sub hire is the sharpest edge. Gear comes in from another company for a specific run, sits on your rig, and has to carry its own certification, its own inspection regime and its own quarantine state, without contaminating your fleet history. Gear also goes out to other companies and comes back with damage nobody logged. Most builds model an item as owned, and then somebody hires in forty motors for a stadium show.

Two fixes. Model ownership as an attribute from day one, with owned, hired in and hired out as states, so a sub hired motor gets a temporary asset record carrying supplier certification and is blocked exactly like your own if the paperwork lapses. And make the job the shared object between systems rather than trying to synchronise item lists. Scheduling owns the job, the register owns what physically went out against it, and the reconciliation runs at pick and at return with the differences shown to a person rather than resolved silently.

What happens when the competent person sign off is not actually completed?

You end up worse off than having no system at all, because the absence of a record now looks like a failure of process rather than the absence of a process. That is the trap. A sign off feature that is technically present and practically skipped creates an expectation of evidence you cannot meet, and an investigator will ask why this build has no sign off when the previous eleven do.

Sign offs get skipped for one reason: the form is too long for the moment it has to be completed in. That moment is the end of a build, in the dark, under time pressure, by somebody already doing three other things, on a phone with poor signal in a concrete building. A twelve field form with mandatory dropdowns will not be filled in, and no amount of policy will change that.

Design for the two minute constraint and treat it as a hard requirement. The rig, the venue and the date are pre populated because the system already knows the job. Equipment used is confirmed from the pick rather than typed. The rigger adds photographs of key points and, if anything differs from the design, records a deviation with a reason. Everything else is optional. The build must also work offline and sync later, because the roof of an arena is where signal goes to die. If a developer cannot demonstrate that flow on a phone in under two minutes, the feature is decorative.

Should you build custom or configure what you already own?

Keep Vectorworks Braceworks and do not attempt to replace it. Load calculation inside a design environment is a different discipline from fleet compliance, it is well solved, and rebuilding it consumes the budget that should be going into the register. Any developer proposing to reproduce it is proposing to spend your money on the part you already have.

Stay with a spreadsheet register and disciplined pre use checks if you are a small production company with one warehouse, one truck of gear, and equipment that rarely leaves your control. At that size a well maintained spreadsheet is proportionate and defensible, and the honest answer is that your risk is concentrated in crew practice rather than in record keeping. Money spent on training and on a second competent person will do more than software.

Build when the fleet is large enough that nobody can hold its state in their head, when gear crosses borders and therefore crosses statutory examination regimes, when you sub hire in and out and need to know whose gear is on your rig, or when a client or an insurer has asked for evidence and it took you a week to produce it. The register plus quarantine plus sign off is the core. Venue records, crew competency, environmental logging and design integration are all genuinely useful and all of them are phase two.

How do hidden costs get into the quote?

Five places, and all of them are visible before you sign if you ask.

• The data load. Several thousand items, warehouse days, tagging hardware and a percentage of the fleet whose provenance cannot be established. This is the most underestimated line in the category.
• Tagging method. Tags on rigging gear take abuse from steel, weather and load outs. Choosing wrong means retagging the fleet twice, which is a physical cost nobody quoted.
• Multi country operation. Each jurisdiction brings its own examination regime and often its own language requirement, and each one is a separate rule set rather than a setting.
• Offline capability. Working on a phone with no signal in an arena roof means local storage, conflict resolution and sync, which is real engineering rather than a checkbox.
• Sub hire. Modelling hired in and hired out gear properly is a data model decision, and retrofitting it after launch touches everything.

The one that surprises people is user training across a freelance crew. Your riggers are not employees, they change between tours, and every one of them needs to be able to complete a sign off correctly the first time they see the app. That constraint should shape the interface, and it belongs in the estimate.

What separates a build that works from one that fails here?

The builds that work block things. An item past its inspection due date cannot be picked, and going out anyway requires an explicit override that records who authorised it and why. A defect raised from a phone quarantines the serial number immediately, and the quarantine travels with the item in the system rather than on a piece of tape that falls off in transit. Everything else in the product is reporting. Those two behaviours are the product.

The builds that fail are the ones where the register is a mirror of reality rather than the gate to it. If the warehouse can pick gear without the system, the system will be out of date within a month and every downstream feature inherits that. Decide early that the pick happens in the software and hold that line even when the truck is loading late, because the night everybody wants to bypass it is exactly the night the record will matter.

When you are choosing a developer, ask how an out of date motor gets stopped, and reject any answer that involves a report somebody checks. Ask them to demonstrate a sign off on a phone, timed, with no signal. Ask how they will handle the initial load of several thousand serial numbered items and whether warehouse days are in their plan. Ask how sub hired gear is modelled. Then settle ownership of the code, the infrastructure and the inspection data in writing before kickoff, because equipment life histories and competent person sign offs may be requested many years after the show, and they need to remain yours for the whole retention period.