HTML Forms already has the data. Every submission lands in hf_submissions with id, form_id, JSON-encoded data, ip_address, user_agent, referer_url, and submitted_at on every row. Each form itself lives in wp_posts as the html-form custom post type, so resolving form_id to a readable form name is a normal join. The default Submissions tab shows a paged table with field columns and a timestamp.

SleekView Charts reads the same hf_submissions table and turns it into chart cards on a single dashboard. A Number card counting submissions for this month from submitted_at, a Donut splitting submissions by form_id across the forms you publish, a Bar of the top referer_url domains driving traffic to forms, and an Area chart of daily submissions across the selected range. Each card is a saved query against the live table, not a screenshot.

This is not an HTML Forms replacement. The plugin still owns the form rendering, the actions on submit, and the email notifications. SleekView Charts adds the reading layer site owners actually need: submissions per form, referrer split, daily trend, and per-field dimensions from the JSON data column on one screen, scoped per role, embeddable on a frontend page for stakeholders who should not need admin access.

HTML Forms stores data well. Every submission lands in hf_submissions with form_id, JSON-encoded data, ip_address, user_agent, referer_url, and submitted_at on every row, and each form lives as a normal html-form post in wp_posts. The reading side is still the per-form Submissions tab, so seeing total volume alongside per-form split, top referrers, and daily trend usually means clicking through several screens or exporting CSVs.

SleekView Charts reads the same hf_submissions table and turns it into chart cards on a single saved dashboard. Marketing sees the daily area and the top-referrer bar. Support sees the submissions-by-form donut.

Admins see the spike alerts and per-form volume. HTML Forms keeps owning the form rendering and the actions on submit; SleekView Charts adds the flexible reading layer that an actual team can share, scope per role, and embed on a frontend page for stakeholders who should not need admin access.