The text arrives at 3 PM on a Thursday: "Hi! Can you do a dinner party for 8 tomorrow night?"

Your calendar is clear. You could technically do it. But should you?

Last-minute bookings are one of the most divisive topics among private chefs. Some refuse them entirely. Others see them as easy money. I've spent five years figuring out when to say yes, when to decline, and how to price them so they're worth the chaos.

Want my complete last-minute booking framework?

Get the first chapter of How to Become a Private Chef free—includes rush pricing calculators, decision trees, and ready-to-use client scripts.

Download Free Chapter →

What Actually Counts as "Last-Minute"?

Let's define terms first, because "last-minute" means different things to different chefs:

  • Standard booking: 7+ days advance notice (ideal)
  • Short-notice: 3-7 days (manageable, minor adjustments)
  • Last-minute: 48-72 hours (requires rush protocols)
  • Rush: 24-48 hours (stressful, premium pricing)
  • Emergency: Same-day (rarely worth it)

These aren't arbitrary. They're based on ingredient sourcing logistics. With 7 days, I can order specialty items, compare suppliers, negotiate pricing. With 48 hours, I'm paying retail at whatever shop has stock. With same-day, I'm hoping the supermarket has what I need.

That's why rush fees exist—they're not greed, they're compensation for limited options and higher costs.

The Real Cost of Last-Minute Bookings

Most chefs only see the money: "It's €800 for 4 hours of work, I'll just do it."

But here's what they're missing:

1. Opportunity Cost

When you fill a Friday night with a rushed €800 event, you're blocking a potential €1,200 advance booking that could have come in for that same date. I learned this the hard way—saying yes to low-margin rush jobs kept my calendar too full for high-margin planned events.

Now I ask: "Would I take this booking if I had 4 weeks' notice at this price?" If the answer is no, I either charge more or decline.

2. Mental Load

Last-minute bookings hijack your brain. You're scrambling to source ingredients, adjusting other commitments, mentally running through backup plans. That stress leaks into the event itself—you're tighter, less creative, more likely to make mistakes.

After a particularly chaotic same-day booking (a client's original chef cancelled), I realized I'd spent 6 hours on logistics for a 3-hour event. The pay worked out to €45/hour—less than I made in restaurants.

3. Reputation Risk

When you rush, quality suffers. Maybe you can't get the exact fish you wanted. Maybe you're plating while mentally calculating if you remembered to pack dessert forks. Clients don't know you had 24 hours' notice instead of 2 weeks—they just know dinner wasn't perfect.

One mediocre rushed event will cost you more in lost referrals than you made from the booking.

My Last-Minute Booking Framework

I don't accept or decline rush bookings based on gut feel anymore. I use a decision tree:

Step 1: Check Your Calendar (Honestly)

If the day is already booked: Automatic decline. Never bump or squeeze in events.
If you have plans (personal or professional): Decline unless the fee is genuinely life-changing.
If the calendar is clear: Move to Step 2.

Step 2: Assess the Request

Menu complexity: Can you execute it with 48 hours' notice and available ingredients?
Guest count: Larger groups need more logistics—rush bookings work best for 6-12 guests.
Dietary restrictions: Complex allergies or rare diets (Jain, kosher, medical) need time. Rush bookings should be straightforward.
Client tone: If they're already demanding or dismissive during the inquiry, they'll be worse under time pressure. Decline.

Step 3: Apply Rush Pricing

If you decide to proceed, never charge your normal rate. Here's my pricing structure:

  • 48-72 hours: Base rate + 25% rush fee
  • 24-48 hours: Base rate + 50% rush fee
  • Same day: Base rate × 2, or decline

Example: My standard rate for 8 guests is €85/person = €680 base.
48-hour booking: €680 + €170 (25%) = €850 total
Same-day booking: €680 × 2 = €1,360 total

This isn't gouging—it's accurately pricing the disruption, limited sourcing, and stress. If they balk at the rush fee, offer your next available date at normal pricing. Most people understand.

Step 4: Set Clear Boundaries

Before accepting, I send this message:

"I can accommodate your event on [date], but given the 48-hour timeline, here's what that means:

✅ The menu will be [describe style/dishes] based on what I can source by tomorrow morning.
✅ Minor substitutions may occur if specific ingredients aren't available—I'll confirm the final menu 12 hours before the event.
✅ The rush fee is €[amount], covering expedited sourcing and schedule adjustments.
✅ Final guest count and dietary restrictions must be confirmed by [time] today—no changes after that.

If you'd prefer more menu flexibility and no rush fee, my next available date is [date]. Let me know which works best."

This does three things: 1) Manages expectations upfront, 2) Justifies the rush fee, 3) Offers an alternative so they don't feel trapped.

