Downtown DC towers rarely let a visitor walk straight to an elevator. A guard desk checks identification, prints a badge, and calls upstairs before anyone moves past the turnstiles. While that screening runs, the ground-floor coffee bank fills with people who have five spare minutes and nothing else to do. The lobby machine works hardest during the exact window security controls.
This piece is about the screening queue and the guest pour it creates, not about milk turning or a hot loading dock. On K Street and around Farragut, the pantry plan that ignores the guard desk keeps missing why the lobby bank empties while the floors upstairs still look calm.
Why the screening desk sets the pour curve
A visitor cannot badge past the lobby until the guard desk clears the check, so guests pool at ground level in predictable waves. A ten o’clock meeting block sends a dozen people through screening at once, and most of them grab a cup while they wait for an escort. None of that shows on the tenant headcount finance used to size the pantry.
The queue also stacks by appointment culture. Association meetings, agency briefings, and law firm client visits cluster into mid-morning and early afternoon, and every one of those blocks pushes a fresh line through the guard desk. Read only the badged floor count and you will underbuy for the hours that shape a visitor’s first impression of the building.
Score how your ground-floor setup handles guest load with the break room readiness quiz. Timing for a pilot sits in the two week trial FAQ. For how DC building types differ on visitor flow, read the local field notes.
Log the queue, not just the floors
Ask the lobby ambassador to mark pours during screening waves separately from ordinary desk-worker cups. A quick tally when a visitor in a temporary badge takes a drink is enough. By the second week you can see whether the ground-floor bank is really a staff amenity or a guest-facing station that the guard desk feeds all day.
The numbers usually surprise the tenant. A tower that reports light occupancy can still drain the lobby dairy before noon because three screening waves parked guests at the machine. That is not a headcount miss, it is a security-flow pattern, and it deserves its own restock line rather than a share of the upstairs average.
Name the driver on each peak. A morning screening wave, a scheduled briefing block, and a walk-in vendor line are different reasons the bank ran dry. Blended into one lobby figure, they hide the buffer the ground-floor station actually needs before a heavy visitor day.
Restock rules that match the guard desk
Vendor cadence built on tenant seat count leaves the lobby short whenever screening waves stack. A guest-facing bank often needs a protected mid-morning top-up ahead of known meeting blocks, while quieter upper floors run fine on a steadier weekly rhythm. One rule copied to both wings wastes product in the calm floors and empties the busy lobby.
For DC accounts we set Swiss bean-to-cup machines at the point of heaviest traffic, send technicians on a weekly or biweekly loop, pour genuine dairy at the wand rather than shelf-stable substitutes, and invoice only on the cups a station actually pours. Metered billing fits a screening-fed lobby because the invoice climbs with visitor volume instead of a flat seat guess. Our house roast is fully Arabica, drawn from Papua New Guinea, Brazil, and Colombia lots and roasted here in the United States.
Compare that against pod or single-serve programs on the about page, and keep recent DC pieces in view on the blog index.
Pilot the lobby bank first
Put a free two-week trial on the ground-floor station the guard desk feeds, not a quiet upper pantry that only sees badged staff. Ask the ambassador to log guest pours apart from desk pours so the week-two summary shows the real split when finance asks why dairy moved faster than the occupancy report suggested.
Recruiting and client-hospitality talk both lean on a good first impression at the door. That promise falls apart when the lobby machine sits empty during a screening wave because it was stocked for desk count. Getting the guest-hour supply right is a hospitality decision before it is a facilities line item.
Preventative maintenance rides with the service cadence on DC accounts, so the lobby machine is not flashing an error while a guest waits for an escort. Volume-matched visits beat a break-fix ticket opened after a screening wave already found the fault.
Presenting the split at renewal
When pantry data goes to renewal, keep badged desk pours in one table and lobby guest pours in another. Add screening-wave hours, meeting-block counts, and dairy discard by floor type. Metered invoices back those tables because spend already followed each curve rather than a flattened lobby total.
Keep guest volume out of one building-wide average. A screening-fed lobby and a badged upper floor can share a single contract and pour on opposite schedules. Decision makers who see each label can approve a restock rule that keeps the ground floor ready for visitors without overbuying for the quiet wing.
Revisit the break room readiness quiz when facilities and the front-of-house team disagree on what the lobby station should hold before a heavy briefing week.
Closing the lobby gap before renewal
Treat the screening queue as a real driver of ground-floor pours, not a rounding error on tenant headcount. Log the guest waves, name the driver on each peak, and let cup-based billing carry the lobby share into numbers finance can defend.
To trial screening-aware cup logging on your lobby floor, open the Request a trial form on the Washington DC overview. Call 571-218-0864 or email tyler.burdett@breakcoffeeco.com with building type, guard-desk routine, and receiving rules. Tyler Burdett and the local team can set ambassador logging for screening waves and badged pours before week one begins.
