You talking apples and oranges here - what you describe is not a leveling
issue at all. Example - Before leveling Betty is assigned to Task A that is
expected to take 10 hours, starting Monday at 8am. That means the task will
finish Tuesday at 10am, right? She is also assigned to Task B, scheduled to
start Tuesday that is expected to also take 10 hours, by coincindence. Using
the normal calendars Task B would start Tuesday at 8. But Betty is already
committed until 10. There's 2 hours overlap. Leveling on a day-by-day
basis means that the smallest overlap it will pay attention to is a full
day. A 2 hour overlap is too small for it to see so it ignores it.
LEveling on an hour-by-hour basis says the smallest overlap it will see is
one hour. Now the overlap is visible. Now leveling can do something and
what it does is delay Task B until the earliest start time that it can have
without overlaping the previous task, ie 10am. But that's not because
leveling is looking at it on an hourly basis. That's because tasks will
start as soon as possible. If that happens to somewhere into the work day
that's where it will put it. It's exactly the same behavior if 10 hour Task
A were linked to Task B as predecessor/successor. Task B would be scheduled
to start at 10am on Tuesday, regardless of whether resources were assigned
to them or not. What you are asking is for Project only to schedule tasks to
start at the start of the workday and it can't do that. Absent constraints,
Project will always schedule tasks to start at the earliest possible moment
that links and resource availability permits.
Go to the tools menu, options, the view page, and turn on display of times
in your date format. I'll bet you'll discover that you may THINK all your
tasks are integer values of days in duration but either there's at least one
that is a fraction of a day so that subsequent tasks are not starting at the
exact start of the work day or that your project start date does not
correspond to the start of he workday so all start times are offset into the
workday. Remember a 1 day task starting at noon on Monday finishes at noon
on Tuesday, not the end of the day Monday. That's the only way you could
have had an overallocation of less than a full day - if the resource is
assigned to a task that is not an exact multiple of a full workday in length
or does not start or end exactly on the workday start and end
