I was able to do it once and the fireworks finale went off as we came over the hill. It was amazing.
I’ve never been able to get the timing right. That is so cool!
I don’t visit that often, though the last 20 months suggests otherwise.
But since I won’t buy LL, I HAVE been using TP’s.
Since I’m using TP’s I (a) feel like I should contribute to the data, and (b) like to see the actual compared to projected.
The hardest part for me is hitting the button as I’m climbing onto the ride as I’m also trying to store my phone.
My kids are always interested in the wait times, too, so that helps.
Yes! Usually I’m trying to put my phone away while waiting for the ride vehicle to show up. The couple of times I tried to time waits, I ended up throwing them away because I didn’t stop them until after the ride.
Did a little digging after my earlier comment, and I wonder if anything came out of this 2021 poll? @len might know if it’s on a roadmap somewhere… Even just a mini app only for submitting times would be amazing (and maybe seeing the next step in an existing TP).
I usually forget at the proper start time but remember a minute or 2 later. I wish there was way to adjust your timer to account for that.
Agreed
I already have my phone out checking wait times, so tapping the “start timer” isn’t a big deal to remember. I usually stop the timer when we’re next to get on the ride, so it’s likely an insignificant amount shorter than the actual wait. Hit the stop, then stow the phone.
Ive done this with BTMR and it was magical. But not 7DMT which is like right under them yes?
Ditto
I also make plans and then don’t really look at them at all on the trip. “I am the map”. Lol
There was a point where I thought maybe the TP app could avoid the timing issue by utilizing location services in the app and detect when a user enters a queue automatically. However, this becomes a little tricky because sometimes the start of a queue extends beyond the entrance. For example, often the line for Haunted Mansion extends out into the Liberty Square sidewalk area along the river. There could be some ways around this, though, even then, by monitoring when a person who is NEAR the ride entrance (kind of “in the zone”) of where a ride entrance is, and then start a timer…but then monitor for the user’s phone to actually end up in the ride queue area. Like a “tentatively, starting timer…but waiting to make sure”. Then, once the app is sure the user is actually in the queue, consider the time when they entered to be valid. The bigger issue might be detecting when the rider is about to get on, because location services aren’t entirely accurate, and inside a building, even less so.
BUT, there still could be a way the TP could HELP. That is, if it detects that a user is within a certain distance of a ride entrance for a ride that is in the current touring plan (or maybe a mode in general for detecting if near any ride entrance?) it sends a notification reminder about starting the timer. (Obviously, this would be an “opt in” feature.) In this way, if I could otherwise forget, the app would remind me to start the timer. And then when you start the timer maybe have a way to adjust the start time, like it has a way to select that you got in line 1, 2, or 3 minutes ago. (Any more than that, and it probably is best not to actually record since the time delta might be overly inaccurate.)
As data people ourselves, we try to time our waits as much as possible. In the parks, we like to compare TP wait time with published wait times. As others have said, we don’t use touring plans as much as we used to because we have the fortune of going more now (Thank you Breeze Airway & PSM airport).
Having said that, with the rise of the pre-show, its easy to loose the plot and we forget to submit the time occasionally….
I try to submit the posted time and then time my actual wait for every attraction I go on. I do it for two reasons: I know it helps others in the parks if TP has real data, and I like to see how “off” the posted times are. If I am using a LL, I also like to have the accurate data on how long I waited.
It didn’t seem like enough people would use it, to warrant the build and support costs. We’re working on making the app better & easier to use.
My TPs aren’t loading this morning via the app. I’m off to check the website
I can view it through the website, but of course that doesn’t help me with timing waits. I just wanted to let you know. I’m taking my own data using my stopwatch if you want the info for later ![]()
EDIT TO ADD: it’s working now
Do you time your waits through your plan? I always just do it through the attraction list in the app.
I always do it through my plan in the app! Haha!
I’ve never timed my waits through my plan. I didn’t even know that you could–LOL. I just go to the attraction name by tapping the park on the app. There’s a green “time your wait” prompt to click for each ride.
And good for you for timing those waits!
Thank you! I thought it was just me!

