After looking through the code we found there were 4 steps:
100 - This value is present after the user submits a ticket from the app. The pod is now on the way to the retrieval station
200 - The pod has arrived at the retrieval station and is waiting for the user to "enter" the pod. At this stage, the app on the phone should have changed images. When the user taps the screen on the app, the pod should begin moving toward the final destination.
300 - Pod is on the way to the final destination.
400 - The pod has arrived at the final destination and is waiting for the user to "exit" the pod. The image on the app should change. When the user taps the screen, the pod should be freed and begin roaming around the track on it's own.
This information was in the code. I don't think it was in the documentation. I only found references it to in the Android Code and the saw the status changes on the Server.js code.