Coordinator Panel

 

Create Transport Agent

At least 8 characters.
Region is fixed to your own -- set automatically. A biker covering more than one district can be assigned to all of them here.
Scoped to the district(s) selected above -- check all this TA covers, or add one not listed yet.
Labs on record in your region -- check all this TA delivers to, or add one not listed yet.
A hub is a facility that also relays traffic onward -- scoped to the district(s) selected above -- check all this TA delivers to, or add one not listed yet.
Which days this TA is expected to move at all. Leave all unchecked for no fixed schedule (never flagged). A pickup logged on an unscheduled day is flagged for your review in Pending Review, never blocked.

Your Transport Agents

Login IDNameRegionDistrictsFacilitiesActions

Pending Review

RegionSubmittedByTripTracking IDPhotoFlagsActions

Hub Shipments

Shipments that have been sitting at a hub for over 3 days with nobody picking them up further. Drops off this list on its own after 7 days.

Recently Rejected

Records a coordinator rejected -- shown here so a data clerk who entered or corrected one can see what happened to it, even though they can't approve or reject it themselves. Drops off this list on its own 24 hours after being rejected.
RegionRejectedBySubmitted byTripTracking IDNotes

Create a Record

For a trip reported to you by phone or in person -- not something a transport agent already submitted from the mobile app. This goes into the same Unverified Data queue as a mobile submission, flags and all.

What's being moved

Narrows the pickup/drop-off place lists and the transport agent list below to this district -- leave on "Any district" to see every place and TA in the region.
Select the transport agent who actually moved this, if someone else's trip is being recorded on their behalf (e.g. reported to you by phone). Leave on the default if you handled it yourself. Picking a TA narrows the health-facility, hub, and lab lists below to just the place(s) that TA is assigned to.

Pickup

Drop-off

Quantity of what was transported

Finishing details

Capture Rejection

For a rejection discovered after the original drop-off was already recorded -- e.g. a hub or lab notices spoiled, mislabeled, or clotted samples days later. This creates a new, zero-distance record on the same tracking ID, purely to capture the rejection -- it doesn't change what's already recorded as delivered.

Where the rejection was found

Defaults to your own region -- change it if the rejection was found elsewhere (e.g. on a batch that was referred across regions).
Every rejection is tied to the Spoke site that originally collected the sample -- this is what the rejection gets reported against, not the hub/lab below.

Which delivery

What was rejected

This is what the rejection gets reported against -- same as "Date of deposit" for a normal pickup/drop-off -- not the date you happen to be entering this.

TA Performance

Transport AgentDistrictsLegsApproval Rate Trips (verified)Items MovedAvg Transit Photo ComplianceStalledOpen FlagsOn-Duty Hours