Level of Effort Planning & Execution on EV Projects

What level of effort is

This closes the EVM module and the track by addressing a subtle but important measurement choice. Most work is discrete — you can tell when a foundation is poured or a drawing is issued. But some work — running the project office, supervising, providing IT support — just happens continuously. How you measure such work in EVM is the LOE question.

Discrete, apportioned, and level of effort

EVM recognizes three ways to measure a piece of work's earned value, chosen to fit the nature of the work:

• Discrete effort — Work with measurable output — earned value claimed against tangible progress (milestones, % complete, units). The gold standard; use it wherever possible.
• Apportioned effort — Work tied proportionally to discrete work (e.g., QA inspection that scales with production) — it earns value in step with the work it supports.
• Level of effort (LOE) — Work with no measurable output — earns value by time. Use only where genuinely unavoidable (management, support).

Why too much LOE blinds your EVM

Because LOE always reports "on plan," it contributes no real performance signal. A little is fine — genuine support work. But if a large share of the project is measured as LOE, the EVM numbers get diluted: real problems in the discrete work are masked by the always-green LOE, and the overall indices look healthier than the project actually is.

Bringing Project Controls together

With this lesson, the Project Controls & EVM track is complete. You've gone from setting up the control structures, through measuring and forecasting cost, to the full integrated discipline of earned value — and finished with the measurement nuance (LOE) that keeps EVM honest. The thread throughout: measure reality against the plan, objectively, and act early.

Nine things to remember

1. Level of effort (LOE) is work with no discrete output — measured by time.
2. For LOE, EV = PV by definition — so it never shows a schedule variance.
3. Three measurement methods: discrete, apportioned, and level of effort.
4. Discrete is the gold standard — measure work by output wherever possible.
5. Apportioned effort scales with the discrete work it supports (e.g., QA).
6. Reserve LOE for genuine support/management work — don't mislabel measurable work.
7. LOE contributes no performance signal — it's always "on plan."
8. Too much LOE blinds your EVM — it masks real problems; watch the LOE %.
9. Project Controls in one line: measure reality against the plan, objectively, and act early.