About 40% of clients take the later date. The ones who proceed are mentally prepared for limitations.

The "Rush Menu" Strategy

Here's a secret that makes last-minute bookings way less stressful: Keep 3-5 tested menus that use commonly available ingredients.

I call these my "rush menus"—dishes I can execute with 48 hours' notice using ingredients I can find at any quality supermarket or my regular suppliers:

  • Mediterranean Seafood: Prawns, sea bass, mussels—available fresh almost always
  • Dry-Aged Beef: My butcher always has ribeye or striploin
  • Italian Comfort: Fresh pasta, risotto, osso buco—pantry-friendly
  • Asian Fusion: My signature style, ingredients I stock at home
  • Plant-Based: Vegetables, grains, legumes—easy to source

When a rush booking comes in, I don't start from scratch. I say: "I have availability and can offer one of these menus. Which style interests you?"

This turns a 3-hour menu design scramble into a 15-minute conversation. Clients appreciate having options, and I'm executing dishes I've cooked 50+ times.

Ready to Build a Profitable Private Chef Business?

Get the complete playbook—pricing strategies, client acquisition, operations systems, and the exact frameworks I use to run a fully booked private chef business in Lisbon.

Get the Book →

By the Inaugural World Cook Champion • MICHELIN Guide Selected Chef

When to Just Say No

Some bookings aren't worth any amount of money. I automatically decline if:

  • The client haggles over the rush fee — They don't value your time
  • They want a complex custom menu — Impossible to source and test
  • Dietary restrictions are extensive or medical — Risk is too high
  • They've already been difficult during inquiry — Will be worse under pressure
  • You're already stressed or tired — You'll do bad work
  • The event is more than 2 hours away — Travel time kills profitability

Early in my career, I said yes to everything. A client wanted a 7-course vegan tasting menu for 12 people—with 36 hours' notice. I pulled it off, but I was so stressed I snapped at my partner that night and barely slept. The client loved it, but I made €62/hour after expenses. Never again.

Now, my rule is: If I feel dread when I see the request, the answer is no—regardless of price.

How to Communicate Rush Fees Without Losing Clients

