<p><b>Problem</b><br>Many GoGoX bookings are cancelled because no driver ever accepts them, so GoGoX earns nothing on them.</p><p><b>What it answers</b><br>At the moment a booking is made, how likely is it that no driver will ever accept it? XGBoost scores each booking from 14 inputs known at booking time and flags the riskiest 20% (cut-off fixed on May). Problem A: in which weekday-hour periods are bookings lost, and what is closing that gap worth? Problem B: does any driver action (R1 S$1 completion credit, R2 van push, R3 book-ahead prompt) pay for itself, and what should GoGoX do with the risk score (van offer, surcharge, step-up pay, bundling)? Model 2 (step 9b) predicts which free driver nearby will take a job.</p><p><b>How to use</b><br>Reset, then Execute all. Read steps 1 to 10 from left to right; step 9b (the driver model) sits below them.</p><p><b>Where the results go</b><br>Nothing is written to disk. Step 10 shows the results in six interactive views: 10A answers in words, 10B when bookings are lost, 10C the check of model 1, 10D what to do with the risk score (van offer, Friday-evening and night surcharge, step-up pay), 10E bundling and 10F the check of model 2, the driver model (May decides, June checks). Open a view to read it or to save its picture.</p><p><b>Data</b><br>GoGoX's booking export (one row per booking attempt, January to June 2026) and URA's Master Plan 2014 subzone boundaries. January to April trains the model, May chooses the inputs, the cut-off and the actions, June tests them once.</p>