PublishPress Content Checklist (formerly PublishPress Checklists) enforces editorial standards at publish time: minimum word count, featured image, alt text, category present, custom checks. Each post carries the evaluation result in wp_postmeta, so the data is there for any post type the checklist applies to. The meta box inside the editor is excellent at the per-post layer. The site-wide layer (which posts are passing right now, which ones silently fail a specific requirement, which authors miss the same checks repeatedly) lives one query away from a real audit table.

SleekView reads the same evaluation data the meta box computes and joins it with each post. Required-count, passed-count, the list of failing items and each individual requirement become first-class columns. Sorts work the way a copy editor expects: pass ratio ascending to expose the worst-performing posts, post_date descending to scope to recently published content, author for a per-writer view. Filters compose, so "every failing post by a specific author missing the alt-text requirement this month" is one composed view, and "every published post that fails the featured-image check" is another.

PublishPress Content Checklist keeps owning the requirement definitions and the enforcement gate. The table view adds the site-wide audit surface the meta box was not built to be.

Editorial quality systems quietly degrade unless someone audits them at the level of the whole site rather than the next post. PublishPress Content Checklist is excellent at enforcing rules at publish time and exposes a clean meta box inside the editor. What it does not do by default is look back across the catalogue.

Sites ship a year of posts that pass on publish day, then add a new requirement, and end up with hundreds of posts that silently fail it. A composable audit table turns the checklist from an at-the-door bouncer into an ongoing quality surface that the editorial team can actually work against.