How Do I Get My QSR Crew to Upsize and Attach Items in 2026?

What the upsize and attach problem actually is

Most quick-service operators think they have a motivation problem. They almost never do. They have a measurement problem wearing a motivation costume.

Walk into a store where attach is flat and look at what the crew is actually graded on. It is nearly always drive-thru times, order accuracy, and labor percentage. Those three numbers get posted on the wall, called out in the pre-shift, and repeated by the district manager. Attach rate gets mentioned in a quarterly meeting. So the crew optimizes exactly what you told them to optimize: they clear the order and move the car. A crew member who pauses four seconds to ask "want to make that a large for sixty cents?" is, under the posted scoreboard, *underperforming*. You built that incentive. They are just reading it correctly.

The second thing worth naming: upsize and attach are two different behaviors, and lumping them together is why coaching fails. Upsize is a same-item size change — small fries to large, medium drink to large, single patty to double. It is one sentence, it happens at the moment the item is already in the order, and it converts at the highest rate of anything you can ask. Attach is adding a *new* item — a dessert, a side, a second drink, a sauce upgrade, a bakery item. It requires the crew member to have a specific item in mind and a reason to name it. Attach is harder, converts lower, and carries more margin per hit. If your coaching says "suggestive sell more," you have given the crew a single vague instruction covering two different motor skills. They will do neither.

Third: the economics are why this matters more than almost any other lever available to a store operator. Every dollar of upsize and attach lands on traffic you have already paid for. You spent nothing extra on marketing, nothing extra on rent, nothing extra on the labor hour — the car is already at the window. A meaningful share of that incremental dollar drops to store-level profit because the fixed costs are already covered. Compare that to chasing new traffic, where you pay in coupons, LTO marketing spend, and third-party delivery commissions to get the same top line. Attach is the cheapest revenue in the building.

And this is where the RevOps framing earns its keep. Operators tend to think of revenue operations as a software-company discipline — pipeline stages, quota attainment, comp plans, scorecards. The mechanics are identical at a QSR register. You have a funnel (car arrives → order taken → items suggested → items accepted → ticket rings), a conversion rate at each step, a set of frontline humans whose behavior determines the conversion, and a comp structure that either rewards the behavior or ignores it. A sales VP would never tell an account executive "sell more" and then pay them purely on call volume. That is precisely what most stores do to their crew.

The same pattern shows up in every adjacent frontline business, which is a useful sanity check. Liquor stores struggle to get staff to move premium tiers instead of the well brand. Apparel floors struggle to get associates to complete the outfit rather than ring the single item. Auto service advisors struggle to attach the cabin filter to the oil change. Every one of these is the same structural failure: the scoreboard measures throughput, the margin lives in the attach, and nobody wired the two together.

The step-by-step process for building the behavior

Here is the sequence that actually moves the number, in order, with the work each step requires.

Step one — pull the baseline by person, not by store. Your POS already has this. Export per-cashier or per-employee item detail for the last 30 days and calculate, for each crew member: upsize rate (size-upgraded items ÷ eligible items), attach rate (transactions containing a target add-on ÷ total transactions), and average ticket. Do this before you announce anything. You will find a spread that surprises you — it is common for the top and bottom performers in a single store to be separated by a factor of three or more on attach, working the same window, on the same shifts, with the same menu. That spread is your entire opportunity, and it proves the problem is behavioral rather than a customer-demand ceiling.

Step two — pick two targets per daypart, not ten. This is the step operators skip and it is the one that decides the outcome. A crew member cannot hold nine suggestive-sell items in their head during a lunch rush. Give them exactly two: one upsize and one attach, specific to that daypart. Breakfast might be "large coffee" and "hash brown." Lunch might be "large combo" and "dessert." Late night might be "large drink" and "extra side." Two items, named, posted at the station. The narrowness is the feature — it turns a judgment call into a reflex.

Step three — write the actual sentence. Not a script in the corporate sense, not a paragraph. One sentence per target, written down, tested at the window, and short enough to say in under three seconds. The construction that works is assumptive and specific: "Want to make that a large for sixty cents?" beats "Would you like to upsize?" every time, because the first names the item, names the price, and gives a yes/no. Vague asks ("anything else?") convert near zero — they are a closing signal, not an offer. The word "for" followed by a small number does enormous work, because it reframes the ask as a trade rather than a spend.

Step four — rehearse it in the pre-shift, standing up, out loud. Five minutes. Two rounds. One crew member plays the customer, one plays the window. It feels ridiculous for the first week and then it does not. The reason this step is non-negotiable is that the ask has to survive a rush, and anything that has not been said out loud a dozen times in calm conditions will not be said at all when six cars are stacked. This is the same logic behind sales role-play in a software org and behind pre-shift lineup in fine dining — the rehearsal is what makes the behavior automatic rather than deliberate.

