I think I might be a little confused by what you're trying to say. To put some concrete numbers, in your example it would be, say, letting apps be submitted for the last week of the month, but none are processed until maybe the first three days of the month (so 7 days for apps to be submitted, 3 days for us to process) and the 4th day is the scheduled intro day.
What we're proposing kind of hits a few things that have been mentioned. Basically, there would be, lets say, 4 days to submit applications. We'll review them within that time frame, but we won't actually send out notices until the 5th day (we already review those that come in during the final day as they come in and then spend the following further reviewing if needed). So in that sense, our app review schedule isn't really changed. And then, the intro log is set up and everyone goes in at once. Since we link the intro logs in the acceptance notices, the log always goes up a few hours before we process. So it could be expected that the intro log would always go up on the 5th or 6th of every month assuming the app cycle is on a 4-day schedule.
Also, another reason why we're considering shortening the app period is because there may not really need to be a long period for applications. If anything, most of our applications actually come in on the first day, and I don't think this will change no matter how long the applications are. So we'll still have ample time to go through most apps. It's no different than how we already do the "first batch" apps, really—we're essentially just cutting the "batches" in half.
THIS IS ASSUMING I understood what you were trying to say to begin with. A set IC intro day isn't a bad idea, but that is essentially what we'd be doing regardless and what the shortening app period is helping with.
Oh, the other reason why we stick with applications happening at the beginning of the month is because AC runs at the end of the month. If someone idles out or drops, someone else can pick up the character fairly quickly if they wanted do. This wouldn't be possible in your current proposed system with applications occurring during the last week of the month.
no subject
I think I might be a little confused by what you're trying to say. To put some concrete numbers, in your example it would be, say, letting apps be submitted for the last week of the month, but none are processed until maybe the first three days of the month (so 7 days for apps to be submitted, 3 days for us to process) and the 4th day is the scheduled intro day.
What we're proposing kind of hits a few things that have been mentioned. Basically, there would be, lets say, 4 days to submit applications. We'll review them within that time frame, but we won't actually send out notices until the 5th day (we already review those that come in during the final day as they come in and then spend the following further reviewing if needed). So in that sense, our app review schedule isn't really changed. And then, the intro log is set up and everyone goes in at once. Since we link the intro logs in the acceptance notices, the log always goes up a few hours before we process. So it could be expected that the intro log would always go up on the 5th or 6th of every month assuming the app cycle is on a 4-day schedule.
Also, another reason why we're considering shortening the app period is because there may not really need to be a long period for applications. If anything, most of our applications actually come in on the first day, and I don't think this will change no matter how long the applications are. So we'll still have ample time to go through most apps. It's no different than how we already do the "first batch" apps, really—we're essentially just cutting the "batches" in half.
THIS IS ASSUMING I understood what you were trying to say to begin with. A set IC intro day isn't a bad idea, but that is essentially what we'd be doing regardless and what the shortening app period is helping with.
Oh, the other reason why we stick with applications happening at the beginning of the month is because AC runs at the end of the month. If someone idles out or drops, someone else can pick up the character fairly quickly if they wanted do. This wouldn't be possible in your current proposed system with applications occurring during the last week of the month.