What I like most about forms.app is how flexible it is for building all kinds of internal and audience-facing forms to support our broadcast and digital content operations at Chicago Broadcast Collective. I’m the Operations Director here, so I handle cross-team coordination, content scheduling, and media asset management across multiple team locations. We already rely on OneScreen for our digital signage and internal content display, and forms.app fits perfectly into that stack to collect information and streamline workflows for our production and creative teams. Before using forms.app, we were stuck using clunky shared Google forms with limited customization, and it was hard to tie submissions directly into our media workflows.

A great example was our recent on-air segment request process. Our producers, writers and remote field reporters needed a simple way to submit segment proposals, including run time estimates, guest details, and required media assets. In the past, they’d fill out a basic form, and all responses would land in a single spreadsheet. I’d then have to manually sort every entry, forward details to the scheduling team, and chase people for missing attachments. It was messy and took up so much of my time.

With forms.app, I built a custom form tailored exactly to our broadcast needs. I added conditional logic so if someone selected a live on-air segment, extra fields for guest pre-screening and equipment requirements would pop up automatically. Reporters could upload raw video clips, image assets and supporting documents right within the form submission. Every time a producer submitted a new segment request, forms.app sent an automatic alert to our scheduling team and me. We could review all submissions in the built-in dashboard, tag entries by air date, and flag urgent content requests.

I also use forms.app for our internal team equipment checkout requests. Crew members can submit requests for cameras, mics and field gear, and the form auto-routes those submissions to our equipment manager. We can even pull form data and display key request summaries on our OneScreen digital signage in the main production office, so the whole team can quickly see pending equipment bookings.

What really stands out is how easy it is to tweak forms on the fly without waiting for a developer. When our broadcast schedule changes or we need to add new fields for compliance checks, I can jump in and update the form myself in minutes. It cuts out so much manual data entry and back-and-forth emails. For a mid-sized broadcast team spread across multiple workspaces, forms.app keeps all our request workflows centralized. It saves our production staff time on paperwork and lets our team focus more on creating content rather than filling out and chasing down forms. Review collected by and hosted on G2.com.

To be honest, while forms.app works fine for basic internal requests, it has several noticeable drawbacks that slow down our daily broadcast and content operations at Chicago Broadcast Collective, especially when I’m managing tight production timelines and cross-team workflows alongside our OneScreen digital systems.

The biggest issue I deal with daily is its **unstable conditional logic and notification glitches**. I rely heavily on conditional fields to standardize our production requests — things like live segment bookings, studio time applications, and field crew assignment forms. Quite often, the conditional rules don’t trigger consistently. Sometimes mandatory hidden fields fail to pop up, so staff submit incomplete forms with missing critical details like studio equipment needs, segment runtimes, or live broadcast safety checks.

I had a very noticeable issue during our weekly weekend news block scheduling recently. I created a studio booking form that was supposed to require extra compliance fields for live broadcasting whenever someone selected “live on-air segment.” Half of our producers submitted their bookings without those required fields popping up. By the time I reviewed all submissions, nearly eight pending studio requests were missing safety confirmation and technical setup info. I had to pause my OneScreen content scheduling work, message every producer individually, and manually verify and correct each form entry. It created extra rework and nearly delayed our weekend broadcast prep.

Another downside is the lack of detailed submission version tracking. In broadcast operations, team members often update their segment plans, change guest lineups, or adjust production times after their initial form submission. But forms.app doesn’t log edit history clearly. I can only see the latest version of the form, with no record of what was changed or when. This makes it really hard for me to audit changes, align schedules, or figure out why last-minute production conflicts happened. Review collected by and hosted on G2.com.