Step five — build the weighted scorecard and publish it. List every KPI a complete crew member produces: size upsizes, combo conversions, add-on attach, dessert and drink attach, app or loyalty signups, average ticket, order accuracy, and speed of service. Assign each a weight with your shift managers. Score each crew member 1-to-5 on every line. The composite is the sum of (weight × level) across all lines. Weight upsize and attach heaviest — that is the entire point of the exercise. A crew member who is a level 5 on speed and a level 1 on attach now scores in the middle of the pack instead of the top, and the gap is visible to them without a manager saying a word.

Step six — wire the bonus to the composite. Not to attach alone (you will get pushy crew and blown drive-thru times), not to speed alone (you will get the current problem). To the composite. This is the single change that converts a coaching program into a durable system, because it removes the need for anyone to nag.

Step seven — re-weight when the menu moves. New combo drops, LTO dessert launches, you need to move a slow-turning SKU before it wastes — change the weights that night. The crew re-aims on the next shift with no retraining, because the structure never changed, only the numbers inside it.

The whole loop is roughly a two-week build and then a permanent operating rhythm. Nothing in it requires new software. The scorecard can live in a spreadsheet, on a whiteboard, or in a purpose-built tool — the discipline matters far more than the container.

Costs, timelines, and what to expect

Your real cost is manager time, not software. Building the initial scorecard — listing KPIs, agreeing weights with shift managers, pulling the first baseline — is a few hours of work. Maintaining it is roughly fifteen to thirty minutes a week per store to update scores off the POS export and run the coaching conversation. Pre-shift rehearsal is five minutes per shift, which is labor you are already paying for during the lineup. If a manager tells you there is no time for this, the honest reading is that the composite has not been wired to anything that manager is graded on either.

Software, if you want it, spans free to modest. A well-built spreadsheet is genuinely the best value for a single location — it is free, fully transparent, and every formula is inspectable. Its cost is your time to maintain it and the very real risk that it goes stale and nobody notices. Restaurant POS platforms like Toast and Square for Restaurants capture the inputs you need — per-employee sales, item attach, modifier data — with Square offering a free plan and paid restaurant plans starting in the low-to-mid double digits per location per month, and Toast running tiered plans plus payment processing. Neither weights the matrix for you; they supply the raw data and you build the scoring layer. Gamification and recognition platforms like Spinify and Hoopla put leaderboards on screens and typically price per user per month or by quote. Scorecard-and-coaching platforms like Ambition are the closest paid analog to the weighted-matrix method and are usually quoted rather than list-priced, which tends to make them a multi-unit or franchise-group decision rather than a single-store one. Commission and attainment tools like QuotaPath can wire a multi-component score to actual pay, with a free tier and paid plans in the low double digits per user per month. Scheduling systems like 7shifts are not scorecards but supply the labor context that lets you normalize attach per labor hour instead of per shift, which matters if your crew work wildly different volumes. Loyverse sits at the free-POS end for very small operators. Prices across all of these move; check current published pricing before you commit, and confirm what falls inside your franchisor's approved-vendor list.

Timeline, realistically. Week one is baseline and design — no announcement, no pressure, just data and weights. Week two you launch: publish the matrix, post the two targets and two sentences per daypart, start pre-shift rehearsal. Weeks three and four are the awkward stretch where the ask sounds mechanical and some crew quietly skip it; this is normal and it is where most programs die because the operator concludes it "didn't work." Push through. By roughly week five or six the ask has become automatic for the crew who are going to adopt it, and the spread on your scorecard tells you clearly who is coaching-resolvable and who is a role-fit problem. Give the whole thing a full quarter before you judge it.

Where the money shows up. Track average ticket and per-crew attach rate as the primary measures, not total sales — total sales moves with traffic and weather and will lie to you in both directions. Watch drive-thru time alongside them as a guardrail metric: if attach climbs and service time degrades past your threshold, the sentence is too long or the ask is landing at the wrong moment in the order. Set a specific ceiling on service time before you start, so the trade-off is a number rather than an argument.

Budget the bonus honestly. The incentive pool has to be funded from the incremental margin the program creates, and it has to be big enough to notice — a bonus that rounds to a few dollars a shift buys you nothing but cynicism. Model it before you launch: estimate the incremental attach dollars at a conservative lift, apply your margin on those items, and share a defensible slice of it. Crew do this math faster than you expect. If the number is insulting they will simply stop asking, and you will have burned the mechanism for the next attempt.

Where operators get this wrong

Coaching the person instead of the line. "You need to sell more" is not coachable. "Your dessert attach is a level 2, here is the sentence, say it on every combo this shift, we'll look at it tomorrow" is coachable. The weighted matrix exists to convert a personality conversation into a specific, bounded, next-shift action. Every coaching conversation should point at one line on the scorecard, not at the composite and not at the human.