This is where most chefs stumble. They either apologetically mention the fee (signaling it's negotiable) or bluntly state it (coming across as greedy).

Here's the script I use:

"I have availability and would love to help. For events within 48 hours, there's a rush fee of 50% to cover expedited ingredient sourcing, schedule adjustments, and availability priority. This ensures I can deliver the same quality despite the tight timeline.

Total for [guest count] would be €[total with rush fee]. If you'd prefer to avoid the rush fee, my next available date is [date] at €[normal total]. Which works better for you?"

Key elements:

  • "I have availability and would love to help" — Positive, not punitive
  • "Ensures I can deliver the same quality" — Frames it as protecting their experience
  • Offer an alternative date — Gives them control, not an ultimatum

About 90% of clients accept the rush fee without pushback. The 10% who complain are usually not great clients anyway.

The Hidden Benefit: Client Quality

Here's something I didn't expect: Clients who book last-minute and willingly pay rush fees are often less price-sensitive overall.

Think about it—they're prioritizing convenience and availability over cost. They're also more forgiving of minor imperfections because they understand the constraints.

Some of my best long-term clients started with rush bookings. They saw I could deliver under pressure, appreciated my professionalism, and came back for planned events at normal rates.

The key is never compromising on standards. A rush booking is still a showcase of your work. If you treat it like a throwaway job, it'll hurt your reputation. If you treat it like any other event (just properly compensated), it can lead to great relationships.

My Current Last-Minute Policy

After 5 years of trial and error, here's what I do now:

  • I accept 1-2 rush bookings per month max — Keeps them profitable, not overwhelming
  • I charge 25-50% rush fees, non-negotiable — Clients who pay are the right clients
  • I only offer rush menus, no custom builds — Saves time, ensures quality
  • I set hard boundaries on changes — Guest count/menu locked 12 hours before
  • I track profitability carefully — If a rush booking nets less than €100/hour, I don't do it again

This approach means I'm saying no to most last-minute requests. But the ones I accept are genuinely profitable, low-stress, and don't disrupt my advance bookings.

The Biggest Mistake: Setting a Precedent

If you accept a last-minute booking at your normal rate, you've just trained that client to expect it.

I once accommodated a client's 24-hour request at normal pricing "as a favor." Three months later, they texted me 18 hours before another event expecting the same treatment. When I explained rush fees, they were offended: "You didn't charge me last time!"

I lost the booking and the relationship. Lesson learned: Your pricing policy today sets expectations for every future interaction.

Consistency matters more than occasionally saying yes to keep someone happy.

Final Thought: You're Running a Business, Not a Rescue Service

Poor planning on a client's part does not constitute an emergency on yours.

You're allowed to say no. You're allowed to charge more. You're allowed to have boundaries.

The chefs who build sustainable, profitable private chef businesses are the ones who treat their time as valuable—not the ones who say yes to everything out of fear or scarcity.

Last-minute bookings can be lucrative. But only if you price them correctly, manage them strategically, and decline the ones that aren't worth the chaos.

Want My Complete Private Chef Business System?

Everything I've learned from 5 years building a fully-booked private chef business—pricing, client acquisition, operations, marketing, and scaling strategies.

Includes: Rush booking calculator • Client scripts • Menu templates • Financial projections • Marketing playbook • 90-day launch plan

Get the Guide →

From the Inaugural World Cook Champion • MICHELIN Guide Selected 2024-2026

Frequently Asked Questions

What is considered a last-minute private chef booking?

Industry standard: Less than 72 hours is "last-minute". 48 hours or less is "rush". Same-day is "emergency". Each tier should have different pricing and availability rules.

How much should I charge for a last-minute booking?

48-72 hours: +20-30% rush fee. 24-48 hours: +40-50% rush fee. Same day: +75-100% or flat decline. These fees compensate for schedule disruption, limited ingredient sourcing, and opportunity cost.

Should I accept same-day private chef bookings?

Only if: You have zero other bookings that day, the menu is simple and you have ingredients ready, the client understands limited customization, and they're willing to pay 2x your normal rate. Otherwise, decline and offer next available date.

How do I communicate rush fees without losing the client?

Be transparent and frame it as logistics, not greed: "For events within 48 hours, there's a rush fee of [X]% to cover expedited sourcing, schedule adjustments, and availability priority. This ensures I can deliver the same quality despite the tight timeline."

What if a client gets upset about the rush fee?

Stay calm and professional: "I completely understand. My next available date without a rush fee is [date]. Would that work instead?" If they refuse and demand the rushed date at normal price, politely decline. Clients who don't respect your policies will be difficult throughout the event.

Can last-minute bookings actually be profitable?

Yes, if priced correctly. A last-minute €1,200 event (€800 base + €400 rush fee) can be more profitable than a planned €900 event because you're compensated for the chaos. But don't let them dominate your calendar—they're stressful and prevent advance planning.

Should I prioritize last-minute bookings over advance bookings?

Never. Always honor confirmed advance bookings. Last-minute requests should only fill gaps in your calendar. Moving or compromising an advance booking for a rush job damages your reputation and stresses you out.

How do I make last-minute bookings less stressful?

Keep a "rush menu" ready—4-5 tested menus you can execute with commonly available ingredients. Maintain relationships with 24-hour suppliers. Have backup equipment ready. Document your rush booking process so it's repeatable, not chaotic.

What's the biggest mistake chefs make with last-minute bookings?

Saying yes at normal pricing out of fear or desperation. This sets a bad precedent, attracts problem clients, and burns you out. If you're going to disrupt your life for a rush booking, charge accordingly or decline.