Level of Effort (LOE)

Ongoing work that results in no discrete deliverable; progress and completion are gauged by time spent rather than by a specific output.

Key Points

  • Represents supportive or sustaining activities without a distinct end product.
  • Measured by duration or time-phased effort, not by completed units or tangible deliverables.
  • Typically spans alongside related work and should not drive the schedule's critical path.
  • In earned value, EV for LOE generally accrues with planned time (EV aligns with PV), so schedule variance is minimal; cost variance may still occur.

Example

During a six-month project, the project manager provides ongoing administration and weekly status reporting from start to finish. The effort is planned at 10 hours per week, and progress is tracked by the passage of weeks, not by a single discrete deliverable.

PMP Example Question

Which of the following is best classified as Level of Effort (LOE) work?

  1. Configure five network switches and document the configuration.
  2. Complete the design review meeting and issue approved drawings.
  3. Provide project management oversight and weekly status reporting throughout execution.
  4. Develop and deploy a new login feature by the end of Sprint 3.

Correct Answer: C — Provide project management oversight and weekly status reporting throughout execution

Explanation: This is ongoing, time-based support work without a discrete deliverable, which fits LOE. The other options produce identifiable outputs.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More