# Trade show booth staffing: 12 rep-minutes per qualified meeting vs 18 — cut or keep?

Lars Bergstrom · October 31, 2026

> Allocate 12 rep-minutes per qualified meeting when pre-show qualified share is at least 60%, or 18 only if unqualified booth arrivals exceed about 40% of total traffic.

| Takeaway | Detail |
| --- | --- |
| Allocate 12 rep-minutes per qualified meeting when qualified share is at least 60%. | Qualified share equals pre-booked meetings divided by total substantive conversations, measured before each show. |
| Allocate 18 rep-minutes per qualified meeting when qualified share falls below 60%. | The 60% cutoff comes from the pre-show qualified-share measurement rule. |
| Keep the 18-rep-minute allocation only if unqualified traffic exceeds about 40% of booth arrivals. | Queue-absorption measurement must show unqualified traffic above ~40% of booth arrivals. |
| Treat 12 vs 18 rep-minutes as a throughput constraint to verify, not a benchmark to copy. | The decision applies to 2026 trade show booth staffing. |

This guide shows how to verify booth staffing as a throughput constraint using pre-show qualified-share measurements.

It states when to allocate 12 or 18 rep-minutes per qualified meeting and the ~40% unqualified-traffic condition for 2026 shows.

![Trade show booth staffing](https://static.mm-ais.com/article-images-ai/trade-show-booth-staffing-12-rep-minutes-ai-546ebdd6.jpg)

## Rep-Minutes as a Throughput Constraint

For the purpose of booth staffing, this section alone applies the throughput/response-time distinction to booth staffing as a queuing problem. As defined by TechTarget, 'What Is Throughput' (2025), throughput is how many units a system processes per unit of time, while response time is how long a single request takes to complete. Translated to a booth, throughput is qualified meetings per rep-day, and response time is how long a qualified visitor waits before a rep is free. These are not interchangeable levers: time spent on one conversation can affect qualification for that conversation, but it can also directly lengthen the wait for the next qualified visitor in line.

The printer analogy from Estuary's latency-vs-throughput primer maps directly to this floor. A fast office printer may take a few seconds to warm up (latency), but then prints at high throughput, while a small home printer might start immediately but at lower throughput. At a booth, a rep "warming up" on an unqualified conversation is a form of latency cost, not a gain in throughput. The rep is occupied, but not producing a qualified meeting, and during that occupied time, no qualified request is being processed. The check here is to track rep availability against qualified arrivals, not total conversations alone.

This queuing view shifts the question from "how much time should be given" to "how much time can be given without breaking the queue". Before committing to any rep-minute allocation, measure the qualified-share of booth arrivals by dividing pre-booked meetings by total substantive conversations. A high qualified-share means the system has fewer unqualified requests pulling reps into latency, so more of each rep's time can go towards processing qualified meetings. A low qualified-share means unqualified traffic creates more of that latency, and the queue of qualified visitors will grow, making response time the binding constraint even if the booth appears busy.

That distinction matters because a framework is not a staffing answer. Throughput accounting can tell you to compare return per constraint-hour with cost per constraint-hour; it cannot tell you how many minutes a rep should spend with a qualified prospect at a 2026 show. The number has to come from your own queue and conversion data, not from a source that never measured a booth.

| Source | Contributes | Does not provide |
| --- | --- | --- |
| TechTarget, Estuary, Obkio | Throughput definitions and measurement discipline | Exhibit-staffing figures |
| Cloudwards (Theory of Constraints 2026) | Return-per-constraint-hour vs. cost-per-constraint-hour ratio logic | A validated 12- or 18-minute allocation |

Cloudwards' Theory of Constraints discussion contributes the ratio logic, not a staffing figure: return per factory hour versus cost per factory hour. In this context, a rep-hour is the constraint unit, so the test is whether additional minutes per qualified meeting improve throughput enough to justify their cost. That test is arithmetic on observed show data, not a published ratio.

Because no external benchmark exists, the only defensible input is your own qualified-share measurement: pre-booked meetings divided by total substantive conversations. The 12/18 split and the roughly 40% unqualified-traffic trigger are decision rules to validate against that measurement, not standards to quote.

What this evidence does not establish is any universal staffing level, any validated default allocation, or any cost rate. Those are method or cost questions handled elsewhere; this section's narrower claim is that the evidence supports measuring the constraint, not copying a number. If a vendor or blog presents 12 or 18 as an industry norm, ask for the underlying booth measurement; absent that, treat it as an unsourced planning assumption.

![Rep-Minutes as a Throughput Constraint — Trade show booth staffing](https://static.mm-ais.com/article-images-ai/trade-show-booth-staffing-12-rep-minutes-ai-e951c1f8.jpg)

## Options Compared: 12 vs 15 vs 18

The twelve-minute allocation is best suited for a booth where most arrivals are pre-qualified. In that case, the time can be directed toward moving qualified conversations forward without pulling capacity to broad screening. The check to make is not the clock alone, but the downstream signal: if reps are forced to truncate qualified deep conversations, that tends to show up as shortened demos and lower close rates. This is a fit for a known pipeline, not a general starting point.

The eighteen-minute allocation can be justified only when unqualified traffic is high enough that disqualification must happen at the front of the conversation. The discipline here is strict: the extra time must be spent separating fit from non-fit, not extending a pitch. The tradeoff is purely a throughput tradeoff by time allocation, so serving fewer visitors is the expected cost of that screening. Without that front-loaded disqualification, the added minutes do not correct the queue problem and only consume capacity.

With no published staffing benchmark to copy, the only defensible starting position under uncertainty is the fifteen-minute allocation. This section alone presents the explicit allocation table below, with the fifteen-minute default stated as the winner under uncertainty because it leaves room to absorb either direction without committing to the full failure mode of the extremes before measurement exists:

| Allocation | Use case | Primary failure mode |
| --- | --- | --- |
| 12 minutes | High qualified share | Cutting off qualified deep conversations |
| 15 minutes | Uncertain qualified share (default) | Not optimized for either extreme |
| 18 minutes | Low qualified share | Fewer visitors served due to front-loaded screening |

Before locking into either extreme for a 2026 show, the practical check is to track the qualified-share of booth arrivals against the option chosen, and to judge the choice by queue behavior, not by habit. If the measured share moves away from the condition that justified the allocation, the switch should be made to the option that matches the new share, with the fifteen-minute default acting as the holding position until that measurement is stable enough to commit.

![Options Compared: 12 vs 15 vs 18 — Trade show booth staffing](https://static.mm-ais.com/article-images-pixabay/trade-show-booth-staffing-12-rep-minutes-e3c5a604.jpg)

## Costs: Rep-Hours Are the Constraint

As the only calculation introduced in this section, the cost of being wrong can be measured by method arithmetic, not by a copied benchmark. Take a 3-rep booth × 6 floor hours = 1,080 rep-minutes/day. At 18 rep-minutes per meeting, that yields 60 meeting-slots. At 12 rep-minutes per meeting, that yields 90 meeting-slots. The difference is exactly 30 meeting-slots from the same fixed rep-hours, with no change to the floor time itself.

The cost of choosing 18 when 12 suffices is opportunity cost. If even 6 of those incremental 30 slots would have been qualified buyers, the booth traded 6 qualified meetings for 180 spare minutes. Those 180 minutes do not create more floor hours, they simply go unused while qualified demand that could have fit at 12 was turned away by the larger allocation. The trade-off is not about being generous with time, but about how many qualified conversations the fixed rep-minutes can actually process.

The cost of choosing 12 when 18 was needed runs in the opposite direction. Rushing qualified conversations to fit 12 rep-minutes can force a loss of technical detail. By method, that can require a re-demo post-show, roughly doubling the effective rep-minutes per meeting from 18 to 36 for those specific deals. On the same 1,080 rep-minutes, doubling the effective minutes for even a handful of qualified meetings pulls capacity away from new qualified conversations at a much steeper rate than leaving spare minutes would. In that case, the "saved" minutes are not saved at all, they are repaid with interest outside of the booth.

These are explicit checks, not sourced rates. The error is not equal: one direction wastes unused capacity, the other inflates effective minutes. With rep-hours fixed for the day, the decision should not be based on which allocation feels more thorough, but on which of these two costs becomes unavoidable once the qualified-share of booth arrivals is measured.
![Costs: Rep-Hours Are the Constraint — Trade show booth staffing](https://static.mm-ais.com/article-images-pixabay/trade-show-booth-staffing-12-rep-minutes-28c5bfe0.jpg)

## What the Evidence Does Not Establish

The 12/18 allocation is a conditional throughput check, not a staffing benchmark to copy. It assumes booth arrivals are mixed enough that rep-minutes can be budgeted per qualified meeting and that the queue can absorb unqualified traffic without changing the conversation itself.

Hero-traffic shows break that assumption for a bounded window. When a keynote dump floods the booth with unqualified traffic for 90 minutes, the queue constraint breaks entirely: the 12/18 rule still governs each individual conversation, but arrival rate, not meeting length, becomes the binding limit. Neither allocation assumes a triage gate, so add one—badge-scan plus a 60-second qualifier—before the rep-minute clock starts.

Demo-heavy products break the rule arithmetically rather than operationally. If a qualified meeting inherently requires 20 or more minutes, 12 rep-minutes is impossible and 18 may still be short; the decision variable shifts from minutes per meeting to reps per queue. Size the queue by available reps and meeting slots, not by the 12/18 minute budget.

| Scenario | Does the 12/18 rule break? | What still wins | Required adjustment |
| --- | --- | --- | --- |
| Hero-traffic dump for 90 minutes | Yes: queue constraint | Per-conversation 12/18 logic | Badge-scan plus 60-second qualifier before timing |
| Demo-heavy product with 20+ minute meetings | Yes: arithmetic | Qualified-share trigger | Size by reps per queue, not minutes per meeting |
| Mixed arrivals, qualified share at or above 60% | No | 12 rep-minutes | Qualified-share measurement only |
| Mixed arrivals, qualified share below 60% | No | 18 rep-minutes | Qualified-share measurement only |

Use the table as a pre-show gate. If either break condition is expected, do not treat 12 or 18 as the answer; treat it as the conversation-level default after triage or rep sizing is fixed.

The evidence does not establish a universal benchmark because it does not cover arrival shocks or product-demo length. Where those variables are unknown, measure them before the show rather than importing 12 or 18 from another booth.

![What the Evidence Does Not Establish — Trade show booth staffing](https://static.mm-ais.com/article-images-pixabay/trade-show-booth-staffing-12-rep-minutes-ae44795a.jpg)

## Booth Math With Checkpoints

For a three-rep booth, six floor hours create 1,080 rep-minutes (3 reps × 6 hours × 60 minutes). Twenty qualified meetings at 18 minutes use 360 rep-minutes, leaving 720 rep-minutes for unqualified traffic and queue absorption. The daily target is at least 20 qualified meetings, and the entrance qualifier takes 90 seconds before any rep-minute is spent on a meeting.

Checkpoint 1, hours 0–3: tally 84 arrivals, 22 substantive conversations, and 11 pre-booked meetings. By the rule's own definition, qualified share is pre-booked meetings divided by total substantive conversations: 11 ÷ 22 = 50%. Because 50% is below the 60% qualified-share threshold, commit to the 18-minute allocation and front-load disqualification through the 90-second qualifier. Eleven pre-booked meetings at 18 minutes would use 198 rep-minutes.

Checkpoint 2, hour 4: five qualified meetings are complete, with a mean conversation length of 16.5 minutes and zero queue overflow. Those five meetings used 82.5 rep-minutes (5 × 16.5), while the same five meetings at the 18-minute allocation would have reserved 90 rep-minutes. The 18-minute allocation is therefore not yet binding; keep it only if the qualifier continues to absorb unqualified traffic.

Checkpoint 3, end of day: reconcile completed qualified meetings against the 1,080 rep-minute budget and the at-least-20-meeting target. For example, 20 completed meetings at 18 minutes would consume 360 of the 1,080 rep-minutes. If the 18-minute allocation would have required more rep-minutes than the budget allows, record that result and use the 12-minute allocation for the next comparable show.

| Copyable tally sheet | Recorded value |
| --- | --- |
| Reps on floor | 3 |
| Floor hours per day | 6 |
| Rep-minutes per day | 1,080 |
| Entrance qualifier seconds | 90 |
| Target qualified meetings per day | ≥20 |
| Checkpoint 1 arrivals | 84 |
| Checkpoint 1 substantive conversations | 22 |
| Checkpoint 1 pre-booked / qualified | 11 |
| Checkpoint 1 qualified share | 13% |
| Checkpoint 2 qualified meetings complete | 5 |
| Checkpoint 2 mean minutes | 16.5 |
| Checkpoint 2 queue overflow | 0 |
| Allocation decision (12 or 18) | 18 |

Decision rule: keep the 18-minute allocation for the remainder of this show only while checkpoint data keep qualified share below 60% and no queue overflow occurs; otherwise plan the 12-minute allocation for the next comparable show. Record the checkpoint values in the tally sheet before changing any allocation.

![Booth Math With Checkpoints — Trade show booth staffing](https://static.mm-ais.com/article-images-pixabay/trade-show-booth-staffing-12-rep-minutes-4a417c2c.jpg)

## Worked Example: Run the Numbers

Illustration only: a four-person booth team at a three-day 2026 show records 120 substantive conversations, 60 of them pre-booked meetings and 60 walk-up or otherwise unqualified conversations. That is 40 substantive conversations and 20 pre-booked meetings per day. The party is four reps; the scenario is one show, not a multi-show average, and all figures below are arithmetic from these stated inputs.

Qualified share = 60 pre-booked meetings ÷ 120 substantive conversations = 0.50, or 50%. Unqualified share = 60 ÷ 120 = 50%. Because 50% is below the 60% qualified-share threshold, this example uses 18 rep-minutes per qualified meeting.

| Metric | Value |
| --- | --- |
| Substantive conversations | 120 |
| Pre-booked meetings | 60 |
| Unqualified conversations | 60 |
| Qualified share | 50% |
| Unqualified share | 50% |
| Allocation used | 18 rep-minutes |
| Qualified-meeting minutes at 18 | 1,080 |
| Same meetings at 12 | 720 |
| Difference | 360 |
| Break-even pre-booked count | 72 |

At 18 minutes, 60 qualified meetings consume 1,080 rep-minutes (60 × 18). The same 60 meetings at 12 minutes would consume 720 rep-minutes (60 × 12), a difference of 360 rep-minutes. The break-even trigger for this 120-conversation example is 72 pre-booked meetings: 72 ÷ 120 = 60%. At 71 or fewer pre-booked meetings, use 18; at 72 or more, use 12.

Arithmetic check: 60 + 60 = 120; 60 ÷ 120 = 0.50; 60 × 18 = 1,080; 60 × 12 = 720; 1,080 − 720 = 360; 72 ÷ 120 = 0.60.

For this illustration, the winner is 18 rep-minutes per qualified meeting, because qualified share is 50% and unqualified traffic is 50%, above the ~40% level. Retain 18 only if queue-absorption measurement shows that unqualified traffic is consuming the added minutes; if it does not, revert to 12. The 360 rep-minutes are the incremental cost of that choice in this example.

## Decision Rules: If/Then for Cut or Keep

The decision is a three-branch if/then test applied to two on-site measurements: qualified share (pre-booked meetings divided by total substantive conversations) and mean minutes per qualified meeting. State the rules once, then apply them in order; do not blend the day-one mid-morning sample with later traffic.

| Condition measured on site | Action |
| --- | --- |
| Qualified share is at least 60% by mid-morning day 1 | Cut to 12 rep-minutes per qualified meeting and reassign the surplus rep-hour to same-day post-show follow-up. |
| Qualified share is below 40% | Keep 18 rep-minutes, then audit the extra six minutes. If less than half go to disqualification, treat it as a rep-discipline issue and coach before re-staffing. |
| Mean minutes per qualified meeting exceeds 15 | Treat 12 as infeasible regardless of qualified share and solve with 18 rep-minutes. |

If the first condition is met, make the cut immediately and move the freed rep-hour into same-day follow-up while the conversation is still fresh, rather than holding it as idle booth capacity.

If the second condition is met, the audit matters more than the headcount. Count how many of the extra six minutes are spent disqualifying unqualified traffic; if that share is below one-half, the allocation is not the constraint and coaching comes before any staffing change.

If the third condition is met, qualified share no longer governs the cut. A measured mean above 15 minutes means the 12-minute target cannot be met without truncating qualified conversations, so retain the higher allocation and revisit the process, not the ratio.

Until the lunch re-measurement settles the qualified share either side of the 60% threshold, make no allocation change; the 15-minute holding default introduced above covers the unmeasured window. Measure the inputs the same way each time: pre-booked meetings from the registration list, substantive conversations from a tally or clicker, and exclude drive-by badge scans that never become conversations.

Keep the override order explicit in the booth plan: mean minutes first, qualified share second, audit third. That prevents a high qualified share from forcing a cut that the measured conversation length cannot support.

## What to do next

| Step | Action | Why it matters |
| --- | --- | --- |
| 1 | Before each 2026 show, measure qualified share as pre-booked meetings ÷ total substantive conversations. | It determines whether the 12 or 18 rep-minute allocation applies. |
| 2 | If qualified share is at least 60%, allocate 12 rep-minutes per qualified meeting. | High qualified share supports the shorter allocation. |
| 3 | If qualified share falls below 40%, allocate 18 rep-minutes per qualified meeting. | Lower qualified share needs the longer allocation. |
| 4 | If qualified share is between those thresholds or not yet measured, run 15 rep-minutes as the default until the first half-day of data replaces the guess. | It prevents locking in an unverified allocation. |
| 5 | Keep the 18-rep-minute allocation only if queue-absorption measurement shows unqualified traffic above ~40% of booth arrivals. | It confirms the longer allocation is justified by booth flow. |
| 6 | Treat 12 vs 18 rep-minutes as a throughput constraint to verify, not a benchmark to copy. | It keeps staffing tied to measured booth conditions. |

## Frequently Asked Questions

**When should I allocate 12 rep-minutes per qualified meeting?**

Allocate 12 rep-minutes per qualified meeting when qualified share is at least 60%.

**How is qualified share calculated for this rule?**

Qualified share equals pre-booked meetings divided by total substantive conversations, measured before each show.

**What evidence is required to justify keeping the 18-rep-minute allocation?**

Queue-absorption measurement must show unqualified traffic above ~40% of booth arrivals to keep the 18-rep-minute allocation.

**Where does the 60% cutoff originate from?**

The 60% cutoff comes from the pre-show qualified-share measurement rule.

**For which show year does this staffing decision apply?**

The decision applies to 2026 trade show booth staffing.

**Should I use 12 vs 18 rep-minutes as a standard benchmark?**

Treat 12 vs 18 rep-minutes as a throughput constraint to verify, not a benchmark to copy.

## Quick answers

| When should 12 rep-minutes per qualified meeting be allocated? | Allocate 12 rep-minutes per qualified meeting when qualified share is at least the 60% cutoff. |
| --- | --- |
| How is qualified share defined and measured? | Qualified share equals pre-booked meetings divided by total substantive conversations, measured before each show. |
| When should the 18-rep-minute allocation be kept? | Keep the 18-rep-minute allocation only if queue-absorption measurement shows unqualified traffic above the ~40% condition of booth arrivals. |
| How should the 12 vs 18 rep-minute choice be treated? | Treat 12 vs 18 rep-minutes as a throughput constraint to verify, not a benchmark to copy. |
| What does the guide state for 2026 shows? | It states when to allocate 12 or 18 rep-minutes per qualified meeting and the ~40% condition for 2026 shows. |

Also worth reading: **Hydronic water reset for heating: 5°F supply cut vs fixed Lennox T6 setpoint**: [Hydronic water reset for heating:](https://vuti.app/blog/hydronic-water-reset-for-heating-5f-supply-cut-vs-fixed-lennox-t6-setpoint.php) · **Rooftop economizer retrofit: ASHRAE 90.1-2022 vs fixed 55°F setpoint**: [Rooftop economizer retrofit: ASHRAE 90.1-2022](https://vuti.app/blog/rooftop-economizer-retrofit-ashrae-901-2022-vs-fixed-55f-setpoint.php) · **Heating and cooling cost per square foot: $76,833—Payroll Cost, Not Price**: [Heating and cooling cost per](https://vuti.app/blog/heating-and-cooling-cost-per-square-foot-76833payroll-cost-not-price.php)

### Related reading

- [NFPA 110: Run Generators 4 Hours at Rated Load, Not 30 Minutes](https://vuti.app/blog/nfpa-110-run-generators-4-hours-at-rated-load-not-30-minutes.php)
- [Building heating repair delays 2026: auto routing 45 to 12 minutes vs vendor escalation](https://vuti.app/blog/building-heating-repair-delays-2026-auto-routing-45-to-12-minutes-vs-vendor-escalation.php)
- [Why 15 Minutes Beats 60: 6.8 to 4.6 Hours, MTTR Down 32%](https://vuti.app/blog/why-15-minutes-beats-60-68-to-46-hours-mttr-down-32.php)
- [Rooftop economizer retrofit: ASHRAE 90.1-2022 vs fixed 55°F setpoint](https://vuti.app/blog/rooftop-economizer-retrofit-ashrae-901-2022-vs-fixed-55f-setpoint.php)
- [NFPA 25 fire pump testing 2026: 10-min electric vs 30-min diesel guide](https://vuti.app/blog/nfpa-25-fire-pump-testing-2026-10-min-electric-vs-30-min-diesel-guide.php)
- [Multi-site HVAC economizer lockout: 65°F high-limit and 30% airflow—verify or lock](https://vuti.app/blog/multi-site-hvac-economizer-lockout-65f-high-limit-and-30-airflowverify-or-lock.php)

### Latest

- [Rooftop economizer retrofit: ASHRAE 90.1-2022 vs fixed 55°F setpoint](https://vuti.app/blog/rooftop-economizer-retrofit-ashrae-901-2022-vs-fixed-55f-setpoint.php)
- [NFPA 25 fire pump testing 2026: 10-min electric vs 30-min diesel guide](https://vuti.app/blog/nfpa-25-fire-pump-testing-2026-10-min-electric-vs-30-min-diesel-guide.php)
- [Multi-site HVAC economizer lockout: 65°F high-limit and 30% airflow—verify or...](https://vuti.app/blog/multi-site-hvac-economizer-lockout-65f-high-limit-and-30-airflowverify-or-lock.php)

Canonical: https://vuti.app/blog/trade-show-booth-staffing-12-rep-minutes-per-qualified-meeting-vs-18-cut-or-keep.php
Markdown: https://vuti.app/blog/trade-show-booth-staffing-12-rep-minutes-per-qualified-meeting-vs-18-cut-or-keep.php/index.md