The FireworkOS Show Packet: One Record for the Truck and the Field
A good show packet is boring. That is a compliment. The best show packet answers the obvious operational questions before anyone has to ask them.
Field Operations · 4 min read · Updated August 2026
The crew should not be discovering missing information in a parking lot. The driver should not be calling the office asking where transportation paperwork is. The lead should not be digging through email for the site contact.
Start with the show record
The show already contains the event information, so that record should be the source for the packet. When the packet is generated from the same show the office planned, there is less opportunity for customer names, addresses, times or other details to drift between documents.
The same principle applies to the load: outbound product documentation should come from the confirmed load, not an old planning spreadsheet.
Put transportation documents with the shipment
FireworkOS keeps outbound Bills of Lading and related show documents tied to the show so the office can retrieve the same packet the driver is carrying.
That is useful on show day and even more useful three months later. Search the show. Open the documents. Done.
Give the lead useful field access
Paper still has a place in professional fireworks operations. Connectivity fails. Phones die. Some records need or benefit from a physical copy. FireworkOS is not built on the idea that printing is obsolete. It is built on the idea that paper should not be the only copy of the truth.
The lead can use mobile workflows for current show information and field updates while the truck still carries the paper packet the company uses.
Capture field changes while they are still facts
A lot changes between the yard and firing site. Product can be pulled, a substitution can be made, something may not be used, or a field decision may change what returns.
FireworkOS is designed so field information can be captured from the phone while the person who knows what happened still remembers what happened.
Build the return workflow into the packet
The return trip is part of the show. FireworkOS supports return-document and reconciliation workflows so the crew can record what is coming back and the receiving side has something to reconcile against.
This is especially important with partial cases and loose product. A return should tell inventory what quantity actually came back, not simply “one case.”
Close the show with a usable record
When the operation is finished, the company should be able to open the show and see what was planned, what was loaded, what documents were generated, who was assigned, what came back, what changed and whether there are unresolved exceptions.
A show record that answers those questions is useful operational history. A folder full of PDFs is just storage.
The show packet should follow the job
Office. Magazine. Truck. Field. Return. Reconciliation.
The packet is the field-facing expression of the same show record. Information the crew needs travels with the job, and information the crew creates travels back with it.
Firework OS supports operational recordkeeping and documentation. It does not guarantee compliance or provide legal advice. Your company remains responsible for meeting applicable ATF, DOT, state, and local requirements.
Review the feature detail, compare packages, or book a demo to walk through the workflow with your operation.