Field note
What belongs in a ride-hailing export handoff
· Desktop Canvascore
Clients sometimes send every table their warehouse can produce. That slows briefings and raises privacy risk. For app analytics focused on operations, start smaller.
Usually enough
- Trip leg times and approximate pickup/drop zones (to corridor level)
- Cancellation timestamps and reason codes if available
- Partner online/offline intervals
- Vehicle class and city tags
- Flags for known promotions or outages
Leave out of the first drop
Passenger names, precise home addresses, payment instrument details, and free-text chat logs. If a later question needs a narrow extra field, we ask for it after scoping.
Hygiene that saves days
Consistent time zones, one row per leg, and a data dictionary for cryptic status codes. Malaysian fleets often juggle multiple vendor exports; labelling which system produced which file prevents false patterns.
When you contact us, mention which systems you export from. We return a checklist matched to your briefing type.