Resource Leveling: How to Balance Workloads Across Projects

By Nicole Hullihen, former SaaS Chief Operating Officer and Microsoft MVP · Updated November 1, 2026

A schedule can look perfect on paper and still be impossible, because it assigns the same electrician to two jobs on Tuesday or expects one designer to finish three projects in the same week. When that happens, someone works overtime, quality slips or deadlines are missed. Resource leveling fixes the schedule before the overload happens.

This guide explains how to spot overallocated people and crews and how to rebalance the schedule, with a worked example and a free resource leveling worksheet.

What Is Resource Leveling?

Resource leveling is adjusting task dates and assignments so each resource's workload stays within its available capacity. Resources can be people, crews, equipment or even a single specialized tool. Leveling often moves tasks later, which can extend the project. A related technique, resource smoothing, only moves tasks within their available float so the finish date doesn't change.

Free Resource Leveling Worksheet

Signs You Need Resource Leveling

• The same people work overtime every week.
• Tasks wait because "she's on another job."
• Deadlines slip even though each project's plan looked fine.
• Crews are idle some weeks and overwhelmed others.
• Equipment is double-booked.

These problems usually come from planning each project separately. Leveling looks across all projects at once. See how to manage multiple projects at once.

Step 1: Set Capacity

Start with realistic capacity for each person or crew. A full-time employee might have 40 hours a week, but meetings, travel, admin work and PTO reduce what's available for project work. Many teams plan project work at 70% to 85% of total hours. Subtract approved time off for each week.

Step 2: Map Assigned Work by Week

For each person, add up the estimated hours from every task assigned to them, by week, across all projects. A simple table or chart quickly shows the peaks. See work breakdown structure for task-level estimates.

Step 3: Find Overallocations

Any week where assigned hours exceed capacity is an overallocation. Note how much over and which tasks cause it.

Step 4: Rebalance

Start with float, since moving tasks within their slack doesn't change the finish date. See critical path method.

Worked Example: An Electrical Contractor

An electrical contractor has two crews, A and B, each with 70 hours a week of capacity. Three jobs overlap in weeks 2 and 3.

Crew A is 30 hours over in week 2 and 20 hours over in week 3, while Crew B has 30 hours free in week 2 and Crew A has 40 hours free in week 4. The fixes:

• Reassign a 30-hour panel upgrade from Crew A to Crew B in week 2 (Crew B is qualified).
• Move a 20-hour rough-in on a job with 2 weeks of float from week 3 to week 4 for Crew A.

Both crews now fit their capacity, no deadlines moved and no overtime is needed.

Leveling Equipment and Shared Resources

Resources aren't only people. A single lift, excavator, van or specialized tool can be the bottleneck. Track key equipment the same way: list bookings by day or week and move tasks so two jobs don't need the same equipment at once. See equipment checkout form.

Skills Matter

Reassigning work only helps if the new person has the right skills. Use a skills matrix to see who else can do each type of task, and cross-train so more people can take overflow work. See skills-based scheduling.

Resource Leveling and Overtime

Overallocation often turns into overtime. Under federal law, non-exempt employees must be paid overtime for hours over 40 in a workweek, and some states have daily rules. Leveling reduces unplanned overtime, and when overtime is the right choice, it lets you plan and approve it in advance. See the overtime approval policy.

Using Actual Hours to Improve Leveling

Compare estimated task hours with actual hours from your time records. If tasks regularly take 20% longer than estimated, your leveling will always be too optimistic. Adjust estimates or capacity based on real data. See job cost codes.

How Often to Level

Review workloads weekly for the next two to four weeks, and whenever a new project is added or a big task slips. A short weekly review, looking at a chart of hours by person, catches most problems before they become overtime or missed deadlines.

Common Mistakes

• Planning projects separately without looking at shared people.
• Assuming 40 hours of project capacity per person.
• Forgetting PTO and holidays.
• Reassigning to people without the right skills.
• Moving critical tasks without checking the finish date.
• Never updating the plan as work changes.

Resource Leveling Checklist

A Simple Weekly Workload Chart

You don't need special software to see workloads. Make a grid with people down the side and weeks across the top, and fill in assigned hours. Shade cells green when under 80% of capacity, yellow from 80% to 100% and red above 100%. In a minute, you can see who's overloaded and who has room.

Prioritizing When Everything Is Urgent

Leveling forces a decision about which work comes first. Agree on priorities before the crunch: client deadlines with penalties, revenue-generating work, then internal projects. When two projects compete for the same person, the higher priority project keeps its dates and the other moves. Writing priorities down prevents arguments every time there's a conflict. See how to set team priorities.

