Level of Effort (LOE)

Level of Effort (LOE) specifies what portion of each team member's time is committed to the program. It is expressed as a percentage of FTE (full-time equivalent), as days per year, or as hours per week. LOE is the budget unit that directly drives program cost.

How Is LOE Expressed?

Three standard formats show up in proposals and staffing plans:

• FTE percentage: "0.5 FTE" means half-time on the program. A 1.0 FTE role is fully dedicated. Percentages ("50% FTE") map to the same thing. Use the unit required by the actual budget template, with assumptions stated.
• Days per year: "60 days/year" suits short-term advisors, external evaluators, and technical experts who are not embedded. Useful for episodic technical inputs.
• Hours per week: "15 hrs/wk" is used for part-time officers, local hires on hourly contracts, and subcontracted data collectors. Use it where the employment and costing basis supports hourly work.

Each format converts to the others (1.0 FTE is roughly 220 working days/year or 40 hrs/wk), but donors prefer one specific format. Match the donor's template.

How Do You Calculate LOE?

Build LOE bottom-up from workload, not top-down from budget ceiling:

1. Estimate staff-time workload: indicator count times data collection frequency times analysis burden, plus reporting cycles and learning events.
2. Translate to days per year per role. A quarterly DQA across 20 sites is not a weekend task. A baseline survey is weeks of preparation, field time, cleaning, and analysis.
3. Convert to FTE (days/220) or weekly hours (days times 8 / 52) depending on donor format.

Typical ranges on a mid-size program: M&E Manager 0.5-1.0 FTE, data officer 0.5-1.0 FTE, analyst 0.25-0.5 FTE, enumerators as surge capacity during collection rounds rather than constant FTE.

What Is the Difference Between LOE, Day Rate, and Total Cost?

LOE is the effort. Day rate is the cost per working day for that role. Total staff cost is LOE times day rate times program duration. All three feed the budget narrative, and donor reviewers check each one separately:

• Is the LOE reasonable for the scope?
• Is the day rate reasonable for the role and geography?
• Does the total cost match the staffing line in the budget?

A proposal can fail on any of the three.

How Does LOE Affect a Proposal?

LOE is where staffing credibility gets tested in a proposal. A plan proposing quarterly DQAs, baseline/endline surveys, visits across 30 sites and learning events needs a timed workload estimate. Whether 0.5 FTE is sufficient depends on scope, partner contributions, geography, automation and other resourced roles. Reviewers check LOE against scope: either the scope shrinks or the staffing grows. Common LOE red flags in proposals: (a) management LOE not matched to actual supervision and review work; (b) enumerators budgeted as if they work one day each instead of the multi-week deployments data collection actually requires; (c) external evaluator listed without an LOE estimate. Be specific: name each role, name the percentage, and show that the total team's LOE matches the scope of the MEL plan. Check the actual performance management plan, budget template and agreement for required staffing detail. No default FTE threshold or funder name establishes adequate capacity.

Common Mistakes

LOE that understates M&E workload. Writing a 25-indicator MEL plan and then staffing it at 0.3 FTE because the budget felt tight. Either the indicator set shrinks or the LOE grows. Keeping both is a proposal that cannot execute.

LOE numbers that do not reconcile to the budget narrative. The staffing plan says 0.75 FTE for the M&E Manager, the budget table multiplies 50% against a day rate, and the narrative references full-time. Reviewers catch this fast and read it as sloppy costing.