How Warka Works

Warka works by combining structured data, verification, and multi-channel access. At the core is a standardized listing model that captures identity (official name and codes), hierarchy (region-to-kebele administrative structure), location (address and geo-coordinates), contacts (phone, website, social channels), hours of operation, and services (name, description, steps, documents, fees, and SLAs).

For citizens, Warka provides fast discovery: search by office name, service name, category, or location; filter by region, city/zone, sub-city, woreda, and kebele; and view results in list view or map view. Each listing is designed to answer “Who are they?”, “What do they provide?”, “Where are they?”, and “What should I bring or do next?”

For government offices and businesses, Warka provides a secure management experience to claim a listing, submit evidence, publish service information, and maintain accuracy over time. Updates are tracked, reviewed, and audited to protect the public from misinformation and to protect institutions from impersonation.

Across all channels, Warka prioritizes low-friction access. Users can get the essentials via USSD or SMS, and open richer pages on web or mobile when connectivity allows. Payment-enabled experiences – such as premium verification for businesses or value-added services – are supported through Telebirr.

  • Discovery: search + filters + map + multilingual content.
  • Trust: evidence-based verification + badge system + moderation + audit logs.
  • Access: web + mobile + USSD + SMS + Telebirr Mini App.
  • Continuous improvement: user feedback, office updates, and transparency reporting.

Transparency Report (quarterly data quality & moderation stats)

Warka publishes a quarterly Transparency Report to show how well the directory is performing, where improvements are needed, and how moderation decisions are made. This report exists to build public confidence and to provide institutions with objective feedback on data quality and service clarity.

Each report summarizes listing coverage and completeness (for example: percentage of listings with verified phone numbers, geo-coordinates, office hours, and service steps) and tracks change over time. We also publish moderation statistics: how many updates were submitted, how many were approved, how many were rejected (and why), and how many listings were flagged for potential issues such as duplication or impersonation.

We disclose response times and SLA performance for review workflows, including average verification time, average correction resolution time, and backlog status. Where applicable, we segment data by channel (web, USSD, SMS), geography, and sector to show equity of access and to identify regional gaps.

To protect privacy and security, the report presents aggregated metrics only. Sensitive evidence artifacts (IDs, letters, private contact details) are not published. The report is designed to be actionable: it includes priority improvement themes and commitments for the next quarter.

  • Suggested metrics to publish: coverage by region/sector; completeness scores; verification volumes; correction volumes; SLA performance; top report reasons; duplicate resolution counts; and user satisfaction trends.
  • Report cadence: quarterly, with a public archive and version history.

Changelog & Release Notes

The Changelog is the public record of how Warka evolves. It lists major improvements, new features, bug fixes, and policy updates in a predictable, transparent format. This helps institutions and partners understand what changed, why it changed, and whether any action is required on their side.

Release Notes are grouped by version and date and include clear labels: “Added,” “Improved,” “Fixed,” and “Deprecated.” When a change affects data standards, verification requirements, or user workflows, we provide migration guidance and a reasonable transition period.

We differentiate between platform updates (search, maps, USSD menus, performance) and governance updates (policy changes, moderation rules, evidence requirements). Each entry includes a short rationale focused on citizen impact and trust.

For accountability, the changelog also includes incident postmortems when applicable, summarizing the root cause, impact, mitigation steps, and preventive controls.

  • Example entries: new region filters; improved Amharic search; USSD menu redesign; new badge logic; updated evidence policy; security patches; and performance improvements.
  • Recommended format: version number, release date, summary, detailed items, and known issues.