we have a process that we follow. We log, by week, how many hours we need a particular resource (for budgeting purposes). The requirements are based on different phases of the project itself. certain phases are heavier labor requirements than others (usually the reporting phase and presentations are the biggest committments). For the most part, everyone is available for 20hrs per week- and during heavy periods, 30hrs a week. Toward the end of the project, they are not required at all, or they taper off to 15, to 10hrs etc.

I happened to look at these requirements shortly after I asked the question. For the most part, say, John, is available 20hrs a week from June 2nd to August 29th. Then from September 2nd to November 28th, 30hrs per week. From December 1st to Feb 27th (completion) he goes back down to 20hrs a week. So, I would only have to set 3 lines of what he is required for (50%, 75%, and 50%). You're saying, that if he is working on something August 29th, and it flows into September 4th, Project won't realize he can work more hours on a particular task, from Sep 2nd-4th ?

I felt the Resource Information>Availability would be perfect if I set up their availability ahead of time. But if Project doesn't recognize the change in assignment units in the event a task is scheduled to carry over from their 50% availability into their 75% availability- then maybe it will be a little difficult once I have all 10 of my resources logged and in place. To keep track of them all, and their availability and where their tasks lie- it becomes a semi-manual process...