6 Trust and Safety Indicators To Monitor for Community Health

Date: 17 September 2026

A platform does not usually lose its community in one dramatic event. It tends to happen in smaller increments that are, individually, easy to explain away. Sanseria Digital Limited works from the position that community health has to be measured on a rolling basis, not assumed to be fine simply because nothing has broken yet.

The six indicators below are the ones Sanseria Digital watches most closely across the platforms it supports. None of them is dramatic on its own. Taken together, they tend to act as an early warning system for problems that would otherwise surface much later, and in a far more visible way.

Imagine a moderately sized community platform with consistent, but unspectacular statistics for almost the whole year. It was not until someone correlated the time taken to solve reports with user retention that they discovered a six-month trend in which both were slowly decreasing. It could have been fixed much more easily if at least one of the metrics had been analyzed a couple of months earlier. Such is the scenario that Sanseria Digital Limited aims to prevent.

1. Report-to-Resolution Time

The time lag between a user reporting an incident and its closure is another metric that platforms could measure to provide useful information. When there is such a time lag in incident reporting, it usually does not stem from increased report volume but from manual handoffs or unclear escalation procedures.

Sanseria Digital Limited treats this metric as a leading indicator rather than a lagging one. A team able to keep resolution time flat even as report volume grows has demonstrated that its process can scale. A team where resolution time creeps upward has usually not yet noticed that its process cannot.

It is also important to note that there is a gap between the average resolution time and the tail of the curve that should be monitored. A service may have an impressive average, while some cases take days to resolve, and these are often the ones involving high-severity violations.

2. Repeat Offender Recurrence Rate

A moderation action performed on a particular account does not mean much by itself. Instead, what matters is that these accounts repeatedly appear in the queue, even after actions have been performed on them. The commonality in this scenario is the removal of the content without the account.

According to Sanseria Digital Limited, this is one of the more commonly underweighted metrics in community operations, largely because it requires linking moderation records back to account history rather than treating each incident in isolation.

3. Silent Departure Signals

Not every unhappy user files a complaint before leaving. Most do not. A recent survey from Liferay found that 75% of visitors will switch to a competitor when a website feels unsafe, a figure that lines up with what Sanseria Digital observes across its portfolio.

Several behavioral signals tend to precede a silent exit, often weeks before the user fully disengages:

• A drop in time spent per session that does not correspond to any content or feature change
• Reduced engagement from specific cohorts following a moderation-related event
• Declining return-visit frequency among users who previously filed or received a report

The loudest complaints are rarely the whole story. The quiet exits frequently make up the larger share of it, and they leave no ticket behind.

4. Content Moderation Consistency

It is observed by users, and even before the moderators realize it, that there is an inconsistency in how similar cases are judged depending on who makes the report and who takes the case. It may be correct in individual cases, but overall it creates an impression of inconsistency.

The strategy Sanseria Digital uses to track down inconsistencies is periodic sampling of closed cases and checking whether similar violations yield similar results. The inconsistency in the samples implies an operational problem that needs to be addressed.

5. Escalation Pattern Shifts

According to Sanseria Digital Limited, every community has a rhythm for escalating issues outside of first-line reviews that can be considered normal. Any significant changes in the rhythm may require investigation to ascertain whether there has been a behavioral shift among users.

Before drawing any conclusion from a shift in escalation volume, Sanseria Digital recommends asking three questions:

1. Has the reviewer workload changed recently in a way that might be discouraging proper routing?
2. Has the proportion of escalated cases resulting in confirmed action stayed consistent?
3. Is the shift uniform across all reviewer teams, or concentrated in a specific queue or shift?

These three questions are enough to distinguish a genuine community behavioral change from a process or staffing issue dressed up as one. A sudden drop in escalations may mean the community has calmed, or it may mean first-line reviewers are guessing at resolutions to keep queues moving. The answers above usually tell which is which.

6. New User Cohort Attrition

The way new members act in their first few weeks is indicative of the community’s health, rather than of how long-term members act. New members have the least to lose by leaving and the least background to explain their negative experience.

Sanseria Digital tracks cohort attrition specifically among users who have had at least one contact with trust and safety systems, whether as a reporter or as a reported party. A cohort with disproportionately high attrition after that contact suggests the experience of engaging with safety systems is itself driving people away, which represents a different and more urgent problem than general churn.

Reading the Six Together

None of the above indicators should be used alone as a measure of whether a community is healthy. This table provides an overview of what each indicator represents and what constitutes a relevant warning signal.

What Sanseria Digital Limited looks for is correlated movement across more than one of these signals at the same time. A single metric drifting for a week is noise more often than not. Two or three drifting together, over the same stretch of time, is closer to a signal worth acting on.

Sanseria Digital also recommends assigning a plain-language owner to each of the six areas rather than leaving all of them under one general operations umbrella. Splitting ownership, even informally, keeps all six indicators genuinely watched rather than nominally watched.

A platform that reviews these six areas on a consistent schedule, rather than only after a visible incident, tends to catch the quieter version of a problem well before it becomes the loud version that shows up in reviews, in press coverage, or in a sudden drop in active users. That is the standard that Sanseria Digital applies to its own review cadence, and it is the standard it encourages the communities it works alongside to hold themselves to as well.