Keep resource use realistic#

A schedule can be logically valid and still be impossible to build. If the plan needs 40 pipefitters in December and none in January, the logic is happy, but no one can hire and lay off a crew like that. Owl PM keeps the schedule achievable two ways: charts that show how hard each resource is worked over time, and guardrails that flag overbooked crews and wild swings on every change.

You'll need resources loaded and assigned first.

Step 1: See the hours over time#

Open Dashboards → Resources in the project tree. Every project has it.

1231A sharp peak: planned hours jump to about 1,600 in one week in December, then fall away. That's a plan you can't staff.2The dashed lines: the baseline's planned hours and the hours your resources have available.3Hours by resource: one row per resource, darker where it's busier, so you can see who the peak lands on.

• Hours by week stacks each week's planned hours by resource. The dashed lines are the baseline's hours and the hours your resources have available.
• Hours by resource shows the same hours as a heatmap, one row per resource.

A flat, gently ramping profile is staffable. A sharp spike, like the one here in December, is the sign of a plan that looks fine on the Gantt but would mean hiring a crew and letting it go a few weeks later. Use the By Resource menu on a chart to break the hours down another way.

See Charts and analytics for building your own.

Step 2: Let guardrails catch it on every change#

Spotting a peak by eye on one chart is fine; catching it across every resource, on every change, is what a guardrail is for. Two default guardrails do this on every project, with no setup:

• Crews are booked beyond what they can do: no labor resource is booked over full time (8h/d, one unit per hour) at any moment, however many of its activities overlap.
• Crew sizes swing month to month: each labor resource ramps smoothly over one continuous stretch. No idle month (5% of its peak or less) between busy ones, and no change from one month to the next of more than half its peak month.

1231What the rule protects, in words: crews that can be staffed.2The rule applies to each resource. Its definitions name the parts: the hours per month, the peak, the active months, the idle ones and the swings.3The failing resources, each with its idle months and its largest swing: "largest swing 1,126h (needs at most 583h, half of peak)."

Each failing resource says what broke the rule. Here the Lead Mechanical Engineer has 4 idle months in a 13-month stretch, and a month-to-month swing of 1,126 hours against a limit of 583 (half its peak month).

Both guardrails are warnings, and both check labor resources only (equipment, cost and quantity resources aren't checked). They mark the Gantt too: hatching on a bar shows the stretch of work where a resource is overbooked or swings, and the resource carries a warning badge in the project tree and the Resources sheet.

Note: On a project with no resources assigned, both guardrails have nothing to check and pass. They start working the moment you load resources.

See How guardrails work for guardrails on resources and other tables.

Step 3: Smooth the schedule#

When a check fails, resolve it like any guardrail: open it and click Propose fix, or work it out with Owl. The fix is usually to spread the peak work out, re-sequence overlapping activities, or change how much of a resource each activity draws, until the profile ramps instead of spikes.

Smoothing can push the finish date out. That's the real trade-off surfacing, and it's better to see it now than to find out mid-project that the plan was never staffable. See Fix issues with your schedule for the full fix-and-check loop.

What to do next#

• Confirm the whole plan is sound: Find issues with your schedule shows every guardrail's status, resource checks included.
• Report the staffing picture: put resource hours on a custom dashboard next to cost and progress.