🚧 Under construction — VoTechWorks is being built. A free tech program — complimentary, as our commitment to get America working.
voTechWorksGrade 13 · a vocational technology learning center, by urbanicity
newSchoolWorks.com › VoTechWorks › Business & Cross-Cutting › Construction Management / Estimating › Construction Project Scheduling › Lesson 5
BUS-CONS57-02 · Lesson 5 · 12 clock hours · lab

Resource Loading and Crew Leveling

Objective. Students will assign labor resources to schedule activities, identify resource over-allocations, and apply leveling techniques to produce a feasible resource-loaded schedule.

⚠ Pending professional review

This lesson, its worked examples and its practice questions has not yet been verified by a credentialed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.

VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.

What Is Resource Loading?

A project schedule tells you when work happens. A resource-loaded schedule also tells you who and how many do that work each day. Resource loading is the process of assigning specific labor resources—carpenter crews, concrete crews, MEP subcontractors—to each activity in the schedule, along with the quantity available each day.

Once resources are assigned, scheduling software can calculate how many workers of each type are needed on any given day. It then displays that information as a resource usage histogram: a bar chart with time across the horizontal axis and resource demand on the vertical axis. A horizontal line on the histogram marks each resource's availability limit. Any bar that rises above that line is an over-allocation—you are demanding more workers than you actually have.

Over-allocations are a serious planning problem. Ignoring them means the schedule is not feasible; work will slip, costs will rise, and crews may be asked to work unsafe overtime or be spread too thin to maintain quality.

Reading the Resource Histogram

Before you can fix a problem you must be able to read the histogram correctly.

Note the magnitude of each over-allocation (how far above the line) and duration (how many days it persists). A single day of two extra carpenters is easier to resolve than three weeks of sustained over-allocation.

Resource Leveling: The Goal

Resource leveling is the process of adjusting the schedule so that resource demand never exceeds availability on any day, while still completing the project as close to the original end date as possible. The two main manual techniques are:

1. Delaying an activity (adding lag or shifting the start date): Use an activity's total float to push it later. Float is consumed, but the project finish date does not move—unless you exhaust all float on a path.

2. Splitting an activity: Pause work on an activity, reassign the crew elsewhere, and resume the activity later. Most scheduling software supports activity splitting. Document each split clearly.

When float is exhausted on every parallel path, the only remaining option is to extend the project end date. The goal in this lab is to stay within five days of the original baseline, so plan your moves carefully.

Step-by-Step Leveling Process

1. Identify the worst over-allocation first. Sort by resource type and find the period with the greatest excess.

2. List all activities drawing on that resource during the over-allocated period. Identify which are on the critical path (zero float) and which have float to spend.

3. Shift or split a non-critical activity. Choose the activity with the most float and the smallest impact on downstream logic. Record the original start, new start, float consumed, and reason in your change log.

4. Re-run the histogram. Check whether the over-allocation is resolved. If not, repeat.

5. Move to the next over-allocation. Work through all resource types in turn.

6. Verify the critical path and project end date after all changes. If the finish date moved, document by how many days.

Documenting Changes: The Change Log

Every adjustment must be recorded. The change log is not a formality—it is the audit trail that a project manager or owner uses to understand why the schedule looks the way it does. Each entry should include: activity ID and name, original start/finish, new start/finish, float consumed (in days), resource affected, and a brief rationale.

Incomplete change logs are one of the most common reasons professional schedule reviews fail. In credentialed practice (CMAA and NCCER standards both address this), an undocumented change is treated as an error.

Trade-offs and Group Discussion

After leveling, some activities that were originally on the critical path may now have float (because a parallel path was extended), and some non-critical activities may have become critical after their float was consumed. This is normal. The group discussion step asks you to identify:

Understanding these trade-offs is a core competency for both the NCCER Project Management credential and the CMAA CMIT exam.

Safety Note

Resource loading decisions directly affect site safety. Over-allocated crews are often pressured to work longer hours, skip pre-task planning, or crowd shared work areas. When reviewing your leveled schedule, flag any activity where crew density on a confined structure, scaffold, or elevated slab would exceed safe limits even if the software shows no labor over-allocation. Always coordinate with the site safety plan and ensure PPE requirements and OSHA-mandated crew-to-supervisor ratios are maintained when finalizing resource assignments.

Key terms8

Resource loadingThe process of assigning specific labor, equipment, or material resources to schedule activities along with their quantity and availability limits.
Resource usage histogramA bar chart generated by scheduling software that displays the quantity of a resource demanded across the project timeline, with an availability limit line to reveal over-allocations.
Over-allocationA condition in which the scheduled demand for a resource on a given day or period exceeds the maximum quantity available.
Resource levelingThe process of adjusting activity start dates, adding lag, or splitting activities to eliminate over-allocations while minimizing impact on the project end date.
Total floatThe amount of time an activity can be delayed from its early start without delaying the project completion date; the primary resource of time that leveling consumes.
Activity splittingA leveling technique in which work on an activity is paused, the crew is reassigned elsewhere, and the activity resumes later when the resource becomes available again.
Availability limitThe maximum number of units of a given resource that can be deployed in any one time period, set in the scheduling software from the resource availability table.
Change logA written record documenting every schedule adjustment made during leveling, including original and revised dates, float consumed, resource affected, and the reason for the change.

Worked examples4

