You have 300 jokes. You can’t find them. That’s not bad luck. That’s a system. Just not a good one.
The folder called “JOKES - NEW (2)” is not a system. Neither is the Notes app, the Google Doc, or the spreadsheet you built and abandoned sometime around your third open mic. You know this already. The question is what you keep telling yourself about it.
Why None of Your Current Tools Work
The problem isn’t that you’re disorganized. The problem is that your tools were designed for people who write things once and walk away. Your material doesn’t do that. Your material is a living, mutating, occasionally feral thing that rewrites itself every time you bring it to a new room.
The Notes app is a capture tool. Great for writing down “accountant at a funeral” at 2am. Useless six months later when you want every bit you’ve ever written about your dad. What you actually get is one long scroll of untagged consciousness, three versions of the airport bit with no timestamps, and zero way to know which one worked. It’s not a filing system. It’s an archaeological dig site, except the artifacts are your ideas and they’re all labeled “thing with the guy.”
Google Docs adds structure, but the wrong kind. A doc doesn’t know that the airline bit and the hotel bit belong to the same thematic cluster, or that both have been riding shotgun in your closer for three months. It can’t tell you the punchline you just rewrote is version seven. It just sits there, holding whatever you typed, hoping you remember where you put it. You won’t.
Spreadsheets are what happens after that. They hold for a while. Then you miss one update, one bit retitled, one column shifted, and the whole thing becomes a monument to a system you almost finished.
What Good Material Management Actually Looks Like
Your material needs three things. They are not the same thing, and treating them like they are is how you end up with 47 pages of raw notes and nothing you can actually grab before you walk onstage.
The bits themselves. A bit is not a sentence in a doc. It’s a living thing. The punchline you wrote six months ago is different from the one you’re doing tonight, which will be different again in a year (if the bit survives, which is not guaranteed). You want every version preserved, not overwritten, so you can see the arc and go back when the new version stops working. Tags, alternates, notes, all of it belongs attached to the bit. Not scattered across separate documents you’ll never find again.
The sets. A set is not a document. It’s an arrangement of bits that already exist. Your club set, your festival set, the corporate-safe version you dust off three times a year and feel weird about afterward, those are configurations of the same material. Not three separate things to maintain. The moment you start maintaining them separately, you’re maintaining three copies of every punchline. Tighten one, and the other two are wrong before you finish typing.
The log. This is the part most people skip, and I get it, logging feels like homework. But right now you’re performing on pure memory and telling yourself the patterns are obvious. They’re not. Every time you perform a bit, you learn something about it: which room it killed, which crowd sat on it, whether the punchline is landing consistently or just sometimes and you only remember the sometimes. Without a record, that information evaporates. With one, you start seeing your material clearly. This bit works in clubs and dies at corporate. This callback only lands after a setup you stopped doing. This is less thrilling than writing new material. It works every single time.
Building the System
Step 1: Give Every Bit a Home in One Place
Pick one place. Commit to it like it owes you money. Every bit needs a title, the current working version, a spot for alternate punchlines and tags, and a way to see its history. Duplicates are the enemy, not because tidiness is a virtue, but because the moment you have two versions, you’ll never fully trust your own material. You’ll be second-guessing word choices at 11pm onstage when you should be thinking about timing.
Step 2: Separate Capture from Storage
Your Notes app or voice memo recorder is for capture. Only capture. That 3am idea, the one that feels like genius and might be nothing, write it there. Then get it out of there. Build a weekly habit of moving raw captures into your main system, fleshed out, properly tagged, given a real title.
Skip this step and you end up with 400 unreviewed voice memos and seventeen notes that say “the thing with the guy.” Those are not ideas. Those are tombs.
Step 3: Build Sets from Your Material Library
Sets should be assembled from bits that already exist, not retyped from scratch every time. If you change a bit, that change should ripple everywhere the bit appears. The manual version of this breaks constantly. You tighten the punchline in the bit card, forget to update the club set doc, forget you also emailed yourself a showcase draft last month, and suddenly you have three versions again. Back to square one, except now you also feel bad about yourself.
Step 4: Log Every Performance
After every show: what you performed, what hit, what bombed, anything worth remembering. Five minutes of notes after a set reveals patterns over months. Which bits work in clubs versus that room last Tuesday where nothing worked and the ceiling was too low. Which opener lands consistently. Which closer only works on weekends. Which bit you’ve been “about to cut” for four months because you keep hoping it’ll come around.
It won’t. The log will tell you that. Kindly.
How Caligari Handles This
Caligari keeps your material in one place and keeps it connected. That’s it. That’s the whole pitch.
Your Cabinet is where every bit lives. Each bit gets its own card. Versions are tracked automatically, you don’t manage any of that, it just happens in the background like a responsible adult. Tags let you find thematic clusters in seconds: every bit about your dad, everything that plays clean, everything under 90 seconds when a booker emails you at 6pm asking for a tight five.
Sets are built from your Cabinet. You pull bits in, watch the runtime update live, reorder until the shape feels right. Change a bit in your Cabinet and it updates everywhere that bit appears. There’s no list of places to remember to update. The list doesn’t exist.
Your Logbook records every show. Log what you performed, note what landed. Over time, the picture gets sharp: this bit has an 80% kill rate across rooms. This one is inconsistent in ways you can now name out loud. This opener has never missed. The Logbook doesn’t tell you what to do with that information. It just makes sure you can’t pretend you didn’t have it.
Joke DNA analysis (on Pro) goes further. It reads your writing patterns and transforms the bit, surfacing where a punchline setup is buried, where the structure is working against you. It does not write the jokes. That part is still yours.
Start by getting everything into one place. One source of truth. Not the best tool, not the most organized system, just one. From there, you can build something real. From “JOKES - NEW (2)” you cannot build anything. That folder is a graveyard with a misleading name.
Your future self, the one about to go on in twelve minutes at a room they’ve never played, will genuinely thank you.
Once your material is organized, the next challenge is building a set that holds together under performance pressure.