Recruiters & employers
Prepare & Depart

Anti-Trafficking Awareness Resources

Rights information arrives too late when workers only learn the red flags after something has already felt wrong.

A worker may not know whether a recruiter’s request is normal, whether a fee is allowed, or whether a threat about their job or visa should be reported. They may stay quiet because the situation feels confusing, not because they accept it. The employer may have policies, but the worker needs anti-trafficking awareness resources before risk appears.

Why red flags are hard for workers to name

Workers often arrive with limited local knowledge and a strong desire to keep the job. That can make them vulnerable to pressure, misinformation, debt, withheld documents, threats, or illegal fees.

If the only rights information sits in a long policy, workers may not recognize a problem early enough to ask for help.

A worker can sense that a situation is unfair but still not know what to call it. Without plain examples, reporting paths, and language support, the safest choice can feel like silence.

Why anti-trafficking awareness resources need to be practical

A useful page does not lecture workers. It explains warning signs, rights, fee rules, document safety, wage protections, and who to contact.

It should also make clear that asking a question is allowed before the worker is certain something is wrong.

How to build it

Seven steps inside SumHubs

01
Start by confirming approved anti-trafficking, fee, wage, and reporting language with compliance or legal leadership.
02
Put rights information, red flags, official contacts, and reporting paths in the Resource Library.
03
Add an FAQ for questions workers may be afraid to ask, including fees, threats, passports, deductions, housing pressure, and retaliation.
04
Translate critical guidance into worker languages.
05
Make emergency and confidential reporting paths visible without forcing workers through a supervisor.
06
Review the content before each recruitment cycle.
07
Pilot with one worker group and measure one number: how many workers can correctly identify where to report a concern.

You don't have to start from a blank page.

You do not have to build this from a blank page. This solution exists as a pre-built template, free to start and adapt in an afternoon. If you would rather see it with your own rights language, reporting paths, and worker languages first, request a sample hub and we will build one for your institution.