Gallery
The challenge
On a road-freight platform, live tracking is what shippers want most. They want to know where their load is and when the truck will arrive. But a truck's location is also information about the transporter's business and about the driver behind the wheel. Trucking-sector advisers in the region stress written disclosure and consent before GPS data and driver performance are collected. On many freight platforms that consent never becomes part of the system. It is a WhatsApp message, a PDF in someone's inbox or a line in the terms of service. When a shipper asks to track a transporter mid-trip, or a transporter later asks what they agreed to, nobody can find the answer quickly. Ops staff end up chasing "OK to track" in chat groups while trips are already moving. Zigu needed consent to be an operations object the team can see, check and file, not a conversation that disappears.
Solution
- **Separate consent queues in the admin.** One queue holds tracking-consent requests from the SaaS fleet companies that run their own trucks on the platform. The other holds tracking consents from transporters working through the LaaS side. Each row shows the company, the contact, the type and the status, so staff can see at a glance whose consent is on file and whose is not. - **The document travels with the record.** Every consent row has Download and Upload actions. Staff can attach the signed consent document to the right company and pull it up again when a question comes in, instead of searching email. - **Status, not memory.** Consents carry a status such as Approved. "Have they agreed?" becomes a lookup in the admin rather than a question for whoever handled the onboarding. - **Next to the trips it affects.** The consent queues sit under the same requests area as the transporter trip-request queue. That queue lists shipment ID, shipper, transporter, trip date, location and truck and trailer registration, with Copy, Excel and PDF export. Above it are the LaaS trip boards: available, requested, upcoming, active and completed. - **Roles that match the work.** Company users carry role badges such as Company Admin, Fleet Manager, Trip Planner and Document Verifier, each with Login, Block User and Edit controls. Paperwork like consent and documents can belong to a verifier rather than to whoever happens to be online.
Results
Consent to tracking is kept as a record with its document and status inside the same admin that runs trip requests and company users. Staff can answer "do we have consent from this transporter?" from one screen instead of reconstructing it from chat history.
Related project
Zigu: Transporter & LaaS Trip Operations Admin
Zigu operations Admin, built/customized for a client: a LaaS trip marketplace and fleet SaaS for Southern Africa road freight, from open load to completed trip.
View project in portfolio