Content Moderation Workflow Metrics
This dataset provides detailed operational metrics from social media content moderation workflows, including case resolution times, escalation patterns, review outcomes, and moderator workload statistics. It is designed to support process optimization, compliance audits, and strategic improvements for moderation teams operating in dynamic digital environments.
Sample rows
preview · 8 of 50 rows · all 16 columns| case_idstring | moderator_idstring | resolution_time_minutesfloat | escalatedboolean | review_outcomestring | content_idstring | team_idstring | case_created_atdatetime | case_resolved_atdatetime | escalation_reasonstring | policy_violationsstring | moderator_workload_cases_openinteger | moderator_workload_cases_closed_todayinteger | moderator_shift_datedate | compliance_flagboolean | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| A7k9Zx_8 | MOD-001 | 30.45 | false | approved | CNT-1001 | TEAM-01 | 2024-05-01T08:34:45 | 2024-05-01T09:05:12 | blank | blank | 3 | 6 | 2024-05-01 | true | Routine review, no violations detected. |
| bQ7s8pXv | MOD-002 | 51.28 | true | flagged | CNT-1002 | TEAM-02 | 2024-05-01T09:12:10 | 2024-05-01T10:03:27 | Complex hate speech pattern detected | POL-12,POL-04 | 5 | 3 | 2024-05-01 | true | Escalated for senior review due to sensitive content. |
| HKz_9T8a | MOD-003 | 2.87 | false | removed | CNT-1003 | TEAM-01 | 2024-05-01T10:15:00 | 2024-05-01T10:17:52 | blank | POL-01 | 4 | 7 | 2024-05-01 | true | Immediate removal due to clear violation. |
| J_4kLm7P | MOD-004 | blank | false | pending | CNT-1004 | TEAM-03 | 2024-05-02T11:03:21 | blank | blank | blank | 6 | 2 | 2024-05-02 | blank | Awaiting further evidence from user. |
| vP9aB6sR | MOD-005 | 46.18 | false | flagged | CNT-1005 | TEAM-04 | 2024-05-02T13:14:59 | 2024-05-02T14:01:10 | blank | POL-08 | 2 | 5 | 2024-05-02 | true | Flagged for repeat spam violations. |
| K9zL_7wX | MOD-001 | 5.2 | false | approved | CNT-1006 | TEAM-01 | 2024-05-03T08:00:00 | 2024-05-03T08:05:12 | blank | blank | 4 | 6 | 2024-05-03 | true | No issues found, content is compliant. |
| z7Xn_kl2 | MOD-002 | 35.08 | true | flagged | CNT-1007 | TEAM-02 | 2024-05-03T10:10:25 | 2024-05-03T10:45:30 | Potential copyright infringement | POL-09,POL-11 | 3 | 4 | 2024-05-03 | true | Escalated for legal team review. |
| N4k3B_vM | MOD-003 | 17.17 | false | removed | CNT-1008 | TEAM-01 | 2024-05-03T11:45:00 | 2024-05-03T12:02:10 | blank | POL-02 | 2 | 8 | 2024-05-03 | true | Offensive language detected, removed. |
| M8k7Bv6P | MOD-005 | 27.33 | false | approved | CNT-1009 | TEAM-04 | 2024-05-04T09:00:10 | 2024-05-04T09:27:30 | blank | blank | 5 | 7 | 2024-05-04 | true | Content matches guidelines. |
| B9wK6zQp | MOD-004 | 36.25 | false | removed | CNT-1010 | TEAM-03 | 2024-05-04T12:13:45 | 2024-05-04T12:50:00 | blank | POL-04 | 3 | 5 | 2024-05-04 | true | Harassment policy violation. |
| L_8kZ7mX | MOD-002 | blank | false | pending | CNT-1011 | TEAM-02 | 2024-05-04T14:30:00 | blank | blank | blank | 2 | 1 | 2024-05-04 | blank | Waiting for additional moderator input. |
| Kv9_8LpZ | MOD-003 | 20.25 | false | flagged | CNT-1012 | TEAM-01 | 2024-05-05T09:45:15 | 2024-05-05T10:05:30 | blank | POL-06 | 3 | 6 | 2024-05-05 | true | Flagged for review by policy team. |
| Hk7vN_2P | MOD-001 | 38.17 | false | approved | CNT-1013 | TEAM-01 | 2024-05-05T11:02:00 | 2024-05-05T11:40:10 | blank | blank | 4 | 7 | 2024-05-05 | true | Content is within acceptable guidelines. |
| Q4_9V7xL | MOD-005 | 30 | true | flagged | CNT-1014 | TEAM-04 | 2024-05-05T12:30:00 | 2024-05-05T13:00:00 | Possible misinformation | POL-10 | 2 | 6 | 2024-05-05 | true | Sent to fact-checking team. |
| T_5rP2kV | MOD-004 | 12.5 | false | approved | CNT-1015 | TEAM-03 | 2024-05-06T08:10:00 | 2024-05-06T08:22:30 | blank | blank | 5 | 9 | 2024-05-06 | true | Quick resolution, compliant. |
| rJ7kW_6p | MOD-002 | 4.5 | false | other | CNT-1016 | TEAM-02 | 2024-05-06T10:15:00 | 2024-05-06T10:19:30 | blank | blank | 1 | 3 | 2024-05-06 | true | Content moved to archive for further review. |
| mK7zL_5x | MOD-003 | 33.75 | false | removed | CNT-1017 | TEAM-01 | 2024-05-06T12:00:00 | 2024-05-06T12:33:45 | blank | POL-03 | 2 | 5 | 2024-05-06 | true | Explicit content removed. |
| X9k_6vPw | MOD-005 | 8.33 | false | approved | CNT-1018 | TEAM-04 | 2024-05-07T08:30:00 | 2024-05-07T08:38:20 | blank | blank | 2 | 3 | 2024-05-07 | true | Routine verification, compliant. |
| K_8Qv6Xp | MOD-004 | 35 | true | pending | CNT-1019 | TEAM-03 | 2024-05-07T09:45:00 | 2024-05-07T10:20:00 | User appeal request | blank | 4 | 2 | 2024-05-07 | false | Appeal under review, decision pending. |
| Qv9_6PzK | MOD-001 | 15 | false | flagged | CNT-1020 | TEAM-01 | 2024-05-07T11:00:00 | 2024-05-07T11:15:00 | blank | POL-07,POL-02 | 3 | 8 | 2024-05-07 | true | Disinformation flagged. |
What the 50 rows show
from the 50-row sampleMOD-002 (moderator id) stands out: 5 of its 10 rows have escalated = true, against 3 of 40 for the rest.
- 16%escalated = true
- 30.0median resolution_
time_ minutes - 4teams
- 2median moderator_
workload_ cases_ open - 5median moderator_
workload_ cases_ closed_ today
Median 30.0, from 2.9 to 60.0.
- string 8
- integer 2
- float 1
- date 1
- datetime 2
- boolean 2
Columns
16 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 8 columns | |||
case_id | string | Unique identifier for each moderation caseunique | A7k9Zx_8 |
content_id | string | Unique identifier for the content under review | CNT-1001 |
moderator_id | string | Unique identifier for the moderator assigned to the case5 moderators | MOD-001 |
team_id | string | Identifier for the moderation team handling the case4 teams | TEAM-01 |
escalation_reason | string | Reason for escalation, if applicableoptional | Possible misinformation |
review_outcome | string | Final outcome of the moderation reviewapproved · removed · flagged · pending · other | approved |
policy_violations | string | Comma-separated list of policy codes violated, if anyoptional | POL-12,POL-04 |
notes | string | Additional notes or comments about the caseoptional | Disinformation flagged. |
| Numbers 3 columns | |||
resolution_time_minutes | float | Time taken to resolve the case, in minutes0 or more · optional | 30.45 |
moderator_workload_cases_open | integer | Number of open cases assigned to the moderator at the time of this case0 or more · optional | 3 |
moderator_workload_cases_closed_today | integer | Number of cases closed by the moderator on the day this case was resolved0 or more · optional | 6 |
| Dates and times 3 columns | |||
case_created_at | datetime | Timestamp when the moderation case was created | 2024-05-01T08:34:45 |
case_resolved_at | datetime | Timestamp when the moderation case was resolvedoptional | 2024-05-01T09:05:12 |
moderator_shift_date | date | Date of the moderator's shift for this caseoptional | 2024-05-01 |
| True or false 2 columns | |||
escalated | boolean | Indicates if the case was escalated to a higher authority or team | false |
compliance_flag | boolean | Indicates if the case resolution met compliance standardsoptional | true |
Use it for
A social media dashboard
The escalated rate, resolution_
time_ minutes by moderator_ id and a breakdown of review_ outcome. Excel, Power BI or Tableau. Why do 8 of 50 rows have escalated = true?
A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Cases50A7k9Zx_830.45MOD-001bQ7s8pXv51.28MOD-002z7Xn_kl235.08MOD-002
A software demo
Believable cases with content_
id, moderator_ id and team_ id to fill a screen in front of a buyer.
This dataset50 rows16 columns
Yours1,000 rows16 columns
blueprint · content-moderation-workflow-metrics
Behind this dataset
Same schema. As many rows as you need.
These 50 rows came out of a blueprint — 16 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- Each row represents a single moderation case handled by a human or automated reviewer.
- Resolution time is measured in minutes from initial flag to verdict.
- Escalation status is tracked as a binary field (escalated/not escalated).
- Review outcome must be one of: approved, removed, warned, or unresolved.
- Moderator workload per shift is capped at a maximum of 50 cases.
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- content-moderation-workflow-metrics