PSA

The problem

Most of the people using it aren’t technical. Daily operations (members, activities, approvals) had to feel obvious to someone who has never used an admin panel.

From request to approval

How a renewal, rank change or staffing request moves through the association, read by people who have never used an admin panel.

1. 01 · Dashboard

   A leader files a request

   Renewals, rank changes, staffing and other requests all start the same way, from the member’s profile.

   One flow for every request type
2. 02 · Approval routes

   It follows the right route

   Each request type has its own multi-level route, set up by the association, showing people and positions by name, never by ID.

   Configurable · multi-level
3. 03 · Mobile app

   Reviewers decide on the go

   The next reviewer gets a push notification and approves from the app’s reviews inbox, even with a weak connection.

   Push · offline-first
4. 04 · Member record

   Everyone sees where it stands

   The request reads as a timeline with plain states, and once approved the member’s record updates, down to their digital ID card.

   Timeline · digital ID with QR

Key decisions

1. 01

   Arabic first, right-to-left included, with English (and French on the website), so leaders work in the language they think in. Approvals read as a timeline with plain states, and routes show people and positions by name, never by ID.

2. 02

   Every scout gets a digital ID card, designed from a written spec: built from their existing profile, coloured by position, with a QR code of their scout ID, PNG and PDF export, and an Add-to-Wallet client.

3. 03

   The mobile app is offline-first: encrypted sign-in storage, a biometric lock, cached profiles and an offline check-in queue that syncs later, plus push notifications for reviews.

Outcome

About 2,000 members use the system for daily operations. I built it as a volunteer to bring the association online.