The Mistake: Too Many Indicators in Your Proposal

Why packing your proposal logframe with 30+ indicators can cost points with reviewers and make the M&E budget hard to fund.

What Goes Wrong

You open the RFP template. It has 25 indicator rows. You fill them all. Or the program team hands you a design document with 40 output-level metrics and asks you to "put them in the logframe." Or you inherit a proposal from a prior submission with 35 indicators and a tight deadline, so you leave them in.

The result is a logframe where every activity has two or three indicators, every outcome has four, and the impact row has three overlapping measures of the same thing. The MEL plan that follows claims to collect data on all of them. The M&E budget cannot actually fund that. The team knows this; they have seen prior projects where half the indicators were never reported. They submit anyway.

Illustrative Indicator Count by Program Size

Program sizeIllustrative rangeWarning zone
Small ($250K-1M, 1-2 years)6-12 indicators15+
Mid-size ($1M-5M, 2-3 years)8-18 indicators22+
Large ($5M-15M, 3-5 years)12-22 indicators28+
Very large ($15M+, 5+ years)15-25 indicators30+

These ranges are illustrations, not reviewer rules, and the size bands are for this page only; other pages use different bands for their own examples. The warning zone column is not a hard cutoff; it marks counts that deserve a second look at feasibility. Staying inside the illustrative range does not make your logframe good by itself; it may remove one easy reason to score you down.

Why It Happens

Four drivers produce this mistake. First, template pressure: if the donor gave you 25 rows, it feels risky to leave some blank. Second, stakeholder hedging: each team member contributes "their" indicator, and nobody wants to delete a colleague's contribution. Third, false completeness: teams mistake a long indicator list for a thorough M&E plan, when the two are almost opposites. Fourth, inherited proposals: teams lift logframes from prior submissions without cutting, adding the new program's indicators on top of the old ones.

The underlying issue is that an indicator list feels like coverage. More indicators seem to mean more accountability. In practice, a longer list means less of each indicator gets measured well, more data goes uncollected, and the system loses credibility when partial results get reported as complete. A 15-indicator logframe that every M&E officer reports against cleanly is worth more to a donor than a 30-indicator logframe with quarterly gaps.

Frequently Asked Questions

How many indicators should a proposal have?

There is no universal number or automatic penalty threshold. Keep enough measures to cover the results and decisions, including applicable obligations, and cost each data source. A short list can miss essential changes; a longer list can be appropriate when justified and funded.

Why might reviewers flag logframes with too many indicators?

Some reviewers read the indicator count as a signal of M&E maturity. Thirty indicators in a $500K budget can suggest the team has not prioritized, which may mean they will struggle to collect data consistently, that the budget is under-sized for what they promise, and that the team may not understand which indicators actually matter for decisions. The fix is not fewer words per indicator. It is fewer indicators.

How do I cut indicators without hurting the logic?

Start by asking what decision each indicator informs. Indicators that do not feed a specific decision (a program adaptation, a donor report, a resource reallocation) are candidates to cut. Then ask which indicators overlap: if indicator 7 and indicator 12 both measure similar behavior change, keep the one with the stronger data source. Finally, move low-priority indicators to a work plan monitoring list rather than your logframe. Work plan tracking does not need a logframe entry.