That resource allocations are feasible it does necessarily means you got a good plan. Even when you can hire infinite resources you must watch idle time if you cannot accommodate all resources to some productive work, the ideal target. Therefore you shall plan the resource availability as to reduce idle time, might be to reduce all or perhaps not all as to leave some buffer. These are decisions you as a manager and planner shall consider in order to make better schedules.
The following figures represent the same job, both are feasible schedules.
- In the first one the availability of resource A is such that will yield 160 hours of idle resources. Of course they will hide, they will slow productivity, they will protect their job. If the resource A hourly rate, including labor burden is 50$/hour it means $8,000.00 will be spent on idle time.
- In the second one the availability of resource A is reduced but it is till possible without delaying total job duration. Such plan projects $0.00 spent on idle time.
Which one is a better plan, maybe option 2 if you do not have other jobs to assign resource A, and this you shall decide.


You shall also understand the limits of your software, some are incapable of responding to variable quantity and variable workloads that an experience Project Manager will assign even if the paper plan is incapable of doing it. They will move idle resources to other activities, increasing the number of workers on the activity for a limited time. They will move the paper schedule to the port-o-let for a better use of useless/idle paper. This will reduce idle time, will make for a more efficient use of resources, might reduce some activities durations and even might reduce total project duration. In jobs with hundreds of activities this is better done by a computer.
Learn to use the resource leveling tool to make better plans, not just feasible plans.