Mobile app for reporting gender-based violence incidents in Fiji

In Fiji, a person facing sexual violence, intimate partner abuse, coercion or online harassment often needs two things at once: a safe way to record what happened and a reliable route to help. A mobile app can connect those needs, but it should strengthen existing response services rather than become another barrier between a survivor and trained support.

Design must reflect shared phones, uneven coverage outside Suva and the outer islands, and Fiji’s multilingual communities. iTaukei, Fiji Hindi and English should be available from the outset, while low-bandwidth SMS and voice options remain essential. Sensitive information must never depend on a stable data connection or a notification visible to someone else.

For Australian funders and technology partners, the opportunity is substantial through Sydney and Melbourne’s digital-health, development and Pacific engagement networks. Australian teams know the value of mobile-first services, yet expect accessible pathways, trusted referral partners and clear rules about emergency escalation.

An app should be treated as a coordinated public-service response, not simply a technology product. Its value depends on service availability, trained caseworkers, referral agreements and continuous risk management. The test is whether it helps a survivor reach appropriate assistance faster and more safely, with or without an app.

Why a reporting app must sit within a response network

GBV reporting is rarely a single event. Someone may need emergency help, a confidential conversation, documentation for legal or safeguarding purposes, or information about local options. The app should let users choose that destination without forcing them to complete a long form before receiving help. The safest channel depends on the person, device and urgency, so each option needs a defined role.

Reporting route	Advantages	Limitations	Appropriate role
Mobile app	Guided disclosure, optional evidence upload, consent-based referrals and service-status updates	Device sharing, data costs, notification exposure and connectivity gaps	Main route for people with a safe device and reliable access
SMS or USSD	Works on basic phones and weak connections; supports brief updates	Limited media and identity checks; weaker session protection	Fallback, callback and scheduled safety check-ins
Phone or staffed hotline	Human assessment, empathy and support for complex cases	Wait times, staffing limits and possible after-hours gaps	Urgent escalation and an alternative to digital reporting
In-person service	Complete assessment and immediate physical support	Travel, stigma, safety concerns and operating hours	Community, health, shelter and specialist pathways

Each channel has a role, and no channel should be the default for every incident. Messaging apps such as WhatsApp may expose notifications or chat history on a shared device, so sensitive exchanges need clear policies and user-controlled privacy settings.

Designing a survivor-centred reporting journey

A trauma-informed journey begins with three clear choices: get help now, report an incident, or understand the available options. Questions should be plain, optional and proportionate. Ask only what is needed for safety or referral, allow users to skip questions, and never require graphic detail, proof of harm or a minimum word count before access to assistance.

Consent should govern every handoff. If identity is needed for a referral, explain why before collection; a promise of anonymity would be unsafe when a service requires contact. The interface should include a quick exit, app lock, neutral naming, discreet notifications and optional location sharing, with a clear record of what the user has agreed to share.

Localisation is part of safeguarding, not decoration. iTaukei, Fiji Hindi and English should use culturally appropriate wording, while project teams should test everyday labels such as “Get help now” or “Talk to someone” instead of relying on clinical phrases like “incident disclosure”. Audio guidance, screen-reader compatibility, large text and offline draft recovery widen access for people with low digital confidence or disability.

If the model is later adapted for Aboriginal and Torres Strait Islander communities in Australia, participation must be led by local organisations, with community-controlled data and clear authority over consent, storage and access. That principle should inform the Fijian design without treating communities as uniform or importing a single governance model.

Turning a report into coordinated support

The referral engine should use a verified directory of Fiji-based police, health, counselling, shelter, legal-aid and specialist gender-based violence services, including opening hours, eligibility and after-hours options. The app must distinguish information sharing from emergency escalation and show whether a report has reached a person, an automated queue or simply an information page.

Each consented referral needs a case reference, a named receiving service and a closed-loop status update. Information should be proportionate to the request, and no report should be marked resolved merely because it was submitted. Service agreements must address capacity, response times, failed handoffs and safe follow-up rather than presenting a directory as a guarantee of support.

For multi-stakeholder coordination, the ICTD-ASP platform offers a useful bridge among development agencies, governments, service providers and technical partners. Jointly launched by the Asian Development Bank and International Telecommunication Union, it can help convene referral partners, share project learning and build capacity around digital safeguards.

Australian contributions should be matched to the local market. State and territory governments fund many response services, while Commonwealth programmes, legal aid bodies and nongovernment organisations operate across borders. A national Australian partner therefore needs jurisdiction-specific referral knowledge and agreements rather than assuming one uniform service system.

Protecting privacy, safety and trust

Security controls should match the sensitivity of the data. Collect only necessary details, encrypt traffic and stored records, use multifactor authentication for staff, log access, and set retention and deletion rules. Where Australian organisations handle the information, the Privacy Act 1988 and Australian Privacy Principles provide a useful assurance baseline alongside applicable Fijian requirements.

Mandatory reporting and safeguarding duties need documented escalation paths based on applicable law. Automatic referral to police can expose a survivor or increase danger, so decisions should follow trained assessment, explicit exceptions and locally defined rules. The same applies to child protection, imminent harm and cases requiring specialist clinical input.

Cyber incidents, lost devices, insider misuse, service overload and retraumatisation are operational risks. Response plans should cover notification duties, vendor failure, staff wellbeing and continuity of urgent referrals. Australian buyers commonly require documented cyber assurance, incident playbooks and evidence that subcontractors understand their responsibilities.

A practical path from pilot to trusted service

Start with survivor-led discovery rather than a finished feature list. Pay Fijian survivor organisations, disability advocates, community leaders and front-line workers for their expertise, and test concepts with both Suva-based services and providers serving outer islands. Safety experts should review the reporting flow before sensitive data is collected.

Build a deliberately small first release covering guided reporting, offline drafts, consented referral, callback and SMS fallback. Test it on low-cost Android devices, shared handsets, weak networks, outages and all three main languages. Australian grant and procurement processes commonly assess credible consortia, matched co-funding and measurable outcomes, allowing vendors to contribute skills while local organisations retain ownership of service relationships and data.

Measure completed, safe handoffs, time to assistance, referral acceptance, abandonment, user-reported safety and equitable access across locations. Publish governance arrangements and learning, and include an independent safety review in every expansion decision. Scale only when referral partners can absorb demand and no unacceptable safety trade-offs have emerged. The practical takeaway is a staged, survivor-governed service in which completed support and survivor safety—not app downloads or raw report counts—determine whether expansion is justified.