DCMA-14 Metric 10: Do Construction Schedules Need to Be Resource-Loaded?

No, not every construction schedule needs to be resource-loaded under DCMA. The IMS data item description does not require resource loading, and the resources check applies only if the contractor loads resources. Contracts or GAO-style best practices may still require it, and then every task with a duration over zero should carry dollars or hours.

This is metric 10 in the DCMA-14 schedule assessment. The title of many guides ("unresourced schedules fail") overstates it, and the distinction matters when you write or review a specification.

What does the DCMA resources check say for a construction schedule?

The pamphlet applies the check to tasks with a duration greater than zero. It states that the IMS data item description, DI-MGMT-81650, does not require the contractor to load resources directly into the schedule, and that the metric applies only if the contractor does resource-load (DCMA-EA PAM 200.1). It gives no numeric threshold.

Tools reflect this. Deltek's Acumen documentation, for example, describes how its DCMA metrics operate on activities with a baseline duration over zero (Deltek, Acumen help v8.5). Vendor scoring models differ on how much weight to give resources, so a tool's overall score is not a reliable guide to what the pamphlet requires.

When is resource loading required anyway?

Three sources can require what DCMA does not: the contract, the program's schedule specification, and published best practices adopted by an owner.

GAO's Schedule Assessment Guide, GAO-16-89G, issued in December 2015, lists ten best practices, including assigning resources to activities (GAO-16-89G). Mosaic Projects' summary of the guide notes that it expects schedules to be resourced and risked (Mosaic). Federal programs and owners that borrow from GAO may therefore ask for loading in their own specifications.

In practice, read the contract's schedule section for words like "cost-loaded," "resource-loaded," "schedule of values" and "earned value." Those words, not the DCMA pamphlet, decide what you must deliver. The same contract language belongs in an owner's DCMA-14 specification.

What is the difference between cost loading and resource loading?

The two are often confused, and the DCMA check accepts either, since it looks for dollars or hours.

If you are asked for "a resource-loaded schedule," ask what the reviewer wants to do with it. A cost-loaded schedule that ties to the schedule of values may fully satisfy the requirement. A crew-level loading for every activity may be far more detail than the project can maintain.

How much resource loading is practical on a construction project?

Loading every activity with labor, equipment and material is rare outside programs that mandate it. A practical middle path is:

• Cost-load all work activities so the sum of activity costs matches the contract value or schedule of values, with weighted progress feeding pay applications.
• Load labor and equipment on critical and near-critical work, especially where a crew or crane is the actual constraint.
• Leave milestones, LOE and zero-duration activities unloaded, since DCMA's check applies only to tasks with a duration over zero.
• Document the method in the schedule narrative so a reviewer knows what the loading represents.

This approach gives the owner cash-flow visibility and gives the scheduler resource constraints where they matter. It also keeps the check clean: if the schedule is loaded, no non-zero-duration task should sit with zero dollars and zero hours.

Where does resource loading help beyond the DCMA check?

The metric itself only checks that dollars or hours exist. The value of loading comes from what it enables. A cost-loaded schedule produces a planned-value curve, which supports the schedule-performance reporting that earned value programs depend on. A labor-loaded schedule produces a histogram that shows whether the plan needs 40 carpenters in one month and 8 in the next, a pattern that usually points to a sequencing problem rather than a staffing one.

Loading also exposes durations that do not make sense. If a 10-day activity carries 4,000 labor hours, the duration or the quantity is wrong. Reviewers use this cross-check to test whether durations are realistic, which the logic and float metrics never do.

Worked example: reconciling a cost-loaded schedule

Illustrative example: assume a $12,000,000 contract with a schedule of values broken into 40 line items, and a schedule with 220 incomplete activities that have a duration over zero. The scheduler loads cost by distributing each line item across the activities that perform it.

Neither the 9 unloaded activities nor the $60,000 gap necessarily means the schedule is wrong. They are the list a reviewer will ask about, and the answer should already sit in the narrative. A tidy explanation, such as "mobilization and bond costs are carried on the general conditions activity and not distributed," is usually enough.

Percent complete then follows from how cost is spread. If cost is spread evenly across a long activity, earned value will look smoother than the work actually was. If cost is front-loaded on submittals or procurement, early earned value will look higher than field progress. Agree the loading rules with the owner at baseline, not after the first pay application dispute.

How should an owner specify resource loading?

If you are the owner, name what you want the loading to support, and avoid a one-line "resource-loaded schedule" requirement. A useful specification states:

• whether the schedule must be cost-loaded, labor-loaded, or both, and to what level;
• what the cost total must reconcile to (the schedule of values or contract price);
• how weighting and percent complete are determined for payment;
• whether leveling is required, permitted or prohibited;
• which activities may remain unloaded (milestones and level-of-effort, for example);
• how changes in loading are submitted and approved.

Without these, the DCMA check can be satisfied by a schedule that is loaded in a way that does not help anyone. With them, the metric becomes a quick test of whether the contractor followed the specification.

How do you resource-load in P6 without damaging the schedule?

Resource loading in P6 interacts with activity types, calendars and leveling. Treat it as a controlled change, not a data-entry task.

1. Set the activity type correctly. Task-dependent activities keep their duration regardless of resources. Resource-dependent activities can change duration when resources change, which may move dates unintentionally.
2. Use a resource dictionary with consistent IDs, rates and calendars, instead of ad hoc resource names.
3. Assign to activities, not to summaries, and avoid duplicate assignment across WBS levels.
4. Compare before and after. Save a copy of the dates and float before loading, then confirm critical path and finish date did not change unless you intended them to.
5. Do not level silently. Leveling can change dates; if the contract does not call for it, leave it off or document the approach.
6. Reconcile totals to the contract value or budget.

Loading also changes how you split work. Activities that are too long are hard to load and status accurately, which links this to high duration activities.

What do reviewers flag about resources?

• A schedule that is loaded on most activities, but leaves non-zero-duration tasks with no dollars or hours.
• Loading that does not reconcile to the schedule of values or budget.
• Resource-dependent activities whose durations changed after loading, with no explanation.
• Overallocated resources with no leveling plan.
• A claim of "resource-loaded" that contains only a single lump-sum cost on a summary activity.

Meeting the resources metric is not proof of a good plan. A fully loaded schedule can still carry unrealistic durations or poor logic, as discussed in passing DCMA versus having a good schedule.