Shared inventory sounds simple in theory. In practice, it means two departments both think they have the table lamp — and neither can find it during technical rehearsals. Here’s why the “shared spreadsheet” breaks down, and what actually fixes it.
1. Every department ends up with their own version of the truth
Costumes has a spreadsheet. Props has a Google Doc. Lighting has a running list in someone’s email drafts. Each started with good intentions and has drifted in a different direction ever since. When a designer asks what’s available, the answer depends entirely on who they happen to ask — and whether that person’s list is current.
2. “I thought you had it” is a production problem, not a people problem
When props and lighting both have a reasonable claim to a table lamp, and neither department has visibility into what the other has pulled, things go missing without anyone being careless. The problem isn’t communication — it’s that there’s no single record both departments are looking at. A shared system with real-time status changes that entirely.
3. The inventory that lives in someone’s head
Every organization has that person — the one who knows where the good stuff is stored, what’s actually available, and what got lent to the dance department two years ago. When they graduate, retire, or move on, that knowledge goes with them. A documented, shared inventory isn’t just about convenience — it’s institutional memory that stays with the program regardless of who’s running it.
4. One record, updated in real time, visible to everyone who needs it
The fix isn’t a better spreadsheet — it’s moving to a single live record. When a piece is pulled, it’s marked pulled. When it comes back, it’s marked available. Everyone looking at the same system sees the same thing at the same time. That’s not just a software feature — it’s the difference between a working inventory and a record of intentions.