Report a bug the team can actually reproduce.

You create the drop, pay, and hand the parcel to a rider or hub. Recipients do not need their own login for pickup PIN.

1. Sign up, choose Sender, complete profile (name, phone, photo if prompted).
2. Create a drop: origin and destination cities, pickup and delivery addresses, parcel size/weight, recipient name and phone.
3. Complete payment / escrow. Confirm the drop appears as awaiting pickup with a tracking code.
4. At handoff, show the QR or give the PIN to the field agent or hub. Do not invent a status change yourself.
5. Watch tracking move: pickup → origin hub → in flight → destination hub → out for delivery → delivered.
6. After pickup, rate the rider if asked. Confirm the recipient can get the delivery PIN.

• Wrong city pair, missing recipient phone, or fare that doesn’t match the route.
• QR/PIN that the agent or hub cannot scan or accept.
• Tracking stuck, jumping states, or never showing in flight after the hub says it left.

You pick up from senders, drop at the origin hub, collect from the destination hub, and deliver to recipients. KYC must be approved before live jobs.

1. Sign up as Field agent. Submit KYC (NIN, selfie, vehicle/licence docs). Wait for ops approval if you cannot see jobs.
2. Turn on location. Open available job cards; claim a pickup that matches your city.
3. Navigate to the sender. Scan their QR or enter the PIN. Capture the required parcel photo if the app asks.
4. Take the parcel to the origin hub. Complete the hub handshake (hub scans you, or you scan/PIN as the app instructs).
5. For last mile: collect from the destination hub (scan hub QR / handshake), then deliver to the recipient using PIN only — no recipient QR.
6. Confirm the job leaves your list and earnings/payout views still make sense.

• Jobs you cannot claim, maps that point at the wrong place, or camera freeze on scan.
• Handoff rejected with a vague error — copy the full message and the drop ID.
• Location permission denied still letting you “complete” a scan (or blocking you with no explanation).

You are the legal choke point: intake, airway bill, flight dispatch, arrival, and release. Do not skip AWB before marking in flight.

1. Complete hub readiness: personal profile, KYC (NIN + live selfie), site details, GSA licence, indemnity bond. Intake stays blocked until these are in order.
2. Inbound from field / sender: Intake tab → scan sender or agent QR (or PIN). Capture condition photo, then accept custody.
3. Awaiting AWB: on Manifest / AWB, attach the GSA airway bill and photo. Parcel should show as Scanned In, still at origin hub.
4. Mark in flight only after AWB is captured. If AWB is missing, the app should show an inline error — not freeze.
5. Arrival: intake from airline, capture final condition photos.
6. Release: show QR for a last-mile agent, or use tracking + sender PIN for a recipient pickup (no QR for recipients).

• Readiness gate wrong (you’re blocked after docs, or allowed in with empty site/GSA).
• Intake queue mixing inbound-from-field with inbound-from-flight incorrectly.
• Able to mark in flight without AWB, or AWB saved but Manifest still says Awaiting AWB.

Recipients usually do not run the full app as their own role. They confirm delivery or collect at a hub with a PIN the sender shares.

1. Get the tracking code and delivery PIN from the sender (SMS, WhatsApp, or in-app share).
2. If a rider delivers to the door, give the PIN when asked. Confirm the parcel is yours and note obvious damage.
3. If collecting at the hub, the hub should ask for tracking code + PIN — not a QR scan on your phone.
4. After success, the sender’s tracking should show delivered and escrow should be able to release.

• PIN rejected when it matches what the sender sees.
• Hub insisting on a QR you don’t have.
• Delivered in the rider app but still in transit for the sender.