AIA Convention Exhibitor Guide: Dates, Audience, and Booth Planning

The 2027 event at a glance

Many people still search for the event as the AIA Convention. The current official name is the AIA Conference on Architecture & Design, and the 2027 edition is marketed as AIA27. Use the official name in customer invitations, travel documents, and show materials so people can match your message to the current program.

The four-day conference and the two-day expo are not interchangeable. The current official pages place the AIA27 Expo on May 20 and 21. Do not offer a booth meeting on May 19 or 22 unless the detailed schedule later confirms exhibitor access. Daily expo hours had not been posted when this guide was checked.

Test the exhibit decision before you book

Write down the project question your booth will answer. It could be, “Can this rainscreen detail work on our substrate?” or “Which finish can tolerate the cleaning method in this facility?” A claim such as “innovative building solutions” gives the visitor nothing to check and gives your staff no clear conversation to prepare.

Next, place the answer on the booth. Show the relevant joint, finish, attachment, control screen, or installation step, then place the supporting file beside it. The visitor should be able to see what was tested, which configuration the result covers, and what still needs a project-specific review.

If your U.S. team cannot supply that answer, the matching document, and a person who owns the follow-up, postpone the exhibit. Attend first and listen to the questions architects ask. That choice is cheaper than building a booth around claims your team cannot support after the show.

Choose the visitor and the opening question

AIA describes the expo audience broadly as architects, engineers, contractors, and design professionals. The exhibitor page says they come looking for technical expertise, new products, and project solutions. That is organizer positioning, not a promise that every visitor controls a specification or purchasing decision.

Plan the booth for one primary visitor: an architect or design professional evaluating a real application. Choose an opening question that reveals the condition behind the interest. “What are you detailing?” or “Which performance condition is holding up the selection?” is more useful than “Would you like to hear about our product?”

Record only what the follow-up team can use: firm, project type, project stage, location, application, the visitor’s role, and the unanswered question. A badge scan without this note cannot tell sales whether to send a sample, ask for a drawing, or arrange a technical call.

Show the detail that decides the application

Let the visitor inspect the condition that changes the product’s use. Show the edge when edge treatment affects installation. Expose the joint, fastener, backing, or transition when it affects performance. Use a mockup large enough to reveal the detail when a small sample would hide it.

Label each sample with its product code, finish, and status. Beside it, name the exact report or technical sheet and the configuration that document covers. Keep test wording separate from marketing copy: a result for one thickness, substrate, or fastening method does not automatically apply to the rest of the range.

When a requested condition falls outside the file, say so. Record the condition and route it to the person who can confirm it. Guessing at compliance may keep a booth conversation moving for two minutes, but it can stop the product review as soon as the project team opens the report.

Make comparison easy to verify

Use the same headings across comparable samples. Start with the few fields that affect the application: dimensions, weight, substrate, installation method, finish, maintenance, and the document available for review. Add another field only when it changes the selection.

Mark each value as standard, optional, or subject to project review. Label a prototype as a prototype. If lead time, certification, warranty, or regional availability changes by configuration, print the condition beside the number instead of making staff retract a blanket promise later.

Give booth staff a short “not a fit” sheet. List the exposures, substrates, project locations, or installation conditions that require another review. A direct limitation saves both teams from sending drawings and samples into a review that cannot succeed.

Build the real booth budget before production

The current AIA27 booking page lists standard exhibit space from $48.50 per square foot. Each 100 square feet includes four expo badges. Non-island booths include an eight-foot back drape, three-foot side drape, and an identification sign. Furniture and utilities are not included in the space rental.

Treat the starting rate as space cost, not a finished-booth budget. Keep separate lines for the exhibit structure, graphics, flooring, furniture, electrical service, material handling, labor, shipping, storage, and cleaning. The official page says optional items will appear in the 2027 Exhibitor Service Manual, expected in January 2027; leave those lines provisional until the current rates are available.

A digital marketing package is also required for the AIA27 mobile app and online directory, with packages starting at $500. Use that listing to keep the company name, product category, booth number, and promised documents consistent. Do not treat a directory entry as a substitute for invitations or qualified meeting outreach.

All booths must follow the official booth specifications. AIA asks exhibitors to submit a dimensioned rendering when a design falls outside them. Obtain written approval before production or construction. Otherwise, an overhead element or enclosed display can become a redesign or removal cost.

Assign the conversation and the follow-up

Name the person who will answer product questions and the person who will capture the next step. The technical lead must know the product codes, application limits, available documents, and installation dependencies. The host can receive new visitors and complete the lead note while the technical lead stays in the conversation.

Brief both people on the difference between interest and project fit. Someone collecting ideas for a future material library needs a useful reference and permission-based follow-up. A visitor with a current drawing, condition, and review date needs a named technical owner. Do not force both conversations into the same sales score.

Use one shared lead note. Capture the question in the visitor’s words, what your team showed, what the visitor requested, who owns the response, and the promised date. Labels such as “hot” or “qualified” are not useful unless the note explains the project condition behind them.

Agree on the next review before the visitor leaves

Choose one next action that matches the project stage. Send a sample when the team must judge finish or texture. Request a drawing when the attachment or transition needs review. Schedule a technical call when the requested answer sits outside the booth team’s authority.

Prepare those routes before the expo. Use the same product code on the sample, technical sheet, web page, and follow-up email. Give every file an owner and revision date. Remove superseded files from the booth devices so staff do not send the wrong version.

The follow-up message should restate the visitor’s question, attach or link the promised item, and confirm the next date. A generic “nice to meet you” email leaves the recipient to reconstruct the conversation and does not advance the review.

Decide whether to exhibit or attend first

If the left column describes your position, turn the booth plan into a budget and production brief. If the right column is closer, visit AIA27 and record the details architects inspect, the files they request, and the questions that keep them in a conversation.