WP Document Revisions stores controlled documents as a document custom post type with a workflow_state taxonomy (Draft, In Review, Final, Archived) and a document owner stamped through post meta or post_author. Every save creates a real WordPress revision, so wp_posts accumulates a long version history per parent document.

SleekView reads the document CPT, its workflow_state taxonomy, owner ID joined to wp_users, and a count of attached revisions per parent. Workflow state, owner name, and revision count sit as real columns alongside title and modified date. Filter to In-Review documents owned by a specific lead, sort by revision count to find the most-edited policies, or pull every Archived document from last quarter without leaving the table.

Inline edits go through the standard CPT update path, so workflow_state change actions still fire, email notifications still trigger, and access-control capabilities still apply. Reassign owners across stuck drafts in one pass, or move a batch of approved drafts to Final from the row.

WP Document Revisions exists because regulated organisations need versioned documents with workflow states, owners, and audit trails that the default WordPress post table does not provide. The trade-off is that the audit trail is only useful if someone can read it at a glance, and the CPT list is not built for governance. Compliance officers cannot answer questions like how many drafts are stuck in review or how many policies have not been touched this year by scrolling a standard post-type table.

SleekView reads the document CPT, workflow_state taxonomy, owner ID, and revision counts and exposes them as one sortable grid. The default admin keeps its per-document editorial role, the table becomes the governance surface that audits and reviews can actually start from.