Building a Fireworks Show in FireworkOS

Start with one show record

When a show is created in FireworkOS, the goal is simple: stop re-entering the same information. The show record becomes the operational home for the event — customer, location, date, contacts, timing and the other information the office and field team need to identify the job.

Every later workflow can reference the same show. Instead of asking, “Which spreadsheet is this show in?” the answer becomes, “Open the show.”

Build the product plan against real inventory

A product list is not useful if the product is not actually available. FireworkOS connects show planning to inventory so product can be allocated from the stock the company actually has.

A shell, cake or other item committed to one show is no longer quietly treated as fully available to another show scheduled for the same weekend. Shortages surface while there is still time to solve them.

Allocation also creates the baseline for later reconciliation: what the show was supposed to take, what was loaded, what was returned and what was ultimately expended.

• Allocate specific quantities from known stock.
• See competing reservations across shows on the same weekend.
• Use open partial product before breaking another full case.

Keep the show connected to the people running it

Crew belongs in the show workflow, but not in the Magazine module. FireworkOS keeps crew records separately and uses those records when people are assigned to work. A crew profile can hold roles, qualifications, documents and expiration dates.

The magazine record answers: What product moved? The crew record answers: Who is qualified and assigned? The show ties those operational pieces together without turning one module into a junk drawer.

Move from planning to load preparation

Once the product plan is ready, the show allocation feeds the load and packing workflow so the warehouse team is working from the same product list the office planned. That cuts out one of the most common sources of inventory errors: retyping.

FireworkOS is built so the operational documents come from the show record instead.

Build the transportation packet from the load

The truck should not leave with paperwork that describes a different shipment than the product physically sitting in the vehicle. FireworkOS connects outbound load confirmation to the documents generated for the show, including Bills of Lading and the broader show packet.

The chain is: show plan → allocation → confirmed load → transportation documents. FireworkOS also supports two-person verification for sensitive load actions so one person is not silently responsible for both entering and confirming the same movement.

Give the field team the information they actually need

A show packet is only useful if the person in the field can find the information while standing at the site. FireworkOS is designed mobile-first. The goal is to put relevant show details, documents and field workflow where the person doing the work can reach them from a phone.

Paper can still travel in the truck where required or useful. Digital does not mean paper is forbidden; it means office and field work from the same underlying record.

Close the loop when the show comes back

The show is not complete just because the sky is dark again. Product, partial cases and loose shells may return. FireworkOS uses return and reconciliation to compare the outbound record against what physically comes back: What left? What was used? What returned?

When the numbers agree, the show closes cleanly. When they do not, the variance stays visible until somebody explains it.

The bigger idea

The biggest change FireworkOS makes to show planning is continuity. The same show record follows the job from office to magazine, magazine to truck, truck to field and field back into inventory.

It should make the handoffs boring. The finale can be chaotic. Your operation shouldn’t be.