![]() |
upgrade waitlists and system migration
I have a pair of CR1s waitlisted for the end of March.
CO metal, from my CO plat account. Come 3/3 should I yank them and have them reapplied? That way they will be listed as 1k RPUs rather than plat which will be higher up the waitlist regardless of time of request, right? Unfortunately the flight in question is CO 117 so right now the website can't give proper upgrade list information despite the fact that it's a CO metal flight. |
Originally Posted by rruaco
(Post 18043899)
Come 3/3 should I yank them and have them reapplied I personally am making copies of everything on 3/2/10212, and not touching a thing for a few weeks down the line. If you want to take a chance to update your higher status, you're taking a chance of losing your CR-1 request date, in case of a tie. Up-2-U, though!!! |
Originally Posted by LilAbner
(Post 18044069)
God only knows what is going to occur on 3/3/2012 and we're all going to have something "YANKED" on that day, I fear.
I personally am making copies of everything on 3/2/10212, and not touching a thing for a few weeks down the line. If you want to take a chance to update your higher status, you're taking a chance of losing your CR-1 request date, in case of a tie. Up-2-U, though!!! |
Losing the date of request isn't an issue, because status trumps request time - and since there are presently no 1Ks on continental any wait listed request made by a 1K on 3/3 should in theory jump to the front of the queue.
This is based on status not updating on records until a FF number is removed and readded - it might be different for upgrades I suppose and the system will magically pull in your new status as soon as it updates. I'm 100% behind you on making backup copies of booking information though! |
Originally Posted by goalie
(Post 18045061)
I am also making sure that any schedule changes (even those of just a few minutes) are accepted/modified before 3/3/12
I'm not going that far. I'm handling it selectively. Right now UA can force UA space, and CO can open CO space. Once they're combined on one system, they can presumably open all space. So in some cases it may be advantageous to wait. In others it may be advantageous to resolve it now. |
Originally Posted by channa
(Post 18045215)
I'm not going that far. I'm handling it selectively. Right now UA can force UA space, and CO can open CO space. Once they're combined on one system, they can presumably open all space.
So in some cases it may be advantageous to wait. In others it may be advantageous to resolve it now. |
| All times are GMT -6. The time now is 8:48 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.