We Are Falcon has released an update to Falcon Rundown that lets production teams add their own columns to the main overview. The change is intended to make the cloud-based rundown system fit the language and control points of an individual newsroom, event team or production company instead of imposing one fixed table structure.
Suggested uses include production status, location, responsible editor, platform, deadline, client and internal notes. Those examples cover both editorial and operational planning, but the larger point is that teams can decide which information must remain visible while they scan a busy collection of stories and rundowns.
The release also expands rundown metadata. We Are Falcon says the additional metadata makes it easier to identify current, recently updated or immediately relevant rundowns without opening each one. In a facility handling several shows, clients or versions at once, that kind of overview can reduce the time spent checking whether an item is still active.
Metadata is not limited to the user interface. Falcon Rundown exposes it through a REST API, which allows external systems to read or use the same fields in integrations and automation. A broadcaster could, for example, align a planning dashboard, booking system or internal status page with the editorial state already maintained in the rundown platform.
The update reinforces a broader trend in broadcast software: the rundown is becoming both a human workspace and a structured data source. Custom columns help the production team see its own priorities, while the API makes those priorities available to the rest of the technical stack. We Are Falcon describes the release as a small interface change with a larger effect on clarity in complex productions.
