Build the attendee-origin worksheet first
Open a spreadsheet and give every confirmed delegate one row: country, city, nearest airport, whether a direct flight to Greece exists, and whether they need a visa or a Schengen transit. Don't summarise yet. The raw list is the evidence.
Then sort into four bands. Band one flies direct to Athens. Band two flies direct to Thessaloniki. Band three needs a connection through a hub, Istanbul, Vienna or Frankfurt for example. Band four is domestic Greek travel. Count each band, convert to percentages, and write the percentages at the top of the sheet. That's your attendee map, and it's the first thing a venue sales team should see.
This is where planning meetings often go wrong. Someone says "Athens is easier for everyone" and the room nods. The sheet usually disagrees. If your list is heavy on Western Europe, check direct services into both cities for your actual travel dates. If it leans toward the Balkans or Turkey, test whether Thessaloniki shortens journeys. For long-haul origins, check where the connections really land before anyone assumes.
Score flight access, hotel supply and programme length
Once the bands exist, score each city on the three variables that actually move. Weight them by what your delegates complain about, not by what looks tidy in a proposal.
| Variable | What to score | How to weigh it |
|---|---|---|
| Flight access | Direct routes to each city from your top ten origin airports, plus connection depth | Heaviest for international lists; lighter for Greek-only lists |
| Hotel supply | Room count near the venue at your target star level, and whether one hotel can take the block | Heaviest for large delegations and short programmes |
| Programme length | Half-day, full-day, multi-day, or conference plus social programme | Multi-day events tolerate a less central venue; single-day events don't |
Flight access feeds straight into cost. Every connection adds a hotel night at the front and a tired delegate at the opening session. Score it honestly and the city choice often makes itself.
Hotel supply works the same way. A city with deep supply near the venue lets you negotiate from strength. A city with thin supply near the venue means the block and the event space have to be solved together, which is why we keep the room block and the event-space quote together rather than in two conversations. When you send a request for proposal, include your attendee map and your room-block estimate in the same email.
Programme length is the quiet decider. A one-day conference wants delegates landing the night before and leaving the same evening, so airport proximity to the venue matters more than the city centre. A three-day conference with a gala dinner and a half-day excursion can absorb a venue thirty minutes from the terminal because the schedule has slack built in. Match the city to the shape of the week, not to the postcard.

What each city does well for conference groups
The official Athens convention bureau presents historic, contemporary, coastal and open-air event settings, according to This is Athens Convention Bureau, and that range is the honest summary of Athens. You can run plenary sessions in a hotel ballroom, a reception in a museum courtyard and a closing dinner by the sea without leaving Attica. For a delegation that wants one city to do everything, that breadth is hard to beat.
Thessaloniki is a different proposition. Its centre is compact enough that delegates can often walk between hotel, venue and dinner, which changes the feel of the event from logistics to hosting. For groups arriving from the Balkans, the Black Sea region and Turkey, it can shorten journeys and reduce the connection risk that eats into programme time. For a smaller, two-day, conversation-heavy conference, that compactness is often the deciding factor. Our guide to choosing a Thessaloniki conference base around the programme unpacks how the venue decision follows the schedule there.
One concession. Athens isn't automatically the safe default, and treating it that way is how conferences end up with delegates scattered across a large city and a bus schedule nobody enjoys. Thessaloniki isn't automatically the cheaper or friendlier option either, and you should check early whether a single venue there can run as many large concurrent sessions as you need under one roof. Neither city is right in the abstract. The attendee map decides.

Check the venue against your attendee map
Before you sign anything, put the shortlisted venues back through the worksheet. A venue that scores well on paper can still fail on the day.
- Ask how delegates arrive from the nearest airport, and at what times of day the last practical transfer runs.
- Ask how many delegates can be accommodated in one hotel block, and what happens to overflow.
- Ask whether the plenary room, the breakout rooms and the exhibition space sit in one building or several, and add the walking time to your schedule.
- Ask what access the venue provides for delegates with reduced mobility, in writing.
- Ask for a clause covering your room block and event-space quote in the same contract, so one can't be repriced without the other.
- Ask what documentation the venue needs from you: delegate list, insurance certificate, deposit schedule, signed floor plan.
- Confirm current permit and tax requirements with the competent authority before you commit.
If part of the programme is a working session rather than a conference, the same logic applies with different weights, and our team retreats in Greece page covers the charter and venue combinations that groups use when the format is smaller and more residential.
When the answer is neither city centre
The worksheet sometimes points away from both centres. If your delegates land at Athens airport and your programme is short, a venue in the airport corridor can beat a central Athens hotel on transfer time alone, which is why we keep a separate overview of conferences in Spata, Attica. The same logic applies around Thessaloniki, where the trade-off between airport and centre is worth testing in the same way.
Run the sheet twice, once with each city winning on flight access, and see which version produces fewer red rows. That comparison, not a preference for one city, is your recommendation to the board.
Send us your delegate headcount, your dates and your draft programme. We'll pass them to venues in both cities that match the shape of your event, and you can compare answers against your own worksheet.
Planning questions
How do I know whether Athens or Thessaloniki suits my delegate list?
Build the attendee-origin worksheet before shortlisting venues. Count delegates by destination airport and direct-flight availability to each city, then sort them into direct, connecting and domestic bands. The city with fewer connecting journeys usually wins, and the percentages tell you by how much.
Does programme length change which city I should choose?
Yes, and more than most planners expect. A single-day conference favours a venue close to the arriving airport, while a multi-day programme with social elements can absorb a venue further from the terminal. Match the city to the shape of the week.
What should go into the proposal request to both cities?
Send the attendee map, your room-block estimate and the draft programme in one request, and ask the venue to quote the block and the event space together. Keeping both numbers in the same document stops one being repriced after you commit.