Leveling Across Departments

Shared people, like a bookkeeper who supports every project or a single estimator, are often the bottleneck. Include them in the workload chart even if they aren't assigned to project tasks directly, and plan around their busiest periods, such as month-end close or bid deadlines.

Communicating Changes

When leveling moves a task, tell everyone affected: the person doing the work, the project lead and, if a date changes, the client. Explain why the change protects quality and the overall schedule. People accept moved dates more easily when they understand the reason and see the plan.

Using PTO in Leveling

Approved time off reduces capacity, and time off is easy to forget during project planning. Pull upcoming PTO into the workload chart each week, and check project workloads before approving long vacations during busy periods. See how to handle overlapping PTO requests.

Hiring or Subcontracting Decisions

If leveling shows the same people overloaded week after week, the problem isn't the schedule; it's capacity. Use the workload data to decide whether to hire, cross-train or subcontract. A few months of consistent red cells is strong evidence for adding help. See capacity planning.

Resource Leveling for Service Businesses

Leveling isn't only for project-based work. Service businesses can level technician workloads across scheduled jobs, maintenance visits and installs. Look at booked hours by technician by day, move flexible maintenance visits to lighter days and keep room for emergency calls. Balanced technician schedules mean fewer late arrivals and less overtime.

Common Questions From Project Leads

• "What if moving a task breaks a dependency?" Check dependencies before moving; tasks that follow may need to move too.
• "Can I level by day instead of week?" Yes, for short projects or crews that switch jobs daily.
• "Should I level to 100% capacity?" No; leave room for surprises and urgent work.
• "Who decides which project waits?" Use written priorities agreed by leadership.

Resource Leveling Quick Reference

Example: A Marketing Agency

A five-person marketing agency kept missing deadlines even though every project plan looked reasonable. A workload chart showed the designer was booked at 140% of capacity for three weeks while the copywriter was at 60%. The owner moved two non-urgent internal projects later, shifted some layout work to a freelancer and had the copywriter take on simple graphics. Deadlines were met, and the designer stopped working weekends.

Resource Leveling in Spreadsheets

A spreadsheet works for small teams. List tasks in rows with the assigned person, start week, end week and hours per week. Use a summary table with SUMIFS to total hours by person by week, and conditional formatting to color cells over capacity red. When you change a task's dates, the totals update automatically, so you can test different options before committing.

Leveling and Client Expectations

Sometimes leveling shows that a promised date isn't realistic without overtime or extra help. Tell the client early, with options: keep the date with added cost, move the date or reduce scope. Clients usually prefer an honest conversation weeks ahead over a missed deadline. Build leveling into your quoting process so new projects get realistic dates from the start.

Getting Started This Week

1. List everyone who works on projects and their weekly capacity.
2. Add up their assigned hours for the next four weeks.
3. Highlight anything over capacity.
4. Fix the biggest overload using float or reassignment.
5. Repeat next week.

Measuring Results

Track a few numbers before and after you start leveling: overtime hours, missed deadlines, tasks waiting on unavailable people and how often the same employees are over capacity. If overtime and missed deadlines drop, leveling is working. If one person stays overloaded no matter what, plan training or hiring.

Leveling and Employee Wellbeing

Constant overload leads to burnout and turnover, especially among your most skilled people, who tend to get the most work. Leveling protects them by spreading work fairly and making overload visible before it becomes a pattern. Ask employees how their workload feels, too; the numbers don't always show stress from difficult clients or complex tasks.

Common Leveling Scenarios

Most leveling problems fall into one of these patterns, so the fixes become routine after a few weeks.

Keep a short note of each fix you make, so the next time a similar conflict appears, the solution is already documented and quick to apply.

Revisit capacity numbers every quarter too, since meetings, admin work and travel tend to grow quietly over time and reduce real project hours.

Update the chart whenever those numbers change.

Accurate capacity makes every leveling decision better.

Final Thoughts

Resource leveling turns impossible schedules into workable ones. Set realistic capacity, map assigned hours across all projects, find overloads and fix them using float first, then splitting, reassigning or delaying work. Review workloads weekly and use the data to decide when you need more people. Balanced workloads mean fewer missed deadlines, less overtime and less burnout.

Balance Workloads With Updoot

Updoot's project management shows tasks and owners across projects, scheduling shows who's working when and the employee time clock records actual hours, so you can see overloaded people before deadlines slip.

Sources

• U.S. DOL: Overtime Pay

Frequently Asked Questions