Attendees Are Not Staff. They Don’t Need the Details.

There is a funny thing that happens with longtime attendees.

At some point, we forget they’re attendees.

They’ve been coming for years. They know the venue. They recognize the staff. They know which reception everyone goes to, where registration usually is, and probably have opinions about the coffee.

So we start talking to them differently.

“It’s basically the same as last year.”

“You know how this works.”

“They moved that room again.”

“Check-in works differently this year.”

I’ve done this too.

“It’s basically the same as last year” is a perfectly useful sentence if you spent six months working on last year’s event.

Less useful if you attended it.

Because longtime attendees may know your event extremely well.

They know how attending it works.

That’s not the same thing.

Familiar Doesn’t Mean Informed

Someone who has attended your event for ten years may know its personality better than the person you hired three months ago.

They know when people start arriving.

They know which sessions tend to fill up.

They know where everyone gathers afterward.

They know that the five-minute walk between two buildings is absolutely not five minutes once 800 people are trying to make it at the same time.

What they don’t know is what happened in your planning meetings.

They weren’t on the call when the registration process changed.

They don’t know that the hotel contract created a different arrival procedure this year.

They don’t know why one platform was replaced, one entrance moved, or one part of the schedule had to change.

And they shouldn’t need to.

The attendee experience is the finished product.

All the machinery required to make it happen belongs behind it.

We Accidentally Make Attendees Honorary Employees

Event teams have their own language.

We use it all day, every day, so eventually it stops sounding like event-industry language to us.

“Go see housing.”

“That’s a registration issue.”

“Check with production.”

“Talk to ops.”

Perfectly normal sentences backstage.

Slightly different when you’re standing in front of an attendee who just wants to know where to go.

The labels change from event to event.

The problem doesn’t.

Who is housing?

Where is production?

And why does the attendee need to understand your organizational chart to get an answer?

Sometimes we do something even more tempting: we explain the problem.

Their badge isn’t printing, so we tell them the system isn’t syncing.

Their reservation is missing, so we explain what happened with the rooming list.

The information in the app is wrong, so we tell them which vendor is responsible for updating it.

All of that may be true.

None of it gets them their badge, finds their reservation, or tells them where lunch is.

Sometimes the Best Service Is a Boring Answer

Events go sideways.

Not necessarily in spectacular, everyone-run-for-cover ways.

Usually in tiny ways.

A name is missing.

A room changes.

A shuttle is late.

A QR code refuses to behave.

Someone has two confirmations for two different things, neither of which appears to exist when they arrive.

Behind the scenes, five people may be trying to figure out what happened.

There may be texts flying, radios going off, someone calling the venue, someone else logging into a platform, and another person trying to remember who has access to the thing everyone suddenly needs access to.

The attendee does not need the live play-by-play.

They need:

“We’ve got it. Here’s what happens next.”

That isn’t about hiding a problem.

If a change affects someone, tell them.

If there is a delay, be clear about it.

If you made a mistake, own it.

But there is a difference between transparency and transferring the problem to the attendee.

They need the information that helps them move forward.

They don’t need the entire story of how the sausage got made, dropped on the floor, picked back up, and eventually turned into lunch.

There Is One Place Where Longtime Attendees May Know More Than You Do

Here’s the twist.

The attendee you’ve been treating like an honorary staff member actually is an expert.

Just not in running your event.

They’re an expert in attending it.

And if they’ve been coming for years, they have something your team may not have: a long memory of what the experience has felt like from the other side.

They remember when registration was easier.

They know that an email everyone on the team thinks is perfectly clear never quite answers the question attendees actually have.

They remember the year transportation worked beautifully and the year everyone stood outside wondering whether the shuttle was ever coming.

They know which little tradition matters far more to attendees than anyone realized.

They notice when something that used to take one step now takes four.

That perspective is incredibly valuable.

The trick is not confusing it with operational knowledge.

Your longtime attendees don't need to know why you changed registration platforms.

But if several of them tell you registration has become harder, listen.

They don't need to understand how your communications calendar works.

But if they keep saying they can never find the email with the information they need, listen.

They don't need a seat in the production meeting.

But they have a very good seat from which to tell you what your production decisions actually feel like.

Keep the Roles Clear

The goal isn't to explain less for the sake of explaining less.

It's to explain the right things.

Tell attendees what they need to know.

Make the next step obvious.

Give context when context helps.

Fix what you can without requiring them to understand why it broke.

And remember that familiarity with your event does not turn someone into a member of the team.

Even if they’ve attended for ten years.

Even if everybody knows their name.

Even if they already know where the good coffee is.

Your longtime attendees may know things about your event that you don't.

Ask them.

Just don't make them run it.