Reading a real government A/V bid: one brand for every conference room
A public invitation to bid, read cold on camera: the single-brand room spec, what wireless sharing really shares, and the cable problem hiding in the BYOD design.
This is a genuine first look - a public invitation to bid for a government office's A/V package, opened cold on camera. The room list is ordinary: conference rooms, a grand jury room, a media conference room. What stands out is the spec: every standard conference room names one product, the 65-inch Neat Board Pro with a Neat Pad controller. When a bid is that specific, the useful question is what those devices actually do for this building's way of working.
The bid says Microsoft Teams is primary but the rooms must handle Webex, Zoom, RingCentral, and GoToMeeting - so these are BYOD rooms. That's actually a point in favor of an all-in-one device: camera, mics, and speakers live behind one vendor's USB stack, which matters because real users unplug the cable and plug it right back in, and half-initialized USB stacks are where service tickets come from. The catch is the cable itself: the included USB-C pigtail is short, has to dangle from the display, and doing it properly - through the wall, under the floor, with DP alt mode intact - is a $600-700 line item almost nobody budgets.
The back half is the design I'd propose for the multi-source room: keep the document camera as a content source (not a camera - protect the people view), split its HDMI so it feeds both the local PC and an auto-switcher, and set switch priorities: local PC, then document camera, then laptop. Plus one experiment worth running before trusting any of it.
What to take from it
- A public bid that names one brand for every standard conference room is worth pausing on - several products (Yealink A40/A50 and others) could serve those rooms, so the spec deserves a "why."
- "Wireless sharing" isn't one thing: unless the platform exposes a real content-share path, shared screens arrive as just another camera feed, which changes how meetings actually work.
- Teams-primary but BYOD-everything is a common government pattern - and it makes single-vendor USB stacks genuinely valuable, because users unplug and re-plug without waiting and fragmented stacks get stuck mid-initialization.
- The included BYOD cable is short by design. Routing USB-C properly (wall, floor, table) with display-port alt mode intact costs real money - budget $600-700, not $0.
- Keep the document camera as a content source, not a camera: the room's people-view is worth protecting, and HDMI out lets you split it to the local PC and the switcher.
- Auto-switch priorities that match how people work: local PC first, document camera when it's powered on, laptop when it's plugged in.
- Before trusting a design, find the experiment: do the board's external USB ports pass through in BYOD mode? Probably not - but it's worth a try.
Read the full transcript
Lightly edited for readability; the issuing organization is left unnamed here.
Hey everyone, it's bid review time. What do we have here? An invitation to bid for a government office's audio-visual package. I've only glanced at it to check that there are pictures or diagrams - and there are - so we're seeing this together for the first time.
I like skipping right to the scope of work and the rooms. What have we got? Conference room, grand jury room, conference room… ooh, a media conference room. That's interesting. A larger conference room. We're going to skip the smaller ones - those are simple. That's a Yealink A40 or an A50 or something like that, and honestly, if you go Yealink, those A40s and A50s are so good. Not a sponsor - I am vendor-neutral.
Oh, look at this: "For operational continuity, all standard conference rooms will have the 65-inch Neat Board Pro units with Neat Pad meeting controllers." Huh. Very specific. Why so specific? Because there are other really great products that could probably work in those conference rooms.
Are the Neat Boards touchscreen? Let's check - yes, 65-inch touchscreens. Those are pretty cool. You can run apps on them, so you can run Zoom Rooms. As I was looking for the specs, I saw this: "Enjoy wireless sharing for Google Meet, Microsoft Teams, or Zoom via a wide-angle ultrasonic tweeter and integrated Bluetooth support." An ultrasonic tweeter for screen sharing - that probably means you install a Neat app on your computer, it listens for the ultrasonic signal, and it shares to a virtual device in the Neat Board Pro.
What I want to know is how it shares content into the different platforms. For Microsoft Teams, if the board is running Teams Rooms, it has to expose an ingest so the share can arrive as content. Otherwise it arrives as a camera - just another camera view you switch to, mixed with or instead of the room camera. Same with Zoom desktop or Teams desktop: there's no way to share content into those applications that isn't a camera. If the board is running Teams Rooms or Zoom Rooms natively, there's a chance it can share content as a real second source - the same way you'd share your screen from a laptop.
Searching the spec page for "Teams Rooms" turned up nothing, and since this is a government entity it's likely a Teams shop - so my guess on camera was that you'd get an installed app rather than the full Teams Rooms experience. But I spoke too soon: the bid says Microsoft Teams is the primary conferencing application, and the BYOD system is designed to allow multiple web conferencing solutions - Webex, Zoom, RingCentral, GoToMeeting. So they just want to bring anything into the room and use it. That's fine.
And BYOD on these devices is pretty good - because the USB stack for the speakerphone, the microphone, the speakers, and the camera all live inside the Neat device. One vendor has full control over it. Versus buying a Logitech camera, some other Bluetooth speakerphone, and a USB hub or switching device: now you've got multiple manufacturers with different USB stacks, and as things get unplugged and replugged, each device has to clear and reinitialize its stack. Some do a much better job of that than others.
And users unplug things. It's one thing to unplug, wait ten seconds, let the software sort itself out, and plug back in. But users be users: they unplug and plug straight back in, the device gets stuck halfway through initialization, and there's your service ticket. Hopefully Neat has built that stack to be atomic - once it's shutting down it completes the shutdown, once it starts it completes the startup, and it can't catch itself in between.
The other thing: the BYOD USB-C cables that ship in the box aren't very long. Let's see what this one comes with. USB-C power delivery - nice. USB-C DP alt mode - very normal, but it means whatever cable you use has to support DisplayPort alt mode, and not all of them do. In my experience these ship with a shorter cable, maybe three meters - about ten feet - which means you can't route it through the wall and under the floor to the table. It has to dangle from the display and droop over to the table, which is not the nicest thing. Someone's going to walk through it and break it.
So you go buy a third-party USB-C cable - and it is so easy to buy one that won't work. There was a time I kept a stack of USB-C cables, extensions, and extenders, and I'd have to try them between Windows machines and Macs and whatever else. What I found is you get what you pay for. The best short ones are just copper between the connectors; once you go long you need signal extension - maybe fiber in the middle - which means more electronics in the pins. A lot of USB-C pins are shared, multi-mode: the cable has to configure pins for DP alt mode, and depending on resolution and frame rate I believe it can enlist more pins for bandwidth. My point: expect to spend six or seven hundred dollars on a long USB-C run that neatly routes from the board, through the wall, under the floor, and up to the table where people can actually plug in.
Okay, Amos - so how would you do it? The room has multiple sources: a document camera, a local PC, a laptop, and BYOD. First, keep the document camera as a content source, not a camera. There's so much value in the room cameras staying on - protect the fact that the far end can see you and where you're looking. So the document camera should have an HDMI output. That's nice, because you can split it: run one leg into the local PC as the bid wants, and the other into an HDMI switcher - so when you share, you're choosing between the local PC and the document camera. I would never want to share the document camera by passing it through the local PC. That's too much.
So the auto-switcher gets three priorities. First, the local PC - share that into the Neat Board. Second, the document camera - if it's powered on, share it; a tabletop unit should have a power button. Third, the laptop through its HDMI out - if it's plugged in, share that. You could run BYOD to both the local PC and the laptop through a USB auto-switcher, but I don't love that. It feels risky.
What would be neat: plug the document camera into the USB-A port on the Neat Board and have it exposed through BYOD as one more device - so the laptop or room PC sees the camera, the microphone array, the speakers, and a USB document camera. I don't know that it works; it would have to be tested. Do the external USB ports on the Neat Board Pro switch over in BYOD mode? I'm guessing probably not. But it'd be worth a try.
Have a bid or quote like this on your own desk? Start with three questions and the answer key →
Find out what your rooms are actually costing you.
One meeting. One verdict, in writing. If you don’t need me after that, I’ll be the one who says so.
Got it. Your note is in my queue - you’ll hear from me within one business day.
// no ticket number, no autoresponder theater. Just a reply from me.