The TranslatePress AI add-on (Automatic Language Translator) extends TranslatePress with DeepL and Google as automatic providers. It writes every machine translation into the same per-language trp_dictionary_* tables that TranslatePress uses for human edits, with the translated_by column set to a known value for automatic and the status column initialized to a machine state. A separate trp_machine_translation_log table records provider, characters used, and timestamps for billing reconciliation.

That layout is great for converting machine rows into human-reviewed rows inside the visual editor, and weak for any kind of management reporting. The default TranslatePress admin lists strings one row at a time and shows a small character counter in the AI settings page, but it does not answer "how many machine rows are still waiting on review" or "which language has the largest auto-translation backlog" without SQL across each dictionary table.

SleekView Charts reads trp_dictionary_* joined to trp_machine_translation_log and renders four cards on top of that. A Number for total machine-status rows still awaiting review. A Pie split by target language. A Bar of machine vs human counts per language. An Area of automatic translations created per week from the log. TranslatePress AI keeps owning the provider call. SleekView only reads what is already in the database.

TranslatePress AI fills the dictionary tables faster than any human team. That speed is the entire point of the add-on, and also exactly why it needs a reporting layer. Machine translations marked as automatic still ship to live users and to search engines while they wait for human review.

The default admin shows one string at a time and the AI settings page shows a character counter, but neither answers "how many machine strings are still in the queue" or "how fast is the team converting machine to human status" without SQL. SleekView Charts reads the same trp_dictionary tables and the trp_machine_translation_log and renders four cards that answer those questions in one glance. The data is already correct because TranslatePress AI wrote it.

Charts just gives the team a dashboard to look at it. Unreviewed AI on production pages is a brand risk, and a live backlog dashboard makes it visible.