articles
Approval log
Per-article review, the review trail, batch approval, and how to export the log.
Quibo writes the draft; a person decides whether it publishes. The approval log is the record of that decision and of everything that led to it. It is what lets you show, if asked, that AI-generated content on your site went through human review under your editorial responsibility. Background on why that matters is on AI Act and your blog.
Review one article
Open any article under Articles. The Review trail panel at the bottom of the page shows:
- whether the article has been reviewed, by whom and when;
- every logged action, newest first, with the person and a short summary of what changed;
- the Provenance block: provider, model ids, cover image model, pipeline version, generation time, keyword and language.
There are several ways to record your approval:
- Mark as reviewed: records the review without publishing or scheduling anything. Use it when you have read the article and want to keep it in Ready for later.
- Schedule: picking a date on the article page, or dragging the article onto the calendar, records the review and the schedule.
- Publish now: records the review and the publish.
- Batch approve on the calendar records the review for every article it schedules.
The first of these on an article stamps it as reviewed by you. Later actions are still logged, but the reviewer does not change.
What is logged
| Action | When | What the entry contains |
|---|---|---|
| Edited | Save draft, or save the FAQ | Which fields changed (meta title, meta description, body word count before and after; FAQ item count) |
| Reviewed | Mark as reviewed | Who and when |
| Scheduled | Schedule button, calendar drag and drop, batch approval | The scheduled time; whether it came from the calendar or from a batch |
| Unscheduled | Unschedule | Who and when |
| Published | Publish now, the scheduler, or "Mark as published" on a stuck article | The published URL; whether the scheduler did it (attributed to "system") or it was forced manually |
| Refreshed | Refresh this article | The original it replaces, with its title and slug; logged on the new draft |
| Regenerated | Retry generation on a failed article | The pipeline stage it resumed from |
Entries are append-only. Nothing in Quibo edits or removes an entry. Each entry carries a snapshot of the article it refers to (title, slug, site, public URL and provenance), so the log stays complete after the article body is removed 30 days after publishing, after the article is deleted, and after a site is removed. Export it any time as CSV or JSON.
Batch approval
Per-article review is the default on every plan. Batch approval (the Batch approve button on the Calendar) schedules every Ready article at once on a cadence you pick. It is included on Agency, Business and lifetime tiers 4 and 5. On other plans the dialog opens, but confirming it shows a message pointing to the plans page and asks you to schedule each article from its page.
Batch approval records your approval for every article in the batch and writes one Scheduled entry per article, marked as coming from a batch with the batch size. Use it for drafts you have already read in the editor. Approving a whole month without opening the articles is not editorial review, and the log will show that pattern.
Export the log
Owners and admins can export the whole organization's log, or one article's log, as CSV or JSON:
- From an article page: the Export approval log link in the Review trail panel downloads that article's entries as CSV.
- For everything: open Settings, Privacy & data and use Export approval log. Pick CSV or JSON and, if you want, a date range; the file downloads straight away. Owners and admins only.
CSV columns: article_id, title, site, url, action, user_email, created_at, changes (JSON). Exports are limited to 10,000 rows, oldest first; narrow the date range for larger histories.
Keep an export with your editorial records for each publishing period. Together with the provenance block and the markup on the published page, it documents the whole chain from generation to publication.