Running a contest instead of building a system. Contests spike a number for a week and then it collapses, because the contest was the reason for the behavior and the contest ended. Worse, contests reward whoever already had the highest volume shifts. Recognition and leaderboards are a fine *amplifier* on top of a scorecard tied to pay — they are a poor substitute for one.

Asking too many items. The operator who posts nine suggestive-sell items gets zero. Two per daypart. This is the single most common self-inflicted wound.

Asking at the wrong moment. Upsize belongs at the moment the item enters the order — right after they say "medium fries," not at the end of the transaction. Attach belongs just before the total, when the order feels complete and one more item is a small addition rather than an interruption. Reverse those two and both convert worse. If your attach rate is stuck despite good compliance on saying the words, audit *when* the words are being said before you change what they are.

Not normalizing for shift. The crew member on Tuesday breakfast will never post the raw numbers of the crew member on Friday dinner rush. If your scorecard compares raw counts, you have built a shift-assignment lottery and the crew will see it as unfair within a week. Score on *rate* — attach per eligible transaction — or normalize per labor hour. Fairness is not a nicety here; a scorecard the crew believes is rigged is worse than no scorecard, because it teaches them the whole system is theater.

Letting the scorecard go stale. A published matrix that has not been updated in three weeks does active damage. It signals that management stopped caring, which gives the crew explicit permission to stop caring. If you cannot commit to a weekly update, commit to biweekly and hit it — cadence reliability matters more than cadence frequency.

Ignoring the channel split. Attach behavior on a kiosk, in the app, and through third-party delivery is a *menu-design and prompt-design* problem, not a crew-behavior problem. Digital channels often out-attach humans on some items precisely because the prompt never gets tired, never gets embarrassed, and never skips a rush. If a meaningful share of your orders are digital, your crew scorecard covers a shrinking slice of the ticket and you should be running the same weighted logic on your digital prompt placement in parallel. This is the upstream effect operators miss: the crew program and the digital merchandising program are the same program aimed at two surfaces.

Punishing the ask instead of the result. Some crew will ask cleanly and still convert poorly because of their station, their daypart, or their customer mix. Score compliance (did they ask) separately from conversion (did the customer say yes) at least during the first month. Crew will tolerate being held to the behavior far longer than they will tolerate being held to an outcome they do not fully control — and the behavior is the part you can actually coach.

Skipping the "why" with the crew. Tell them plainly: this is how the store funds raises and hours, and here is the slice of it that comes back to you. Crew who understand the mechanism argue with it far less than crew who experience it as a new rule from the office. Most resistance to a scorecard is not resistance to work — it is resistance to being measured by a system nobody explained.

Choosing your approach by store size and situation

The right build depends on how many units you run, how much of your ticket is digital, and whether your franchisor already mandates a program. A single independent store and a twelve-unit franchise group should not make the same choice.

One store, tight budget. Whiteboard and spreadsheet. Post the matrix in the crew room, update it Sunday night off the POS export, pay the bonus in cash or on the schedule. You do not need software; you need the discipline to update it every week without exception.

Two to five stores. The spreadsheet starts to crack because you now need comparability across locations and your shift managers all maintain it slightly differently. This is the point to standardize the KPI list and weights centrally, even if the container is still a sheet. A purpose-built scorecard tool starts to earn its cost here mainly by removing the maintenance burden from managers who will otherwise let it slide.

Six or more stores, or a franchise group. Automate the data pull off the POS and put the scorecard on screens. The manual sheet will not survive at this scale, and the variance between your best and worst store becomes the more valuable thing to manage than the variance between crew members inside one store. Check franchisor vendor rules before you buy anything.

Heavy drive-thru mix. Weight speed of service meaningfully in the composite so attach never comes at the cost of the times, and keep the sentences shortest here. Test the ask at the order point and at the window separately — they convert differently and the answer is store-specific.

Heavy digital mix. Split the program. Run the crew scorecard on the in-store and drive-thru share, and run a parallel effort on kiosk and app prompt placement, default combo configuration, and cart-page attach modules. Do not let the crew scorecard take credit or blame for digital ticket movement.

High turnover. Shorten everything. If your average crew tenure is measured in weeks, a nine-KPI matrix is wasted effort — run three lines (one upsize, one attach, one guardrail), one sentence per target, and rebuild the onboarding so the ask is taught in the first shift rather than added later. The behavior has to be part of the job from minute one or it never lands.

The decision that never changes regardless of size: the ask has to be specific, rehearsed, measured by rate rather than raw count, and connected to something the crew member cares about. Everything else is packaging.

Related questions

