Every producer has said it — probably ten times already today:

"It’s in the crew letter. Didn’t you read it?"

And every crew member has thought:

“Um… sorta? But seriously? Can’t you just tell me?”

It’s frustrating. I get it.

It sucks to put time into a document that literally no one reads.

But here’s the truth:

Your crew letter is long, boring, and often recycled from three shows ago.

It’s packed with too much detail, too little formatting, and almost no consideration for how crew actually take in information — usually at a glance, in the middle of another gig, while juggling five other things.

It’s not that crew doesn’t care.

It’s not that they’re lazy.

And no — they’re not trying to annoy you.

They just don’t have time to dig.

That thing they need to know? It's buried under a novel of copy-pasted jargon.

And by the time they find it, they’ve already texted you.

Twice.

Communication isn’t about blasting info and getting pissed when people don’t read it.

It’s about making sure someone can actually receive it.

If your team is missing things, that’s not a crew problem — that’s a delivery problem.

So what’s the fix?

✅ Keep it short.

✅ Make it scannable.

✅ Send quick updates when things change — not just once at the beginning.

✅ Use tools that meet your crew where they actually are.

That’s where STNDBY comes in.

It doesn’t replace the crew letter —it makes it usable.

STNDBY pulls out what matters, makes it searchable, and keeps everyone on the same page — without another mass email buried under the Wi-Fi code for the wrong hotel.

Because great communication isn’t about yelling louder. It’s about speaking in a way people can actually hear.

So no, sending the letter again won’t fix it.

But you know what will?

👉 A tool that pulls the answer out of the doc for them

👉 That doesn’t require digging, scrolling, or guessing

👉 That respects their time — and yours

That’s why we built STNDBY.

Not to replace your crew letter — but to help people actually read it.