Edit Flow Pro stores custom editorial statuses as a taxonomy attached to posts, editorial metadata as postmeta under keys prefixed _ef_editorial_meta_ and User Group assignments in usermeta and a custom taxonomy. The Story Budget and Calendar views are good visual overviews, but neither lays the data out as the column-perfect editorial cockpit a team needs once dozens of pieces are running in parallel.

SleekView reads the same wp_posts joined with the Edit Flow status taxonomy and pivots editorial metadata into proper columns. Status, editor, due date, word count and channel become first-class fields. Sorts work the way a managing editor expects: due date ascending, status grouped, editor for per-person load. Filters compose, so "every Tech-section post In review past due" is one composed view, and "every Pitch assigned to a specific editor this quarter" is another. Inline edits on status and editor route through the standard WordPress save path, so Edit Flow hooks fire exactly the way they would from the editorial sidebar.

The plugin keeps owning custom statuses, editorial metadata and the notification module. The table view adds the cross-pipeline surface the Story Budget hints at but does not deliver.

Editorial workflow plugins capture the right data and then surface it through views that work for one piece at a time. Edit Flow Pro is no exception: custom statuses, editorial metadata, User Groups and a notification module are all there, and the Story Budget gives them a visual board. The gap is the cross-pipeline question.

Composable filters, real sorts and inline edits turn the same records into an editorial cockpit. The plugin keeps owning the workflow and the per-post detail, the table view becomes the cross-pipeline surface, and editorial leadership finally has the cockpit the data has always supported.