How much can attach realistically move average ticket?

It varies enormously by menu, daypart, and starting point — a store already running disciplined suggestive sell has far less headroom than one starting cold. Measure your own per-crew spread first: the gap between your best and worst performer is your credible ceiling, not an industry benchmark.

Should I pay individual bonuses or team bonuses?

Team bonuses on the composite reduce infighting over station assignment and work better in small crews where one person's numbers depend on where they were placed. Individual bonuses drive harder but need careful rate normalization. Many operators run a team pool with an individual multiplier.

Does this apply outside quick service?

Directly. Liquor stores moving premium tiers, apparel floors selling complete outfits, and service shops attaching parts to a repair order all face the same structure: throughput is measured, margin lives in the attach, and nobody connected them. The weighted-matrix method transfers with only the KPI names changed.

What if my franchisor already runs an attach program?

Adopt their targets as your KPI lines rather than competing with them. Your added value is the weighting, the per-crew visibility, and the store-level bonus — the franchisor rarely supplies those. Confirm compliance rules before publishing anything that scores individuals.

How do I keep the ask from annoying customers?

Cap it at one upsize and one attach per transaction, make it specific and priced, and stop cold at the first no. Complaints almost always trace to repeated asking or vague pitching, not to a single well-placed suggestion.

FAQ

What if a crew member is fast but never suggests add-ons?

They will score low on the weighted matrix because upsize and attach carry the heaviest weights, so a level 5 on speed paired with a level 1 on attach lands a mediocre composite. The scorecard makes the gap visible without a manager repeating themselves, and because the bonus follows the composite rather than order count, the incentive to suggest the large and the side is constant rather than something that shows up in a quarterly review.

How do I set the weights for each KPI?

Set them with your shift managers, not alone — they know which behaviors are realistic at which stations. Weight upsize and attach heaviest because they grow average check on traffic you already paid for, keep accuracy and speed as meaningful guardrails so the ask never wrecks the times, and give loyalty or app signups a smaller share unless that is a current company priority. Publish the weights so nothing about the score is a mystery.

Can I change the matrix for a new promotion?

Yes, and this is one of the main reasons to run a weighted structure rather than a fixed rule. When a new combo or limited-time offer drops, re-weight overnight and post the new numbers; the crew re-aims on the next shift because the structure is unchanged and only the emphasis moved. No retraining, no new script framework, just different targets inside the same familiar scorecard.

Does this work for a small QSR with only a few crew members?

It works well and is arguably easier, because you can coach every person individually every week. With three to five crew, trim to three or four KPI lines instead of nine — the point is that the composite honestly reflects the whole ticket, not that the matrix is elaborate. Score on rate rather than raw count so whoever draws the slow shifts is not penalized for the schedule.

What if a crew member resists the new scoring system?

Explain the mechanism plainly: the matrix rewards the whole ticket, the incremental margin funds the bonus pool, and here is the slice that comes back to them. Show them their own scorecard rather than the ranking. Most resistance is really objection to being measured by something nobody explained, and it fades once the first bonus lands. Persistent refusal after a fair explanation and a month of coaching is a role-fit conversation, not a scorecard problem.

How often should I update the matrix weights?

Update immediately when the menu or a priority shifts — a new LTO, a seasonal item, a push on loyalty signups. Outside those events, review monthly with your managers and change nothing unless there is a reason; weights that move constantly stop feeling like a target and start feeling like a moving goalpost. Update the *scores* weekly regardless, because a stale scorecard signals that management stopped caring.

Sources

• https://www.nrn.com/ — Nation's Restaurant News, quick-service operations and industry coverage
• https://www.qsrmagazine.com/ — QSR Magazine, drive-thru and crew operations reporting
• https://www.restaurantbusinessonline.com/ — Restaurant Business, unit economics and menu strategy
• https://pos.toasttab.com/ — Toast, restaurant POS platform and pricing
• https://squareup.com/us/en/point-of-sale/restaurants — Square for Restaurants, POS plans and reporting
• https://www.7shifts.com/ — 7shifts, restaurant scheduling and team management
• https://www.ambition.com/ — Ambition, weighted scorecards and coaching cadences
• https://quotapath.com/ — QuotaPath, commission tracking and attainment
• https://spinify.com/ — Spinify, frontline gamification and leaderboards
• https://loyverse.com/ — Loyverse, free POS and loyalty for small operators

Related on PULSE

• How Do I Get My Liquor Store Staff to Sell Premium and Attach Items?
• How Do I Get My Apparel Team to Sell Complete Outfits, Not Single Items?
• How Many Crew Members Should I Schedule Each Shift at My Hamburger Franchise?
• How Do I Track Service-Fee Attach Rate by Rep?
• How Do I Set Attach Rates for My Service Fees?