1. Activity A (carpenter framing, 4 days) starts on Day 1 and requires 6 carpenters per day. Activity B (carpenter blocking, 3 days) also starts on Day 1 and requires 4 carpenters per day. Carpenter availability is 8 per day. Activity B has 5 days of total float. By how many carpenters are you over-allocated on Days 1–3, and what is the simplest fix?
  1. Step 1 – Calculate daily demand during the overlap: Activity A needs 6 carpenters; Activity B needs 4 carpenters; total = 6 + 4 = 10 carpenters on Days 1–3.
  2. Step 2 – Compare to availability: 10 demanded − 8 available = 2-carpenter over-allocation on each of Days 1–3.
  3. Step 3 – Identify the activity with float: Activity B has 5 days of total float; Activity A has zero float (assume critical).
  4. Step 4 – Delay Activity B by 4 days (its duration), so it starts Day 5. Days 1–4: only Activity A uses 6 carpenters (within the 8-unit limit). Days 5–7: only Activity B uses 4 carpenters (within limit).
  5. Step 5 – Float consumed: Activity B used 4 of its 5 days of float; 1 day of float remains. Project end date does not move.
Answer: Over-allocation was 2 carpenters on Days 1–3. Delaying Activity B by 4 days resolves the over-allocation, consumes 4 days of float, and leaves the project finish date unchanged.
2. A concrete crew of 5 workers is available each day. Three activities run in parallel and each demands 2 concrete workers per day for a 3-day period, creating a peak demand of 6. You cannot extend the project end date. Activity X has 0 float, Activity Y has 2 days of float, Activity Z has 4 days of float. What is the minimum total float you must consume to resolve the over-allocation?
  1. Step 1 – Identify the over-allocation: 3 activities × 2 workers = 6 demanded; 5 available; over-allocation = 1 worker per day for 3 days.
  2. Step 2 – Determine which activities can move: Activity X cannot move (0 float). Activity Y (2 days float) or Activity Z (4 days float) can be delayed.
  3. Step 3 – Choose Activity Z (most float) and delay it by 3 days so it no longer overlaps with X and Y: demand during Days 1–3 drops to 2 (X) + 2 (Y) = 4 ≤ 5. Activity Z runs Days 4–6.
  4. Step 4 – Float consumed: Activity Z used 3 of its 4 days of float; 1 day remains. Activity Y's float is untouched.
Answer: Delaying Activity Z by 3 days consumes exactly 3 days of float and eliminates the over-allocation. The project end date does not move because Activity Z still finishes before its late finish date.
3. After leveling, the project originally scheduled to finish on Day 60 now finishes on Day 63. The pass requirement is within 5 days of the original baseline. Does this schedule pass or fail, and how many days of buffer remain?
  1. Step 1 – Calculate the duration increase: Day 63 − Day 60 = 3 days of extension.
  2. Step 2 – Compare to the allowance: allowance is 5 days; actual extension is 3 days.
  3. Step 3 – Determine pass/fail: 3 ≤ 5, so the schedule passes.
  4. Step 4 – Calculate remaining buffer: 5 − 3 = 2 days of buffer remaining before the schedule would fail.
Answer: The schedule passes. The project extended 3 days, which is within the 5-day allowance, leaving 2 days of buffer.
4. An MEP subcontractor can supply 3 electricians per day. Activity P (rough-in, 5 days, 3 electricians/day) and Activity Q (trim-out, 4 days, 2 electricians/day) overlap for 2 days. What is the peak daily demand during the overlap, and by how many workers does it exceed availability?
  1. Step 1 – Identify the overlap: Activities P and Q share 2 days of concurrent work.
  2. Step 2 – Calculate peak demand: Activity P needs 3 electricians + Activity Q needs 2 electricians = 5 electricians per day during the 2-day overlap.
  3. Step 3 – Subtract availability: 5 demanded − 3 available = 2-electrician over-allocation.
  4. Step 4 – State the result clearly for the change log: peak demand = 5 electricians/day; availability = 3 electricians/day; over-allocation = 2 electricians for 2 days.
Answer: Peak demand is 5 electricians per day during the 2-day overlap, exceeding the 3-electrician availability limit by 2 workers each day.
In class: Students add labor resources (carpenter crew, concrete crew, MEP subcontractors) with defined availability limits to their software schedule and run the resource usage histogram to locate peak over-allocations. · Students apply manual resource leveling by splitting activities or adding lag, then re-run the histogram; they document each change made and the float consumed in a written change log. · Groups compare leveled schedules and discuss trade-offs: which activities shifted to non-critical paths and what overall project duration change resulted; findings recorded in a one-page summary.
Materials: Computers with scheduling software, resource availability table provided by instructor, printed resource histogram output for annotation, change log template
Check: Resource-loaded schedule file and change log: pass requires zero remaining over-allocations on any day, all changes documented, and project completion date within five days of the original baseline. Lab log entry required.

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.

Project Scheduling and Controls
1. A resource usage histogram shows bars above the availability line during a two-week window. What does this indicate?
Project Scheduling and Controls
2. When applying manual resource leveling, which activity should you delay first?
Project Scheduling and Controls
3. A carpenter crew of 8 is available each day. Activity X needs 5 carpenters and Activity Y needs 6 carpenters on the same day. What is the over-allocation?
Project Scheduling and Controls
4. Activity splitting is best described as:
Project Scheduling and Controls
5. After resource leveling, a project originally planned to finish on Day 90 now finishes on Day 96. If the pass criterion is within five days of the baseline, what is the result?
Project Documentation and Controls
6. Which information is MOST important to record in the change log for each leveling adjustment?
Safety and Risk Management
7. From a safety standpoint, why must a project manager review crew density even after the resource histogram shows no over-allocation?
Project Scheduling and Controls
8. During a group comparison of leveled schedules, Team A finds that Activity M, which was originally non-critical, is now on the critical path. What most likely caused this?
Record this lesson on my transcript. Sign in with your key and enrollment email to record lessons (enroll free if you have no key). This page stays open to read and practise.
← Previous lessonProgram planNext lesson →