TAKUZA
Building a public site and staff dashboard for an anti-trafficking network, where some features handle reports about people who may be in danger.
Case study · 2026 · 1 month
The problem
TAKUZA, a network of 45 Catholic congregations across Zambia's 11 dioceses, needed a site its staff could update without a developer. It also needed safe ways for the public to report concerns and for its team to file field reports, where a careless design could expose someone at risk.
The solution
A public site that reads all its content from a database, a separate staff dashboard on its own subdomain, and submission flows designed so sensitive details never leave the system.
A site the team can run
The public site covers TAKUZA's story, team, network and youth ambassadors, along with survivor stories, events, a gallery, downloads and learning pages on human trafficking, safe migration and St Josephine Bakhita. Every page reads from the database. Page text is stored as editable blocks, and staff manage everything from a dashboard on hub.takuza.org, kept separate from the public site.
Designing for sensitive information
Several features handle information about people who may be in danger, so they were built around what could go wrong:
- Anyone can report a concern anonymously.
- Email alerts to staff carry only a subject and a link to the dashboard, never the report itself, because email sits outside the system.
- Team members file field reports with attachments using a five-digit code issued from the dashboard. The code screen is protected against guessing, and attachments are stored privately and served only to signed-in staff.
An assistant with limits
Gina, the site assistant, answers common questions from a script and only passes free-typed questions to a language model. She is designed never to call an offer of work or travel safe, never to take a report, and never to make up a phone number, because a wrong answer here could send someone into danger.
Built from their own material
TAKUZA supplied about 200MB of content, including photos, reports and their brand palette. The palette was adjusted by role rather than copied colour for colour, so buttons and text meet accessibility contrast standards.
Outcomes
Staff update every page and record from the dashboard without a developer
Concerns can be reported anonymously
Report contents never leave the system by email
Field reports and attachments are restricted to signed-in staff
The assistant answers common questions without taking reports or giving unverified contact details
Next case study
AccommoZED