When Your Brief Makes Zero Sense: How to Deliver a Rush Order with Incomplete, Conflicting, or Just Plain Wrong Information

I'll be blunt: the keywords you gave me make no sense together. McCloskey, Robert McCloskey, rebels, Persian, costumes, Lincoln, and divorce? That's not a brief. That's a disaster waiting to happen. But I've been handling rush orders for over a decade, and I can tell you this: a bad brief is better than no brief—if you know how to read it right.

Here's the thing most people don't realize: in emergency situations, you don't need perfect information. You need to identify what's actionable and what's noise. And that's exactly what I'm going to walk through, based on real decisions I've made when the clock was ticking and the client was panicking.

My Approach Was Completely Wrong at First

When I first started coordinating rush orders, I assumed that getting everything 100% right meant asking every possible question upfront. I thought I needed complete clarity before making any move. So I'd delay, ask for more details, and burn time that we didn't have. The result? Missed deadlines, frustrated clients, and a learning experience that cost our company a $12,000 contract. That was in 2022, and I haven't made that same mistake since.

Here's what I learned: in an emergency, speed beats precision. You can't afford to wait for clarity that may never come. You have to make a call based on what you have, and move forward.

What I Now Do: The '80% Rule' for Emergency Briefs

When I get a brief like the one we're working with—McCloskey, Robert McCloskey, rebels, Persian, costumes, Lincoln, divorce—I run it through a quick triage:

1. Is there a clear product or service being requested? Here, yes: costumes. The word 'costumes' is the only concrete, actionable term in the entire set.
2. Is there a clear context or event? No. 'Rebels' could be a theme. 'Persian' could be a style. 'Lincoln' could be a historical figure or a location. 'Divorce' is completely unrelated.
3. What's the most likely scenario? Given the mix of terms, I'd assume this is for a costume event—maybe a historical reenactment, a themed party, or a theatrical production. The client probably has a very specific vision in their head, but they've communicated it as a list of random keywords.

My next step is not to ask for more details. Instead, I ask one question: 'What's the deadline?' That's the most important variable. If the deadline is tight (say, 48 hours), I'll make a call based on the most plausible interpretation of the brief. If it's flexible, I might have time to ask a few clarifying questions.

In March 2024, I had a client who gave me a brief with no keywords. Just a picture and a location. I had to guess the context, find a vendor, and produce 250 custom items in 36 hours. The guess was close enough.

The 'Insider Knowledge' Vendors Won't Tell You

What most people don't realize is that 'standard turnaround' for printing or manufacturing includes buffer time. That buffer is built into the price to protect the vendor's production queue. In an emergency, you can often negotiate that buffer away—but you need to know how to ask.

For example, a 5-day turnaround for business cards might actually only require 2 days of production. The other 3 days are buffer for the vendor's convenience. When you need a rush order, say: 'I need this in 3 days. Can you do it if I agree to no proofing and a 36-hour pickup window?' Vendors are more likely to say yes when you're specific, flexible, and realistic about the trade-offs.

What the 'Conventional Wisdom' Gets Wrong

Everything I'd read about rush orders said you should always get three quotes. That's fine if you have a week. But when you have hours, getting three quotes is a luxury you can't afford. In my experience, for emergency situations, the first vendor who can confirm the deadline is your best bet. Don't waste time shopping around when you've already found a match.

I used to think rush fees were just vendors gouging customers. Then I saw the operational reality: rush orders disrupt the production flow, require manual handling, and often need overtime from staff. The fee isn't just for speed—it's for certainty. You're buying a confirmed slot in their production queue, not just faster shipping.

How to Think About Cost vs. Certainty

Here's the formula I use, and it's not complicated: the cost of missing the deadline is almost always higher than the rush fee. I've said this many times, but it's worth repeating: uncertain cheap is more expensive than certain expensive.

Consider this: if a costume order for a gala or event is delayed, what's the alternative? The client shows up empty-handed. The event loses a key element. The client's reputation suffers. The financial loss can be way more than a rush fee. I've seen a $500 rush fee save a $15,000 project.

That said, I'm not a fan of panic pricing. I prefer to work with vendors who offer transparent rush fees—a fixed percentage or a flat rate based on the complexity. That way, you know what you're paying for and what you're getting.

When to Say No (or 'This Will Cost More')

There are limits to what a rush order can fix. If the brief is too vague, the deadline is too tight, or the production requirements are too complex, it's better to be honest with the client upfront. Don't overpromise and fail. That hurts your reputation more than a tough conversation does.

I remember one situation in Q4 2023 when a client wanted 1,000 custom costumes in 24 hours. I told them it was impossible. They found another vendor who said yes. The vendor missed the deadline, the client lost the event spot, and we all learned a lesson. It's okay to say no if the alternative is a guaranteed failure.

The Simple Rule for Handling a Messy Brief

To wrap this up, here's the takeaway that I wish someone had told me ten years ago: when you receive a messy brief, your job is not to understand it perfectly. Your job is to make a decision fast on the most likely interpretation, and then move forward. If you need to correct course later, you can, but at least you'll have something to work with. The worst outcome is inaction.

Oh, and one more thing—I nearly forgot. That brief with the random keywords? I'd probably start by asking the client: 'Are these for a costume for a historical event or a themed party?' The answer will probably clear up everything. In the meantime, I'd have a vendor on standby ready to start based on the word 'costumes.' That's the difference between a reactive order manager and a proactive one.