WP Document Revisions stores documents as a document custom post type with a workflow_state taxonomy (typically Draft, In Review, Final, Archived) and a document owner stored as the post author or a custom meta. Every save creates a real WordPress revision, so the wp_posts table accumulates a long version history per document. The default admin lists documents in a standard post-type table, but governance questions like how many drafts are stuck in review or which owner has the heaviest queue need a separate report.

SleekView reads the document CPT plus its revisions and workflow taxonomy, joining with users for owner-name resolution. Charts adds the dashboard pass: total documents KPI, workflow-state donut, owner-load bar, and modified-cadence area.

Document-controlled environments like compliance, HR policy, association governance, and regulated industries are where this matters most. Audit trails are the value of WP Document Revisions, but trails are only useful if someone can read them at a glance.

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: a compliance officer cannot answer questions like how many drafts are stuck in review or how many policies have not been touched this year by scrolling a CPT list. SleekView already exposes the document CPT, its workflow_state taxonomy, revision counts, and modified timestamps as a sortable grid.

Charts adds the four-card dashboard that turns the audit trail into a governance surface. Compliance reviews stop being a CSV-export ritual and start being a one-page conversation around a live dashboard. The WP Document Revisions admin keeps its editorial role for the per-document approve-and-publish flow.