The menu that took three and a half hours a week

There’s a folder on Camp Beer Co.’s shared drive with hundreds of menu PDFs in it. Every one of them was the live menu for a few days, until a keg blew and someone rebuilt the file in InDesign, exported it, and put it wherever it needed to go. Add it up and the menu was costing about three and a half hours a week, most weeks.

Camp isn’t a struggling operation. This is BC Beer Awards’ Brewery of the Year, a taproom people cross the valley for, and a tap list that changes constantly. Which is exactly the problem: the more often your menu changes, the more you pay for a menu that’s hard to change.

The old website ran on a drag-and-drop template builder. The menu page was text boxes on a canvas: change one price and a column could slip out of line, or the layout could quietly break in ways only someone with a design eye would catch. So the team did the sensible thing and stopped touching it. The real menu moved to InDesign, where the layout at least stayed put. From there, every keg change meant an export for the website, an export for print, and a third one for the taproom TV, mirrored from an iPad. Three screens, three sources, none of them live.

The part I find interesting is that nobody at Camp would have listed any of this among their problems. Nobody was complaining. The InDesign loop had been absorbed as routine, the way workarounds are: it was just how the menu gets done. The tell wasn’t anyone’s frustration. It was that folder of dated files.

Every business has a folder like that somewhere. It’s the receipt for software that made editing feel dangerous.

The fix wasn’t a better menu page. It was moving where the menu lives. In the rebuild, the design is code and the content is a form: staff type the beer, the style, the price into structured fields and hit publish. There’s no canvas to nudge, and no way to break the layout from the editing side. The QR menu on the tables, the website, and the TV tap board all read the same source, so a beer kicked behind the bar comes off all three screens within the minute. The InDesign loop didn’t get faster. It got deleted.

BEFORE                               AFTER

keg blows                            keg blows
  │                                    │
  ▼                                    ▼
rebuild the file in InDesign         edit one field, hit publish
  │                                    │
  ├─ export PDF → website              ├─ QR menu   · live
  ├─ export PDF → print                ├─ website   · live
  └─ export PDF → iPad → TV            └─ TV board  · live
        ~3.5 hours a week                  ~30 seconds

If you run a place, the transferable bit is the diagnostic, not the stack. Look for the ritual: the file that gets rebuilt and re-exported on a schedule, the spreadsheet that gets retyped into something else, the job everyone does weekly without asking why. Time it honestly for a month. Three and a half hours a week is roughly 180 hours a year, and that quote was sitting in Camp’s shared drive the whole time, filed as PDFs.

The full write-up, with the before-and-after menus scrolled side by side, is on the work page.