BPO
Content moderation
Moderation of listings, reviews, profiles and user-generated content in Portuguese and other languages.
What is delivered
Policy enforcement with calibrated examples and periodic review
Escalation paths for legal and safety cases
Moderator wellbeing support, planned rather than improvised
Why does the variant matter in moderation?
Because offence is contextual and the variant changes the context. There are ordinary, harmless words in Portugal that are insults in Brazilian variants, and the reverse, and the same applies to Angolan and Mozambican expressions. A single lexicon applied to every market produces errors in both directions, and both are visible to the user.
Then there is political and sporting context, which is intensely local. References that in one market are ordinary rivalry talk are in another a signal of organised hate content, and assessing that requires knowing what happened in that country in recent months. No durably written policy captures it.
And there is humour. Irony and sarcasm invert the literal meaning and are more frequent in some platform cultures than others. A native moderator recognises the ironic register; a classifier trained on another market takes it literally, and this is the most consistent automated failure in Portuguese.
How is the operation structured in layers?
Automation handles the obvious volume at both extremes: what unambiguously violates and what is clearly legitimate. The first human layer handles what falls in between, against written policy with examples. The second handles escalations and unprecedented cases, and is also who proposes policy changes.
The middle layer is nearly always the largest and it is where quality is decided. Under-sizing it produces two visible consequences: decision times lengthening and consistency falling, because people under queue pressure decide less uniformly, and inconsistency is more visible to the user than an isolated error.
There is also a frequently forgotten function: someone accountable for keeping policy coherent as borderline cases stretch it. Without it, policy diverges from practice within months and decisions stop being defensible in writing, which is exactly what the regulator will ask for.
Which regulatory obligations apply?
The Digital Services Act requires each decision to be reasoned to the affected user, with the facts, the basis in policy or law, and the available means of appeal. A generic reasoning reused across thousands of cases meets the form and does not meet the obligation.
It also requires an accessible, free internal complaints mechanism handled by someone who did not take the original decision, and periodic transparency reports with numbers by category, means used, average decision time and appeal outcomes. Granularity rises with platform size.
The operational implication is that the record system has to be designed to produce these reports rather than adapted afterwards. Operations that stored decisions without structured categories discover that reconstructing the categorisation retrospectively is expensive and frequently impossible to do accurately.
How is moderation quality measured?
By agreement between reviewers on the same cases, before anything else. If two experienced moderators disagree on twenty per cent of decisions, the policy is ambiguous, and no amount of individual training fixes an ambiguous policy. It is the first number to measure and the most frequently ignored.
Then, overturn rate on appeal separated by content type. Successful appeals clustered on one type indicate insufficient policy or training in that type, not a moderator problem, and are fixable in days unlike almost everything else in this field.
What we do not measure in isolation is decisions per hour. It is the easiest metric to obtain and the one that most quickly degrades quality when it becomes the target, because the fastest way to decide quickly is to stop reading carefully precisely the cases that need care.
How is the team protected?
Let us be direct about what the role involves: regular exposure to disturbing content. The operation has mandatory rotation between queues of differing exposure, daily time limits on the most severe queues, and guaranteed breaks that do not depend on the queue being empty. These are operational rules, verifiable in a report.
There is confidential psychological support available, without using it being visible to the direct line manager. Support that exists but whose use is recorded against performance goes unused, and the operation ends with a benefit on paper and the same risk in practice.
And there is interface design: blurring options, muted playback by default, and review on still frames rather than continuous video where the decision does not require otherwise. These measures have a measurable effect on attrition and, in consequence, on decision consistency.
Which delivery model is appropriate?
For Portuguese market content, onshore moderation with native European-variant moderators, inside the European Economic Area and with no transfer instrument. It is the model producing the best agreement and the only one we recommend for content that may involve sensitive data.
For the Brazilian market, an operation in São Paulo with native moderators of that variant, under standard contractual clauses and an impact assessment where it handles European users' data. Management, policies and reporting are shared; moderators and rubrics are not.
For out-of-hours coverage, the global network covers the European night on local daytime hours. That is preferable to night shifts for work of this nature, because exposure to disturbing content in the small hours worsens an occupational risk that is already significant.
Where content moderation can be run from
Not every delivery model suits every service. The table shows only those that make sense for this work, with the data residency position of each.
| Model | Where | When it makes sense | Personal data |
|---|---|---|---|
| Onshore Portugal | Lisbon, Porto, Braga, Coimbra, Aveiro, Faro, Funchal and Ponta Delgada | When data cannot leave the EEA, or when the end customer is Portuguese | Stay inside the EEA. No transfer. |
| Brazil | Sao Paulo | When scale and cost are the priority, or the market served is Brazilian | No adequacy decision. Requires standard contractual clauses and a transfer impact assessment. |
| Global network | Uzbekistan, the Philippines, Poland, the Dominican Republic, Mexico, Colombia, Turkiye and Africa | When you need continuous cover, specific languages or the lowest cost | Poland is inside the EEA. The others require standard contractual clauses. |
The data column describes the applicable framework and is not legal advice. The detail is in international data transfers.
This service carries a variant decision
Are you serving customers in Portugal, in Brazil or in both? The answer changes the operating design, the scripts, who reviews quality and how results are reported.
Related services
- Customer supportContact centre operations in Portuguese, English and more than thirty languages, across voice, email, chat and social.
- Technical supportLevel 1 and 2 support for software, telecoms and hardware products, with structured escalation.
- Back officeAdministrative processing, document management, data entry and internal operations support.
- Finance and accountingAccounts payable and receivable, reconciliations, invoicing and close support, alongside your own accountants.
Frequently asked questions
Are moderators native to the market?
They are, of the variant they moderate. It is the requirement that most affects decision quality on borderline cases.
Do you cover the African variants?
We do, with moderators from Angola, Mozambique and Cape Verde, and with a local glossary maintained separately from the European standard.
Who writes the policy?
Usually the client, with us contributing the borderline cases the operation encounters, which is where policy needs stretching.
How does appeal work?
Handled by someone who did not take the original decision, reasoned, and within an agreed deadline. An appeal reviewed by the original decision-maker is not an appeal.
Do you produce the transparency reports?
We produce the data underpinning them, structured from the start. Publication is the platform's, which is who holds the obligation.
What support exists for the team?
Queue rotation, daily exposure limits and confidential psychological support. These are operating conditions rather than benefits.
What volume do you support?
From a few thousand to millions of items a month, with the balance between automation and the human layer shifting with scale.
Is automation alone enough?
Not on borderline cases, which are precisely the ones generating complaints, appeals and reputational risk.
Let us look at the numbers for your case
Tell us which processes you want to outsource, in which languages and at what volume. We come back with a euro estimate and an operating design, with no commitment.
We reply within 6 hours on working days. If you would rather write: info@corpshore.solutions