What Actually Works When You're Running Events at Scale
David Cartisano has been running events long enough to know that most advice you read online is either too vague or written by people who manage Instagram photo ops, not three-day conferences with 800 attendees and a budget that can evaporate if you miss one vendor payment deadline. I've worked with a lot of planners, and Cartisano's approach stands out because it's relentlessly practical. There's no mystique around it. The core of his method starts with what he calls the reverse timeline model. Most planners build schedules forward from the event date, which means they constantly discover they've underestimated how long something takes. Cartisano flips it. He starts with load-out and works backward to the first decision point, then maps every single dependency in between. This catches the stuff that derails events—permits, fire marshal inspections, AV tech that needs 48 hours to test a full rig, the one subcontractor who can't do setup before Thursday. I ran a corporate summit where we'd scheduled vendor load-in for 6 AM. The venue had a contractual window starting at 8 AM, and the catering coordinator hadn't factored in the transit time for three separate food trucks. We lost two hours of prep and the first service was already running late when it started. Cartisano would have built that transit buffer into the reverse timeline on day one. You can see it in every project he's documented.
The Venue Dependency Audit
Before any contract is signed, Cartisano runs what he calls a dependency audit. This isn't a checklist you fill out once. It's a living document that maps every single requirement a venue imposes against every single vendor you need to bring in. Power requirements. Load-bearing floors for staging. Ceiling height restrictions for hanging rigging. Loading dock dimensions for truck access. Most planners check a handful of these. The audit checks all of them and flags conflicts before they become expensive problems. One edge case that comes to mind: we were pulling an outdoor event into a converted warehouse downtown because the original venue had a scheduling conflict. The permit department required a fire suppression inspection that the space hadn't had since it was a textile factory in 1987. That inspection alone added 11 days to our timeline and $4,200 we hadn't budgeted for. If I'd used the dependency audit approach earlier, we'd have caught the occupancy classification issue before committing to the space.
Vendor Negotiation Leverage Points
Cartisano's negotiation strategy hinges on understanding what vendors actually care about beyond the quoted price. Production companies want their name in your marketing materials. Caterers want confirmed headcounts three weeks out so they can order perishables without risk. Photographers want good light and a clear shot list. When you approach each vendor with awareness of their actual pain points, you negotiate differently. He structures contracts with escalation clauses tied to milestone completion—not just the event date. If a vendor delivers AV setup 24 hours late, they absorb a percentage of the cost. If they're early and everything passes inspection, they get a bonus. It sounds aggressive, but it's what keeps people accountable. I've seen planners skip this entirely and then spend the month before the event chasing confirmation emails that go unanswered.
Get the Full Details
Attendance Forecasting That Doesn't Suck
Most event planners estimate attendance by taking last year's number and adding five percent. Cartisano uses a weighted regression model that factors in invitation volume, RSVP response rate over the first seven days, historical no-show percentages for similar events, and whether the date falls near a competing industry conference. The output is usually within three percent of actual attendance. That margin matters when you're deciding whether to book a venue for 400 or 500 people. The model breaks down when you're launching something entirely new with no historical data. In those cases, he defaults to a conservative estimate and builds in a overflow protocol—extra seating blocks, flexible catering orders, and a hold with the venue for capacity increases up to 15 percent. It costs more upfront but prevents the scramble that happens when 80 people show up beyond your projections.
Where This Approach Falls Short
The reverse timeline model and dependency audit require tools and discipline that not every planner has. Cartisano uses a combination of Smartsheet, Procore, and custom scripts that parse venue requirement documents automatically. A solo planner running small events probably doesn't need this infrastructure, and trying to force it into a lightweight workflow usually ends in frustration. For events under 150 people, a well-maintained spreadsheet and a solid relationship with your venue contact will get you 90 percent of the way there without the overhead. Another limitation: this methodology assumes you have at least 90 days from initial planning to event date. Events planned in under 60 days don't survive the dependency audit because there simply isn't time to map every variable. In those situations, Cartisano switches to a triage mode where you identify the three highest-risk dependencies and focus all your energy there. Everything else gets accepted as a calculated gamble.
What to Actually Take Away
The biggest mistake I see planners make is treating Cartisano's framework as something to adopt wholesale. It isn't. Pick the reverse timeline concept and apply it to your next event with a single project. Then add the dependency audit for your biggest vendor. Don't try to implement everything at once. The framework is valuable because it reveals the hidden work that causes most event failures, but the tooling and discipline required mean it works best when you layer it in gradually rather than attempting a full overhaul on short notice. If you want to study his approach directly, he's published several case studies through the International Live Events Association conference proceedings, and his methodology shows up in a few production management textbooks that are available through standard academic channels. The concepts are well-documented if you're willing to read past the surface-level summaries.
